Thanks for that Thomas.
I couldn?t find the Ant target you gave me in the binary JBoss distribution so
figured it was in the source.
I download the source, built it from JBOSS_HOME/build then ran the Ant target
you gave me in JBOSS_HOME/testsuite
I found I had to add the following line into the testsuite build.xml file to
get it to complete:
<pathelement path="${project.tools}/lib/ant-junit.jar"/>
?just after this one on line 206:
<pathelement path="${project.tools}/lib/ant.jar"/>
I then ran your ant target on this build file in testsuite - it didn?t pass the
JUnit test for some reason but I was able to find the necessary JBoss
message style web service xml files and service classes.
I war?d everthing and deployed it.
It deploys OK but still gives the following errors that I was getting with my
message based service:
14:32:53,710 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type:
{http://org.jboss.test.webservice/message}Response
| 14:32:53,710 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type:
{http://org.jboss.test.webservice/message}Order
| 14:32:53,710 WARN [TypeMappingDescription] Class not found:
org.jboss.test.webservice.message.Order
| 14:32:53,710 WARN [TypeMappingDescription] Class not found:
org.jboss.test.webservice.message.Response
It works OK though. However when you undeploy it from the jmx-console using
the MBean for the service under the jboss.web.deployment section,
then deploy it again - although it (the service) deploys and undeploys it no
longer works when invoked by a client.
It throws the following exception:
java.lang.IllegalArgumentException: object is not an instance of declaring class
Is this something to do with the fact this service is not *properly* being
deployed to Axis by JBoss as a message service although it will work like one?
(I feel it's not being properly deployed because of what i can see in the
dynamically created WSDD file and WARN messages at the JBoss console
upon deployment)
Or is this to do with the casting of Elements to SOAPElements?
One other thing, the example client SOAP message given on the Message Endpoint
tutorial Wiki (http://wiki.jboss.org/wiki/Wiki.jsp?page=WSMessageEndpoints)
seems to be wrong.
It looks like this:
<env:Envelope>
| <env:Body>
| <ns1:Order xmlns:ns1='http://ws.sample'>
| <Customer>Kermit</Customer>
| <Item>Ferrari</Item>
| </ns1:Order>
| </env:Body>
| </env:Envelope>
?but I find that for the service to work the element immediately under the Body
must have the same name as the exposed method. In this case processElement.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882254#3882254
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882254
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
