August 2008 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Problem consuming .net webservice with jbossws-3.0.1-nat

by felipepontes

Claudio, I'm facing the same problem. I need consume web services behind a proxy server. Did you resolved it? Felipe. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171857#4171857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171857

17 years, 1 month

1
0
0 / 0

[JBossWS] - Consuming rpc/encoded WS

by medalhas

Hi, I have deployed application, that has some WS developed on JAX-WS. This WS are consumed by other applications so cannot change them. Now i have this third party WS that i have to consume, but they are developed with NuSOAP(php) and are rpc/encoded. As JAX-WS doesn't support rpc/encoded i cannot use the wsconsume, what is best way to consume this webservices? Environment: Java 5 JBoss 4.2.2 jbossws-3.0.1-native-2.0.4.GA Seam 2.0.2SP1 Regards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171848#4171848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171848

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Trying to use jboss.xml instead of @WebContext

by karypid

Hello, I am using the very latest: JBossAS 4.2.3.GA and JBossWS-Native 3.0.3.GA. When my EJB is coded as follows: @Stateless | @WebService( | serviceName="MyBasicWS", portName = "MyBasicWSSOAP", | targetNamespace = "http://www.example.org/MyBasicWS/", | endpointInterface = "org.example.mybasicws.MyBasicWS") | @WebContext(authMethod="BASIC") | @RolesAllowed("friend") | public class MyBasicWSImpl { | public String echo(String in) { | System.out.println("RECEIVED: " + in); | return in; | } | } I use the following jboss.xml to set the security domain: <!DOCTYPE jboss PUBLIC | "-//JBoss//DTD JBOSS 4.2//EN" | "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd"> | <jboss> | <security-domain>java:/jaas/JBossWS</security-domain> | <webservices> | <context-root>myBasicWS</context-root> | </webservices> | </jboss> Everything works like a charm with the combination above (I must access the EJB as kermit/thefrog from the default jbossws-xxxx.properties files). However, I want to get rid of the @WebContext annotation. My idea (which does not work) is the following combination: @Stateless | @WebService( | serviceName="MyBasicWS", portName = "MyBasicWSSOAP", | targetNamespace = "http://www.example.org/MyBasicWS/", | endpointInterface = "org.example.mybasicws.MyBasicWS") | //@WebContext(authMethod="BASIC") | //Undesirable | //The above should be picked up from jboss.xml | @RolesAllowed("friend") | public class MyBasicWSImpl { | public String echo(String in) { | System.out.println("RECEIVED: " + in); | return in; | } | } Then, I try to express that the EJB must use BASIC authentication method as follows: <!DOCTYPE jboss PUBLIC | "-//JBoss//DTD JBOSS 4.2//EN" | "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd"> | <jboss> | <security-domain>java:/jaas/JBossWS</security-domain> | <webservices> | <context-root>myBasicWS</context-root> | </webservices> | <enterprise-beans> | <session> | <ejb-name>MyBasicWSImpl</ejb-name> | <port-component> | <port-component-name>MyBasicWSSOAP</port-component-name> | <auth-method>BASIC</auth-method> | </port-component> | </session> | </enterprise-beans> | </jboss> In this case however, the client throws an authorization failure exception: javax.xml.ws.soap.SOAPFaultException: Authorization failure | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:77) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107) | at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:577) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | at $Proxy19.echo(Unknown Source) | at test.TestBasicWS.basicAuthTest(TestBasicWS.java:41) On the server side, I see this: 15:41:47,349 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[friend], principalRoles=[] | 15:41:47,349 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.ejb.EJBAccessException: Authorization failure | at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120 Apparently, JBoss disregards the BASIC-auth and does NOT assign a principal to the session. Therefore the role-based authenticator denies access to the method (as it should). Apparently, my jboss.xml does not tell JBoss to associate basic-auth with the published web service. I was suspicious of what I should put in the "port-component-name" value. Supposedly, the documentation says: Maps to the port-component-name in the webservices.xml descriptor. However, I do not use a webservices.xml file but use the @WebService annotation instead. In the code above I use the value for the "portName" attribute of @WebService but I also tried the ejb-name (MyBasicWSImpl) and the serviceName (MyBasicWS) with no luck. Any clues as to how I can achieve this while keeping the code JBoss-clear? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171766#4171766 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171766

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Multiple WSDL bindings warning

by alessio.soldano＠jboss.com

That's a warning message saying that the wsdl you're consuming has multiple bindings for the same interface. The last binding is actually used in those cases. If you have problems with the generated log, also consider you can just limit the logs of org.jboss.ws.metadata.wsdl.WSDLDefinitions class, without affecting your business code or any other JBoss class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171748#4171748 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171748

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Deploying JDeveloper/Oracle webservices on JBossWS

by alessio.soldano＠jboss.com

Check you classpath and verify which version of wsdl4j you're currently using. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171745#4171745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171745

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: wsconsume and rpc/encoded soap message

by alessio.soldano＠jboss.com

Please search in the forum for this topic. In few words jbossws native has really basic rpc/enc functionalities, we should actually say that rpc/enc is not supported any more. That's because the WS-I Basic Profile disallowed it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171744#4171744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171744

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Trying to use jboss.xml instead of @WebContext

by alessio.soldano＠jboss.com

Which version of JBoss Application Server are you using? If it's 4.2.2.GA please try moving to 4.2.3.GA as this might be due to an already fixed bug. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171739#4171739 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171739

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: WS URL different for 4.2.2 and 4.2.3

by alessio.soldano＠jboss.com

That's most probably because of this: https://jira.jboss.org/jira/browse/JBWS-1813 IOW there was a bug which was fixed in AS 4.2.3.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171726#4171726 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171726

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: jbossws with apache

by alessio.soldano＠jboss.com

"r.eloc" wrote : "palin" wrote : | | I would check what url apache is actually trying to connect to; I mean, it's ok that you get a "http GET not supported" if you access an endpoint using your browser. As a matter of fact, endpoints support POST, GET is supposed to work only for wsdl retrieval calls. | | | | Why is GET not supported? All the other web service frameworks I have used (Apache Axis, .NET) have supported that, it's quite useful when developing and testing. I'd say because when you invoke a service, you provide the soap request message, thus you need POST. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171718#4171718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171718

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Create the simplest WebService possible

by alessio.soldano＠jboss.com

Hi Sergio, I don't want to start a flame, just need to understand how to move to further improve the jbossws docs (which, btw, improved a lot since 1 year ago). "smmartins" wrote : | - changed several JBoss libs from place | Do you mean what is explained here? http://jbws.dyndns.org/mediawiki/index.php?title=Installation (section "Using JBossWS Native with JDK 6) anonymous wrote : | - Found two really useful web pages: | - http://www.theregister.co.uk/2007/01/23/ejb_web_services/ | The fast introduction to the WS world is covered in the pages belonging to this wiki category http://jbws.dyndns.org/mediawiki/index.php?title=Category:WS_Culture. The development strategies using the tools as well as the client generation and run steps are described here http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools. Do you think something is missing? (maybe a page for real beginners-who-don't-want-to-read-lots-of-pages with a super-slim walkthrough?) Or you did not find those pages, so they should be better advertised / more easily reachable from the doc home page? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171715#4171715 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171715

17 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users August 2008