To further clear my previous post, here's my complete description:
I've got 3 java files
1 - My WS interface
2 - My WS Implementacion
3 - My Handler class (in this case a class for handling attachments)
With the WS Plugin, I've generated my WS artifacts (WSDL file, web.xml, webservices.xml and jaxrpc-mapping.xml).
Problem is that webservices.xml didn't include any link to the handler, so I had to manually insert them (see above post).
Then it was just a case of packagin my files into a .WAR file (ant - f packaging-build.xml) and deploy it to my JBoss AS.
Hope this helps anyone with this sort of problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981699#3981699
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981699
Hello,
had same problem with arrays..
was able to fix it by specifying WebResult and WebParam in my webservice methods..
As far as i read, the less you annotate your webservice method, the more jbossws will try to 'figure out' what the parameters/result would be..
No problem with primitive/wrappres return, but if you start to have 'arrays' or custom classes, then i guess jbossws would need a little help in order to generate WSDL etc..
You'd need to annotate your webservice method with
@WebResult
@WebParam
check jbossws samples, (or google it) i have found a similar example that uses WebParam and WebREsult and that fixed my problem
HTH
marco
try to speci
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981696#3981696
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981696
I've solved this problem by:
1º Generating the artifacts first (JbossIDE WS Pluggin (2.0 Beta2))
2º Manually editing webservices.xml to include the following lines:
....
| </service-impl-bean>
| <handler>
| <handler-name>ServiceAttachmentHandler</handler-name>
| <handler-class>provisioning.ServiceAttachmentHandler</handler-class>
| </handler>
| </port-component>
| .....
Handler is now properly interpreted as shown in the jboss log.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981693#3981693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981693