Hi Chris,
I finally found the problem.
It was caused by the configuration of the https connector from tomcat.
I used this configuration
| Connector port=9100 address=${jboss.bind.address}
|maxThreads=100 strategy=ms maxHttpHeaderSize=8192
|
A servlet filter has been implemented to rewrite incorrect ports in the WSDL
file that JBoss WS publishes. This is availble for both 2.6 and 2.4 in
Subversion...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4020938#4020938
Reply to the post :
When I checked the other day, I didn't have the problem with the missing port
in the WSDL file. I'll check again.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016500#4016500
Reply to the post :
hi,
setting the hostname and port directly in the file
portal-wsrp.sar/portal-wsrp.jse/WEB-INF/wsdl/wsrp_services.xml
has the same effect than the solution with the security-constraints (as Julien
told me first).
Means that my wsdl looks like this
wsdl:definitions
Which version of JBoss WS are you using? The solution provided in the Wiki will
only work with JBoss WS 1.0.4.GA...
As far as having to modify the internal file manually, I totally agree with
you. However, I haven't been able to find how to have JBoss WS to pick up the
port automatically
Hi Chris,
I use
jbossws-1.0.4.GA (date=200611151648)
(as the log file stated).
Do you not have the problem with the missing port in the wsdl:import?
Actually will it hurt? I can access JBoss Portlet by means of WSRP (over SSL,
simplest case just encrypted communication, without client
thanks Chris for the update, this wiki needs to be added to the documentation
too.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013758#4013758
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4013758
It's on my todo list... ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013826#4013826
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4013826
___
jboss-user mailing list
I have been reading the JBoss WS documentation and as far as I can tell, you
only need to replace all the soap-address elements in
portal-wsrp.sar/portal-wsrp.jse/WEB-INF/wsdl/wsrp_services.xml by the correct
URL (including port). For example:
wsdl:port binding=bind:WSRP_v1_Markup_Binding_SOAP
Hi Julien,
thanks for your reply.
I added the security constraints to the web.xml file
located in jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse. There is no
portal-wsrp.war directory. It seems to work except for the wsdl:import.
After adding the security-constraints the shown wsdl looks
Hi Julien,
I just would like to inform you, that I have til now official support
and opened a call in network.jboss.com
ID is 00014082
Regards Karin
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012387#4012387
Reply to the post :
I am not the specialist here but I can try to help you. Chris which is our WSRP
lead is currently away for a few days.
You could try to secure the endpoints in web.xml located in :
jboss-portal.sar/portal-wsrp.sar/portal-wsrp.war/WEB-INF/web.xml
try with the ServiceDescriptionService endpoint
12 matches
Mail list logo
