Hi everyone,
I'm new in this forum and my problem is the following:
I can't configure my jboss to dynamic modify the wsdl of my web-services.
My configuration is:
Apache whith AJP connector
jboss 4.2.3
jboss Messaging
jbossws-native-3.0.5 (I tought that the problem was fixed in this version)
I'm tring to modify
server/messaging/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
and set xxxxxx.xx
where xxxxxx.xx is my apache virtual-host, but nothing to do.
I start my jboss with "-b <server name>".
When I ask for wsdl sometime I receve:
<soap:address location="http://xxxxxx.xx"/> OK
than I try to stop and restart jboss and I receve:
<soap:address location="http://<server name>"/> WRONG
Why ? :(
Can some one help me ?
Thanks
Nicola.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205789#4205789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205789
Hello all:
i use the following
JDK 5
JBoss 4.2.3 GA
JBossWS jbossws-native-3.0.5.GA
NetBean 6.5
I managed to created a JAX-WS web service successfully and deployed to JBoss. I'm able to view the wsdl file no problem either.
However, in NetBean 6.5, when I tried to create web service client by pointing to the wsdl location, I get the following error
You are loading JAX-WS 2.0 API from jar:file:./jboss-4.2.3.GA/client/jboss-jaxws.jar!/javax/xml/ws/Service.class but this tool requires JAX-WS 2.1 API.
I'm wondering what am I doing wrong? If I switch the server to GlassFish1, then I don't get the issue at all.
Any insight is greatly appreciate it.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205703#4205703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205703
Hi again!
The web service context is injected OK.
wsCtx is not null it's just the user principal object that I try to retrieve from the wsCtx that is null. But maybe this is a result of JBWS-2074?
I've not tried it yet but I guess that
org.jboss.security.SecurityAssociation.getPrincipal().getName()
would work.
Is there a JIRA for the memory leak/pojo endpoints never being released problem as well?
Or will that problem be handled by JBWS-2486?
Have you been able to reproduce the problem, it sound like a significant problem. I've tried removing @pre @post annotated methods but that does not help.
/Mikael
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205449#4205449
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205449