[JBossWS] - how to return an empty http response instead of soapmessage
by kukeltje
Hi,
I'm implementing an ebMS 2.0 Message Service Handler with JBossWS 2.0.0 and related frameworks. According to the ebMS 2.0 spec, In all cases a soapmessage is received and in many cases a soapmessage has to be returned. Therefor I choose the 'message' way of communicating. However in some cases an empty response (no soapmessage, just an http 200 ok) has to be returned. First thing I tried was returning 'null' hoping that would do the trick. Unfortunately it didn't.
I can do several things now
- do not use the 'message' way but start using the source
- try something with a soaphandler by e.g. setting the messagecontext to null
- return a basic soapmessage and write a servletfilter that deletes this if it encounters it
The first option would result in to much coding (imo), the second might not work and the last one doesn't feel 'right'
Does anybody have a different suggestion?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081601#4081601
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081601
19 years
[JBossWS] - Problem migrating Weblogic web services to JBoss
by vshorreo
Hi
We are migrating to JBoss an existent web services module, originally developed to Weblogic. We have the beans that implement the business logic and the wsdl file that was generated for Weblogic using a Servicegen task. The existent beans have been adapted to an EJB-based JBoss web service, that is, with an endpoint class and generating the wsdl and xml files with wstools within an Ant task. The wsdl generated by the JBoss tools is quite different to the one that was generated by the Weblogic Servicegen tool.
On the other hand, there is a previosuly developed client that worked fine with the webservices in Weblogic, but doesn't work now with the new web services in Jboss. We have developed a new client using wsdl2java included in the Eclipse Webtools plugin based on Axis runtime and it communicates with the server, although there are problems regarding null values (Axis SOAP requests are not comlpetely understood by the server regarding these values).
Our biggest problem is that the existent client should not be changed, and we are not able to get it working with the new web services in JBoss (probably because the wsdls are quite different)
Is there anyway to migrate the web services to JBoss without changing the current wsdl?
Any ideas to solve this issue?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081380#4081380
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081380
19 years
[JBossWS] - Re: Error: Could not transmit message
by palin
Hi Paoletto,
"paoletto" wrote :
| | Caused by: java.net.UnknownHostException: fornost
| | at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
| | at java.net.Socket.connect(Socket.java:507)
| | at java.net.Socket.connect(Socket.java:457)
| | at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
| | at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
| | at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
| | at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
| | at sun.net.www.http.HttpClient.New(HttpClient.java:287)
| | at sun.net.www.http.HttpClient.New(HttpClient.java:299)
| |
it seems you're trying to access an unknown host "fornost"... I would suggest to check whether you can reach it from the host your jboss is running on. Also consider upgrading from 1.0.3 (if you're using this) to 2.0 and using jaxws, you might have a lot of benefits.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081050#4081050
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081050
19 years