Re: [jboss-user] [JBoss Web Services] - How do I rewrite soap:address to always HTTPS
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] replied to the discussion
"How do I rewrite soap:address to always HTTPS"
To view the discussion, visit: http://community.jboss.org/message/550570#550570
--------------------------------------------------------------
> Ulrich Romahn wrote:
>
>
> So, we have multiple options to configure the generation of the service URL:
> 1. we configure it statically by setting "webServiceHost" to our public server name, or
> 2. we configure it using dynamic rewrite based on the request URL
>
> If we use option #1, JBoss will always generate a service URL with "http" no matter what else we do
Generally speaking, something you can do is provide the wsdl you want to be exposed in your deployment. First you deploy without it, then you save the generated wsdl, modify it as you wish, add it and reference it (@WebService(wsdlLocation = "WEB-INF/...")) in your deployment and finally re-deploy.
Something else you might want to try is setting your soap:address to something like " https://REPLACE-ME https://REPLACE-ME", that should force the https protocol to be use in the soap:address when rewriting it. I think this probably has the side effect of overwriting the webServicePort you might want to specify though.
If nothing of this helps, please create a feature request jira. We might think about adding another configuration option (webServiceProtocol) and achieve what you want throught that.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/550570#550570]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months
Re: [jboss-user] [JBoss Messaging] - Unexpected failover behaviour in distributed transaction
by Chris Meadows
Chris Meadows [http://community.jboss.org/people/chrismeadows] replied to the discussion
"Unexpected failover behaviour in distributed transaction"
To view the discussion, visit: http://community.jboss.org/message/550558#550558
--------------------------------------------------------------
> Lakshmi Narayana Gajula wrote:
>
> Hi Chris,
>
> I got the similar error you got.
>
> ERROR [org.jgroups.blocks.ConnectionTable] (ViewHandler,MessagingPostOffice-DATA,10.3.94.132:7900) failed sending data to 10.3.94.122:7900: java.net.SocketException: Socket closed
>
>
> But the environment is WebSphere though. Can you please tell me how you resolved this error?
>
> Thank you very much
>
> Lakshmi Narayana. Gajula
Hi Lakshmi,
Few points:
* I think you'd be better off posting your question to a WebSphere forum.
* I didn't resolve the problem. I didn't get a response from JBoss either. I think they're heavily focussed on HornetQ, so aren't so keen to respond to JBoss messaging issues. Happy to be proved wrong though ;)
* I rewrote what I had to work with JB5 and HornetQ and hit a pile of HASingleton Barrier problems so that my code wouldn't deploy in a cluster. At that point I gave up
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/550558#550558]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months
[JBoss Web Services] - ClassCastException in JAXWS-Handler
by Bernd Franke
Bernd Franke [http://community.jboss.org/people/franbekh] created the discussion
"ClassCastException in JAXWS-Handler"
To view the discussion, visit: http://community.jboss.org/message/550513#550513
--------------------------------------------------------------
Hello,
I'm using JBoss 5.1.0 and JBossWS-Metro 3.2.2. In our application we have deployed Web Services in
the EJB container and the web container. Within the SOAPHandler I put a Java class in the SOAPMessageContext in
order to read it in my business logic implementation. We are using the same jaxws handlers for the web services
deployed in the ejb container and the web container. Everything works fine in the ejb container. Within the handler
deployed in the web container I get a strange ClassCastException:
07:34:33,541 SEVERE [EndpointMethodHandler] aaa.aa.types.User cannot be aaa.aa.types.User
It seems that the handler has another class loader as the implementation at the web container! Within the debugger
the two classes have different IDs.
Does anybody know what went wrong? If it is a class loader problem how can I configure the JBoss Web Class Loader?
Thanks for your help in advance,
Bernd
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/550513#550513]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months