Alex, and still it is strange!
my wsdl :
| ?
|
|
|
|
|
|
|
|
|
as you can see description , id, and name are all NOT optional, but only
description throws an arror, name is pretty quiet. it still seems to me
unlogical.
View the original post :
http://www.jb
Alex, one more question
my problem I can't change parameter's attribute to "optional".
May be you know how to do it?
I use jsr 181 in my WS and a few annotations, that do not allow be make
parameter optional.
does wstools allows this?
Thanks.
With not optional parameter I should somehow fi
Thanks, Alex.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998655#3998655
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998655
___
jboss-user mailing list
jboss-user@lists.
anonymous wrote : How can I produce "fictive" copy?
|
| That means, if I really want to copy only into 2-d parameter, how
| can I "simulate" copy into 1-st parameter and really leave it untouched?
Well, the real problem is, according to your schema, the description element
must be present:
I have forgoten to put exception that I have if I try to copy only to second
parameter:
javax.xml.rpc.JAXRPCException: org.jboss.ws.binding.BindingException:
javax.xml.bind.JAXBException: Failed to parse source: Requested element
{http://entities.customer.xtp.sap.com/jaws}
| id is not allowed
Alex,Thanks a lot for help!!
So it is known feature, Wow!
Then additional question
How can I produce "fictive" copy?
That means, if I really want to copy only into 2-d parameter, how
can I "simulate" copy into 1-st parameter and really leave it untouched?
Is there preferable and simple or any
Peter,
BPEL 1.1 is basically unaware of the XML Schema. If it were aware, every assign
would incur in heavy overhead. Even BPEL 2.0 merely provides a way to validate
that the resulting XML nodes match the schema. However, this is nowhere close
to the effect that you expect.
Please be aware tha
