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=bb&op=viewtopic&p=3862059#3862059
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode
Working with JBoss 4.0.0 I can confirm that you can do rpc/encoded, rpc/literal
and document/literal with JBossWS.
Windows .NET however, does not support rpc/literal. So, you will encounter
problem interoperating JBossWS rpc/literal web service with .NET clients.
Hope this helps.
- Mohammad
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
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 doc
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?
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 canno
