|
»
Non unique body parts! ??
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Non unique body parts! ??
by Felipe Gaucho
::
Rate this Message:
I am defining a WSDL that import messages of another WSDL (reuse of
messages).., but the wsimport throws an warning: Non unique body parts! is there a way to reuse messages without this warning ? can I ignore the warning ? It seems the ID of the message is its contents and not it name.. is it correct ? * the wsdl compiles fine but some operations are failing.. I didn't have time to check if the reason i my messages reuse.... For example: <wsdl:portType name="CejugClassifiedsAdmin"> <wsdl:operation name="CreateCategoryOperation"> <wsdl:input name="NewCategory" message="common-wsdl:Category" /> <wsdl:output ... /> </wsdl:operation> <wsdl:operation name="UpdateCategoryOperation"> <wsdl:input name="CategoryToMerge" message="common-wsdl:Category" /> <wsdl:output ... /> </wsdl:operation> ........ [WARNING] Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signaure on the wire for successful dispatch. In port CejugClassifiedsAdmin, Operations "UpdateAdvertisementTypeOperation" and "CreateAdvertisementTypeOperation" have the same request body block {http://cejug-classifieds.dev.java.net/metadata/common}AdvertisementType. Method dispatching may fail, runtime will try to dispatch using SOAPAction my ANT task: <wsimport debug="true" verbose="${verbose}" keep="true" extension="true" destdir="${generated.dir}" package="${service.wsdl.generated.package}" wsdl="${service.admin.wsdl}" wsdllocation="${service.admin.wsdllocation}"> <produces dir="${generated.dir}" includes="${service.wsdl.generated.package}/**/*.java" /> </wsimport> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Non unique body parts! ??
by Glen Mazza
::
Rate this Message:
Read Note #1 here: http://www.jroller.com/gmazza/date/20071019#notes
HTH, Glen
|
|
|
Re: Non unique body parts! ??
by Felipe Gaucho
::
Rate this Message:
humm.. what means I am forced to create a lot of messages with the
same content, just to sign the underneath technology to keep them uniques :( ..... ok..... we are always trying some abstraction in WSDL, but sometimes it just prove verbose.. +1 to support of WSDL 2.0 in this case ;) On Tue, Jul 1, 2008 at 4:50 PM, Glen Mazza <glen.mazza@...> wrote: > > Read Note #1 here: http://www.jroller.com/gmazza/date/20071019#notes > > HTH, > Glen > > > Felipe Gaucho wrote: >> >> I am defining a WSDL that import messages of another WSDL (reuse of >> messages).., but the wsimport throws an warning: Non unique body >> parts! >> >> is there a way to reuse messages without this warning ? can I ignore >> the warning ? >> >> It seems the ID of the message is its contents and not it name.. is it >> correct ? >> >> * the wsdl compiles fine but some operations are failing.. I didn't >> have time to check if the reason i my messages reuse.... >> >> For example: >> >> <wsdl:portType name="CejugClassifiedsAdmin"> >> <wsdl:operation name="CreateCategoryOperation"> >> <wsdl:input name="NewCategory" message="common-wsdl:Category" /> >> <wsdl:output ... /> >> </wsdl:operation> >> >> <wsdl:operation name="UpdateCategoryOperation"> >> <wsdl:input name="CategoryToMerge" message="common-wsdl:Category" /> >> <wsdl:output ... /> >> </wsdl:operation> >> ........ >> >> >> [WARNING] Non unique body parts! In a port, as per BP 1.1 R2710 >> operations must have unique operation signaure on the wire for >> successful dispatch. In port CejugClassifiedsAdmin, Operations >> "UpdateAdvertisementTypeOperation" and >> "CreateAdvertisementTypeOperation" have the same request body block >> {http://cejug-classifieds.dev.java.net/metadata/common}AdvertisementType. >> Method dispatching may fail, runtime will try to dispatch using >> SOAPAction >> >> my ANT task: >> >> <wsimport debug="true" verbose="${verbose}" keep="true" >> extension="true" destdir="${generated.dir}" >> package="${service.wsdl.generated.package}" >> wsdl="${service.admin.wsdl}" >> wsdllocation="${service.admin.wsdllocation}"> >> <produces dir="${generated.dir}" >> includes="${service.wsdl.generated.package}/**/*.java" /> >> </wsimport> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Non-unique-body-parts%21----tp18210827p18217683.html > Sent from the Metro - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Non unique body parts! ??
by Felipe Gaucho
::
Rate this Message:
<wsdl:message name="AdvertisementType">
<wsdl:part element="common:AdvertisementType" name="advertisement.type" /> </wsdl:message> <wsdl:message name="AdvertisementTypeUpdate" > <wsdl:part element="common:AdvertisementType" name="advertisement.type" /> </wsdl:message> <wsdl:message name="AdvertisementTypeCreate" > <wsdl:part element="common:AdvertisementType" name="advertisement.type" /> </wsdl:message> :( --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Non unique body parts! ??
by Clive Brettingham-Moore-3
::
Rate this Message:
your definition still has the same problem, namely that the request
messages (ie on the wire) for different operations are still indistinguishable. I assume you are using doc-lit - in this case to make the messages distinguishable you will have to use different elements at the XML schema level since this is what goes into the messages. Using rpc-lit you different operations are distinguishable even if they use the same wsdl message since the operation name is incorporated into the SOAP message. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Non unique body parts! ??
by Felipe Gaucho
::
Rate this Message:
rpc-lit ?
* yes, my previous post was wrong,,, and I was forced to create 4x types for each entity CRUD.. :( On Wed, Jul 2, 2008 at 11:57 AM, Clive Brettingham-Moore <java.net@...> wrote: > your definition still has the same problem, namely that the request messages > (ie on the wire) for different operations are still indistinguishable. > I assume you are using doc-lit - in this case to make the messages > distinguishable you will have to use different elements at the XML schema > level since this is what goes into the messages. > Using rpc-lit you different operations are distinguishable even if they use > the same wsdl message since the operation name is incorporated into the > SOAP message. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
