[JBossWS] - buggy tutorials
by gryffin
For the life of me, I can't make a single JBoss WS tutorial work. I've tried the normal JBoss tutorial ( chap12 ) and it seems to omit describing elements of the development enviroment crucial to working the tutorial. Trying to move to JBossWS 1.2.1 meant that documention on using servlet based WS was dropped. Downgrading to JBossWS 1.0.4 has left me with the most inexplicable errors when trying to build the first example "java.lang.NoClassDefFoundError: org/jboss/ws/tools/WSTools". Your idea of what this means is probably no better than mine.
I've been pounding my head against this stuff all day and night.
I've tried using the JBoss 4.0 Official Guide, but it too went off the rails in trying to build the first example. The examples downloaded did not match those in the book.
It's too bad that implementing JBoss is so much like compiling a custom kernel. The difference seems to be that there's more accurate documentation regarding kernel compilation.
Rant over.
What is the recommended path for someone new to Java WS to learn by example how to build servlet RPC style WS with JBoss?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041713#4041713
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041713
17 years
[JBossWS] - Two services with same portname
by jaap.taal
When I deploy two services with the same method name inside one war file something strange happens:
| @WebService
| @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
| public class EchoListString {
|
| @WebMethod
| public List<String> echo(List<String> myList) {
| return myList;
| }
|
| }
|
and
| @WebService
| @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
| public class EchoListBean {
|
| @WebMethod
| public List<BasicBean> echo(List<BasicBean> myList) {
| return myList;
| }
|
| }
|
The echo input xsd (as well as the output) which is generated inside the wsdl is:
<xs:complexType name="echo">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="arg0" type="tns:basicBean" />
</xs:sequence>
</xs:complexType>
the tns:basicBean is used instead of xs:string!
When I change the name of either EchoListString.echo EchoListBean.echo, everything is normal.
I think it's a bug, but i'm not sure!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041670#4041670
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041670
17 years
[JBossWS] - Using (Hash)Map in wrapper class
by jaap.taal
I'm using jboss-4.2.0.CR2 with jbossws-1.2.1.GA
I'm trying to deploy the following simple echo webservice.
| @WebService()
| @SOAPBinding(style = SOAPBinding.Style.RPC)
| public class EchoMapSSTest {
|
| @WebMethod
| public Map<String, String> echoMapSS(Map<String, String> myMap) {
| return myMap;
| }
| }
|
JBoss gives the following error message:
... 28 more
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.util.Map is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at java.util.Map
The JAXB2.0 documentation clearly states that java.util.Map MUST be supported, so I think I'm doing something wrong?
Please help
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041665#4041665
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041665
17 years
[JBossWS] - Re: JbossWS 1.2.1 and .Net 2.0 client
by centecbertl
JBossWS is standard conforming, and per se this is not a JBossWS problem. But it means that updating to new JBossWS versions breaks a lot of client code or requires to put XMLElement on all generated DataStructures for
nillable non-complex Data fields. Thus it is a JBossWS users problem.
Detail:
(i.e. autoboxing Long, Integer, Double types, Date types, BigDecimal,.....
I was lucky, since I generate all these by using androMDA, thus it was easy to add XmlElement to several hundred data structures in the correct places.
It could help other JBossWS users to document the behaviour, and make it configurable (e.g. property nillablesAreRequired).
The situation is even worse on .net side: when a .net client reads a complex data structure it does not set the ...Required fields on its own. Thus something like
| tradeService.updateTradePriceQuote(quotationService.getQuote(isin))
|
with a complex data structure Quote, carrying quotation detail as BigDecimals does not work any longer (what it used to do with JBossWS1.0.x and JSR 181 annotations)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041469#4041469
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041469
17 years