[JBoss-user] [JBossWS] - Re: wrapped document/literal
rpc/encoded works, but should not be used for reasons given by the BasicProfile-1.0 Both literal styles are supported View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3862059#3862059 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3862059 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: wrapped document/literal
Hi again, omatzura wrotes that rpc/literal style web-services should work fine with JBoss. From jasong I understand, that only document/literal works with JBoss so far. I'd like to use rpc/literal but got some problems when I tried it. If it should work in general, I'll give it another try and will post any problems here. So my question is: Does JBoss-4.0.1 support rpc/literal style web-services? Thanks, Dietmar View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861743#3861743 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861743 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: wrapped document/literal
Hi there, What's that? I cannot implement webservices with more than one parameter? This cannot be true! At the moment we're using JBoss-3.2.3-RC1 very heavily in production with plenty of SLSBs exposed as SOAP services for our perl and php clients. In order to migrate to JBoss-4.0.1, we cannot change all of these webservices to use a complex wrapping type. There must be a way to use several (complex) parameters in JBossWS. Any hints? Thanks and greetings, Dietmar View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861574#3861574 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861574 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: wrapped document/literal
Hi! as far as I understand, doc/literal web-services can only have one in/out complex message part (in accordance with basic profile). If you need multiple in-parts you should use rpc/literal style web-services instead (which should work fine with jboss in accordance with j2ee 1.4). correct? regards! /Ole View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861578#3861578 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861578 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossWS] - Re: wrapped document/literal
anonymous wrote : | What's that? I cannot implement webservices with more than one parameter? This cannot be true! | The strong point about doc/literal is, that the message receiver can validate the payload of the message against a given schema. Business entities that exchange complex documents have this requirement. You should first assess whether you want a RPC kind of communication or whether you want to exchange documents. RPC style may feel more natural to technical people whereas DOC style may feel more more natural to people that model business processes are not concerned about the implementation details, like method signatures. In fact, as jason points out, whether your endpoint receives the message in a wrapping complex type or unwrapped as individual parameters is an implementation detail which the client of the web service does not see. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861689#3861689 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861689 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
