We observer a similary problem. The MetaData in the generated WSDD file are
mostly ignored by the Serializer.
The follwoing web service:
|
|
| http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";
|
xmlns:tns="http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";
| xmlns="http://schemas.xmlsoap.org/wsdl/";
| xmlns:xsd="http://www.w3.org/2001/XMLSchema";
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
|
|
| http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";
|
xmlns:tns="http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";
|
xmlns:rts="http://asg-platform.org/scenarios/attractionbooking/routes";
|
xmlns:cts="http://asg-platform.org/scenarios/attractionbooking/contacts";
| xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/";
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
| xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
|
| http://asg-platform.org/scenarios/attractionbooking/routes";
|
schemaLocation="http://tb0.asg-platform.org/~saar/schemas/routes.xsd"; />
|
| http://asg-platform.org/scenarios/attractionbooking/contacts";
|
schemaLocation="http://tb0.asg-platform.org/~saar/schemas/contacts.xsd"; />
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| http://schemas.xmlsoap.org/soap/http";
style="document"/>
|
|
|
|
|
|
|
|
|
|
|
Got this SOAPRequest:
|
| http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
|
| uuid:b80dc2d0-1ee3-11da-baf4-8b01201e0182
| http://localhost:8080/asg-services-mobtelphonelocationservice-1/PhoneLocationEndpointPort
|
|
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
|
| http://www.asg-platform.org/namespaces";
soapenv:mustUnderstand="0">5
| http://www.asg-platform.org/namespaces";
soapenv:mustUnderstand="0">1538
|
|
| http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";>
| http://asg-platform.org/scenarios/attractionbooking/contacts";>
| http://asg-platform.org/scenarios/attractionbooking/attractions";>+49
| http://asg-platform.org/scenarios/attractionbooking/attractions";>0331
| http://asg-platform.org/scenarios/attractionbooking/attractions";>12345
|
|
|
|
|
We receive the following SOAPResponse
| http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
|
| http://www.asg-platform.org/scenarios/attractionbooking/services/MobtelPhoneLocationService";>
|
| Potsdamer Platz
| 10785
|
| 12.0
| 21.0
|
|
| Berlin
|
|
| Potsdamer Platz
|
|
|
|
|
|
All prefixes and namespaces of the enclosed Response data are omited and we
like to have them for later processing.
Also debugging shows, that the Serialization favours JavaBean MetaData, which
do not provide the full QName. Is this a bug ? and is there some configuration
option to enforce all namespaces in SOAPResponse?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893219#3893219
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893219
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
