From do-not-reply at jboss.com Fri Jun 1 02:56:49 2007 From: do-not-reply at jboss.com (DivyaMan0j) Date: Fri, 1 Jun 2007 02:56:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Attachment size limit added using SOAP Message-ID: <10537468.1180681009606.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, Could someone please respond to my query ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050395#4050395 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050395 From do-not-reply at jboss.com Fri Jun 1 03:28:08 2007 From: do-not-reply at jboss.com (Gopi.PM) Date: Fri, 1 Jun 2007 03:28:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Access web service from html/javaScript Message-ID: <17403812.1180682888612.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Can anyone help me with examples on AJAX/JavaScript+JBOSS+Web Service. I am Very new to this topic.A Simple example would really help me. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050399#4050399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050399 From do-not-reply at jboss.com Fri Jun 1 07:18:53 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Fri, 1 Jun 2007 07:18:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - a question Message-ID: <22675967.1180696733680.JavaMail.jboss@colo-br-02.atl.jboss.com> i am updating my aplication from ejb 2.1 to ejb3 anf jboss 4.2. I stop using axis in my server aplication and now i am using jbossws with annotations. The webservices works fine, but i need to change the name of the objects generated in the client aplication in order to avoid changing the client code. For instance: the login web service from the server code: ............ @WebService(endpointInterface="com.satdatatelecom.satdataweb.model.session.session.SesionEndPointInterface", targetNamespace = "http://localhost/jboss-net/services/Sesion", serviceName = "LoginService") @Remote(SesionSession.class) @RemoteBinding(jndiBinding = "/ejb3/EJB3SesionEndPointInterface") @Stateless public class SesionSessionBean implements SesionSession { @PersistenceContext(unitName = GlobalNames.PERSISTENCE_UNIT) private EntityManager entityManager; @WebMethod @WebResult public LoginVO loginUsuario(String idEmpresa, String loginName, String password, String session) throws EmpresaNotFoundException, UsuarioNotFoundException, PasswordException, SessionException, ConcesionException, ConcesionEmpresaException, RemoteException, com.satdatatelecom.satdataweb.model.session.exceptions.SessionException { try{ LoginUsuarioAction action = new LoginUsuarioAction(idEmpresa, loginName, password, session, entityManager); LogMessages.info("login", "El usuario "+loginName+" realiza login", true); return action.execute(); }catch (EmpresaNotFoundException e){ throw e; }catch (UsuarioNotFoundException e){ throw e; } } } jboss publish the service , but when the client uses axis to create the objects needed as LoginVo, which is returned by the login service, i would wish to change the type forn loginvo to LoginVOWS, because in the past all the client aplication worked with it in its code. In the Ejb 2.1 sercer aplication i used in LoginVO: /** * @jboss-net.xml-schema * urn = "satdataweb:LoginVOWS" */ to change the name type now, i tried to use @WebMethod(name="loginVOWs) but it only changes the name in the wsdl document : .................................. ........................... if i wanted the type to be loginVOWs i need to change the wsdl document by myself. ................... .................................. ........................... What can i do? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050459#4050459 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050459 From do-not-reply at jboss.com Fri Jun 1 12:51:03 2007 From: do-not-reply at jboss.com (griff7023) Date: Fri, 1 Jun 2007 12:51:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - SOAP header not being set as request param Message-ID: <14907307.1180716663263.JavaMail.jboss@colo-br-02.atl.jboss.com> I am having trouble migrating a WS from JAX-WS RI 2.0/JBoss 4.0.5.GA to JBossWS/JBoss 4.2.0.GA. The WS starts ok and I can connect a client but the request and response headers are always null. For example, I have an operation SubmitBasket which is defined as follows: | @WebMethod(operationName = "SubmitBasket") | @WebResult(name = "receipt", targetNamespace = "http://www.m-bar-go.com", partName = "response") | public Receipt submitBasket( | @WebParam(name = "header", targetNamespace = "http://www.m-bar-go.com", header = true) | Header inboundHeader, | @WebParam(name = "header", targetNamespace = "http://www.m-bar-go.com", header = true, mode = WebParam.Mode.OUT) | Holder
outboundHeader, | @WebParam(name = "basket", targetNamespace = "http://www.m-bar-go.com", partName = "request") | Basket request) throws BadBasketFault, BadRequestFault; | But when I try to access either the inboundHeader or outboundHeader params they are both null. Looking in the log I can see the following: | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] [user-agent=Java/1.5.0_06] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] [host=127.0.0.1:8080] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] [connection=keep-alive] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] [content-length=540] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=utf-8] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage |
01156986742242df80c7a68036a39aaf
test05000005501sale050101030501020205010301 | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.utils.DOMUtils] createElement {http://schemas.xmlsoap.org/soap/envelope/}S:Envelope | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://schemas.xmlsoap.org/soap/envelope/}Envelope | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://schemas.xmlsoap.org/soap/envelope/}Envelope | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] addNamespaceDeclaration: xmlns:S='http://schemas.xmlsoap.org/soap/envelope/' | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.utils.DOMUtils] createElement {http://schemas.xmlsoap.org/soap/envelope/}S:Header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://schemas.xmlsoap.org/soap/envelope/}Header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] addChildElement: {http://schemas.xmlsoap.org/soap/envelope/}Envelope -> {http://schemas.xmlsoap.org/soap/envelope/}Header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.utils.DOMUtils] createElement {http://schemas.xmlsoap.org/soap/envelope/}S:Body | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://schemas.xmlsoap.org/soap/envelope/}Body | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] addChildElement: {http://schemas.xmlsoap.org/soap/envelope/}Envelope -> {http://schemas.xmlsoap.org/soap/envelope/}Body | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.utils.DOMUtils] createElement {http://www.m-bar-go.com}header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://www.m-bar-go.com}header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] addChildElement: {http://schemas.xmlsoap.org/soap/envelope/}Header -> {http://www.m-bar-go.com}header | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPContentElement] setAttribute: [nsURI=http://www.w3.org/2000/xmlns/,name=xmlns,value=http://www.m-bar-go.com] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] removeContents | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.utils.DOMUtils] createElement {http://www.m-bar-go.com}basket | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] new SOAPElementImpl: {http://www.m-bar-go.com}basket | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPBodyImpl] addChildElement: {http://www.m-bar-go.com}basket | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPElementImpl] addChildElement: {http://schemas.xmlsoap.org/soap/envelope/}Body -> {http://www.m-bar-go.com}basket | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPBodyImpl] appendChild: basket | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.soap.SOAPContentElement] setAttribute: [nsURI=http://www.w3.org/2000/xmlns/,name=xmlns,value=http://www.m-bar-go.com] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.MessageTrace] Incoming Request Message | | |
| 01156986742242df80c7a68036a39aaf |
| | | | test | 05000005 | 501 | sale | | | 05010103 | | | 05010202 | | | 05010301 | | | | | | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.CommonMessageContext] put: APPLICATION:javax.xml.ws.binding.attachments.inbound={} | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: POST | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://www.m-bar-go.com}MbargoPayPointImplService,port={http://www.m-bar-go.com}MbargoPayPointSoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.addressing.context.inbound): null | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.soap.SOAPMessageDispatcher] getDispatchDestination: {http://www.m-bar-go.com}SubmitBasket | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindRequestMessage: {http://www.m-bar-go.com}SubmitBasket | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://www.m-bar-go.com}header,value=org.jboss.ws.core.soap.SOAPHeaderElementImpl] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://www.m-bar-go.com}header,value=null] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://www.m-bar-go.com}basket,value=org.jboss.ws.core.soap.SOAPBodyElementDoc] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: ENDPOINT | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=ENDPOINT,info=[service={http://www.m-bar-go.com}MbargoPayPointImplService,port={http://www.m-bar-go.com}MbargoPayPointSoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] | 2007-06-01 16:43:40,864 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: PRE | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=PRE,info=[service={http://www.m-bar-go.com}MbargoPayPointImplService,port={http://www.m-bar-go.com}MbargoPayPointSoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]] | 2007-06-01 16:43:40,864 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] | 2007-06-01 16:43:40,880 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false | 2007-06-01 16:43:40,880 TRACE [org.jboss.ws.core.CommonMessageContext] put: APPLICATION:org.jboss.ws.allow.expand.dom=true | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.server.ServiceEndpointInvokerJSE] invokeServiceEndpoint: submitBasket | 2007-06-01 16:43:40,880 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.servlet.request): APPLICATION:javax.xml.ws.servlet.request=org.apache.catalina.connector.RequestFacade at 14f1c67 | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestPayload | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://www.m-bar-go.com}header | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: null -> null | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] syncEndpointInputParam: null -> null(0) | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://www.m-bar-go.com}basket | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://www.m-bar-go.com}>basket,javaType=class com.thelightagency.mbargo.ws.lightweight.paypoint.Basket] | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize: [xmlName={http://www.m-bar-go.com}basket,xmlType={http://www.m-bar-go.com}>basket] | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialized: com.thelightagency.mbargo.ws.lightweight.paypoint.Basket | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.soap.XMLContent] objectValue: com.thelightagency.mbargo.ws.lightweight.paypoint.Basket | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: org.jboss.ws.core.soap.SOAPBodyElementDoc -> com.thelightagency.mbargo.ws.lightweight.paypoint.Basket | 2007-06-01 16:43:40,880 DEBUG [org.jboss.ws.core.EndpointInvocation] syncEndpointInputParam: com.thelightagency.mbargo.ws.lightweight.paypoint.Basket -> com.thelightagency.mbargo.ws.lightweight.paypoint.Basket(2) | As you can see the message on the wire has a header but for some reason it is reported as null during the unbind. Any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050554#4050554 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050554 From do-not-reply at jboss.com Sat Jun 2 11:40:08 2007 From: do-not-reply at jboss.com (FabBoco) Date: Sat, 2 Jun 2007 11:40:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Newbie Question: WebService & Object Parameter Message-ID: <25248489.1180798808539.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I have a very simple web service | | public interface MyWebService | { | public String sayHello(String to); | public Long add(MyClass e1); | } | | @Stateless | @WebService(name="MyService", serviceName="MyService") | @Remote(MyWebService.class) | @RemoteBinding | @SOAPBinding(style=SOAPBinding.Style.RPC) | public class MyWebServiceBean implements MyWebService | { | @WebMethod | public String sayHello(String to) | { | return "Hello "+to; | } | | @WebMethod | public Long add(MyClass e1) | { | return e1.getL1()+e1.getL2(); | } | } | | this is myClass | public class MyClass implements Serializable | { | private Long l1; | private Long l2; | | public Long getL1() | { | return l1; | } | | public void setL1(Long l1) | { | this.l1 = l1; | } | | | public Long getL2() | { | return l2; | } | | | public void setL2(Long l2) | { | this.l2 = l2; | } | | } | | I deploy it and I issue the following command to generate the auxiliary classes | | wsconsume.sh -k http://fabocoxp:8080/MyWebServiceBeanService/MyWebServiceBean?wsdl -s src -p test.webServices.aux | | I call the webService with this code (using the auxiliary classes) | MyService_Service myss = new MyService_Service(); | MyService myService = myss.getMyServicePort(); | | System.out.println(myService.sayHello("Bob")); | | The problem is that | myService.add(...); | accept a parameter of class testSeamWebApp2.webServices.aux.MyClass that is the auxiliary class. myClass is a class belonging to a library shared between client end server. To call the web service, I have to use the auxiliary class, not my library class coping values from one to the other. It's very boring. Moreover, if MyClass contains other classes, the coping operation as to be performed for inner classes to. This is almost impossible ! Is there any way to use the original myClass as parameter type ? Thank you very much Fab. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050679#4050679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050679 From do-not-reply at jboss.com Mon Jun 4 03:15:40 2007 From: do-not-reply at jboss.com (king_country2000) Date: Mon, 4 Jun 2007 03:15:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem using .NET Compact Framework Client Message-ID: <27154124.1180941340254.JavaMail.jboss@colo-br-02.atl.jboss.com> We had the same issue in that the .NET compact framework does not handle unqualified too well. Setting up a package-info.java with | @javax.xml.bind.annotation.XmlSchema(namespace = "http://a.c.f.i.com", elementFormDefault=javax.xml.bind.annotation.XmlNsForm.QUALIFIED) | package a.c.f.i; | in the directory containing all the objects being transferred to the client solved it for us. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050809#4050809 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050809 From do-not-reply at jboss.com Mon Jun 4 06:21:37 2007 From: do-not-reply at jboss.com (kapilesh.arekar) Date: Mon, 4 Jun 2007 06:21:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - javax.xml.rpc.JAXRPCException: Cannot obtain operation meta Message-ID: <19760963.1180952497031.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Folks I am trying to resolve a problem a few days and I am stuck here. I am relatively new to webservices and trying to figure out what is the problem. I am using JBoss 4.0.5 GA which has bundled JBossWS 1.4. When I run a webservice client I get an error. Note: I have used "+++" to seperate peices of Source Code Will appreciate if some one could point me to the problem. I am assuming that there is a problem is with some mapping file ,because I am able to invoke the sayHello method via the second method . Also I read same kind of problem faced by another person,but had no reply posted http://lists.jboss.org/pipermail/jbossws-users/2007-January/001196.html Note - I picked up the server code from example stated in the URL below http://www.soapui.org/jbossws/topdown_example.html Thanks a ton in advance +++++++++++++++++++++++++++++++++++ ERROR +++++++++++++++++++++++++++++++++++ Contacting webservice at http://localhost:8080/HelloWorld output:Hello How are you, Kapilesh! Exception in thread "main" javax.xml.rpc.JAXRPCException: Cannot obtain operation meta data for: {http://localhost:8080/HelloWorld}sayHello at org.jboss.ws.jaxrpc.CallImpl.getOperationMetaData(CallImpl.java:840) at org.jboss.ws.jaxrpc.CallImpl.getOperationMetaData(CallImpl.java:820) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:618) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) at helloworld.client.HelloClient.main(HelloClient.java:50) +++++++++++++++++++++++++++++++++++++++++++++ I am invoking the webservice in 2 ways . One fetching the remote interface and one use a CallImpl My client code is as follows :- +++++++++++++++++++++++++++++++++++++++++++++++ package helloworld.client; import helloworld.*; import javax.xml.rpc.Service; import javax.xml.rpc.Call; import javax.xml.rpc.ServiceFactory; import org.jboss.ws.jaxrpc.ServiceImpl; import org.jboss.ws.jaxrpc.CallImpl; import org.jboss.ws.jaxrpc.encoding.*; import javax.xml.namespace.QName; import java.net.URL; public class HelloClient { public static void main(String[] args) throws Exception { String TARGET_NAMESPACE = "http://localhost:8080/HelloWorld"; String argument = "Kapilesh"; System.out.println("Contacting webservice at " + TARGET_NAMESPACE ); ServiceFactory factory = ServiceFactory.newInstance(); URL wsdlLoction = new URL(TARGET_NAMESPACE+"?wsdl"); QName serviceName = new QName(TARGET_NAMESPACE, "HelloWorldService"); ServiceImpl service = (ServiceImpl)factory.createService(wsdlLoction, serviceName); QName operationName = new QName(TARGET_NAMESPACE, "sayHello"); //first method IHelloWorld hello = (IHelloWorld) service.getPort(IHelloWorld.class); // System.out.println("hello.hello(" + argument + ")"); System.out.println("output:" + hello.sayHello(argument)); CallImpl call = (CallImpl)service.createCall(); call.setOperationName(operationName); // System.out.println(call.isParameterAndReturnSpecRequired(operationName)); // second method Object retObj = call.invoke(new Object[]{argument}); } } +++++++++++++++++++++++++++++++++++++++++++++++ I have deployed a webservice on a server and I am able to deploy it sucessfully... 15:08:30,968 WARN [PortComponentMetaData] element in webservices.xml not namespace qualified: HelloWorldPort 15:08:31,437 WARN [JSR109ServerMetaDataBuilder] Adding wsdl targetNamespace to: {http://localhost:8080/HelloWorld/}HelloWorldPort 15:08:31,812 INFO [TomcatDeployer] deploy, ctxPath=/HelloWorld, warUrl=.../tmp/deploy/tmp52320HelloWorld-exp.war/ 15:08:32,062 INFO [WSDLFilePublisher] WSDL published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/HelloWorld.war/HelloWorld.wsdl 15:08:32,093 INFO [ServiceEndpointManager] WebService started: http://localhost:8080/HelloWorld ++++++++++++++++++++++++++++++++++++++++++++++++ On the server side I have the following files deployed WEB-INF/classes/helloworld/HelloWorldService.class WEB-INF/classes/helloworld/IHelloWorld.class WEB-INF/classes/helloworld/impl/HelloWorld.class WEB-INF/classes/HelloWorld-mapping.xml WEB-INF/HelloWorld-mapping.xml WEB-INF/jaxrpc-mapping.xml WEB-INF/web.xml WEB-INF/webservices.xml WEB-INF/wsdl/HelloWorld.wsdl ++++++++++++++++++++++++++++++++++++++++++++++ webservices.xml ++++++++++++++++++++++++++++++++++++++++++++++ HelloWorld WEB-INF/wsdl/HelloWorld.wsdl WEB-INF/HelloWorld-mapping.xml IHelloWorldPort HelloWorldPort helloworld.IHelloWorld HelloWorld ++++++++++++++++++++++++++++++++++++++++++++++++ web.xml ++++++++++++++++++++++++++++++++++++++++++++++++ HelloWorld helloworld.impl.HelloWorld HelloWorld /* ++++++++++++++++++++++++++++++++++++++++++++++++ jax-rpc-mapping.xml ++++++++++++++++++++++++++++++++++++++++++++++++ helloworld http://localhost:8080/HelloWorld/ helloworld.HelloWorld serviceNS:HelloWorld IHelloWorldPort IHelloWorldPort helloworld.IHelloWorld portTypeNS:IHelloWorld bindingNS:IHelloWorldBinding sayHello sayHello 0 java.lang.String wsdlMsgNS:IHelloWorld_sayHello String_1 IN java.lang.String wsdlMsgNS:IHelloWorld_sayHelloResponse result ++++++++++++++++++++++++++++++++++++++++++++++++ HelloWorld-mapping.xml ++++++++++++++++++++++++++++++++++++++++++++++++ helloworld http://localhost:8080/HelloWorld/ helloworld.HelloWorldService serviceNS:HelloWorldService HelloWorldPort HelloWorldPort helloworld.IHelloWorld portTypeNS:IHelloWorld bindingNS:HelloWorld sayHello sayHello 0 java.lang.String wsdlMsgNS:sayHelloRequest sayHelloRequest IN java.lang.String wsdlMsgNS:sayHelloResponse sayHelloResponse ++++++++++++++++++++++++++++++++++++++++++++++++ HelloWorld.wsdl ++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++ My Java Class Files are as follows :- /* * JBoss, the OpenSource EJB server * Distributable under LGPL license. See terms of license at gnu.org. */ //Auto Generated by jbossws - Please do not edit!!! package helloworld; import javax.xml.rpc.*; public interface HelloWorldService extends javax.xml.rpc.Service { public helloworld.IHelloWorld getHelloWorldPort() throws ServiceException; } +++++++++++++++++++++++++++++++++++ /* * JBossWS WS-Tools Generated Source * * Generation Date: Mon Jun 04 14:47:16 IST 2007 * * This generated source code represents a derivative work of the input to * the generator that produced it. Consult the input for the copyright and * terms of use that apply to this source code. */ package helloworld; public interface IHelloWorld extends java.rmi.Remote { public java.lang.String sayHello(java.lang.String sayHelloRequest) throws java.rmi.RemoteException; } +++++++++++++++++++++++++++++++++++++++++++++ HelloWorld.java ++++++++++++++++++++++++++++++++++ package helloworld.impl; import helloworld.IHelloWorld; public class HelloWorld implements IHelloWorld { public String sayHello(String sayHelloRequest) { return "Hello How are you, " + sayHelloRequest + "!"; } } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050878#4050878 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050878 From do-not-reply at jboss.com Mon Jun 4 07:42:03 2007 From: do-not-reply at jboss.com (oskar.carlstedt) Date: Mon, 4 Jun 2007 07:42:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: javax.xml.rpc.JAXRPCException: Cannot obtain operation m Message-ID: <32981976.1180957323446.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! I read another thread on this forum having the same problem. It sounds that the SOAPAction http header is not set. Can you try to invoke the service by using SoapUI http://www.soapui.org, or enable the RequestDumperValve in tomcat's service.xml ($JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml). Doing so you can see all the sent request parameters, headers etc. Kind regards Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050899#4050899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050899 From do-not-reply at jboss.com Mon Jun 4 11:57:22 2007 From: do-not-reply at jboss.com (nightcap) Date: Mon, 4 Jun 2007 11:57:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WS-Security deployment Message-ID: <23338932.1180972642532.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I have a problem using WS-Security. When deploying the web service I get the following error at startup: 17:36:32,880 ERROR [ServiceEndpointDeployer] Cannot create service endpoint org.jboss.ws.WSException: Invalid config namespace: http://www.jboss.com/ws-security/config at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.java:91) I use: JBossWS 1.2.1 JBoss-4.0.5 JDK 1.5 This is the config file I use for the WS-Security: WEB-INF/server.keystore wsse WEB-INF/server.keystore jbossws--> Has anybody any idea why I get this error? I get no results when googling the error. Thanks very much! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051014#4051014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051014 From do-not-reply at jboss.com Mon Jun 4 11:59:13 2007 From: do-not-reply at jboss.com (nightcap) Date: Mon, 4 Jun 2007 11:59:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Security deployment Message-ID: <1438455.1180972753343.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry, config file was pasted in wrong: WEB-INF/server.keystore wsse WEB-INF/server.keystore jbossws View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051015#4051015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051015 From do-not-reply at jboss.com Tue Jun 5 03:18:39 2007 From: do-not-reply at jboss.com (smuehlba) Date: Tue, 5 Jun 2007 03:18:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Error: Unable to createEndpointReference Provider Message-ID: <20851175.1181027919958.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I have the same problem! I've tested to change libraries, but without any success... Any idea? Thanks in advance... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051204#4051204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051204 From do-not-reply at jboss.com Tue Jun 5 03:31:30 2007 From: do-not-reply at jboss.com (nightcap) Date: Tue, 5 Jun 2007 03:31:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Security deployment Message-ID: <11656005.1181028690618.JavaMail.jboss@colo-br-02.atl.jboss.com> This is now resolved, the problem was that I referred to the jboss-ws-security.xml in the @EndpointConfig annotation and not to the standard-jaxws-endpoint-config.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051206#4051206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051206 From lifeandcare at gmail.com Tue Jun 5 04:04:12 2007 From: lifeandcare at gmail.com (Noorul Hasan Khan) Date: Tue, 5 Jun 2007 13:34:12 +0530 Subject: [jbossws-users] JBoss : Digest Authentication not works in web application Message-ID: <510e5dd0706050104j72aa925o855475ddc4f6281@mail.gmail.com> Hi, I have implemented BASIC authentication on JBossAS successfully. But when I want to use DIGEST authentication, it does not work. I have done according to http://docs.jboss.org/jbossas/guides/webguide/r2/en/html_single/#d0e708 but it not works. I have added a security policy in jboss-4.0.5.GA\server\default \conf\login.config.xml, props/ProWS- users.properties props/ProWS- roles.properties MD5 rfc2617 false true true org.jboss.security.auth.spi.RFC2617Digest I have added users in jboss-4.0.5.GA\server\default\conf\props\ProWS-users.properties, # A sample users.properties file for use with the UsersRolesLoginModule admin=6b205f65c5200e6cdfaa38915407eb17 ashish=b81277561fad2cce151847f72b850414 noorul=930ab5c31004b14a83c93b53554c25d2 I have added roles in jboss-4.0.5.GA\server\default\conf\props\ProWS-roles.properties , # A sample users.properties file for use with the UsersRolesLoginModule admin=ShinseiAdmin ashish=ShinseiAdmin noorul=ShinseiAdmin I have assigned security policy in jboss-4.0.5.GA\server\default\deploy\ProWebs.war\WEB-INF\jboss-web.xml, java:/jaas/ProWS /ProWebs I have added security-constraint in jboss-4.0.5.GA\server\default\deploy\ProWebs.war\WEB-INF\web.xml, HtmlAdaptor An example security config that only allows users with the role ShinseiAdmin to access the HTML ShinseiWS web application /* GET POST ShinseiAdmin Public /public/* GET POST DIGEST ProWebs ShinseiAdmin But it not works. Please help me. Warm Regards Noorul Hasan Khan Software Engineer Prologix Software Solutions Pvt. Ltd., India -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20070605/8d32ea7a/attachment.html From do-not-reply at jboss.com Tue Jun 5 04:20:39 2007 From: do-not-reply at jboss.com (kapilesh.arekar) Date: Tue, 5 Jun 2007 04:20:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: javax.xml.rpc.JAXRPCException: Cannot obtain operation m Message-ID: <18381215.1181031639784.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for ur response oskar . I enabled the Request dumper value. In "HelloClient.java" When I use the following code and exeute it runs correctly and returns me a reply. +++++++++++++++++++++++++++++++++++++++++++++ Sample 1 Here I need a Remote interface to invoke the service:- ++++++++++++++++++++++++++++++++++++++++++++++ IHelloWorld hello = (IHelloWorld) service.getPort(IHelloWorld.class); // System.out.println("hello.hello(" + argument + ")"); System.out.println("output:" + hello.sayHello(argument)); // CallImpl call = (CallImpl)service.createCall(); //call.setOperationName(operationName); // System.out.println(call.isParameterAndReturnSpecRequired(operationName)); //Object retObj = call.invoke(new Object[]{argument}); +++++++++++++++++++++++++++++++++++++++++++++++ The following Headers appear in the Log in the log +++++++++++++++++++++++++++++++++++++++++++++ 13:28:15,750 INFO [[localhost]] REQUEST URI =/HelloWorld 13:28:15,750 INFO [[localhost]] authType=null 13:28:15,750 INFO [[localhost]] characterEncoding=null 13:28:15,750 INFO [[localhost]] contentLength=-1 13:28:15,750 INFO [[localhost]] contentType=application/x-www-form-urlencoded 13:28:15,750 INFO [[localhost]] contextPath=/HelloWorld 13:28:15,750 INFO [[localhost]] header=user-agent=Java/1.5.0_09 13:28:15,750 INFO [[localhost]] header=host=localhost:8080 13:28:15,750 INFO [[localhost]] header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 13:28:15,750 INFO [[localhost]] header=connection=keep-alive 13:28:15,750 INFO [[localhost]] header=content-type=application/x-www-form-urlencoded 13:28:15,750 INFO [[localhost]] locale=en_US 13:28:15,750 INFO [[localhost]] method=GET 13:28:15,750 INFO [[localhost]] parameter=wsdl= 13:28:15,750 INFO [[localhost]] pathInfo=/ 13:28:15,750 INFO [[localhost]] protocol=HTTP/1.1 13:28:15,750 INFO [[localhost]] queryString=wsdl 13:28:15,750 INFO [[localhost]] remoteAddr=127.0.0.1 13:28:15,750 INFO [[localhost]] remoteHost=127.0.0.1 13:28:15,750 INFO [[localhost]] remoteUser=null 13:28:15,750 INFO [[localhost]] requestedSessionId=null 13:28:15,750 INFO [[localhost]] scheme=http 13:28:15,750 INFO [[localhost]] serverName=localhost 13:28:15,750 INFO [[localhost]] serverPort=8080 13:28:15,750 INFO [[localhost]] servletPath= 13:28:15,750 INFO [[localhost]] isSecure=false 13:28:15,750 INFO [[localhost]] --------------------------------------------------------------- 13:28:15,812 INFO [[localhost]] --------------------------------------------------------------- 13:28:15,812 INFO [[localhost]] authType=null 13:28:15,812 INFO [[localhost]] contentLength=-1 13:28:15,812 INFO [[localhost]] contentType=text/xml 13:28:15,812 INFO [[localhost]] header=X-Powered-By=Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5 13:28:15,812 INFO [[localhost]] header=Content-Type=text/xml 13:28:15,812 INFO [[localhost]] header=Transfer-Encoding=chunked 13:28:15,812 INFO [[localhost]] header=Date=Tue, 05 Jun 2007 07:58:15 GMT 13:28:15,812 INFO [[localhost]] message=null 13:28:15,812 INFO [[localhost]] remoteUser=null 13:28:15,812 INFO [[localhost]] status=200 13:28:15,812 INFO [[localhost]] =============================================================== 13:28:15,890 INFO [[localhost]] REQUEST URI =/HelloWorld 13:28:15,890 INFO [[localhost]] authType=null 13:28:15,890 INFO [[localhost]] characterEncoding=null 13:28:15,890 INFO [[localhost]] contentLength=-1 13:28:15,890 INFO [[localhost]] contentType=application/x-www-form-urlencoded 13:28:15,890 INFO [[localhost]] contextPath=/HelloWorld 13:28:15,890 INFO [[localhost]] header=user-agent=Java/1.5.0_09 13:28:15,890 INFO [[localhost]] header=host=localhost:8080 13:28:15,890 INFO [[localhost]] header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 13:28:15,890 INFO [[localhost]] header=connection=keep-alive 13:28:15,890 INFO [[localhost]] header=content-type=application/x-www-form-urlencoded 13:28:15,890 INFO [[localhost]] locale=en_US 13:28:15,890 INFO [[localhost]] method=GET 13:28:15,890 INFO [[localhost]] parameter=wsdl= 13:28:15,890 INFO [[localhost]] pathInfo=/ 13:28:15,890 INFO [[localhost]] protocol=HTTP/1.1 13:28:15,890 INFO [[localhost]] queryString=wsdl 13:28:15,890 INFO [[localhost]] remoteAddr=127.0.0.1 13:28:15,890 INFO [[localhost]] remoteHost=127.0.0.1 13:28:15,890 INFO [[localhost]] remoteUser=null 13:28:15,890 INFO [[localhost]] requestedSessionId=null 13:28:15,890 INFO [[localhost]] scheme=http 13:28:15,890 INFO [[localhost]] serverName=localhost 13:28:15,890 INFO [[localhost]] serverPort=8080 13:28:15,890 INFO [[localhost]] servletPath= 13:28:15,890 INFO [[localhost]] isSecure=false 13:28:15,890 INFO [[localhost]] --------------------------------------------------------------- 13:28:15,906 INFO [[localhost]] --------------------------------------------------------------- 13:28:15,906 INFO [[localhost]] authType=null 13:28:15,906 INFO [[localhost]] contentLength=-1 13:28:15,906 INFO [[localhost]] contentType=text/xml 13:28:15,906 INFO [[localhost]] header=X-Powered-By=Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5 13:28:15,906 INFO [[localhost]] header=Content-Type=text/xml 13:28:15,906 INFO [[localhost]] header=Transfer-Encoding=chunked 13:28:15,906 INFO [[localhost]] header=Date=Tue, 05 Jun 2007 07:58:15 GMT 13:28:15,906 INFO [[localhost]] message=null 13:28:15,906 INFO [[localhost]] remoteUser=null 13:28:15,906 INFO [[localhost]] status=200 13:28:15,906 INFO [[localhost]] =============================================================== 13:28:16,234 INFO [[localhost]] REQUEST URI =/HelloWorld 13:28:16,234 INFO [[localhost]] authType=null 13:28:16,234 INFO [[localhost]] characterEncoding=UTF-8 13:28:16,234 INFO [[localhost]] contentLength=235 13:28:16,234 INFO [[localhost]] contentType=text/xml; charset=UTF-8 13:28:16,234 INFO [[localhost]] contextPath=/HelloWorld 13:28:16,234 INFO [[localhost]] header=soapaction="http://localhost:8080/HelloWorld/sayHello" 13:28:16,234 INFO [[localhost]] header=content-type=text/xml; charset=UTF-8 13:28:16,234 INFO [[localhost]] header=user-agent=Java/1.5.0_09 13:28:16,234 INFO [[localhost]] header=host=localhost:8080 13:28:16,234 INFO [[localhost]] header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 13:28:16,234 INFO [[localhost]] header=connection=keep-alive 13:28:16,234 INFO [[localhost]] header=content-length=235 13:28:16,234 INFO [[localhost]] locale=en_US 13:28:16,234 INFO [[localhost]] method=POST 13:28:16,234 INFO [[localhost]] pathInfo=/ 13:28:16,234 INFO [[localhost]] protocol=HTTP/1.1 13:28:16,234 INFO [[localhost]] queryString=null 13:28:16,234 INFO [[localhost]] remoteAddr=127.0.0.1 13:28:16,234 INFO [[localhost]] remoteHost=127.0.0.1 13:28:16,234 INFO [[localhost]] remoteUser=null 13:28:16,234 INFO [[localhost]] requestedSessionId=null 13:28:16,234 INFO [[localhost]] scheme=http 13:28:16,234 INFO [[localhost]] serverName=localhost 13:28:16,234 INFO [[localhost]] serverPort=8080 13:28:16,234 INFO [[localhost]] servletPath= 13:28:16,234 INFO [[localhost]] isSecure=false 13:28:16,234 INFO [[localhost]] ------------------------------------------------++++++++++++++++++++++++++++++++++++++++++++++++ If you look at the above log you will see Soap headers been set +++++++++++++++++++++++++++++++++++++++++++++++ Sample 2. I use the Call Implementation. I have commented out the Remote interface call and use call.invoke() instead +++++++++++++++++++++++++++++++++++++++++ //IHelloWorld hello = (IHelloWorld) service.getPort(IHelloWorld.class); // System.out.println("hello.hello(" + argument + ")"); // System.out.println("output:" + hello.sayHello(argument)); CallImpl call = (CallImpl)service.createCall(); QName operationName = new QName(TARGET_NAMESPACE, "sayHello"); call.setOperationName(operationName); System.out.println(call.isParameterAndReturnSpecRequired(operationName)); Object retObj = call.invoke(new Object[]{argument}); ++++++++++++++++++++++++++++++++++++++++++++ The output I get is as follows. If you notice the last part i.e the setting of Soap Headers is missing. +++++++++++++++++++++++++++++++++++++++++++ 13:22:41,421 INFO [[localhost]] REQUEST URI =/HelloWorld 13:22:41,421 INFO [[localhost]] authType=null 13:22:41,421 INFO [[localhost]] characterEncoding=null 13:22:41,421 INFO [[localhost]] contentLength=-1 13:22:41,421 INFO [[localhost]] contentType=application/x-www-form-urlencoded 13:22:41,421 INFO [[localhost]] contextPath=/HelloWorld 13:22:41,421 INFO [[localhost]] header=user-agent=Java/1.5.0_09 13:22:41,421 INFO [[localhost]] header=host=localhost:8080 13:22:41,421 INFO [[localhost]] header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 13:22:41,421 INFO [[localhost]] header=connection=keep-alive 13:22:41,421 INFO [[localhost]] header=content-type=application/x-www-form-urlencoded 13:22:41,421 INFO [[localhost]] locale=en_US 13:22:41,421 INFO [[localhost]] method=GET 13:22:41,421 INFO [[localhost]] parameter=wsdl= 13:22:41,421 INFO [[localhost]] pathInfo=/ 13:22:41,421 INFO [[localhost]] protocol=HTTP/1.1 13:22:41,421 INFO [[localhost]] queryString=wsdl 13:22:41,421 INFO [[localhost]] remoteAddr=127.0.0.1 13:22:41,421 INFO [[localhost]] remoteHost=127.0.0.1 13:22:41,421 INFO [[localhost]] remoteUser=null 13:22:41,421 INFO [[localhost]] requestedSessionId=null 13:22:41,421 INFO [[localhost]] scheme=http 13:22:41,421 INFO [[localhost]] serverName=localhost 13:22:41,421 INFO [[localhost]] serverPort=8080 13:22:41,421 INFO [[localhost]] servletPath= 13:22:41,421 INFO [[localhost]] isSecure=false 13:22:41,421 INFO [[localhost]] --------------------------------------------------------------- 13:22:41,484 INFO [[localhost]] --------------------------------------------------------------- 13:22:41,484 INFO [[localhost]] authType=null 13:22:41,500 INFO [[localhost]] contentLength=-1 13:22:41,500 INFO [[localhost]] contentType=text/xml 13:22:41,500 INFO [[localhost]] header=X-Powered-By=Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5 13:22:41,500 INFO [[localhost]] header=Content-Type=text/xml 13:22:41,500 INFO [[localhost]] header=Transfer-Encoding=chunked 13:22:41,500 INFO [[localhost]] header=Date=Tue, 05 Jun 2007 07:52:41 GMT 13:22:41,500 INFO [[localhost]] message=null 13:22:41,500 INFO [[localhost]] remoteUser=null 13:22:41,500 INFO [[localhost]] status=200 13:22:41,500 INFO [[localhost]] =============================================================== 13:22:41,562 INFO [[localhost]] REQUEST URI =/HelloWorld 13:22:41,562 INFO [[localhost]] authType=null 13:22:41,562 INFO [[localhost]] characterEncoding=null 13:22:41,562 INFO [[localhost]] contentLength=-1 13:22:41,562 INFO [[localhost]] contentType=application/x-www-form-urlencoded 13:22:41,562 INFO [[localhost]] contextPath=/HelloWorld 13:22:41,562 INFO [[localhost]] header=user-agent=Java/1.5.0_09 13:22:41,562 INFO [[localhost]] header=host=localhost:8080 13:22:41,562 INFO [[localhost]] header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 13:22:41,562 INFO [[localhost]] header=connection=keep-alive 13:22:41,562 INFO [[localhost]] header=content-type=application/x-www-form-urlencoded 13:22:41,562 INFO [[localhost]] locale=en_US 13:22:41,562 INFO [[localhost]] method=GET 13:22:41,562 INFO [[localhost]] parameter=wsdl= 13:22:41,562 INFO [[localhost]] pathInfo=/ 13:22:41,562 INFO [[localhost]] protocol=HTTP/1.1 13:22:41,562 INFO [[localhost]] queryString=wsdl 13:22:41,562 INFO [[localhost]] remoteAddr=127.0.0.1 13:22:41,562 INFO [[localhost]] remoteHost=127.0.0.1 13:22:41,562 INFO [[localhost]] remoteUser=null 13:22:41,562 INFO [[localhost]] requestedSessionId=null 13:22:41,562 INFO [[localhost]] scheme=http 13:22:41,562 INFO [[localhost]] serverName=localhost 13:22:41,562 INFO [[localhost]] serverPort=8080 13:22:41,562 INFO [[localhost]] servletPath= 13:22:41,562 INFO [[localhost]] isSecure=false 13:22:41,562 INFO [[localhost]] --------------------------------------------------------------- 13:22:41,578 INFO [[localhost]] --------------------------------------------------------------- 13:22:41,578 INFO [[localhost]] authType=null 13:22:41,578 INFO [[localhost]] contentLength=-1 13:22:41,578 INFO [[localhost]] contentType=text/xml 13:22:41,578 INFO [[localhost]] header=X-Powered-By=Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5 13:22:41,578 INFO [[localhost]] header=Content-Type=text/xml 13:22:41,578 INFO [[localhost]] header=Transfer-Encoding=chunked 13:22:41,578 INFO [[localhost]] header=Date=Tue, 05 Jun 2007 07:52:41 GMT 13:22:41,578 INFO [[localhost]] message=null 13:22:41,578 INFO [[localhost]] remoteUser=null 13:22:41,578 INFO [[localhost]] status=200 13:22:41,578 INFO [[localhost]] ================================================ ++++++++++++++++++++++++++++++++++++++++++++++ The reason I donot want to use SOAP is that the client is a PHP client and currently only supports XML-RPC and expects a response in pure XML. Is there a way where i could configure the webservice to take in XML-RPC calls respond in XML-RPC without wrapping it in a soap envelope. May be I am sounding a little weird . Thanks so much ifor the help so far View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051222#4051222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051222 From do-not-reply at jboss.com Tue Jun 5 08:06:07 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:06:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Error: Unable to createEndpointReference Provider Message-ID: <30421130.1181045167032.JavaMail.jboss@colo-br-02.atl.jboss.com> How you you invoking the client? What version (AS+JBossWS) are you using? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051296#4051296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051296 From do-not-reply at jboss.com Tue Jun 5 08:14:39 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:14:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SOAP header not being set as request param Message-ID: <15465386.1181045679409.JavaMail.jboss@colo-br-02.atl.jboss.com> Looks like a bug to me. I've created an issue for this: http://jira.jboss.com/jira/browse/JBWS-1694 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051300#4051300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051300 From do-not-reply at jboss.com Tue Jun 5 08:17:26 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:17:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: wsconsume, now what? server side deployment Message-ID: <4336533.1181045846697.JavaMail.jboss@colo-br-02.atl.jboss.com> This should help: http://jbws.dyndns.org/mediawiki/index.php/Quick_Start If it doesn't, please feel free to add a 2 minute tutorial to the WIKI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051301#4051301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051301 From do-not-reply at jboss.com Tue Jun 5 08:39:30 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:39:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServiceRef injection does not work Message-ID: <32933768.1181047170020.JavaMail.jboss@colo-br-02.atl.jboss.com> Well, looking at the wsrunclient script i'd say it's really pointless. In order for @WebServiceRef annotations to work on the client side it needs an IoC container that's capable of providing the injection. EJB3 comes with a ClientLauncher (take a look at the jaxws/samples/webserviceref/WebServiceRefClientTestCase.java) that can do it, however its not being used from the script. To me it look like the wsrunclient simply provides a classpath for simple (i.e. Service.create) invocations. I did setup an issue for this: http://jira.jboss.com/jira/browse/JBWS-1695 Are you intersted in contributing this functionality? I'll gladly advice you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051306#4051306 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051306 From do-not-reply at jboss.com Tue Jun 5 08:45:13 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:45:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MIssing wsdl4j.jar in scripts Message-ID: <9747791.1181047513587.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the report. Your fix will be included in 2.0: http://jira.jboss.com/jira/browse/JBWS-1696 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051308#4051308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051308 From do-not-reply at jboss.com Tue Jun 5 08:53:20 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:53:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: wsrunclient for jax-ws Message-ID: <14859473.1181048000615.JavaMail.jboss@colo-br-02.atl.jboss.com> It's the Stax API (stax-api.jar) missing from on the client classpath. Did you use the JBOSS_HOME/bin/wsrunclient.sh ? It does setup the correct classpath for you... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051314#4051314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051314 From do-not-reply at jboss.com Tue Jun 5 08:56:30 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 08:56:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: ant task produces java.lang.NoClassDefFoundError: com/s Message-ID: <29872464.1181048190692.JavaMail.jboss@colo-br-02.atl.jboss.com> Could you post the build file excerpt that defines the wsconsume task? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051315#4051315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051315 From do-not-reply at jboss.com Tue Jun 5 09:10:33 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 09:10:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SWA / MTOM attachments Message-ID: <26152279.1181049033764.JavaMail.jboss@colo-br-02.atl.jboss.com> Sreedhar, MTOM and SwA are two diffrent things. Both deal with attachments but in different manner. Actually when talking about attachments you'll encounter SwA, SwARef and MTOM/XOP. SwA has interop issues which SwARef did solve and MTOM relieves the interposed SOAP processors from having to deal with resource consumption while processing messages in transit. However, looking at your detailed report (thanks, that simplifies things a lot) i can see two things: anonymous wrote : | org.jboss.ws.binding.BindingException: Mime type text/xml not allowed for parameter mimepart allowed types are [application/xml] | anonymous wrote : | URL temp = new File("resources/jaxrpc/samples/swa/attach.xml").toURL(); | See first one states that the endpoint does only accept attachment of the type "application/octet-stream". Looking at your samples code in the second quote, you create a URL to a *.xml file. The JAF API will create a DataHandler instance with the content-type 'text/xml' from that, which then would be submitted. If you change the client to use the right content-type everything works fine. Please consult the JAF API for further information on this topic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051323#4051323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051323 From do-not-reply at jboss.com Tue Jun 5 09:12:28 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Tue, 5 Jun 2007 09:12:28 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 1.2.0CR2 with JEMS 1.2 (and JBoss 4.0.5) fails Message-ID: <20774339.1181049148985.JavaMail.jboss@colo-br-02.atl.jboss.com> good idea ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051325#4051325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051325 From do-not-reply at jboss.com Tue Jun 5 10:27:32 2007 From: do-not-reply at jboss.com (bcowan) Date: Tue, 5 Jun 2007 10:27:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Stop enforcing parameter names? Message-ID: <606759.1181053652400.JavaMail.jboss@colo-br-02.atl.jboss.com> I've recently updated a web service from JBoss 4.0.2 to 4.0.5 with JBossWS 1.2.1, and it's causing problems. The new setup enforces the proper naming of method parameters, instead of just taking them positionally. Some older clients don't send the proper parameter names. For example, Axis generated clients just call them "in0", "in1", "in2", etc. Whereas the old server happily accepted this, the new one throws a NotFound exception because the WSDL lists them as "String_1", "String_2", and so on. Is there any way to stop enforcing parameter names? The WSDL specifies the proper order, and this is all we need. It is important so remain compatible with old clients without changing the WSDL. Thanks, Bruce View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051378#4051378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051378 From do-not-reply at jboss.com Tue Jun 5 10:55:10 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Tue, 5 Jun 2007 10:55:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Stop enforcing parameter names? Message-ID: <33026954.1181055310792.JavaMail.jboss@colo-br-02.atl.jboss.com> The question is, whether the incomming message conforms to the abstract contract published by the endpoint. If the message is invalid with that respect it simply is invalid View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051401#4051401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051401 From do-not-reply at jboss.com Tue Jun 5 11:10:08 2007 From: do-not-reply at jboss.com (bigdaddy66) Date: Tue, 5 Jun 2007 11:10:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBossWS with JBoss 4.2.0 and Axis 1.4 don't work with WSSecu Message-ID: <3617845.1181056208025.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, i want to setup a testbed to communicate secure between JBoss 4.2.0 and Axis 1.4 with WSS4J 1.5.2. I already setup an WSFacade (EJB2.1) with a simple Add-Method to sum up two Integer. The Method works (the whole WSFacade has more Methods that are all already used and working fine. Now i want to setup WSSecurity with WSS4J. No Authentication - only Signing and Encryption between the Server (JBoss) and the Client (Axis). I developed a simple standalone J2SE-Application which successful call the add-method and get the result - all fine without signing etc. Now with signing i receive following error-message in the jboss-console: anonymous wrote : | 16:51:27,394 ERROR [WSSecurityDispatcher] Internal error occured handling inbound message: | org.jboss.ws.extensions.security.SecurityTokenUnavailableException: Could not locate certificate by issuer and serial number | at org.jboss.ws.extensions.security.KeyResolver.resolveX509IssuerSerial(KeyResolver.java:122) | at org.jboss.ws.extensions.security.KeyResolver.resolve(KeyResolver.java:92) | at org.jboss.ws.extensions.security.KeyResolver.resolveCertificate(KeyResolver.java:129) | at org.jboss.ws.extensions.security.KeyResolver.resolvePublicKey(KeyResolver.java:139) | at org.jboss.ws.extensions.security.KeyResolver.resolvePublicKey(KeyResolver.java:159) | at org.jboss.ws.extensions.security.element.Signature.(Signature.java:56) | at org.jboss.ws.extensions.security.element.SecurityHeader.(SecurityHeader.java:87) | at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:182) | at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:145) | at org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:66) | at org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandlerInbound.handleRequest(WSSecurityHandlerInbound.java:42) | at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleRequest(HandlerWrapper.java:121) | at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequestInternal(HandlerChainBaseImpl.java:291) | at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequest(HandlerChainBaseImpl.java:251) | at org.jboss.ws.core.jaxrpc.handler.ServerHandlerChain.handleRequest(ServerHandlerChain.java:54) | at org.jboss.ws.core.jaxrpc.handler.HandlerDelegateJAXRPC.callRequestHandlerChain(HandlerDelegateJAXRPC.java:108) | at org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB21$HandlerCallback.callRequestHandlerChain(ServiceEndpointInvokerEJB21.java:248) | at org.jboss.ws.integration.jboss42.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor.java:83) | at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) | at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169) | at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) | at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) | at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350) | at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181) | at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168) | at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) | at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138) | at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648) | at org.jboss.ejb.Container.invoke(Container.java:960) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB21.invokeServiceEndpointInstance(ServiceEndpointInvokerEJB21.java:189) | at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:207) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:212) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | I can't find the errormessage in this forum or the internet (except the sourcecode of jboss) The error comes clear to the client as SOAP Fault: anonymous wrote : | Exception in thread "main" AxisFault | faultCode: {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}SecurityTokenUnavailable | faultSubcode: | faultString: Could not locate certificate by issuer and serial number | faultActor: | faultNode: | faultDetail: | {http://xml.apache.org/axis/}stackTrace:Could not locate certificate by issuer and serial number | .... CUT | What can happend? Now to my little client: | public static void main(String[] args) throws Exception { | URL url = new URL( | "http://127.0.0.1:8080/WSFacadeSessionService/WSFacadeSession?wsdl"); | | QName qname = new QName("http://model.nhb.cerebral.de", | "WSFacadeService"); | | ServiceFactory factory = ServiceFactory.newInstance(); | Service service = factory.createService(url, qname); | | WSFacadeEndpoint endpoint = (WSFacadeEndpoint) service | .getPort(WSFacadeEndpoint.class); | | int a = 5; | int b = 7; | int sum = endpoint.add(a, b); | | System.out.println(a + " + " + b + " = " + sum); | | } | My PWCallback simple set the password. (Its only a testbed, u can know the stupid passwd :-)) | public void handle(Callback[] callbacks) throws IOException, | UnsupportedCallbackException { | | for (int i = 0; i < callbacks.length; i++) { | if (callbacks instanceof WSPasswordCallback) { | WSPasswordCallback pc = (WSPasswordCallback) callbacks; | | pc.setPassword("guenthermuh"); | | } else { | throw new UnsupportedCallbackException(callbacks, | "Unrecognized Callback"); | } | } | } | Now the DDs: client-config.wsdd: | | | | | | | | | | | | | | | | | | | | | my crypto.properties: | org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin | org.apache.ws.security.crypto.merlin.keystore.type=jks | org.apache.ws.security.crypto.merlin.file=client.keystore | org.apache.ws.security.crypto.merlin.keystore.alias=clientcert | org.apache.ws.security.crypto.merlin.keystore.password=guenthermuh | org.apache.ws.security.crypto.merlin.alias.password=guenthermuh | To the certificates later. Now the JBoss-server: in the webservices.xml in the port-component-block i added this: | | | Standard Secure Endpoint | | | | SecureHandlerChain | | | | WSSecurityHandlerInbound | | | org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandlerInbound | | | | | | my jboss-wsse-server.xml: | | META-INF/wsse.keystore | guenthermuh | META-INF/wsse.truststore | guenthermuh | | | | | | | | | | to "sign type="x509v1" " - the same error exist with x509x3 as type definition I can post the webservice request when you want.It has the security-header etc. To the certificates: i generated all with the keytool like the schema described here in the forums. alice (JBoss) has in his wsse.keystore there own private and public-key (signed) and i imported the public-key from Bob (signed too). the wsse.truststore only has the public-key from alice. (Alias: wsse) Bob has only a keystore: client.keystore - alias: clientcert. it included his own private and publickey (signed) and the publickey from alice (signed too). so, what is wrong? :-) And does i need the WSSecurityHandlerOutbound for a fullsecure communication? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051413#4051413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051413 From do-not-reply at jboss.com Tue Jun 5 11:10:51 2007 From: do-not-reply at jboss.com (bigdaddy66) Date: Tue, 5 Jun 2007 11:10:51 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS with JBoss 4.2.0 and Axis 1.4 don't work with WS Message-ID: <22213455.1181056251557.JavaMail.jboss@colo-br-02.atl.jboss.com> Btw. the certificates are selfsigned (with the keytool) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051415#4051415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051415 From do-not-reply at jboss.com Tue Jun 5 11:20:09 2007 From: do-not-reply at jboss.com (bcowan) Date: Tue, 5 Jun 2007 11:20:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Stop enforcing parameter names? Message-ID: <31276095.1181056809657.JavaMail.jboss@colo-br-02.atl.jboss.com> "thomas.diesler at jboss.com" wrote : The question is, whether the incomming message conforms to the abstract contract published by the endpoint. If the message is invalid with that respect it simply is invalid At this point we're much more concerned about consistency. Updating to a newer server version has invalidated several thousand clients because the server has changed the way it validates the messages. Granted that those clients don't conform 100% to the published WSDL, but the tools at the time (including JBoss) ignored parameter names so it has never been an issue. Since the WSDL specifies the type and order of the parameters, validation of the actual name wasn't (and perhaps isn't) required. We just need the current version of the JBoss web service stack to handle messages in compatible manner with the prior version. Judging by your response, it sounds like there is no such compatibility option. Regards, Bruce View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051420#4051420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051420 From do-not-reply at jboss.com Tue Jun 5 11:55:17 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Tue, 5 Jun 2007 11:55:17 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Stop enforcing parameter names? Message-ID: <9218063.1181058917141.JavaMail.jboss@colo-br-02.atl.jboss.com> You can setup an endpoint that consumes raw XML. Have a look at JAXWS @Provider, also an XML preproccessing phase might do the job for you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051443#4051443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051443 From do-not-reply at jboss.com Tue Jun 5 17:58:01 2007 From: do-not-reply at jboss.com (jopere) Date: Tue, 5 Jun 2007 17:58:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Duplicate SOAP body/envelope tags in SOAP message Message-ID: <14381276.1181080681800.JavaMail.jboss@colo-br-02.atl.jboss.com> I have written two web services that I have tested separately and now I am trying to call one web service from the other. I have a client that is succesfully calling web service A, but when A tries to call web service B I get this message: 16:08:03,834 ERROR [SOAPFaultExceptionHelper] SOAP request exception javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://acxiom.com/greeting/1.0}GetGreetingEjbInterf acePort does not contain operation meta data for: {http://schemas.xmlsoap.org/soap/envelope/}Envelope This is the SOAP message that is being sent: Note that there are two env:Envelope and two enb:Body tags. I am not sure what I need to do to get this to work. I am using JBOSS 4.0.4, jdk 1.5.0.7 and jwsdp 2.0. I use wstools to generate the server artifacts for web service a using this configuration file: Web service A is the client to web service B and I use wscompile to generate the artifacts using this configuration file: Web service B uses WSTOOLS and this configuration file: Any help would be appreciated! John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051551#4051551 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051551 From do-not-reply at jboss.com Wed Jun 6 03:57:26 2007 From: do-not-reply at jboss.com (fambad) Date: Wed, 6 Jun 2007 03:57:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem with inheritance and JBossWS Message-ID: <5316553.1181116646314.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a problem with the new JBossWS-1.2.1.GA in JBoss 4.2.0.GA and inheritance. To describe this problem first I have to describe my code structure: For an example I have three classes (ClassA, ClassB and ClassC). ClassC inherits of ClassB and ClassB inherits of ClassA (ClassA --> ClassB --> ClassC). Now I have a webservice method that returns ClassB. In this method an instance of ClassC is being created and returned. This was not a problem in the former JBossWS version (and also in the other J2EE 4 styled webservices) but now in JBossWS 1.2 I only get returned an object of ClassB but I supposed to get an obejct of ClassC. | public class ClassA { | private String propA; | | // here setter and getter for propA | ...... | } | | public class ClassB extends ClassA { | | private String propB; | // here setter and getter for propB | ...... | } | | public class ClassC extends ClassC { | private String propC; | // here setter and getter for propC | ...... | } | | @WebService | @SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED ) | public class MyWebService { | | @WebMethod() | public ClassB getClassB() { | ClassC classC = new ClassC(); | classC.setPropA("propA"); | return classC; | } | | /** | * --> this method is only used to publish ClassC otherwise it is not known | * in this webservice | */ | @WebMethod() | public ClassC getClassC() { | ClassC classC = new ClassC(); | classC.setPropA("propA"); | return classC; | } | | } | | } Now I call getClassB() and the result that I got is an object of ClassB and not of ClassC. What can I do to get an object of ClassC. I also looked at the returned SOAP message and there you can see that only informations about the ClassB instance are submitted. In JBoss 4.0.5 (JBossWS1.0.3) the SOAP message contains the type of the returned object and all data are being submitted correctly. I also tried the SOAP parameter style BARE but nothing changed. And whenI use RPC/Literal then I get an error in the .NET Client that an instance of ClassB was expected but got an instance of ClassC. I also tried it with a JAVA client but there was the same occurance. Any help would be appreciated! Marco. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051611#4051611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051611 From do-not-reply at jboss.com Wed Jun 6 04:46:47 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Wed, 6 Jun 2007 04:46:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - problem calling webservice from client Message-ID: <4528726.1181119607662.JavaMail.jboss@colo-br-02.atl.jboss.com> when i try to run the client it raises next exception. I use jboss 4.2 and jbossws 1.2. My aplication code is like this: public interface SesionSession { public com.satdatatelecom.satdataweb.model.session.vo.LoginVO login .......} -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- @WebService(endpointInterface="com.satdatatelecom.satdataweb.model.session.session.SesionEndPointInterface", targetNamespace = "http://localhost:8080/jbossws/services/Sesion", serviceName = "loginUsuario") @Remote(SesionSession.class) @RemoteBinding(jndiBinding = "/ejb3/EJB3SesionEndPointInterface") @Stateless public class SesionSessionBean implements SesionSession { @PersistenceContext(unitName = GlobalNames.PERSISTENCE_UNIT) private EntityManager entityManager; @WebMethod(action = "urn:Sesion") public LoginVO loginUsuario........................... .............................................. ........................................... } - ------------------------------------------------------------------------------- --------------------------------------------------------------------------------------- @WebService(targetNamespace = "http://net.jboss.org/satdataweb") @WebContext(urlPattern="/*") @SOAPBinding(style = Style.RPC) public interface SesionEndPointInterface extends Remote{ public LoginVO loginUsuario.................... ............................................... ............................................ ----------------------------------------------------------------------------------- ---------------------------------------------------------------------------------- In the client sidfe i do the following. I think the problem is here but i don?t know why public SessionFacadeWSImpl() throws InternalErrorException { try { System.out.println(" -0000001 SFWSI - Kike --->Creando LoginServiceLocator"); LoginUsuarioLocator locator = new LoginUsuarioLocator(); sesionSession = (SesionEndPointInterface) locator.getSesionSessionBeanPort(new URL("http://localhost:8080/jbossws/services/Sesion")); // DataConexion.getUrl(webService); System.out.println("0000002 SFWSI Kike --->Creado LoginServiceLocator , sessionSession ->" + sesionSession.toString() ); } catch (Exception ex) { ex.printStackTrace(); throw new InternalErrorException(ex); } } ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- and finally this is the stub generated by axis in the client ..................... ........................ public com.satdatatelecom.satdataweb.services.beans.LoginVO loginUsuario(java.lang.String arg0, java.lang.String arg1, java.lang.String arg2, java.lang.String arg3) throws java.rmi.RemoteException, com.satdatatelecom.satdataweb.services.beans.EmpresaNotFoundException, com.satdatatelecom.satdataweb.services.beans.PasswordException, com.satdatatelecom.satdataweb.services.beans.SessionException, com.satdatatelecom.satdataweb.services.beans.UsuarioNotFoundException, com.satdatatelecom.satdataweb.services.beans.ConcesionException, com.satdatatelecom.satdataweb.services.beans.ConcesionEmpresaException { if (super.cachedEndpoint == null) { throw new org.apache.axis.NoEndPointException(); } System.out.println("---------------- estoy dentro del Stub ---------------"); org.apache.axis.client.Call _call = createCall(); _call.setOperation(_operations[0]); _call.setUseSOAPAction(true); _call.setSOAPActionURI("Sesion"); System.out.println("---------------- estoy dentro del Stub METIACTION URI---------------"); _call.setEncodingStyle(null); _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, Boolean.FALSE); _call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS, Boolean.FALSE); _call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS); _call.setOperationName(new javax.xml.namespace.QName("http://session.session.model.satdataweb.satdatatelecom.com", "loginUsuario")); setRequestHeaders(_call); setAttachments(_call); try { java.lang.Object _resp = _call.invoke(new java.lang.Object[] {arg0, arg1, arg2, arg3}); This is the exception executiong the client (400)HTTP method POST is not supported by this URL at com.satdatatelecom.satdataweb.model.session.facade.webservice.SessionFacadeWSImpl.loginUsuario(SessionFacadeWSImpl.java:74) at com.satdatatelecom.satdataweb.gui.login.DoLogin.doLogin(DoLogin.java:189) at com.satdatatelecom.satdataweb.gui.login.thread.LoginThread.run(LoginThread.java:90) ***Information about encapsulated exception*** AxisFault faultCode: {http://xml.apache.org/axis/}HTTP faultSubcode: faultString: (400)HTTP method POST is not supported by this URL faultActor: faultNode: faultDetail: {}:return code: 400 JBossWeb/2.0.0.GA - Informe de Error

Estado HTTP 400 - HTTP method POST is not supported by this URL

type Informe de estadomensaje HTTP method POST is not supported by this URLdescripci??n El requerimiento enviado por el cliente era sint??cticamente incorrecto (HTTP method POST is not supported by this URL).

JBossWeb/2.0.0.GA

{http://xml.apache.org/axis/}HttpErrorCode:400 (400)HTTP method POST is not supported by this URL at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at com.satdatatelecom.satdataweb.services.beans.SesionEndPointInterfaceBindingStub.loginUsuario(SesionEndPointInterfaceBindingStub.java:243) at com.satdatatelecom.satdataweb.model.session.facade.webservice.SessionFacadeWSImpl.loginUsuario(SessionFacadeWSImpl.java:51) at com.satdatatelecom.satdataweb.gui.login.DoLogin.doLogin(DoLogin.java:189) at com.satdatatelecom.satdataweb.gui.login.thread.LoginThread.run(LoginThread.java:90) #### [06/06/2007, 10:30:10] ---> Error al conectar. No se puede conectar con el servidor 127.0.0.1: 8080 [06/06/2007, 10:30:10] ---> Error al conectar. No se puede conectar con el servidor 127.0.0.1: 8080 I need some help because i don?t know what to do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051629#4051629 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051629 From do-not-reply at jboss.com Wed Jun 6 08:01:05 2007 From: do-not-reply at jboss.com (cowsudders) Date: Wed, 6 Jun 2007 08:01:05 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Error Deploying documentliteral Web Service created in Netbe Message-ID: <15389170.1181131265712.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all I'm attempting to create a simple document literal web-service in JBoss 4.0.5 by using Netbeans 5.5. All is fine in Netbeans, but I receive the following error when deploying into JBoss: org.jboss.ws.WSException: Cannot load java type: company.name.lsp.security.interfaces.SecurityServiceSEI_InitialiseSession_RequestStruct Can someone please provide some help/guidance as to the commands/tools I need to use in order to create these server artefacts? I assume I need to use wstools - but what command do I need to use? Can I amend the Netbeans build.xml file to run the command automatically? Here is the SEI file: public interface SecurityServiceSEI extends Remote { /** * Web service operation */ public SessionMsg InitialiseSession(SessionMsg msg) throws java.rmi.RemoteException; } Here is the Impl file: public SessionMsg InitialiseSession(SessionMsg msg) throws java.rmi.RemoteException { System.out.println("We are in Initialise Session"); return msg; } If anyone requires more information, please ask and I will provide. Any help that can be provided will be much appreciated - thanks! Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051682#4051682 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051682 From do-not-reply at jboss.com Wed Jun 6 09:11:10 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Wed, 6 Jun 2007 09:11:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <9393762.1181135470259.JavaMail.jboss@colo-br-02.atl.jboss.com> If like to get involved please add a testcase to our testsuite http://jira.jboss.org/jira/browse/JBWS-1702 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051714#4051714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051714 From do-not-reply at jboss.com Wed Jun 6 09:17:29 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Wed, 6 Jun 2007 09:17:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problem calling webservice from client Message-ID: <22782570.1181135849963.JavaMail.jboss@colo-br-02.atl.jboss.com> You seem to be using Axis on the client side not jbossws. Please use [ code ] when you paste code View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051718#4051718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051718 From do-not-reply at jboss.com Wed Jun 6 12:46:13 2007 From: do-not-reply at jboss.com (dibind) Date: Wed, 6 Jun 2007 12:46:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Using JSR181 - problem with value types and arrays Message-ID: <25188961.1181148373732.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am getting same type of error where jboss is trying to load some class which is not there in my application. This happens only when i expose a method as webservice having array parameter. Can anybody help on this? Thanks in advance dibin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051821#4051821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051821 From do-not-reply at jboss.com Wed Jun 6 13:47:29 2007 From: do-not-reply at jboss.com (cowsudders) Date: Wed, 6 Jun 2007 13:47:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Error Deploying documentliteral Web Service created in N Message-ID: <20661513.1181152049533.JavaMail.jboss@colo-br-02.atl.jboss.com> I've now solved the problem if anyone else is suffering the same problem. I abandoned Netbeans and manually used wscompile to build the web-service server artefacts (including the mapping XML file). I then manually created the following: web.xml webservices.xml SEI_Implementation_Class and it successfully deployed into JBoss and it is being called successfully from a .NET application. Cheers Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051854#4051854 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051854 From do-not-reply at jboss.com Wed Jun 6 13:50:07 2007 From: do-not-reply at jboss.com (rphadnis) Date: Wed, 6 Jun 2007 13:50:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: ant task produces java.lang.NoClassDefFoundError: com/s Message-ID: <11477825.1181152207729.JavaMail.jboss@colo-br-02.atl.jboss.com> Can you ensure that the tools.jar for jdk 1.5 or higher is available in the classpath? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051857#4051857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051857 From do-not-reply at jboss.com Wed Jun 6 14:47:38 2007 From: do-not-reply at jboss.com (don@inpowersoft.com) Date: Wed, 6 Jun 2007 14:47:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Basic authentication for WS fails to authenticate from clien Message-ID: <6852037.1181155658342.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a bean that is annotated with @Webservice and @SecurityDomain @Stateless() @WebService() @SecurityDomain("MyDomain") @TransactionAttribute(TransactionAttributeType.REQUIRED) public class DownPartBean implements DownPartLocal, DownPartRemote { ... } MyDomain is setup appropriately in the login-config.xml and is proven to be working from other context. However, if I connect from a ws client even with the user and password set, the authentication always fails. I've also edit the META-INF/jboss.xml file such that it looks like below but it never works. The documentation relating to how to secure an end point does not work for me and I suspect I probably did something wrong. Appreciate any help.. -don jboss.xml MyDomain DownPartBean DownPartBean /lsaplEjbServer/DownPartBean BASIC View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051872#4051872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051872 From do-not-reply at jboss.com Wed Jun 6 15:10:55 2007 From: do-not-reply at jboss.com (vvenkatar) Date: Wed, 6 Jun 2007 15:10:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - unable to create service endpoint error with jbossws-1.2.1.G Message-ID: <21284520.1181157055473.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi: I have a web service that used to work with JBOSS4.0.4. I get the following error message when I attempt to deploy this on jboss4.2.0_GA. I upgraded to jbossws1.2.1 and still see the same problem.... Anybody else having similar problem? I would appreciate any help on this issue. Thanks, Venkatesh 2007-06-06 11:39:32,848 DEBUG [org.jboss.ws.core.server.ServiceEndpointDeployer] create: Ejb3.ear/synappsws.war 2007-06-06 11:39:32,864 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] START buildMetaData: [name=Ejb3.ear/synappsws.war] 2007-06-06 11:39:33,036 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] parse: file:/C:/jboss-4.2.0.GA/server/default/tmp/deploy/tmp55134Ejb3.ear-contents/synappsws-exp.war/WEB-INF/wsdl/synappsws.wsdl 2007-06-06 11:39:33,849 DEBUG [org.jboss.ws.tools.JavaToXSD] Load schema: http://com.sylantro.synapps/synappsws/types=file:/C:/jboss-4.2.0.GA/server/default/tmp/jbossws/JBossWS_com.sylantro.synapps_synappsws_types55135.xsd 2007-06-06 11:39:33,849 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=null,sysid=file:/C:/jboss-4.2.0.GA/server/default/tmp/jbossws/JBossWS_com.sylantro.synapps_synappsws_types55135.xsd] 2007-06-06 11:39:34,162 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://schemas.xmlsoap.org/soap/encoding/,sysid=null] 2007-06-06 11:39:35,413 DEBUG [org.jboss.ws.core.server.ServiceEndpointManager] Using WebServicePort: 8080 2007-06-06 11:39:35,428 DEBUG [org.jboss.ws.metadata.builder.MetaDataBuilder] Replace service endpoint address 'http://65.200.90.230/synapps1/SynappsWebservice' with 'http://127.0.0.1:8080/synapps1/SynappsWebservice' 2007-06-06 11:39:35,444 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] setParameterStyle: WRAPPED 2007-06-06 11:39:35,460 ERROR [org.jboss.ws.core.server.ServiceEndpointDeployer] Cannot create service endpoint java.lang.IllegalArgumentException: Could not determine variable name for element: parameters at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processOutputDocElement(JAXRPCMetaDataBuilder.java:801) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:897) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:214) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:220) at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:77) at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:127) at org.jboss.ws.integration.jboss42.DeployerInterceptorJSE.createServiceEndpoint(DeployerInterceptorJSE.java:132) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) 2007-06-06 11:39:35,460 DEBUG [org.jboss.ws.integration.jboss42.DeployerInterceptorJSE] destroy: file:/C:/jboss-4.2.0.GA/server/default/tmp/deploy/tmp55134Ejb3.ear-contents/synappsws.war 2007-06-06 11:39:35,460 DEBUG [org.jboss.ws.core.server.ServiceEndpointDeployer] destroy: Ejb3.ear/synappsws.war 2007-06-06 11:39:35,460 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051880#4051880 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051880 From do-not-reply at jboss.com Wed Jun 6 17:39:39 2007 From: do-not-reply at jboss.com (Saki) Date: Wed, 6 Jun 2007 17:39:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem using .NET Compact Framework Client Message-ID: <8644071.1181165979376.JavaMail.jboss@colo-br-02.atl.jboss.com> This is Microsofts Problem in CF. Here the workaround Use wsdl.exe /order to generate your client proxy class, and then remove all the code not supported by NetCF until your project compiles. | | Use Visual Studio to generate your client proxy class, then run wsdl.exe /order in some other directory, and copy just those lines of source code from the resulting class into your project source file that give the explicit ordering. | | Dikeni | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051907#4051907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051907 From do-not-reply at jboss.com Wed Jun 6 18:47:34 2007 From: do-not-reply at jboss.com (jopere) Date: Wed, 6 Jun 2007 18:47:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Duplicate SOAP body/envelope tags in SOAP message Message-ID: <21777426.1181170054715.JavaMail.jboss@colo-br-02.atl.jboss.com> I have determined that the problem is that I need to be able to clear the soap headers before calling the second web service. What's happening is that the second web service is being wrapped in the env/body tags from the first web service, which is why I am geeting multiple tags. I determined this by writing my own code that creates a SOAP message and sends it to the web service. The web service replies correctly. Does anyone know how to clear the SOAP headers or in some other way to get this to work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051924#4051924 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051924 From do-not-reply at jboss.com Thu Jun 7 03:32:35 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Thu, 7 Jun 2007 03:32:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problem calling webservice from client Message-ID: <22069541.1181201555901.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry Thomas. Finally i talked to the client developers and now i can use jbossws in the client side. The new SessionFacadeWSImpl() would be something like this? | System.out.println(" -0000001 SFWSI - Kike --->Creando Servicio"); | URL wsdlURL = new URL("http://127.0.0.1:8080/SesionSessionBeanService/SesionSessionBean?wsdl"); | QName serviceName = new QName("http://localhost:8080/jbossws/services/Sesion", "LoginService"); | Service service = Service.create(wsdlURL, serviceName); | sesionSession = (SesionEndPointInterface)service.getPort(SesionEndPointInterface.class); | System.out.println("0000002 SFWSI Kike --->Creado Servicio , sessionSession ->" + sesionSession.toString() ); | System.out.println("0000002 SFWSI Kike --->Creado Servicio , service ->" + service.toString() ); | | BindingProvider bindingProvider = (BindingProvider)sesionSession; | Map reqContext = bindingProvider.getRequestContext(); | reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, TARGET_ENDPOINT_ADDRESS); | reqContext.put(BindingProvider.USERNAME_PROPERTY, "kermit"); | reqContext.put(BindingProvider.PASSWORD_PROPERTY, "thefrog"); | after it , cain i call the login service from sessionSesion? which class hava i to copy in the client? Only the endpointInterface? Thanks Thomas Regards kike View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051987#4051987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051987 From do-not-reply at jboss.com Thu Jun 7 03:42:42 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Thu, 7 Jun 2007 03:42:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problem calling webservice from client Message-ID: <29483044.1181202162194.JavaMail.jboss@colo-br-02.atl.jboss.com> when i execute the client it askes me for a class, whick does not exists. | class: localhost.jbossws.services.Sesion.jaxws.EmpresaNotFoundExceptionBean could not be found | at com.sun.xml.internal.ws.modeler.RuntimeModeler.getClass(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processExceptions(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processRpcMethod(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processMethod(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processClass(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.buildRuntimeModel(Unknown Source) | at com.sun.xml.internal.ws.client.ServiceContextBuilder.processAnnotations(Unknown Source) | at com.sun.xml.internal.ws.client.ServiceContextBuilder.completeServiceContext(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.processServiceContext(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source) | at javax.xml.ws.Service.getPort(Unknown Source) | at com.satdatatelecom.satdataweb.model.session.facade.webservice.SessionFacadeWSImpl.(SessionFacadeWSImpl.java:47) | at com.satdatatelecom.satdataweb.data.DataUsuario.getSessionFacade(DataUsuario.java:69) | at com.satdatatelecom.satdataweb.gui.login.DoLogin.doLogin(DoLogin.java:182) | at com.satdatatelecom.satdataweb.gui.login.thread.LoginThread.run(LoginThread.java:90) | ***InternalErrorException | my class is named empresaNotFoundException. Why is it asking me for a class with the same name concatenating it with bean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051988#4051988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051988 From do-not-reply at jboss.com Thu Jun 7 05:02:03 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Thu, 7 Jun 2007 05:02:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problem calling webservice from client Message-ID: <17073130.1181206923850.JavaMail.jboss@colo-br-02.atl.jboss.com> i tried to not throw exceptions to see what happens and now i have the same problem as when i used axis. javax.xml.ws.WebServiceException: HTTP Status-Code 405: HTTP method POST is not supported by this URL | this is what i do in the client: | URL wsdlURL = null; | try { | wsdlURL = new URL("http://127.0.0.1:8080/SesionSessionBeanService/SesionSessionBean?wsdl"); | } catch (MalformedURLException e1) { | // TODO Auto-generated catch block | e1.printStackTrace(); | } | QName serviceName = new QName("http://localhost:8080/jbossws/services/Sesion", "LoginService"); | Service service = Service.create(wsdlURL, serviceName); | SesionEndPointInterface sesionSession = (SesionEndPointInterface)service.getPort(SesionEndPointInterface.class); | System.out.println("0000002 SFWSI Kike --->Creado Servicio , sessionSession ->" + sesionSession.toString() ); | System.out.println("0000002 SFWSI Kike --->Creado Servicio , service ->" + service.toString() ); | | BindingProvider bindingProvider = (BindingProvider)sesionSession; | Map reqContext = bindingProvider.getRequestContext(); | reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:8080/jbossws/services/Sesion/SesionSessionBean"); | reqContext.put(BindingProvider.USERNAME_PROPERTY, "kermit"); | reqContext.put(BindingProvider.PASSWORD_PROPERTY, "thefrog"); | | try{ | // System.out.println("Conectando con... " + DataConexion.getServer() + ": " + DataConexion.getServerPort()); | FicheroLog.writeIncidencia("Conectando con... " + DataConexion.getServer() + ": " + DataConexion.getServerPort()); | | loginVO = sesionSession.loginUsuario(idEmpresa, login, password, session); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052009#4052009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052009 From do-not-reply at jboss.com Thu Jun 7 07:49:33 2007 From: do-not-reply at jboss.com (nightcap) Date: Thu, 7 Jun 2007 07:49:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Retrieving alias for WS Secure client Message-ID: <10825795.1181216973183.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using X509 certificates to authenticate WebService clients for JBoss 4.0.5 and JBossWS 1.2.1 (JAX-WS). Everything works fine, however, in my web service code, I would like to know the alias for the public key entry in the keystore for the calling client. One way would be to parse the SOAP-document, obtain the element containing the security info, and manually look it up in the keystore. However, I wonder if there is a standardized way, (Jboss-specific is no problem) of obtaining the alias from the keystore given the SOAP message, or at least a way of obtaing the certificate from the SOAP-message without manually digging into SOAP-details. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052078#4052078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052078 From do-not-reply at jboss.com Thu Jun 7 09:12:37 2007 From: do-not-reply at jboss.com (bigdaddy66) Date: Thu, 7 Jun 2007 09:12:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Retrieving alias for WS Secure client Message-ID: <2944484.1181221957752.JavaMail.jboss@colo-br-02.atl.jboss.com> keytool -list -keystore this shows you all aliases in the keystore View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052124#4052124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052124 From do-not-reply at jboss.com Thu Jun 7 09:13:54 2007 From: do-not-reply at jboss.com (bigdaddy66) Date: Thu, 7 Jun 2007 09:13:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Retrieving alias for WS Secure client Message-ID: <863729.1181222034872.JavaMail.jboss@colo-br-02.atl.jboss.com> shit i cant edit - after -keystore must the file of the keystore :-) keytool -list -keystore wsse.keystore keytool is a program from sun shipped with the JRE and JDK. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052125#4052125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052125 From do-not-reply at jboss.com Thu Jun 7 09:29:01 2007 From: do-not-reply at jboss.com (nightcap) Date: Thu, 7 Jun 2007 09:29:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Retrieving alias for WS Secure client Message-ID: <23866783.1181222941105.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks, but using keytool is not what I am looking for. My question is if I from inside the web service method am able to extract the alias corresponding to the client's certificate. This imposes two steps 1. How do I extract the clients certificate from inside the web service method. One way would be to locate the wsse:BinarySecurityToken xml-tag in the SOAP message, extract the Base64-encoded certificate and then create an X509Certificate object from it, but that is not very elegant. 2. Lookup the alias in the keystore. To do that I could use KeyStore.getAliasForCertificate() provided 1. is solved. I am looking for something similair to WebServiceContext.getClientCertificate()... Anybody has a suggestion? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052135#4052135 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052135 From do-not-reply at jboss.com Thu Jun 7 11:52:00 2007 From: do-not-reply at jboss.com (swaminathan.ramaswamy) Date: Thu, 7 Jun 2007 11:52:00 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jbossws 1.2.1 /jboss 4.0.5 : how do i bypass MessageFactor Message-ID: <20926733.1181231520412.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi , I have been encountering the following exception over the last couple of days . I am aware that the reason for this issue is because of using a different SOAPFactory class, while jboss expects org.jboss.ws.core.soap.SOAPEnvelopeImpl. I am trying to run oracle's bpel process on jboss , and the bpel engine needs it's own implementation of SOAPElement/SOAPFactory to process Webservice calls - when i try sending Jboss's SOAPElement , the bpel process fails without any error message Is it possible for me to by pass Jboss' MessageFactory/SOAPFactory classes by setting some classloader hierarchy java.lang.ClassCastException: oracle.j2ee.ws.saaj.soap.soap11.Element11 at org.jboss.ws.core.soap.SOAPEnvelopeImpl.(SOAPEnvelopeImpl.java:59) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:197) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) Thanks, Swami View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052210#4052210 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052210 From do-not-reply at jboss.com Thu Jun 7 16:43:31 2007 From: do-not-reply at jboss.com (rphadnis) Date: Thu, 7 Jun 2007 16:43:31 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: unable to create service endpoint error with jbossws-1.2 Message-ID: <22063280.1181249011273.JavaMail.jboss@colo-br-02.atl.jboss.com> Is it having trouble locating your schema file(s)? Is the schema inline in the WSDL or is WSDL importing your schema. -Rahul View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052300#4052300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052300 From do-not-reply at jboss.com Thu Jun 7 16:49:42 2007 From: do-not-reply at jboss.com (rphadnis) Date: Thu, 7 Jun 2007 16:49:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How is the service URL constructed Message-ID: <11587822.1181249382325.JavaMail.jboss@colo-br-02.atl.jboss.com> I am trying to find out how the service URL is constructed. I have a stateless session bean that is implementing a web service. The stateless session bean is packaged in an EAR file. The name of the service implementation class is SiteRegistrationServiceImpl.class. The URL for the resulting webservice is http://127.0.0.1:8080/SiteRegistrationServiceImplService/SiteRegistrationServiceImpl?wsdl I am using Jboss 4.2.0 GA. I would like the URL of the Service to be "http://127.0.0.1:8080/SiteRegistration/SiteRegistrationService?wsdl" Is there a way to specify this? -Rahul View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052301#4052301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052301 From do-not-reply at jboss.com Thu Jun 7 17:03:40 2007 From: do-not-reply at jboss.com (jopere) Date: Thu, 7 Jun 2007 17:03:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Duplicate SOAP body/envelope tags in SOAP message Message-ID: <17020744.1181250220043.JavaMail.jboss@colo-br-02.atl.jboss.com> I succeeded in calling a web service, from a web service. However, I'd really like someone out there who knows what they are doing to show me how to do this correctly. I am sure there is a better way than what I did. This is how I got it to work: 1. Create web service B as a stateless session bean web service using wstools to create artifacts (ejb 2.1). Deployed web service. 2. Create web service A as a stateless session bean using wscompile to generate web service artifacts. Copied WSDL from web service B and used wscompile to create client artifacts. However, I don't ever use the generated stub/service/serializer classes, because when I do, I get a SOAP message with duplicate body/envelope tags. What I do is create my own SOAP message using a SOAPMessageFactory. Then I added namespacese, attributes and elements to the message so it complies with the WSDL. Next I create a connection and call the web service. When the message returns I parse it, retrieve the return value and pass it back to the client. 3. Create a web client that calls web service A. Web service A calls web service B, which returns a value to A, which returns a value to the client. So, web service A is both a server to the web client and a client to web service B. Web service A recieves the SOAP message from the web client and immediately calls web service B. Here is the code in web service A that calls web service B: SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance(); SOAPConnection connection = scf.createConnection(); MessageFactory msgFactory = MessageFactory.newInstance(); // Create a message SOAPMessage msg = msgFactory.createMessage(); // Create an envelope in the message SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope(); // Bind ns0 namespace envelope.addNamespaceDeclaration("ns0","http://aaa/bbb/1.0"); // Get hold of the the body SOAPBody body = envelope.getBody(); body.addChildElement(envelope.createName("ns0:getGreeting", "", "")) .addAttribute(envelope.createName("ns0"), "http://aaa/bbb/1.0"); URL endpoint = new URL("http://localhost:8082/ws/getGreeting"); msg.saveChanges(); // Make call to web service SOAPMessage soapMessage = connection.call(msg, "http://localhost:8082/ws/getGreeting"); soapMessage.writeTo(System.out); // The return value is in the grandchild element to the body tag. Iterator it = soapMessage.getSOAPBody().getChildElements(); SOAPElement child = it.next(); Iterator it2 = child.getChildElements(); SOAPElement result = it2.next(); responseMessage = result.getValue(); As I said, there has to be an easier way to do this. If someone could show me a simpler way to call a web service from a web service, I'd appreciate it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052309#4052309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052309 From do-not-reply at jboss.com Thu Jun 7 17:47:16 2007 From: do-not-reply at jboss.com (kimbaltrue) Date: Thu, 7 Jun 2007 17:47:16 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.UnsupportedOperationException when connecting Message-ID: <10925618.1181252836265.JavaMail.jboss@colo-br-02.atl.jboss.com> The JSE 6 Annotations use the XmlAccessType Enumeration as a property in the XmlAccessorType annotation, but the JWSDP 2 uses AccessType instead. Somebody did a rename of the class in the JSE 6 release so I'm not surprised if it fails. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052333#4052333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052333 From do-not-reply at jboss.com Fri Jun 8 04:31:35 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Fri, 8 Jun 2007 04:31:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problem calling webservice from client Message-ID: <25856668.1181291495622.JavaMail.jboss@colo-br-02.atl.jboss.com> i could solve the problem adding a pluging to eclipse to show wsdl files. I was calling an url incorrect. Now the client connect to jboss and execute a simple webservice echo, but my service to login crashes, with a error i can`t undestand. The client connects the administration server (jboss) and when i print what is it doing, it prints corrects values and it returns the correct loginVO object, but when it returns to the client i receive the next exception from jboss: | 2007-06-08 10:13:10,821 ERROR [org.jboss.ws.core.server.AbstractServiceEndpointServlet] Error processing web service request | javax.xml.ws.WebServiceException: javax.xml.bind.MarshalException | - with linked exception: | [javax.xml.bind.JAXBException: com.satdatatelecom.satdataweb.model.permiso.vo.ConcesionVO nor any of its super class is known to this context] | at org.jboss.ws.core.jaxws.JAXBSerializer.handleMarshallException(JAXBSerializer.java:109) | at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:89) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052441#4052441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052441 From do-not-reply at jboss.com Fri Jun 8 05:12:41 2007 From: do-not-reply at jboss.com (soofka) Date: Fri, 8 Jun 2007 05:12:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Exceptions in WS - how to remove stack trace from Jboss cons Message-ID: <18899116.1181293961210.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a small issue concerning exceptions throwing in jboss Web Services. Normal exceptions, which are to be caught by service invoker, are also displayed in Jboss console - with whole stack trace. This behaviour makes Jboss log grow vfast. Is there a way to exclude selected exceptions from being displayed in the console? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052454#4052454 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052454 From do-not-reply at jboss.com Fri Jun 8 05:50:20 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Fri, 8 Jun 2007 05:50:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem with exceptions Message-ID: <14795385.1181296220379.JavaMail.jboss@colo-br-02.atl.jboss.com> i am running jboss 4.2 with jbossws. I have two service methods. they work fine if i don't declare the exceptions throwed by them. if i add exceptions to the methods, when i execute the client side it askes my for the the exceptions throwed but with the sufix "bean" and it crashes because the client can't find the classes with that prefix. What can i do? | Exception in thread "Thread-39" class: com.satdatatelecom.satdataweb.model.session.session.jaxws.PalabraProhibidaExceptionBean could not be found | at com.sun.xml.internal.ws.modeler.RuntimeModeler.getClass(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processExceptions(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processRpcMethod(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processMethod(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.processClass(Unknown Source) | at com.sun.xml.internal.ws.modeler.RuntimeModeler.buildRuntimeModel(Unknown Source) | at com.sun.xml.internal.ws.client.ServiceContextBuilder.processAnnotations(Unknown Source) | at com.sun.xml.internal.ws.client.ServiceContextBuilder.completeServiceContext(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.processServiceContext(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(Unknown Source) | at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source) | at javax.xml.ws.Service.getPort(Unknown Source) | at com.satdatatelecom.satdataweb.gui.login.DoLogin.doLogin(DoLogin.java:212) | at com.satdatatelecom.satdataweb.gui.login.thread.LoginThread.run(LoginThread.java:90) | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052475#4052475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052475 From do-not-reply at jboss.com Fri Jun 8 09:28:44 2007 From: do-not-reply at jboss.com (jopere) Date: Fri, 8 Jun 2007 09:28:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How is the service URL constructed Message-ID: <10738917.1181309324095.JavaMail.jboss@colo-br-02.atl.jboss.com> In general, the context-root of the web service will be the name of the jar file the stateless bean is deployed in. So change the name of the jar file and the context-root of the web service is changed accordingly. in general, the alias portion is determined by the name of the ejb in the ejb-jar.xml file. Change the name here, and make sure that webservices.xml references it correctly and it will change the alias of the web service. http://somehost/context-root/alias John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052575#4052575 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052575 From do-not-reply at jboss.com Fri Jun 8 10:24:20 2007 From: do-not-reply at jboss.com (bigdaddy66) Date: Fri, 8 Jun 2007 10:24:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS with JBoss 4.2.0 and Axis 1.4 don't work with WS Message-ID: <31988008.1181312660343.JavaMail.jboss@colo-br-02.atl.jboss.com> noone? what is the failure? i don't think it is an axis-problem - or? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052601#4052601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052601 From do-not-reply at jboss.com Fri Jun 8 11:23:26 2007 From: do-not-reply at jboss.com (johnefranklin@yahoo.com) Date: Fri, 8 Jun 2007 11:23:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wstools exception in jboss4.2 Message-ID: <21204963.1181316206268.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am attaching a wsdl that used to work nicely with JBoss 4.0.5. But when I try to generate the java files from the wsdl using the wstools shipped along with JBoss 4.2, it keeps giving me this error. Exception in thread "main" org.jboss.ws.WSException: [JAX-RPC 2.3.1.2] Unable to unwrap model group with multiple particles. at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrapModelGroup(ReturnTypeUnwrapper.java:120) at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrap(ReturnTypeUnwrapper.java:87) at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:632) at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:395) at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:290) at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:588) at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:618) at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:186) at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:303) at org.jboss.ws.tools.WSTools.process(WSTools.java:137) at org.jboss.ws.tools.WSTools.generate(WSTools.java:69) at org.jboss.ws.tools.WSTools.generate(WSTools.java:119) at org.jboss.ws.tools.WSTools.main(WSTools.java:58) Can someone please look at the wsdl and point me the problem in the wsdl? regards, johnf | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052646#4052646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052646 From do-not-reply at jboss.com Fri Jun 8 13:19:50 2007 From: do-not-reply at jboss.com (hartsock) Date: Fri, 8 Jun 2007 13:19:50 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBossWS, Portlets, JAAS and Multiple JBoss Application Serve Message-ID: <16133933.1181323190567.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm just starting in on a new project. I have been directed to create a SOAP service that will be consumed by a Portlet. The portal server is on a physically separate server from the JBoss EJB3/SOAP server. What I want to do is to take the Authenticated Principal from the Portal and pass it back to the server running the SOAP services. How would I do this? I assume that JAAS plays a role and the secret is in a properly configured realm. The documentation I have assumes the SOAP and Portal programs are on the same server... but these programs are on physically different servers. I can see this being a problem if I have to coordinate authentication between multiple SOAP servers which I know many shops must have to do. So, I figure there must be a straight forward solution that I'm not finding in the JBoss wiki, the JBoss text books I have, or the other training materials. I'm trying to answer this security question before I start writing application code. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052678#4052678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052678 From do-not-reply at jboss.com Fri Jun 8 14:01:49 2007 From: do-not-reply at jboss.com (rphadnis) Date: Fri, 8 Jun 2007 14:01:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How is the service URL constructed Message-ID: <3927964.1181325709486.JavaMail.jboss@colo-br-02.atl.jboss.com> I am not seeing that. The name of the ejb jar file is "sitereg-ejb-1.0-SNAPSHOT.jar" and the name of ear file is "SiteRegistrationService-1.0-SNAPSHOT.ear". Also I am using JAX-WS and EJB3. So I don't have ejb-jar.xml and webservices.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052685#4052685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052685 From do-not-reply at jboss.com Fri Jun 8 15:59:33 2007 From: do-not-reply at jboss.com (jopere) Date: Fri, 8 Jun 2007 15:59:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How is the service URL constructed Message-ID: <2190860.1181332773597.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry, forget all I said in my first post. To set the context root include jboss.xml in your jar file with the following inside it: xxxx The alias portion should be the name of the endpoint class. So if your endpoint class is named yyyy.java, then your web service url will be: http://somehost/xxxx/yyyy I don't know of a way to change the alias portion from being the name of the endpoint class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052732#4052732 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052732 From do-not-reply at jboss.com Fri Jun 8 16:21:32 2007 From: do-not-reply at jboss.com (mpipes) Date: Fri, 8 Jun 2007 16:21:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - upgrade from 4.01 SP1 to 4.05 Message-ID: <17985959.1181334092091.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello - I have atleast 10 webservices that was developed using the Axis style webservices. Now I want to updgrade to the latest version of jboss to take advantage of JBossWS. Does any you know of an easy way to upgrade? Thanks, Mike View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052738#4052738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052738 From do-not-reply at jboss.com Fri Jun 8 17:03:29 2007 From: do-not-reply at jboss.com (tballerstein) Date: Fri, 8 Jun 2007 17:03:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem with String Array in WSDL generated in 4.0.5GA Message-ID: <32307334.1181336609592.JavaMail.jboss@colo-br-02.atl.jboss.com> I am new to JBoss and deploying web services. I am trying to convert are old web services from ATG Platform to JBOSS 4.0.5GA. I have eveything converted to work with JBoss. I have a couple of services deployed and work properly. However I have a couple of services that do not work because one of the datatypes in the object that is being passed is a string array. When the array is passed to the server the array is null. I looked at the wsdl generated and it seems that wsdl generated did not recognize the string array. Here is the part of the wsdl. Entries is my String Array. element maxOccurs="unbounded" minOccurs="0" name="entries" nillable="true" type="string" When I deployed the service I simply deployed the jar file I did not actually create the wsdl file using wstools. I let Jboss deploy and generate the wsdl file. How can I fix this problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052747#4052747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052747 From do-not-reply at jboss.com Fri Jun 8 17:35:05 2007 From: do-not-reply at jboss.com (gryffin) Date: Fri, 8 Jun 2007 17:35:05 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem marshalling data from a List Message-ID: <12709867.1181338505410.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a problem sending a list of item to a client. I send an object, which contains a member that itself stores a list of device objects. These objects store a member that is either a tag or a network device. ( I don't get to define the WSDL or Schema. ) I confirm that my List object does store a collection of devices which each in turn have a tag. | 13:58:54,126 DEBUG [AssociationValuesDAO] Device.deviceList: | [com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 18a5d49, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at f2a0ef, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 123b9c1, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 786e16, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 838143, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 19b7dfa, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 16bb63e, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 89e0c6, | com.boeing.nmt.types.DeviceData$Device$AeroScoutTag at 3fcfb] | I send this across the wire ( server and client are local ). I unpack it and everything works great Until I try to access the tags inside the device objects in the List. They're NULL. | [java] device list: [com.boeing.nmt.client.ws.DeviceData$Device at 102a0a5, com.boeing.nmt.client. | ws.DeviceData$Device at 180b22e, com.boeing.nmt.client.ws.DeviceData$Device at 31fb31, com.boeing.nmt.clie | nt.ws.DeviceData$Device at 162522b, com.boeing.nmt.client.ws.DeviceData$Device at 89dd, com.boeing.nmt.cli | ent.ws.DeviceData$Device at 15b1773, com.boeing.nmt.client.ws.DeviceData$Device at 160bf50, com.boeing.nmt | .client.ws.DeviceData$Device at b05236, com.boeing.nmt.client.ws.DeviceData$Device at 1e55794] | [java] device list size: 9 | [java] dev[1]: com.boeing.nmt.client.ws.DeviceData$Device at 102a0a5 | [java] Exception! java.lang.NullPointerException | I trigger the exception this way: | List devList = aagr.getAssociationValues().getDeviceData().getDevice(); | System.out.println("device list: " + devList.toString() ); | System.out.println("device list size: " + devList.size() ); | // devList.toArray()[0] is a DeviceData.Device.Tag object, for whatever reason, it's NULL | System.out.println("dev[1]: " + devList.toArray()[0].toString()); | System.out.println("dev[1]: " + ((DeviceData.Device)devList.toArray()[0]).toString()); | I look back at the logs to see what JBoss is unmarshalling, and it looks fine. 2007-06-08 13:58:54,158 DEBUG [org.jboss.ws.core.soap.ObjectContent] xmlFragment: [source= | | | true | Dumb luck | | | | | Unknown | | | ... | | | gah | fah | true | | | | ] | 2007-06-08 13:58:54,158 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- | 2007-06-08 13:58:54,220 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 131a24c (Thread http-0.0.0.0-8080-2) I'm using JBoss 4.0.5 w/ JBossWS 1.2.0. Does anyone have an idea what am I missing? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052753#4052753 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052753 From do-not-reply at jboss.com Sat Jun 9 23:39:50 2007 From: do-not-reply at jboss.com (sdjn5337) Date: Sat, 9 Jun 2007 23:39:50 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How to use the examples? Message-ID: <33512158.1181446790666.JavaMail.jboss@colo-br-02.atl.jboss.com> I download the example from the web,when I deploy it.It always occurs error.Could someone tell me how to use the example step by step?Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052866#4052866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052866 From do-not-reply at jboss.com Sun Jun 10 12:44:59 2007 From: do-not-reply at jboss.com (lavrenych) Date: Sun, 10 Jun 2007 12:44:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WebMethod with name Message-ID: <6237587.1181493899336.JavaMail.jboss@colo-br-02.atl.jboss.com> I have method with name "Update" in my WebService class and unable to deploy it. Once I rename it ( "Update1"?), everything runs fine. More info: I am getting when deploying: 2007-06-10 12:22:39,409 ERROR [org.jboss.ws.core.server.ServiceEndpointDeployer] Cannot start service endpoint org.jboss.ws.WSException: param1 is not a valid property on class com.newxt.ws.jaxws.Update at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccesso r(JAXBContextImpl.java:816) For this class: package com.newxt.ws; import javax.jws.WebMethod; import javax.jws.WebParam; import javax.jws.WebService; @WebService public class Echo { @WebMethod public String echo(String input) { return input; } @WebMethod public String Update( @WebParam (name="param1") String param1) { return param1; } } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052920#4052920 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052920 From do-not-reply at jboss.com Sun Jun 10 15:30:10 2007 From: do-not-reply at jboss.com (PeterJ) Date: Sun, 10 Jun 2007 15:30:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How to use the examples? Message-ID: <16445229.1181503810057.JavaMail.jboss@colo-br-02.atl.jboss.com> What example? What error? How can we help you solve your problem if you do not tell us what your problem is? Also include: * the version of JBoss App Server * the version of JBossWS * the version of the JDK View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052943#4052943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052943 From do-not-reply at jboss.com Mon Jun 11 06:49:41 2007 From: do-not-reply at jboss.com (teknokrat) Date: Mon, 11 Jun 2007 06:49:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: ant task produces java.lang.NoClassDefFoundError: com/s Message-ID: <12995957.1181558981361.JavaMail.jboss@colo-br-02.atl.jboss.com> The relevant build.xml fragment is | | | | | | | | | | | | | | | | | When I add tools.jar to the classpath, this works OK. But why can't it find tools.jar anyway as its being executed by the jvm anyway? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053036#4053036 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053036 From do-not-reply at jboss.com Mon Jun 11 10:31:12 2007 From: do-not-reply at jboss.com (xiaozhang51) Date: Mon, 11 Jun 2007 10:31:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle webservices on JBossWS Message-ID: <22450486.1181572272632.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Pekka, Praveen I'm having exactly same problem when i try to deploy a webservice from JDeveloper to JBoss. Did you solve this problem?. thanks Tommy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053122#4053122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053122 From do-not-reply at jboss.com Mon Jun 11 11:52:32 2007 From: do-not-reply at jboss.com (evdelst) Date: Mon, 11 Jun 2007 11:52:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Getting Message-ID: <15589048.1181577152214.JavaMail.jboss@colo-br-02.atl.jboss.com> Same errors for me. I extraced the javax.annotation package from the mentioned jar file and put them in a new jar. Place that in 'server/default/lib' and it works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053166#4053166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053166 From do-not-reply at jboss.com Mon Jun 11 12:15:29 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Mon, 11 Jun 2007 12:15:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS and .NET client Message-ID: <13020687.1181578529589.JavaMail.jboss@colo-br-02.atl.jboss.com> It's actually a client-side error. The wsa:Action header is not set. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053179#4053179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053179 From do-not-reply at jboss.com Mon Jun 11 12:18:06 2007 From: do-not-reply at jboss.com (carlosmot) Date: Mon, 11 Jun 2007 12:18:06 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Two days trying install JbossWS=losing time Message-ID: <23746338.1181578686906.JavaMail.jboss@colo-br-02.atl.jboss.com> I have been two days trying to install XXX and I am lost the time, I have had conflict of versions, manual not updated, jar's missing... sorry but I am fustrated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053184#4053184 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053184 From drf at blackchairdvd.com Mon Jun 11 12:38:57 2007 From: drf at blackchairdvd.com (Douglas Fraser) Date: Mon, 11 Jun 2007 17:38:57 +0100 Subject: [jbossws-users] [JBossWS] - Two days trying install JbossWS=losing time In-Reply-To: <23746338.1181578686906.JavaMail.jboss@colo-br-02.atl.jboss.com> References: <23746338.1181578686906.JavaMail.jboss@colo-br-02.atl.jboss.com> Message-ID: <466D7AA1.4070607@blackchairdvd.com> Welcome to JBoss! :) To be fair, dealing with JBossWS 1.2.1 went fine for me - the ant task helped greatly (compared to the angst I had with older versions) I've gotten things running fine, though JBossWS seems to be very picky in what sort of SOAP messages it accepts (some issue with where and how namespaces are defined in the SOAP message - right now the MessageHandler I wrote can not print the raw XML out as it complains, but the web service processes the message fine) But it is not a showstopper, things work, so I have other work to do.... as for you, you don't mention any specific issue or exactly what you are doing, so I am lost as to what sort of advice I could give doug carlosmot wrote: > I have been two days trying to install XXX and I am lost the time, I have had conflict of versions, manual not updated, jar's missing... > sorry but I am fustrated. > > View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053184#4053184 > > Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053184 > _______________________________________________ > jbossws-users mailing list > jbossws-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossws-users > > > > From do-not-reply at jboss.com Mon Jun 11 12:55:59 2007 From: do-not-reply at jboss.com (sagneta) Date: Mon, 11 Jun 2007 12:55:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - soap:address location using HOSTNAME rather than IP address Message-ID: <8377560.1181580959695.JavaMail.jboss@colo-br-02.atl.jboss.com> Currently I am using JBoss 4.0.4 and using @WebMethod on EJB 2.0 Session Beans to provide SOAP access to various public methods. Everything works fine except that the soap:address location URL contains the actual hostname rather than the IP address. I unfortunately require the IP address as many customers lack decent DNS support, sometimes for security reason. In any event, JBoss produces WSDL with the following snippet at the end: - Notice the sagneta-bos hostname? I need that to be an IP address. I cannot determine from the documentation how to make the JBoss server produce a WSDL XML document that produces an address location URL that uses the IP address rather than the HOST name. It appears that jboss.bind.address is always used. Any help would be appreciated. Thank you, Stephen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053199#4053199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053199 From do-not-reply at jboss.com Mon Jun 11 13:50:42 2007 From: do-not-reply at jboss.com (PeterJ) Date: Mon, 11 Jun 2007 13:50:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Two days trying install JbossWS=losing time Message-ID: <8725409.1181584242491.JavaMail.jboss@colo-br-02.atl.jboss.com> I have installed various different versions of JBossWS on various different versions of JBossAS on different operating systems. It has always taken only a few minutes and has always worked. Note that I am not offering to help for two reasons. First, you didn't ask for help. Second, you provided no information about what problems you have run into - it is impossible to solve problems without knowing what the problems are. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053229#4053229 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053229 From do-not-reply at jboss.com Mon Jun 11 16:39:18 2007 From: do-not-reply at jboss.com (rphadnis) Date: Mon, 11 Jun 2007 16:39:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebMethod with name Message-ID: <30345782.1181594358294.JavaMail.jboss@colo-br-02.atl.jboss.com> Are you doing top down development (starting with WSDL) or bottom up development (starting with service implementation)? There may not be an "update" method in your WSDL ? Or the input request may not have a param1 defined. The stack trace does seem to indicate that the Update java object does not have a field named "param1" or the associated setters and getters are missing. Rahul View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053274#4053274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053274 From do-not-reply at jboss.com Mon Jun 11 16:59:49 2007 From: do-not-reply at jboss.com (lavrenych) Date: Mon, 11 Jun 2007 16:59:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebMethod with name Message-ID: <29765650.1181595589848.JavaMail.jboss@colo-br-02.atl.jboss.com> I am doing bottom up development (starting with service implementation), so everything should work. This is very strange, because, like I said, just renaming method name in java source code solves the problem. Just wondering, what are the other "prohibited" method names... I am using jboss 4.0.5.GA and JbossWS 1.2.1. Here is my web.xml (nothing surprising, but just in case): Echo com.newxt.ws.Echo Echo /Echo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053277#4053277 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053277 From do-not-reply at jboss.com Tue Jun 12 04:27:13 2007 From: do-not-reply at jboss.com (sonicfab) Date: Tue, 12 Jun 2007 04:27:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - level of J2EE required by JBossWS Message-ID: <13120518.1181636833682.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi. I see on the Wiki (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWSSpecStatus) that JBossWS require J2EE 5 for HTTP, SOAP and JAX-RPC support. I also read on the JBossWS FAQ that JBossWS runs on JBoss AS 4.0.4, which to my knowledge is at the J2EE 1.4 level. I'm a bit puzzled. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053381#4053381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053381 From do-not-reply at jboss.com Tue Jun 12 06:38:22 2007 From: do-not-reply at jboss.com (purohitvinod) Date: Tue, 12 Jun 2007 06:38:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: ws-security: Problem using encryption Message-ID: <16145496.1181644702880.JavaMail.jboss@colo-br-02.atl.jboss.com> Me too facing the same problem with the encryption in JbossWS 1.0.4 with JBoss 4.0.5 app server But i observed one thing, i,e. Encryption and Signature both work fine with JSR-181 types in JBossWS 1.2.x. Any clues on how to make this work for JSR-109 EJBs? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053439#4053439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053439 From do-not-reply at jboss.com Tue Jun 12 07:40:21 2007 From: do-not-reply at jboss.com (purohitvinod) Date: Tue, 12 Jun 2007 07:40:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How to configuring WS-Security for JSR-109 EJBs? Message-ID: <15978217.1181648421433.JavaMail.jboss@colo-br-02.atl.jboss.com> Currently i am working on a project which uses JBoss 4.0.5 as the app server with JBossWS 1.0.4 as web service archive. I want to configure WS-Security for JSR-109 EJBs and write a client for the same? Can some one help me out, how to do the same? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053471#4053471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053471 From do-not-reply at jboss.com Tue Jun 12 08:03:41 2007 From: do-not-reply at jboss.com (o66183) Date: Tue, 12 Jun 2007 08:03:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Installing problems WS with JBoss 4.05 and EJB3 Message-ID: <11939132.1181649821653.JavaMail.jboss@colo-br-02.atl.jboss.com> 13:08:35,796 ERROR [ServiceEndpointDeployer] Cannot create service endpoint java.lang.ClassCastException: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5 at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170) at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:59) at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:39) at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40) at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189) at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56) at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33) at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22) at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15) at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38) at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41) at java.util.AbstractList$Itr.next(Unknown Source) at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40) at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189) at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:217) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:76) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:875) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMet Builder.java:128) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataB View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053480#4053480 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053480 From do-not-reply at jboss.com Tue Jun 12 08:49:33 2007 From: do-not-reply at jboss.com (shaiknoor_basha) Date: Tue, 12 Jun 2007 08:49:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: soap:address location using HOSTNAME rather than IP addr Message-ID: <25264997.1181652573844.JavaMail.jboss@colo-br-02.atl.jboss.com> hi dont worry, i have a solution for your problem there are two ways to solve this problem i). u need to start your jboss server with this command on command prompt %JBoss_home%\bin>run.bat -b ii).the second way is find jboss-server.xml in jboss installer foler(Jboss_Home) then in that file(s) replace the ${binding-address} to then start the jboss server normaly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053513#4053513 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053513 From do-not-reply at jboss.com Tue Jun 12 08:50:41 2007 From: do-not-reply at jboss.com (shaiknoor_basha) Date: Tue, 12 Jun 2007 08:50:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: soap:address location using HOSTNAME rather than IP addr Message-ID: <21058510.1181652641613.JavaMail.jboss@colo-br-02.atl.jboss.com> hi dont worry, i have a solution for your problem there are two ways to solve this problem i). u need to start your jboss server with this command on command prompt %JBoss_home%\bin>run.bat -b Ex: run.bat -b 192.234.145.232 ii).the second way is find jboss-server.xml in jboss installer foler(Jboss_Home) then in that file(s) replace the ${binding-address} to then start the jboss server normaly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053514#4053514 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053514 From do-not-reply at jboss.com Tue Jun 12 10:21:45 2007 From: do-not-reply at jboss.com (Maffewl) Date: Tue, 12 Jun 2007 10:21:45 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - 'uniqueness constraint violation' when running wsconsume on Message-ID: <2658331.1181658105824.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, I've been able to deploy a webservice in JBossWS based on a WSDL that I had made running under jboss-net/axis. I used WSConsume and the Top-Down approach to arrive at this point. When i attepmt to use wsconsume on the deployed wsdl, I get errors talking about a uniqueness constraint violation anonymous wrote : | uniqueness constraint violation | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:213) | at org.jboss.com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:88) | at org.jboss.com.sun.tools.ws.processor.Processor.runModeler(Processor.java:82) | at org.jboss.com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:543) | at org.jboss.com.sun.tools.ws.util.ToolBase.run(ToolBase.java:57) | at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl$1.run(WSContractConsumerImpl.java:163) | at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl.consume(WSContractConsumerImpl.java:166) | at org.jboss.ws.tools.jaxws.command.wsconsume.importServices(wsconsume.java:193) | at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:76) | Caused by: uniqueness constraint violation | at org.jboss.com.sun.tools.ws.processor.model.java.JavaMethod.addParameter(JavaMethod.java:76) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.createJavaMethodForOperation(WSDLModeler.java:2411) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.createJavaInterfaceForPort(WSDLModeler.java:2244) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processPort(WSDLModeler.java:536) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processService(WSDLModeler.java:289) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:258) | at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:181) | | then i get a big list of errors that look like this anonymous wrote : 17:03:27,104 ERROR [JBossXSErrorHandler] JBossWS_cls.chase.com_type17794.xsd[domain:http://www.w3.org/TR/xml-schema-1]::[key=sch-props-correct.2]::Message=sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://cls.chase.com/type,rewardsProgramAttributes'. | it seems to be for most of my properties, can anyone tell me why this happens? ive invluded a portion of the deployed wsdl that contains all the nodes that have the element in the example error message | | | | | ... | | | | | | | | | | | | | | ... | | | | | | | | | | | | | | | | | | | | | | | ... | | | | | | | | ... | | | | | ... | | | thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053576#4053576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053576 From do-not-reply at jboss.com Tue Jun 12 11:27:40 2007 From: do-not-reply at jboss.com (Maffewl) Date: Tue, 12 Jun 2007 11:27:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: 'uniqueness constraint violation' when running wsconsume Message-ID: <29875809.1181662060552.JavaMail.jboss@colo-br-02.atl.jboss.com> Ive figured out that the Uniqueness Constraint Violation comes from a message with a part name the same. reference : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4731699 just as a test i changed the name attribute and got around this error. but when I wsrunclient on the client tester i still see the 'A schema cannot contain two global components with the same name' error any thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053619#4053619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053619 From do-not-reply at jboss.com Tue Jun 12 11:30:37 2007 From: do-not-reply at jboss.com (PeterJ) Date: Tue, 12 Jun 2007 11:30:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Installing problems WS with JBoss 4.05 and EJB3 Message-ID: <11869985.1181662237715.JavaMail.jboss@colo-br-02.atl.jboss.com> Are you running JDK 6 by any chance? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053620#4053620 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053620 From do-not-reply at jboss.com Tue Jun 12 12:24:56 2007 From: do-not-reply at jboss.com (carlosmot) Date: Tue, 12 Jun 2007 12:24:56 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Error installing JBossWS with Eclipse + Jboss 4.2 Message-ID: <9528023.1181665496065.JavaMail.jboss@colo-br-02.atl.jboss.com> I have this problem when I try to publish a POJO as web service without annontations: NoClassDefFoundError: javax/xml/rpc/encoding/TypeMapping My configuration is below: Clean wmware image with Windows XP SP2, JDK 1.5.0_11, JWSDP 2.0 and Eclipse downloaded from your site file name: "JBossIDE-2.0.0.Beta2-Bundle-win32.zip" and JBossWS donwloaded from your site file name:"jbossws-1.2.1.GA.zip" and a JBoss server downloaded from your site, file name: "jboss-4.2.0.GA.zip" and Ant 1.70. The system variables: JAVA_HOME, JBOSS_HOME, JWSDP_HOME and ANT_HOME are all OK. My Installation procedure are: I decompress jboss-4.2.0.GA.zip into "c:\jboss-4.2.0.GA" I decompress jbossws-1.2.1.GA.zip into "c:\jbossws" I decompress JBossIDE-2.0.0.Beta2-Bundle-win32.zip into "c:\eclipse" I put JWSDP into JWSDP 2.0 into C:\jwsdp-2.0 ...................................................................................... Into c:\jbossws I rename ant.properties.example in "ant.properties" I also modify "ant.properties" and uncomment the line below: jboss42.home=c:/jboss-4.2.0.GA I launch Ant from a console as below: ant deploy-jboss42 All is ok and Ant says build succesfully------ I test the JBoss installation with "http://localhost:8080/jbossws" and the page appears correctly. .................................................................................... Well, now I launch Eclipse, and I set the properties from Preferences>JBoss Eclipse IDE>JBoss WS>Integrated tools>JBoss WS wstools to: C:\jboss-4.2.0.GA\bin Preferences>JBoss Eclipse IDE>JBoss WS>Integrated tools>JAXB XJC to: C:\jwsdp-2.0\jaxb I leave the rest in blank. ------------------------------------------------------------------- Now I create a Java Project whit 1 interface and 1 class with the code of your documentation: IHelloWorld & HelloWorld without changes. When mouse's rigth button add a JBossws nature to the project and I accept the defualt values. Selecting HelloWorld I clic under JBOSSWS>Publish as Web Service and Eclipse says: Running JBossWS wstools for [ProyectoWS] directory: C:\Documents and Settings\Administrador\workspace\ProyectoWS command: cmd.exe /C C:\jboss-4.2.0.GA\bin\wstools.bat -cp /ProyectoWS -config C:\DOCUME~1\Alumno\CONFIG~1\Temp\wstools-config30423.xml -dest C:\Documents and Settings\Administrador\workspace\ProyectoWS\ProyectoWS =========================================================================" . WSTools Environment . JBOSS_HOME: C:\jboss-4.2.0.GA\bin\\.. . JAVA: C:\Archivos de programa\Java\jdk1.5.0_11\bin\java . JAVA_OPTS: . =========================================================================" . Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/rpc/encoding/TypeMapping at org.jboss.ws.tools.WSTools.process(WSTools.java:130) at org.jboss.ws.tools.WSTools.generate(WSTools.java:69) at org.jboss.ws.tools.WSTools.generate(WSTools.java:119) at org.jboss.ws.tools.WSTools.main(WSTools.java:58) ---------------------------------------------------------------------------- Thanks advanced for your patience and cooperation, sorry for my last post... ..Carlos.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053646#4053646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053646 From do-not-reply at jboss.com Tue Jun 12 13:54:50 2007 From: do-not-reply at jboss.com (Maffewl) Date: Tue, 12 Jun 2007 13:54:50 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: 'uniqueness constraint violation' when running wsconsume Message-ID: <9934082.1181670890138.JavaMail.jboss@colo-br-02.atl.jboss.com> It seems like i was getting the : A schema cannot contain two global components with the same name error because in my wsdl i was declaring 2 that each included an referencing the same xml file, thus trying to include the same file twice. I moved the include calls to the wsdl and am not seeing this error anymore. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053680#4053680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053680 From do-not-reply at jboss.com Tue Jun 12 15:03:28 2007 From: do-not-reply at jboss.com (claudio_br) Date: Tue, 12 Jun 2007 15:03:28 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem with charset UTF-8 in version 1.2.1GA Message-ID: <17301341.1181675008617.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using wsconsume to generate webservice client class in windows machine. When I access the webservice and send a String with character '?' or '?' for example, I got a soap exception. In post http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030510#4030510 was relate same problem. A possible solution is use in jvm parameter -Dfile.encoding=UTF-8. But this affects everything in jvm. I tried to use System.setProperty("file.encoding","UTF-8") before the call webservice, but don?t work, I think a problem with classloader. Am I correct? There is a way of setting the enconding only in soap message without setting system property? Is it a bug with jbossws? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053701#4053701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053701 From do-not-reply at jboss.com Wed Jun 13 03:14:17 2007 From: do-not-reply at jboss.com (jghallen) Date: Wed, 13 Jun 2007 03:14:17 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: soap:address location using HOSTNAME rather than IP addr Message-ID: <2897946.1181718857122.JavaMail.jboss@colo-br-02.atl.jboss.com> Imagine you have a multihomed host. How do you make one JBoss instance listen to both 10.10.10.1 and 127.0.0.1 and a second JBoss instance listen to 10.10.10.2? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053814#4053814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053814 From Ralf.Duvenage at lds.nrw.de Wed Jun 13 04:45:26 2007 From: Ralf.Duvenage at lds.nrw.de (Duvenage, Ralf (LDS)) Date: Wed, 13 Jun 2007 10:45:26 +0200 Subject: [jbossws-users] SOAP : CORBA Message-ID: <5A8271EF2FC33242BCD04EDBC74F6BC8017716DA@lds421.lds.nrw.de> Hi list, does jboss come with some kind of ready to use adaptors for SOAP and CORBA? Need to be able to translate IDL to WSDL (vice versa) as well as synch/asynch messages SOAP <-> CORBA IIOP. thx 4 replies -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20070613/9b952e11/attachment.html From do-not-reply at jboss.com Wed Jun 13 04:54:48 2007 From: do-not-reply at jboss.com (sonicfab) Date: Wed, 13 Jun 2007 04:54:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: level of J2EE required by JBossWS Message-ID: <22965713.1181724888654.JavaMail.jboss@colo-br-02.atl.jboss.com> Can I get an answer on this please ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053858#4053858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053858 From do-not-reply at jboss.com Wed Jun 13 06:07:41 2007 From: do-not-reply at jboss.com (torbjornvatn) Date: Wed, 13 Jun 2007 06:07:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBossWS + VB .NET 1.x consumer Message-ID: <30752643.1181729261575.JavaMail.jboss@colo-br-02.atl.jboss.com> Has run into a problem with an external user of our JBossWS webservice. The external user is trying to use the WS from a VB .NET 1.x project. Our response xml contains elements like this: - which leads to problems because .NET 1.x does not support null Dates. We use this @SoapBinding settings: style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.BARE) Suggestions anyone? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053869#4053869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053869 From do-not-reply at jboss.com Wed Jun 13 07:25:52 2007 From: do-not-reply at jboss.com (bentzys) Date: Wed, 13 Jun 2007 07:25:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wsdl - meaningful URL issue Message-ID: <16901739.1181733952571.JavaMail.jboss@colo-br-02.atl.jboss.com> My setup is JBoss 4.0.5.GA + java 1.6 TomcatDeployer changes the wsdl placeholder REPLACE_WITH_ACTUAL_URL at deploy time. I tried to change it before the deploying and nothing helps. It's changed even the placeholder string is not there. I read at JBoss at Work that you can change it via jboss.xml, but we don't use EJBs. Also, I can't add proxyName at tomcat' server.xml because it cause other issues. I'm using jax-ws and not jbossws. Is there any way to force the wsdl to expose a meaningful URL? thanks in advance --bentzy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053894#4053894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053894 From do-not-reply at jboss.com Wed Jun 13 07:31:11 2007 From: do-not-reply at jboss.com (zauberlehrling) Date: Wed, 13 Jun 2007 07:31:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: asynchronous webservice posible with jboss ? Message-ID: <708324.1181734271952.JavaMail.jboss@colo-br-02.atl.jboss.com> I tried the following: package ws | | import javax.jws.Oneway; | import javax.jws.WebMethod; | import javax.jws.WebService; | import javax.ejb.Stateless; | | | @WebService | @Stateless | public class Hotel { | | @Oneway | @WebMethod | public void | reserve(String input) { | System.out.println("input: "+input); | for (int i =0; i < 60; i++) { | try { | Thread.sleep(1000); | } catch (InterruptedException e) { | e.printStackTrace(); | } | System.out.println("i: "+i); | } | } | } According to the JAX-WS User Guide it should be an asynchronous webservice because of the annotation @Oneway. But it's not. I've tested this JBoss-4.2.0.GA and jboss-5.0.0.Beta2. The call to this webservice is blocking. Any help is appreciated! Thanks in adavance for any help, Frank View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053896#4053896 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053896 From do-not-reply at jboss.com Wed Jun 13 13:53:46 2007 From: do-not-reply at jboss.com (hartsock) Date: Wed, 13 Jun 2007 13:53:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - [MainDeployer] Could not create deployment Message-ID: <9432823.1181757226819.JavaMail.jboss@colo-br-02.atl.jboss.com> I've been working along for several months on an EJB3 project in an archive I called tie.jar when I went to refactored a few class names. Now I suddenly get this error: | 13:43:19,144 INFO [Ejb3Deployment] EJB3 deployment time took: 102 | 13:43:19,231 ERROR [MainDeployer] Could not create deployment: file:/usr/local/jboss-4.2.0.GA/server/ejb3-jbpm/deploy/tie.jar | java.lang.NullPointerException | at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:578) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:332) | at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:273) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:127) | at org.jboss.ws.tools.schema.SchemaTypeCreator.createFieldParticle(SchemaTypeCreator.java:607) | at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:592) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:332) | at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:273) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:127) | at org.jboss.ws.tools.schema.SchemaTypeCreator.handleArray(SchemaTypeCreator.java:525) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:299) | at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:273) | at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132) | at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD.java:109) | at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:556) | at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:141) | at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:245) | at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:168) | at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318) | at org.jboss.ws.deployment.JSR181MetaDataBuilder.processOrGenerateWSDL(JSR181MetaDataBuilder.java:289) | at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:231) | at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75) | at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106) | at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80) | at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy29.create(Unknown Source) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | How do I even go about diagnosing this error? The tie.jar file deployed fine before the name changes and now even if I change the names back the deploy fails. If I use an old copy of the tie.jar in a JBoss server that the new deploy failed on the new jar fails until I stop the server, clear the working files, and restart it. My other EJB3 jar files are unaffected by the problem leading me to believe that this is a problem in my code not in the server configuration. I can't find where my code is causing the SchemaTypeCreator to fail out because there is no trace message about my class file structure at all. None of the classes from the tie.jar ... named tie.ClassName show up... how should I know which classes of mine are causing this issue? I suspect it is a change I made in the classes I refactored but I can't change the names back and get a working copy. Any ideas? Where do I even start? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054085#4054085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054085 From do-not-reply at jboss.com Wed Jun 13 14:26:39 2007 From: do-not-reply at jboss.com (hartsock) Date: Wed, 13 Jun 2007 14:26:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: [MainDeployer] Could not create deployment Message-ID: <16729206.1181759199309.JavaMail.jboss@colo-br-02.atl.jboss.com> Failed deploy looks like this: | | --- Incompletely deployed packages --- | org.jboss.deployment.DeploymentInfo at 54b9c43c { url=file:/usr/local/jboss-4.2.0.GA/server/webservices/deploy/tie.jar } | deployer: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer] | status: Deployment FAILED reason: null | state: FAILED | watch: file:/usr/local/jboss-4.2.0.GA/server/webservices/deploy/tie.jar | altDD: null | lastDeployed: 1181758704984 | lastModified: 1181758704000 | mbeans: | | Notice I've got "NULL" as my reason. Isn't that nice? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054093#4054093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054093 From do-not-reply at jboss.com Wed Jun 13 16:37:52 2007 From: do-not-reply at jboss.com (o66183) Date: Wed, 13 Jun 2007 16:37:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Installing problems WS with JBoss 4.05 and EJB3 Message-ID: <1916454.1181767072430.JavaMail.jboss@colo-br-02.atl.jboss.com> JDK5, the problem was that I haven't set the param annotation for a class method parameter. After I've set @WebParam it works. Nevertheless very strange error message :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054118#4054118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054118 From do-not-reply at jboss.com Wed Jun 13 16:41:07 2007 From: do-not-reply at jboss.com (o66183) Date: Wed, 13 Jun 2007 16:41:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Installing problems WS with JBoss 4.05 and EJB3 Message-ID: <28234109.1181767267953.JavaMail.jboss@colo-br-02.atl.jboss.com> JDK5, the problem was that I haven't set the param annotation for a class method parameter. After I've set @WebParam it works. Nevertheless very strange error message :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054120#4054120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054120 From do-not-reply at jboss.com Thu Jun 14 02:38:08 2007 From: do-not-reply at jboss.com (xiaozhang51) Date: Thu, 14 Jun 2007 02:38:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle webservices on JBossWS Message-ID: <31440136.1181803088443.JavaMail.jboss@colo-br-02.atl.jboss.com> help!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054199#4054199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054199 From do-not-reply at jboss.com Thu Jun 14 09:20:10 2007 From: do-not-reply at jboss.com (heiko.braun@jboss.com) Date: Thu, 14 Jun 2007 09:20:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WIKI users Message-ID: <9025319.1181827210347.JavaMail.jboss@colo-br-02.atl.jboss.com> Unfortunately we did have to delete a large number of WIKI users on jbws.dyndns.org due to a big spam bot invasion. It wasn't possible to identify everyone of you, so please bare with us and simply register for an account again. Thanks for your help, Heiko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054356#4054356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054356 From do-not-reply at jboss.com Thu Jun 14 10:51:40 2007 From: do-not-reply at jboss.com (sonicfab) Date: Thu, 14 Jun 2007 10:51:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: level of J2EE required by JBossWS Message-ID: <13940292.1181832700767.JavaMail.jboss@colo-br-02.atl.jboss.com> Strangely enough, I am not getting any answer to this question. Maybe it is stupid or badly worded. Let me put it another way then : what is the most recent version of JBossWS that I can use on a J2EE 1.4 compliant application server, such as JBoss 4 ? All I want to do is use SOAP 1.2 over http, document-style messages, and WS-Security with X.509 certificates. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054417#4054417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054417 From do-not-reply at jboss.com Fri Jun 15 08:32:58 2007 From: do-not-reply at jboss.com (gsferra@imnet.it) Date: Fri, 15 Jun 2007 08:32:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServiceRef injection does not work Message-ID: <22297674.1181910779013.JavaMail.jboss@colo-br-02.atl.jboss.com> anonymous wrote : | To me it look like the wsrunclient simply provides a classpath for simple (i.e. Service.create) invocations | I have problems with Service.create() too using JBoss 4.0.5GA, latest EJB3 and JBossWS packages. When I start my client I catch the following exception: | javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: Cannot obt | ain wsdl service: HelloService | at javax.xml.ws.Service.create(Service.java:731) | at com.imnet.oam.ws.HelloClient.(HelloClient.java:13) | at com.imnet.oam.ws.HelloClient.main(HelloClient.java:27) | Caused by: java.lang.IllegalArgumentException: Cannot obtain wsdl service: Hello | Service | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildM | etaDataInternal(JAXWSClientMetaDataBuilder.java:131) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildM | etaData(JAXWSClientMetaDataBuilder.java:85) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegat | eImpl.java:140) | at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(Provid | erImpl.java:61) | at javax.xml.ws.Service.(Service.java:83) | at org.jboss.ws.core.jaxws.client.ServiceExt.(ServiceExt.java:60) | at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) | | at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct | orAccessorImpl.java:39) | at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC | onstructorAccessorImpl.java:27) | at java.lang.reflect.Constructor.newInstance(Constructor.java:494) | at javax.xml.ws.Service.create(Service.java:726) | ... 2 more | This is the WSLD generated while deploying the EJB3 web service: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The client code follows: | package org.me.ws; | | import java.net.URL; | import javax.xml.namespace.QName; | import javax.xml.ws.Service; | | public class HelloClient { | private static final String SERVICE_NAME = "HelloService"; | private static final String WSDL_LOCATION = "http://mypc:8080/HelloService/HelloService?wsdl"; | private Service service; | | public HelloClient() throws Exception { | service = Service.create(new URL(WSDL_LOCATION), new QName(SERVICE_NAME)); | } | | public String getMessage() { | Hello hello = null; | | hello = service.getPort(Hello.class); | return hello.sayHello("Jim"); | } | | public static void main(String[] args) { | HelloClient client = null; | | try { | client = new HelloClient(); | System.out.println(client.getMessage()); | } catch (Throwable t) { | t.printStackTrace(); | } | } | } | and finally the service implementation class code follows: | package com.imnet.oam.ws; | | import javax.jws.*; | import javax.jws.soap.SOAPBinding; | import javax.ejb.Stateless; | | @Stateless | @WebService(name="Hello", targetNamespace="http://mypc:8080", serviceName="HelloService") | @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) | public class Hello { | private String message = new String("Hello, "); | | @WebMethod | public String sayHello(String name) { | return message + name + "."; | } | } | The WSDL file is easily accessible using the internet browser or throught the http://localhost:8080/jbossws/services links. I tried to call my service in many different way, changing it's name or targetName but the results are similar. Any ideas? Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054722#4054722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054722 From do-not-reply at jboss.com Fri Jun 15 10:47:36 2007 From: do-not-reply at jboss.com (J2EEUser) Date: Fri, 15 Jun 2007 10:47:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Deployment fails after upgrading from 4.0.3sp1 to 4.2.0.GA - Message-ID: <24871425.1181918856854.JavaMail.jboss@colo-br-02.atl.jboss.com> Our application was deploying and running on JBoss4.0.3.sp1 without any issues. I upgraded JBoss from 4.0.3sp1 to 4.2.0.GA. After that I am getting the following deployment error. Anybody had this issue? Any ideas? Thanks. =============== Exception: 2007-06-14 16:52:42,051 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/opt/nxtn/jboss-4.2.0.GA/server/default/tmp/deploy/tmp53419app.ear-contents/appweb.war org.jboss.deployment.DeploymentException: Cannot start service endpoint; - nested throwable: (org.jboss.ws.WSException: Element credential found in jaxrpc-mapping but not in the schema: null) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:101) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) ============== View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054785#4054785 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054785 From do-not-reply at jboss.com Fri Jun 15 11:07:30 2007 From: do-not-reply at jboss.com (sagneta) Date: Fri, 15 Jun 2007 11:07:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: soap:address location using HOSTNAME rather than IP addr Message-ID: <21413605.1181920050402.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the help everyone. That suggestion of binding to the IP address worked. I understand the multihomed issue of binding to specific IP addresses. I simply didn't know how to do it with JBoss. Thanks all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054803#4054803 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054803 From do-not-reply at jboss.com Fri Jun 15 13:46:21 2007 From: do-not-reply at jboss.com (gmills@wrha.mb.ca) Date: Fri, 15 Jun 2007 13:46:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: level of J2EE required by JBossWS Message-ID: <5908229.1181929581542.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm not surprised your not getting an answer, it is a simple straighforward question. I would suggest switch to Glassfish. This will meet all your requirements and if you run into problems you'll get better support. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054846#4054846 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054846 From do-not-reply at jboss.com Fri Jun 15 17:05:53 2007 From: do-not-reply at jboss.com (mmolnar) Date: Fri, 15 Jun 2007 17:05:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: when i restart jboss server web service is not starting Message-ID: <14813247.1181941553636.JavaMail.jboss@colo-br-02.atl.jboss.com> Probably this problem: http://jira.jboss.org/jira/browse/JBWS-1133 I ran into this myself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054895#4054895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054895 From do-not-reply at jboss.com Sun Jun 17 23:53:54 2007 From: do-not-reply at jboss.com (andrewv) Date: Sun, 17 Jun 2007 23:53:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Can I use JWSDP 1.6 tools and runtime with JBoss 4.0.5 GA ? Message-ID: <25913531.1182138834081.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am currently using JBoss AS 4.0.3SP1 and use (as a client), web services, whose WSDLs are compiled via wscompile in JWSDP 1.6. That works fine. Those WSDLs I use are supplied by a 3rd party, over whom I have no control, and who use the RPC encoded style extensively. I previously tried to use WSTools to compile the WSDLs, but had problems at runtime due to insufficient support for the RPC encoded style in the new JBoss WS SOAP stack. I need to move to 4.0.5 GA for a range of other reasons, and this is currently the stumbling block. It there any way I can retrofit the Sun JWSDP runtimes into JBoss 4.0.5 GA ? If so, are there any steps posted for this retrofit, or can anyone guide me in what I would need to do ? Thanks Andrew View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055082#4055082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055082 From do-not-reply at jboss.com Mon Jun 18 07:08:39 2007 From: do-not-reply at jboss.com (poyge394) Date: Mon, 18 Jun 2007 07:08:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - call .net webservice from jboss Message-ID: <23536820.1182164919825.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, how can i call a .net webservice from jboss 4.2.0GA, can sombody help me with the steps and some code. thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055158#4055158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055158 From do-not-reply at jboss.com Mon Jun 18 07:55:10 2007 From: do-not-reply at jboss.com (dibind) Date: Mon, 18 Jun 2007 07:55:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK Message-ID: <10430288.1182167710912.JavaMail.jboss@colo-br-02.atl.jboss.com> I got the same problem with jboss.4.0.4.GA and jdk 1.5. I got around the problem by deleting saaj-api.jar and saaj-imp.jar from JBOSS_HOME/lib directory and putting jboss-saaj.jar in JBOSS_HOME/lib directory. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055180#4055180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055180 From do-not-reply at jboss.com Mon Jun 18 10:27:54 2007 From: do-not-reply at jboss.com (poyge394) Date: Mon, 18 Jun 2007 10:27:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wsconsume ant task Message-ID: <30140047.1182176874308.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, i try to use wsconsume with ant, | | | | | | | | | | | | I get: | [wsconsume] Command invoked: org.jboss.ws.tools.jaxws.command.wsconsume -k -o C:\workspace\ipl_tradera\output -s C:\workspace\ipl_tradera\gen-src -t http://api.tradera.com/v1/publicservice.asmx?WSDL | [wsconsume] Exception in thread "main" java.lang.NoClassDefFoundError: gnu/getopt/LongOpt | [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.parseArguments(wsconsume.java:82) | [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:75) | | anybody have using wsconsume ant task ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055257#4055257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055257 From do-not-reply at jboss.com Mon Jun 18 11:35:40 2007 From: do-not-reply at jboss.com (rsuser) Date: Mon, 18 Jun 2007 11:35:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Invoking Web Services in Jboss 4.2 Message-ID: <17855171.1182180940655.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I am getting this exception when i invoke the service. I know some jar files i am missing. I am using JRE 1.5 and Jboss 4.2 JbossWS. What i have to do ? My Code is import javax.jws.WebMethod; | import javax.jws.WebService; | | @WebService | public class HelloWorldWS implements HelloWorldInterface | { | @WebMethod | public String sayHello(String toWhom) | { | //System.out.println("I'm Hit! " + toWhom); | return "Hello World: " + toWhom + " on " + new java.util.Date(); | } | } import java.rmi.Remote; | | public interface HelloWorldInterface extends Remote { | public String sayHello(String toWhom); | public void login(String toWhom); | } package com.client; | | import java.io.BufferedReader; | import java.io.InputStreamReader; | import java.io.OutputStream; | import java.net.HttpURLConnection; | import java.net.URL; | import java.net.URLConnection; | import java.util.Properties; | | public class TestClient{ | | /** | * @param args | */ | public static void main(String[] args) { | // TODO Auto-generated method stub | HttpURLConnection httpurlconnection = null; | try | { | // Specify proxy settings | Properties sysProperties = System.getProperties(); | sysProperties.put("proxyHost", "localhost"); | sysProperties.put("proxyPort", "8080"); | sysProperties.put("proxySet", "true"); | | String HostUrl = "localhost"; | String SoapActionUrl = "http://localhost:8080/Test/HelloWorldService?wsdl"; | | URL url = new URL(SoapActionUrl); | URLConnection urlconnection = url.openConnection(); | httpurlconnection = (HttpURLConnection)urlconnection; | | StringBuffer stringbuffer = new StringBuffer(); | | stringbuffer.append(""); | stringbuffer.append(""); | stringbuffer.append(""); | stringbuffer.append("World"); | stringbuffer.append(""); | | byte abyte0[] = stringbuffer.toString().getBytes(); | httpurlconnection.addRequestProperty("Host", HostUrl); | httpurlconnection.addRequestProperty("Content-Length", String.valueOf(abyte0.length)); | httpurlconnection.addRequestProperty("Content-Type", "text/xml; charset=UTF-8"); | httpurlconnection.addRequestProperty("SOAPAction", SoapActionUrl); | httpurlconnection.setInstanceFollowRedirects(true); | //httpurlconnection.addRequestProperty("Proxy-Authorization", "NTLM TlRMTVNTUAABAAAAB7IIogYABgA1AAAADQANACgAAAAFASgKAAAAD0lFMTBEVDZESzJDMVNHTE9CQUw="); | //httpurlconnection.addRequestProperty("Cookie", "niagara_auth=YWRtaW46YWRtaW4="); | httpurlconnection.setRequestMethod("POST"); | httpurlconnection.setDoOutput(true); | httpurlconnection.setDoInput(true); | | | OutputStream outputstream = httpurlconnection.getOutputStream(); | outputstream.write(abyte0); | outputstream.close(); | | System.out.println(httpurlconnection.getResponseMessage()); | | InputStreamReader inputstreamreader = new InputStreamReader(httpurlconnection.getInputStream()); | BufferedReader bufferedreader = new BufferedReader(inputstreamreader); | StringBuffer stringbuffer1 = new StringBuffer(); | String s3; | while((s3 = bufferedreader.readLine()) != null) | { | stringbuffer1.append(s3); | System.out.println(s3); | } | bufferedreader.close(); | httpurlconnection = null; | } | catch(Exception e) | { | e.printStackTrace(); | } | } | } 20:57:43,056 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(Unknown Source) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:243) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:197) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Unknown Source) | 20:57:43,056 ERROR [AbstractServiceEndpointServlet] Error processing web service request | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(Unknown Source) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:155) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:235) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:164) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:623) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:229) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Unknown Source) | 20:57:43,056 ERROR [[HelloWorldService]] Servlet.service() for servlet HelloWorldService threw exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(Unknown Source) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:155) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:235) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:164) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:623) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:229) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Unknown Source) What steps i'm missing View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055273#4055273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055273 From do-not-reply at jboss.com Mon Jun 18 11:43:22 2007 From: do-not-reply at jboss.com (tperrigo) Date: Mon, 18 Jun 2007 11:43:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Multiple WSDL bindings warning Message-ID: <483819.1182181402905.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm trying to consume a .NET web service from an EJB3 Stateless session bean (using JBoss 5 beta 2). I used wsconsume to generate all the client classes; it seemed to work without any problems. However, when I deploy my app (as an ear) and try to call the bean which invokes the web service (using the generated classes), I get the following warning (multiple times): anonymous wrote : | [WSDLDefinitions] Multiple WSDL bindings referrence the same interface: {http://com/werner/multimiler/web}PCMilerSoap | Has anyone encountered this before? How can I fix the issue? Any help would be very much appreciated. Thanks, Tim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055278#4055278 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055278 From do-not-reply at jboss.com Mon Jun 18 13:05:54 2007 From: do-not-reply at jboss.com (poyge394) Date: Mon, 18 Jun 2007 13:05:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - AccessorOrder Message-ID: <14391570.1182186354435.JavaMail.jboss@colo-br-02.atl.jboss.com> I get an NoClassDefFoundError on AccessorOrder when i try to call a webservice from a client. The problem is that i can't found AccessorOrder anywhere, that class dont exists. Any ideas ? | java.lang.NoClassDefFoundError: javax/xml/bind/annotation/AccessorOrder | at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createClassInfo(RuntimeModelBuilder.java:59) | at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createClassInfo(RuntimeModelBuilder.java:41) | at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:123) | at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:49) | at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:41) | at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189) | at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204) | at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:327) | at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:198) | at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:72) | at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:875) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:281) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:274) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:200) | at javax.xml.ws.Service.getPort(Service.java:116) | at tradera.PublicService.getPublicServiceSoap(PublicService.java:58) | at se.sj.ipl.tradera.AddItemXmlWebService.testTraderaPublicApi(AddItemXmlWebService.java:45) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) | at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) | at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) | at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) | at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) | at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) | at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) | at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) | at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) | at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055312#4055312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055312 From do-not-reply at jboss.com Mon Jun 18 14:53:26 2007 From: do-not-reply at jboss.com (rphadnis) Date: Mon, 18 Jun 2007 14:53:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: wsconsume ant task Message-ID: <1148157.1182192806108.JavaMail.jboss@colo-br-02.atl.jboss.com> You need the getopt.jar in the classpath. If you are using Jboss 4.2 then that file is in the client directory under jboss home. -Rahul View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055356#4055356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055356 From do-not-reply at jboss.com Mon Jun 18 15:49:15 2007 From: do-not-reply at jboss.com (hurzeler) Date: Mon, 18 Jun 2007 15:49:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Help I get: Failed to create a new SAX parser Message-ID: <19881447.1182196155841.JavaMail.jboss@colo-br-02.atl.jboss.com> After installing jbossws-1.2.1.GA on jboss4.0.5GA with ant deploy-jboss40 running jdk1.5.0_12 I get the exception below at the startup of jboss. What am I missing. Please help! Thanks. | 05:38:45,000 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml | 05:38:47,171 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://223.1.1.128:3873/] | 05:38:49,562 INFO [ServiceConfigurator] Problem configuring service jboss.web:service=WebServer | org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) | at org.jboss.system.ServiceConfigurator.parseJbxbSerialData(ServiceConfigurator.java:641) | at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:327) | at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460) | at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) | at org.jboss.system.ServiceController.install(ServiceController.java:226) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.install(Unknown Source) | at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy6.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:595) | Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:96) | at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:55) | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96) | ... 87 more | Caused by: javax.xml.parsers.ParserConfigurationException: Feature 'http://apache.org/xml/features/xinclude' is not recognized. | at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92) | ... 89 more | 05:38:49,625 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/ | org.jboss.deployment.DeploymentException: Error parsing meta data file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml; - nested throwable: (org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser) | at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) | at org.jboss.deployment.SchemaBindingSimpleSubDeployerSupport.parseMetaData(SchemaBindingSimpleSubDeployerSupport.java:57) | at org.jboss.kernel.deployment.jboss.JBossBeanDeployer.parseMetaData(JBossBeanDeployer.java:94) | at org.jboss.deployment.SimpleSubDeployerSupport.init(SimpleSubDeployerSupport.java:88) | at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) | at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy6.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:595) | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) | at org.jboss.deployment.SchemaBindingSimpleSubDeployerSupport.parseMetaData(SchemaBindingSimpleSubDeployerSupport.java:50) | ... 73 more | Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:96) | at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:55) | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96) | ... 74 more | Caused by: javax.xml.parsers.ParserConfigurationException: Feature 'http://apache.org/xml/features/xinclude' is not recognized. | at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92) | ... 76 more | 05:38:50,906 ERROR [JUDDIService] JNDI Bind Failed:JAXR | 05:38:50,906 ERROR [STDERR] javax.naming.CommunicationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]] | 05:38:50,906 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269) | 05:38:50,906 ERROR [STDERR] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1309) | 05:38:50,906 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1446) | 05:38:50,921 ERROR [STDERR] at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:484) | 05:38:50,921 ERROR [STDERR] at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477) | 05:38:50,921 ERROR [STDERR] at javax.naming.InitialContext.rebind(InitialContext.java:367) | 05:38:50,921 ERROR [STDERR] at org.jboss.jaxr.juddi.JUDDIService.bindJAXRConnectionFactory(JUDDIService.java:383) | 05:38:50,921 ERROR [STDERR] at org.jboss.jaxr.juddi.JUDDIService.setBindJaxr(JUDDIService.java:320) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:694) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceController.install(ServiceController.java:226) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | 05:38:50,921 ERROR [STDERR] at $Proxy4.install(Unknown Source) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | 05:38:50,921 ERROR [STDERR] at $Proxy6.deploy(Unknown Source) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | 05:38:50,921 ERROR [STDERR] at $Proxy0.start(Unknown Source) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.ServiceController.start(ServiceController.java:417) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | 05:38:50,921 ERROR [STDERR] at $Proxy4.start(Unknown Source) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | 05:38:50,921 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 05:38:50,921 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 05:38:50,921 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 05:38:50,921 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 05:38:50,921 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | 05:38:50,921 ERROR [STDERR] at $Proxy5.deploy(Unknown Source) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | 05:38:50,921 ERROR [STDERR] at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | 05:38:50,921 ERROR [STDERR] at org.jboss.Main.boot(Main.java:200) | 05:38:50,921 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:490) | 05:38:50,921 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) | 05:38:50,921 ERROR [STDERR] Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect] | 05:38:50,921 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243) | 05:38:50,921 ERROR [STDERR] ... 106 more | 05:38:50,937 ERROR [STDERR] Caused by: java.net.ConnectException: Connection refused: connect | 05:38:50,937 ERROR [STDERR] at java.net.PlainSocketImpl.socketConnect(Native Method) | 05:38:50,937 ERROR [STDERR] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) | 05:38:50,937 ERROR [STDERR] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) | 05:38:50,937 ERROR [STDERR] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) | 05:38:50,937 ERROR [STDERR] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) | 05:38:50,937 ERROR [STDERR] at java.net.Socket.connect(Socket.java:519) | 05:38:50,937 ERROR [STDERR] at java.net.Socket.connect(Socket.java:469) | 05:38:50,937 ERROR [STDERR] at java.net.Socket.(Socket.java:366) | 05:38:50,937 ERROR [STDERR] at java.net.Socket.(Socket.java:266) | 05:38:50,937 ERROR [STDERR] at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84) | 05:38:50,937 ERROR [STDERR] at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77) | 05:38:50,937 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239) | 05:38:50,937 ERROR [STDERR] ... 106 more | 05:38:53,312 WARN [XMLLoginConfigImpl] End loadConfig, failed to load config: file:/C:/Program Files/jboss-4.0.5.GA/server/default/conf/login-config.xml | org.jboss.security.auth.login.ParseException: Encountered " | ... | | at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:395) | at org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:333) | at org.jboss.security.auth.login.SunConfigParser.config(SunConfigParser.java:98) | at org.jboss.security.auth.login.SunConfigParser.parse(SunConfigParser.java:57) | at org.jboss.security.auth.login.SunConfigParser.doParse(SunConfigParser.java:79) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:310) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:294) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:268) | at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:176) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy6.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:595) | 05:38:53,546 INFO [WebService] Using RMI server codebase: http://earth:8083/ | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055374#4055374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055374 From do-not-reply at jboss.com Mon Jun 18 16:22:10 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 16:22:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Using JSR181 - problem with value types and arrays Message-ID: <28184661.1182198130509.JavaMail.jboss@colo-br-02.atl.jboss.com> Have a look at the marshal tests in the test suite. there are array tests of all kind View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055385#4055385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055385 From do-not-reply at jboss.com Mon Jun 18 16:24:28 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 16:24:28 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Basic authentication for WS fails to authenticate from c Message-ID: <19183595.1182198268881.JavaMail.jboss@colo-br-02.atl.jboss.com> Please start from the working sample from the testsuite. There is one for BASIC authentication View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055387#4055387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055387 From do-not-reply at jboss.com Mon Jun 18 16:28:57 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 16:28:57 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Duplicate SOAP body/envelope tags in SOAP message Message-ID: <6410853.1182198537941.JavaMail.jboss@colo-br-02.atl.jboss.com> Have a look at the JAXWS client API http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#Web_Service_Clients View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055390#4055390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055390 From do-not-reply at jboss.com Mon Jun 18 16:34:26 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 16:34:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Retrieving alias for WS Secure client Message-ID: <10027302.1182198866439.JavaMail.jboss@colo-br-02.atl.jboss.com> This is currently not supported. You are however welcome to contribute this extension View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055393#4055393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055393 From do-not-reply at jboss.com Mon Jun 18 16:41:49 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 16:41:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jbossws 1.2.1 /jboss 4.0.5 : how do i bypass MessageFa Message-ID: <19436791.1182199309526.JavaMail.jboss@colo-br-02.atl.jboss.com> | /** | * Load a factory using this ordered lookup procedure | * | *
    | *
  1. Use the system property | *
  2. Use the properties file "lib/jaxm.properties" in the JRE directory | *
  3. Use the Services API (as detailed in the JAR specification), if available, to determine the classname | *
  4. Use the default factory implementation class | *
| * | * @author Thomas.Diesler at jboss.com | * @since 14-Dec-2006 | */ | public class SAAJFactoryLoader | Step 3, the Services API uses a classloader. You should probably be able to set the context classloader such that it gives access to the SAAJ impl that you want. Please note, JBossWS will only work with its own SAAJ impl. Please use the jbossws-2.0 code base View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055395#4055395 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055395 From do-not-reply at jboss.com Mon Jun 18 17:13:46 2007 From: do-not-reply at jboss.com (thomas.diesler@jboss.com) Date: Mon, 18 Jun 2007 17:13:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How is the service URL constructed Message-ID: <22419343.1182201226079.JavaMail.jboss@colo-br-02.atl.jboss.com> As of jbossws-2.0.0 this is described here http://jbws.dyndns.org/mediawiki/index.php/JBossWS_FAQs#How_do_I_know_what_endpoint_address_is_being_used.3F View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055406#4055406 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055406 From do-not-reply at jboss.com Mon Jun 18 17:20:07 2007 From: do-not-reply at jboss.com (james_Chiu) Date: Mon, 18 Jun 2007 17:20:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - change HTTP status code in a WS fault Message-ID: <7164124.1182201607457.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, We are using JBoss WS 1.2.1 in our server side. Our client side is implemented in Flex and it communicates with the server side through JBoss WS. Flex can?t not handle a WebFault that gives HTTP status code = 500. Therefore, we are looking for a way that we can change HTTP status code from 500 to 200 when throwing an exception. Would be very appreciated if you can shed some light how to change HTTP status code from 500 to 200. Use a handler, servlet, ? Thanks, James View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055408#4055408 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055408 From do-not-reply at jboss.com Mon Jun 18 18:50:50 2007 From: do-not-reply at jboss.com (meghanai_99) Date: Mon, 18 Jun 2007 18:50:50 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - UnmarshallException for xsd type any Message-ID: <22003965.1182207050972.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I am publishing BPEL processes on JBoss 4.0.5GA, JBossWS 1.2.1 and JBPM 3.2 My xsd defines a certain type as shown below - | | | | | The request message contains wsse:security element as child of 'CredentialsType'. However when the SOAP message is received, I get following exception - org.jboss.ws.WSException: org.jboss.ws.core.jaxrpc.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.Un | marshalException: Failed to parse source: Failed to find read method or field for property 'security' in class com.seren | a.bpel.CredentialsType | at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:248) | at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:95) | at org.jboss.ws.core.soap.DOMContent.transitionTo(DOMContent.java:77) | at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140) | at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171) | at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:243) | at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:111) | at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:126) | at org.jboss.ws.core.server.ServiceEndpointInvokerJSE.invokeServiceEndpointInstance(ServiceEndpointInvokerJSE.ja | va:103) | at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:207) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:212) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | Caused by: org.jboss.ws.core.jaxrpc.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalExceptio | n: Failed to parse source: Failed to find read method or field for property 'security' in class com.serena.bpel.Credenti | alsType | at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:108) | at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:59) | at org.jboss.ws.core.jaxrpc.binding.DeserializerSupport.deserialize(DeserializerSupport.java:59) | at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:178) | ... 34 more The auto-generated CredentialsType class is as follows - public class CredentialsType | { | | protected javax.xml.soap.SOAPElement[] _any; | public CredentialsType(){} | | public CredentialsType(javax.xml.soap.SOAPElement[] _any){ | this._any=_any; | } | public javax.xml.soap.SOAPElement[] get_any() { return _any ;} | | public void set_any(javax.xml.soap.SOAPElement[] _any){ this._any=_any; } | | } Can someone tell me how I can get this working? Let me know if I should provide more information. Thank you, Meghana View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055422#4055422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055422 From do-not-reply at jboss.com Mon Jun 18 18:57:45 2007 From: do-not-reply at jboss.com (meghanai_99) Date: Mon, 18 Jun 2007 18:57:45 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: UnmarshallException for xsd type any Message-ID: <9272428.1182207465971.JavaMail.jboss@colo-br-02.atl.jboss.com> I guess it just needed wrapper element 'any' around wsse security element. It is accepting the SOAP request fine now. Thanks, Meghana View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055424#4055424 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055424 From do-not-reply at jboss.com Mon Jun 18 19:01:31 2007 From: do-not-reply at jboss.com (bruparel) Date: Mon, 18 Jun 2007 19:01:31 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBoss 4.0.2 and JBossWS Message-ID: <4931378.1182207691027.JavaMail.jboss@colo-br-02.atl.jboss.com> We are tied to JBoss release 4.0.2 because of the Client requirements. I would like to know if any release of JBoss Web Services can be deployed in this container that has WS-Addressing and WS-Eventing support. The idea is to use JBoss Web Services functionality exploiting WS-Eventing (and in turn WS-Addressing) coupled with JMS for asynchronous web services communication. If anyone can point me to any documentation/resources in that direction, I will really appreciate it. Thanks. Bharat View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055426#4055426 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055426 From do-not-reply at jboss.com Tue Jun 19 01:55:42 2007 From: do-not-reply at jboss.com (sandello) Date: Tue, 19 Jun 2007 01:55:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: cannot call jboss ws from MS SOAP SDK Message-ID: <16860461.1182232542072.JavaMail.jboss@colo-br-02.atl.jboss.com> I think, this is the bug. I have posted it to the Jira http://jira.jboss.com/jira/browse/JBWS-1712 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055461#4055461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055461 From do-not-reply at jboss.com Tue Jun 19 03:02:50 2007 From: do-not-reply at jboss.com (jaheersk1234) Date: Tue, 19 Jun 2007 03:02:50 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ejb3.client.ClientLauncher in which Jar file? Message-ID: <20682852.1182236570835.JavaMail.jboss@colo-br-02.atl.jboss.com> http://svn.nuxeo.org/trac/nuxeo/browser/demo/Apogee/ECMDemo/lib/jboss-ejb3.jar?rev=4314 u can download jboss-ejb3.jar from the above url regards, jaheer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055470#4055470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055470 From do-not-reply at jboss.com Tue Jun 19 03:19:10 2007 From: do-not-reply at jboss.com (Christy) Date: Tue, 19 Jun 2007 03:19:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem deploying web service Message-ID: <18719891.1182237550867.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! I have a problem: I'm using JBoss 4.2.0 with jbossws-1.2. I wrote simple web service (JAX-WS based) and successfully deployed it in automatic manner ( jbossws did it using only my source class and web.xml). After I restarted JBoss the web service had dissappeared!! Why did it happens? Do I need every time to redeploy it? Thank you for your help! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055475#4055475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055475 From do-not-reply at jboss.com Tue Jun 19 04:13:09 2007 From: do-not-reply at jboss.com (poyge394) Date: Tue, 19 Jun 2007 04:13:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain java type mapping for: {http://org.mazurek Message-ID: <16935270.1182240789738.JavaMail.jboss@colo-br-02.atl.jboss.com> | URL wsdlLocation = new URL("http://example.org/my.wsdl"); | QName serviceName = new QName("http://example.org/sample", "MyService"); | Service service = Service.create(wsdlLocation, serviceName); | Service.create does not exists. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055491#4055491 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055491 From do-not-reply at jboss.com Tue Jun 19 05:35:45 2007 From: do-not-reply at jboss.com (poyge394) Date: Tue, 19 Jun 2007 05:35:45 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Cannot obtain java type mapping for Message-ID: <14774076.1182245745321.JavaMail.jboss@colo-br-02.atl.jboss.com> can anybody give me a guideline pleass client code: | URL url = new URL("http://api.tradera.com/v1/publicservice.asmx?WSDL"); | QName qname = new QName("http://api.tradera.com", "PublicService"); | | ServiceFactory factory = ServiceFactory.newInstance(); | Service service = factory.createService(url, qname); | | PublicServiceSoap pss = (PublicServiceSoap) service.getPort(new QName("http://api.tradera.com", "PublicServiceSoap"), PublicServiceSoap.class); | Exception: | WARN getSOAPAddress, Unprocessed extension element: {http://schemas.xmlsoap.org/wsdl/http/}address | WARN processBinding, Unsupported binding: {http://schemas.xmlsoap.org/wsdl/http/}binding | WARN getSOAPAddress, Unprocessed extension element: {http://schemas.xmlsoap.org/wsdl/http/}address | WARN processBinding, Unsupported binding: {http://schemas.xmlsoap.org/wsdl/http/}binding | WARN processBinding, Unsupported binding: {http://schemas.xmlsoap.org/wsdl/http/}binding | WARN processBinding, Unsupported binding: {http://schemas.xmlsoap.org/wsdl/http/}binding | WARN getBindingByInterfaceName, Multiple WSDL bindings referrence the same interface: {http://api.tradera.com}PublicServiceSoap | WARN getBindingByInterfaceName, Multiple WSDL bindings referrence the same interface: {http://api.tradera.com}PublicServiceSoap | WARN getBindingByInterfaceName, Multiple WSDL bindings referrence the same interface: {http://api.tradera.com}PublicServiceSoap | org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://api.tradera.com}>GetItem | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processDocElement(JAXRPCMetaDataBuilder.java:627) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:886) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:214) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaDataInternal(JAXRPCClientMetaDataBuilder.java:216) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:133) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:85) | at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:111) | at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157) | at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128) | at se.sj.ipl.tradera.AddItemXmlWebService.testTraderaPublicApiStatic(AddItemXmlWebService.java:58) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) | at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) | at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) | at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) | at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) | at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) | at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) | at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) | at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) | at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) | at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) | at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055516#4055516 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055516 From do-not-reply at jboss.com Tue Jun 19 14:04:53 2007 From: do-not-reply at jboss.com (acxjbertr) Date: Tue, 19 Jun 2007 14:04:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - "ArrayOf" parameter types generating BindingExceptions Message-ID: <13590292.1182276293845.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using a "Top Down" (aka wsdl-to-java) approach to create a JSR109 endpoint with JBossWS 1.2.1.GA. The WSDL that was provided to me contains things like: | | | | | | | | | | | | My wstools-config.xml is: | | | | | | | Running the wstools Ant task finishes without a problem. Both the code and mapping document are generated without error. However, when I deploy the service and try to invoke it I get a BindingException saying that the ArrayOfString class cannot be found. Upon inspection of the generated classes there isn't a ArrayOfString.java file nor any references to a ArrayOfString object in FieldSelection.java. FieldSelection uses the actual array type "String[]". When I look at the mapping.xml I see this: | | ArrayOfString | typeNS:ArrayOfString | complexType | | string | string | | | When I remove this snippet from the mapping.xml everything works fine. Is this appropriate behavior? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055761#4055761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055761 From do-not-reply at jboss.com Tue Jun 19 15:48:46 2007 From: do-not-reply at jboss.com (Maffewl) Date: Tue, 19 Jun 2007 15:48:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Endpoint does not contain operation meta data for: getAccoun Message-ID: <7421314.1182282526911.JavaMail.jboss@colo-br-02.atl.jboss.com> I want to try and test the backwards compatibility of a webservice I upgraded from Axis to JBossWS. Up to this point I have consumed the old wsdl w/ wsconsume and have the service deployed in Jboss 4.2.0.GA. I sent in the old xml and it hits the endpoint but i get the following message: [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://xxxxx/account}accountServicePort does not contain operation meta data for: getAccount here is the request I am sending that works in our old environment (axis/jboss.net) but fails in the new environment: | | | ... | | | just for kicks I changed the getAccount tags to : ... as defined in the envelope, and i got a different error [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.WSException: Cannot find child element: {http://xxxxx/type}getAccount which seems to me that it it does find the 'getAccount'. but the reality is, i cant really change the request. I have to try and upgrade transparently. heres a portion of the deployed wsdl on the service if it helps | | | | ... | | | | | | ... | | | | | | | | ... | | | | | | ... | | | | ... | | | | | | | ... | | | | | | | ... | | | | | | | | | | | | ... | | | | | | | | | thanks matt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055800#4055800 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055800 From do-not-reply at jboss.com Tue Jun 19 15:51:53 2007 From: do-not-reply at jboss.com (djayakaran) Date: Tue, 19 Jun 2007 15:51:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem Accessing Web Service Message-ID: <29696555.1182282713397.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I deployed a very simple web service to JBoss-4.2.0.GA, and used JBoss's wsconsume utility to generates stubs. I ran the client in its own JVM as a java application. It invokes the web service... no problem! Then I coded a servlet (actually an Action class much like Struts) to call the web service. In this case the servlet and the web service are deployed within the same EAR. When the servlet invokes the web service from within the same container I get an exception when it tries to get the port. The offending line of code is in the generated service class: return (CurrencyWS)super.getPort(new QName("http://currencyconverter.ws/", "CurrencyWSPort"), CurrencyWS.class); The exception says: javax.xml.ws.WebServiceException: SEI is missing @WebService annotation: interface ws.currencyconverter.CurrencyWS All my annotations seem to be fine... the web service deploys fine and a client running in a separate JVM invokes it successfully. If I run the web service on one machine and the servlet (web server) on another machine they communicate just fine. Can someone tell me what I'm doing wrong? Thanks, David View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055801#4055801 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055801 From do-not-reply at jboss.com Tue Jun 19 17:44:48 2007 From: do-not-reply at jboss.com (meghanai_99) Date: Tue, 19 Jun 2007 17:44:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: UnmarshallException for xsd type any Message-ID: <29596757.1182289488210.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I am still getting this exception. It was my mistake when I thought I am not getting this exception anymore. Can someone tell me how can I get rid off this exception? Even after the exception, the request is received correctly by my BPEL process and it is executed as expected. Here is my SOAP request for that particular element - | | | | ......... | | | | Thank you, Meghana View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055838#4055838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055838 From do-not-reply at jboss.com Tue Jun 19 19:27:08 2007 From: do-not-reply at jboss.com (khkachn) Date: Tue, 19 Jun 2007 19:27:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Suspending input from web services Message-ID: <1633786.1182295628703.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, Is there a way programmaticly to suspend/resume web services from accepting connections? I was going to set a flag somewhere and just return an error, but I was wondering if there is a better way. Also, is there a way to adjust how many threads can be used by web services? Thanks, Ken View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055862#4055862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055862 From do-not-reply at jboss.com Wed Jun 20 03:54:24 2007 From: do-not-reply at jboss.com (gardon) Date: Wed, 20 Jun 2007 03:54:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - how to specify version of WSDL? Message-ID: <5973038.1182326064500.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, is it possible to specify version of WSDL to be generated in wstools or via JBossWS annotations? I haven't found it. I need WSDL version 1.1 to be generated. Thanks for any advice. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055907#4055907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055907 From do-not-reply at jboss.com Wed Jun 20 04:11:10 2007 From: do-not-reply at jboss.com (gardon) Date: Wed, 20 Jun 2007 04:11:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: how to specify version of WSDL? Message-ID: <4603921.1182327070451.JavaMail.jboss@colo-br-02.atl.jboss.com> I use JBoss 4.2.0-GA and JBossWS 1.2.1GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055913#4055913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055913 From do-not-reply at jboss.com Wed Jun 20 06:06:19 2007 From: do-not-reply at jboss.com (molson_m) Date: Wed, 20 Jun 2007 06:06:19 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: ClassCastException - jaxws webservice in jboss1.2.0 Message-ID: <21247997.1182333979027.JavaMail.jboss@colo-br-02.atl.jboss.com> hi....I had similar issues....the same exception...truly the exception is not atall helpful to find out the cause...thanks to this post.......then i noticed in one of my classes, i was using java.sql.Date...i changed it to java.util.Date....and i could deploy the bean successfully...so santhoshitha is right may be jboss didn't have supporting jars for java.sql.Date....! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055947#4055947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055947 From dling at tai.it Wed Jun 20 06:32:13 2007 From: dling at tai.it (Davide Ling) Date: Wed, 20 Jun 2007 12:32:13 +0200 Subject: [jbossws-users] WS-Security UsernameToken and PasswordDigest type Message-ID: <1182335533.7626.14.camel@dling-desktop> Hello Can I send PasswordDigest type passwords in WS-Security UsernameToken with JBossWS 1.2GA? I cannot find documentation about Thanks -- ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~ | Davide Ling | | E-mail: davide.ling at tai.it | | | | TAI S.r.l. | | 50141 FIRENZE - Via Pazzagli, 2 | | Phone: +39 +55 42661 | | Fax: +39 +55 4266357 | ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20070620/c2d5cd13/attachment.bin From do-not-reply at jboss.com Wed Jun 20 06:40:15 2007 From: do-not-reply at jboss.com (sdwfxsf) Date: Wed, 20 Jun 2007 06:40:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 1.2.x Tools Overview (wstools, wsprovide, wscons Message-ID: <20007899.1182336015491.JavaMail.jboss@colo-br-02.atl.jboss.com> How to use the wsconsume tool?I can't open the links you write.Could you speek in detail?Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055961#4055961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055961 From do-not-reply at jboss.com Wed Jun 20 06:47:53 2007 From: do-not-reply at jboss.com (davideling) Date: Wed, 20 Jun 2007 06:47:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 1.2.x Tools Overview (wstools, wsprovide, wscons Message-ID: <6124654.1182336473984.JavaMail.jboss@colo-br-02.atl.jboss.com> Example: wsconsume.sh -k -s src/ http://myContext/myService?wsdl where: -k : keep artifact sources from deletion -s: source folder Bye View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055966#4055966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055966 From do-not-reply at jboss.com Wed Jun 20 07:08:18 2007 From: do-not-reply at jboss.com (sandello) Date: Wed, 20 Jun 2007 07:08:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - MS Soap toolkit and Jboss are understanding wsdl differently Message-ID: <18987068.1182337698916.JavaMail.jboss@colo-br-02.atl.jboss.com> MS Soap client sends a message to JBossWS Server looks like | | | | | 123456789 | 128 | | | | JBossWS can't find element "connID" If axis client sends message | | | | | a | b | | | | JBoss successfully find the element. wsdl | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I think that the "targetNamespace" attribute define namespace for all declared parts: service, messages, etc. Am I right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055971#4055971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055971 From do-not-reply at jboss.com Wed Jun 20 09:58:02 2007 From: do-not-reply at jboss.com (Maffewl) Date: Wed, 20 Jun 2007 09:58:02 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Endpoint does not contain operation meta data for: getAc Message-ID: <18147341.1182347882583.JavaMail.jboss@colo-br-02.atl.jboss.com> i found out some more iinfo and have new questions. as it turns out , i had to do | | ... | | to get it to hit my code. I'm still in the position where I want to try to avoid messing up existing clients, so what are my options at this point? modify the orinigal wsdl? or can the wsconsume or jbossws be configured to handle this appropriatly? thanks again for your help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056042#4056042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056042 From do-not-reply at jboss.com Wed Jun 20 10:09:49 2007 From: do-not-reply at jboss.com (tperrigo) Date: Wed, 20 Jun 2007 10:09:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Multiple WSDL bindings warning Message-ID: <5265077.1182348589761.JavaMail.jboss@colo-br-02.atl.jboss.com> Any ideas on this one? This has really got me stuck... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056045#4056045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056045 From do-not-reply at jboss.com Wed Jun 20 13:28:54 2007 From: do-not-reply at jboss.com (wpfeiffe) Date: Wed, 20 Jun 2007 13:28:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: change HTTP status code in a WS fault Message-ID: <1901678.1182360534861.JavaMail.jboss@colo-br-02.atl.jboss.com> James, Sorry I don't have an answer for you on this, but I just ran into this a few days ago and was wondering if you had a solution. So far I considered creating my own wrapper obect that would be returned by all web services and would contain fault info. Also considered dropping JBossWS and using xFire as I've seen examples on how to set the status code with xFire (some dissension concerning whether it actually works though). Also considered just doing a rest style xml return which flex seems to handle quite nicely. Really my preference is to do some kind of interceptor that would let me set the status code. I already do some pre-processing of my hibernate return objects to kill the proxies which is believe should be in an interceptor as well. Just not sure where to start there. Anyway, I'd be interested in hearing how you solve this, if you do. Thanks, Bill Pfeiffer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056146#4056146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056146 From do-not-reply at jboss.com Wed Jun 20 14:59:53 2007 From: do-not-reply at jboss.com (ravi2box) Date: Wed, 20 Jun 2007 14:59:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBoss 4.0.5.GA web services Message-ID: <28925008.1182365993437.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'd like to know if it's possible to produce and consume web services on the vanilla (i.e without separately downloading JBossWS libs) version of JBoss 4.0.5GA . If i understand this correctly, JBoss 4.0.5GA ships with jbossws-1.0.3 SP1 I am trying to write a simple JSR 181 style web service using the @WebService and @WebMethod annotation. I am using JDK 1.5.0_12 on Windows XP. I am getting a compilation error testws\service\HelloWS.java:8: incompatible types [javac] found : javax.jws.WebService [javac] required: java.lang.annotation.Annotation [javac] @WebService [javac] ^ [javac] testws\service\HelloWS.java:11: incompatible types [javac] found : javax.jws.WebMethod [javac] required: java.lang.annotation.Annotation [javac] @WebMethod [javac] ^ [javac] 2 errors BUILD FAILED Compile failed; see the compiler error out put for details. I see that the jbossws14.sar file has JDK 1.4 compatible JARS - does this mean it won't compile on JDK 1.5?? I have JBOSS_HOME/client and server/default/lib in the classpath already...what other JAR am i missing?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056164#4056164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056164 From do-not-reply at jboss.com Wed Jun 20 18:24:36 2007 From: do-not-reply at jboss.com (oskar.carlstedt) Date: Wed, 20 Jun 2007 18:24:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: change HTTP status code in a WS fault Message-ID: <6946977.1182378276747.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All! I'm not sure if this works, but an id?a might be to implement a simple servlet filter that you put in front of the servlet. The filter will then invoke the http request, check the response code and change it if necessary. A normal servlet has a filter chain, and I think you can configure one in web.xml for this kind of servlet too. Best regards Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056215#4056215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056215 From do-not-reply at jboss.com Wed Jun 20 19:09:38 2007 From: do-not-reply at jboss.com (amitkrsingh) Date: Wed, 20 Jun 2007 19:09:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Soap Error : NAMESPACE_ERR: An attempt is made to create or Message-ID: <16342671.1182380978554.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello All, I am getting following error when my stateless ejb makes a soap call to other server to load some static data. The soap call works fine outside the Jboss container and only when I try to make this call from within Jboss I get this error. Also I wasnt expecting so see "org.jboss.ws.core.soap" in the stack trace, looks like somehow the SOAPContentElement class is being loaded from jbosall-cleintws.jar insted of the bundeled 'saaj' jars. Any insight is welcome. This is my first soap experience so please bear with me if there is something very simple which I have overlooked. Thanks in advance. -Amit /***ERROR*****/ org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(Unknown Source) at org.apache.xerces.dom.AttrNSImpl.setName(Unknown Source) at org.apache.xerces.dom.AttrNSImpl.(Unknown Source) at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(Unknown Source) at org.apache.xerces.dom.ElementImpl.setAttributeNS(Unknown Source) at org.jboss.ws.core.soap.SOAPElementImpl.setAttributeNS(SOAPElementImpl.java:747) at org.jboss.ws.core.soap.SOAPContentElement.setAttributeNS(SOAPContentElement.java:409) at org.jboss.ws.core.soap.SOAPElementImpl.addAttribute(SOAPElementImpl.java:174) at org.jboss.ws.core.soap.SOAPContentElement.addAttribute(SOAPContentElement.java:280) .... at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) /******/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056227#4056227 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056227 From do-not-reply at jboss.com Wed Jun 20 21:19:41 2007 From: do-not-reply at jboss.com (wpfeiffe) Date: Wed, 20 Jun 2007 21:19:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: change HTTP status code in a WS fault Message-ID: <16371494.1182388781245.JavaMail.jboss@colo-br-02.atl.jboss.com> Oskar, I could be wrong on this, but I don't think you have direct access to the servlet handling in the context where JBossWS deploys the web services (like you would within a regular servlet container). I think the handlers are meant to allow for this type of pre-post processing, but I haven't seen any examples of using handlers to access the http mechanisms such as the status code return, but maybe it can. I haven't looked too far into it yet. Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056254#4056254 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056254 From do-not-reply at jboss.com Thu Jun 21 02:02:07 2007 From: do-not-reply at jboss.com (sdwfxsf) Date: Thu, 21 Jun 2007 02:02:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - how to use jboss web service Message-ID: <30563418.1182405727852.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I meet a problem when I use JBoss web service. On client I use wsconsume to generate the java classes. The code is: ApplicationService.java package greenback.esb.test;import javax.jws.WebMethod; import javax.jws.WebParam; import javax.jws.WebResult; import javax.jws.WebService; import javax.jws.soap.SOAPBinding; @WebService(name = "ApplicationService", targetNamespace = "http://test.esb.greenback/") @SOAPBinding(style = SOAPBinding.Style.RPC) public interface ApplicationService { @WebMethod @WebResult(partName = "return") public String process( @WebParam(name = "arg0", partName = "arg0") Po arg0); } ApplicationServiceService.java package greenback.esb.test; import java.net.MalformedURLException; import java.net.URL; import javax.xml.namespace.QName; import javax.xml.ws.Service; import javax.xml.ws.WebEndpoint; import javax.xml.ws.WebServiceClient; @WebServiceClient(name = "ApplicationServiceService", targetNamespace = "http://test.esb.greenback/", wsdlLocation = "http://192.168.168.188:8080/application/applicationESB?wsdl") public class ApplicationServiceService extends Service { private final static URL APPLICATIONSERVICESERVICE_WSDL_LOCATION; static { URL url = null; try { url = new URL("http://192.168.168.188:8080/application/applicationESB?wsdl"); } catch (MalformedURLException e) { e.printStackTrace(); } APPLICATIONSERVICESERVICE_WSDL_LOCATION = url; } public ApplicationServiceService(URL wsdlLocation, QName serviceName) { super(wsdlLocation, serviceName); } public ApplicationServiceService() { super(APPLICATIONSERVICESERVICE_WSDL_LOCATION, new QName("http://test.esb.greenback/", "ApplicationServiceService")); } @WebEndpoint(name = "ApplicationServicePort") public ApplicationService getApplicationServicePort() { return (ApplicationService)super.getPort(new QName("http://test.esb.greenback/", "ApplicationServicePort"), ApplicationService.class); } } ObjectFactory.java package greenback.esb.test; import javax.xml.bind.annotation.XmlRegistry; /** * This object contains factory methods for each * Java content interface and Java element interface * generated in the greenback.esb.test package. * An ObjectFactory allows you to programatically * construct new instances of the Java representation * for XML content. The Java representation of XML * content can consist of schema derived interfaces * and classes representing the binding of schema * type definitions, element declarations and model * groups. Factory methods for each of these are * provided in this class. * */ @XmlRegistry public class ObjectFactory { /** * Create a new ObjectFactory that can be used to create new instances of schema derived classes for package: greenback.esb.test * */ public ObjectFactory() { } /** * Create an instance of {@link Po } * */ public Po createPo() { return new Po(); } } package-info.java @javax.xml.bind.annotation.XmlSchema(namespace = "http://test.esb.greenback/") package greenback.esb.test; Po.java package greenback.esb.test; import javax.xml.bind.annotation.XmlAccessType; import javax.xml.bind.annotation.XmlAccessorType; import javax.xml.bind.annotation.XmlType; /** * Java class for po complex type. * * The following schema fragment specifies the expected content contained within this class. * * * <complexType name="po"> * <complexContent> * <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> * <sequence> * <element name="age" type="{http://www.w3.org/2001/XMLSchema}int"/> * <element name="name" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> * </sequence> * </restriction> * </complexContent> * </complexType> * * * */ @XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "po", propOrder = { "age", "name" }) public class Po { protected int age; protected String name; /** * Gets the value of the age property. * */ public int getAge() { return age; } /** * Sets the value of the age property. * */ public void setAge(int value) { this.age = value; } /** * Gets the value of the name property. * * @return * possible object is * {@link String } * */ public String getName() { return name; } /** * Sets the value of the name property. * * @param value * allowed object is * {@link String } * */ public void setName(String value) { this.name = value; } } the wsdl file is - - - - - - - - - - - - - - - The test class is import greenback.esb.test.ApplicationService; import greenback.esb.test.ApplicationServiceService; import greenback.esb.test.Po; public class Test { public static void main(String[] args){ ApplicationServiceService ss=new ApplicationServiceService(); ApplicationService service=ss.getApplicationServicePort(); Po po=new Po(); po.setAge(12); po.setName("init"); String s=service.process(po); System.out.println(s); } } Did I write the test class right?If it is not correct,what is the right way? When I run the test Class ,it throws an exception Exception in thread "Main Thread" org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:327) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:133) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1544) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.ws.core.soap.SOAPConnectionImpl.callInternal(SOAPConnectionImpl.java:192) at org.jboss.ws.core.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:109) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:309) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:185) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:163) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:149) at $Proxy13.process(Unknown Source) at Test.main(Test.java:19) Caused by: java.lang.ClassCastException: org.apache.axis.message.MessageElement at org.jboss.ws.core.soap.SOAPEnvelopeImpl.(SOAPEnvelopeImpl.java:59) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:87) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:76) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:253) at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:463) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:299) ... 12 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056271#4056271 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056271 From do-not-reply at jboss.com Thu Jun 21 02:09:48 2007 From: do-not-reply at jboss.com (sdwfxsf) Date: Thu, 21 Jun 2007 02:09:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - how to use jboss web service Message-ID: <32376811.1182406188940.JavaMail.jboss@colo-br-02.atl.jboss.com> I am sorry the wsdl file changed after i submit,this is the new one <definitions name='ApplicationServiceService' targetNamespace='http://cvicse.com/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://cvicse.com/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> <types> <xs:schema targetNamespace='http://cvicse.com/' version='1.0' xmlns:xs='http://www.w3.org/2001/XMLSchema'> <xs:complexType name='po'> <xs:sequence> <xs:element name='age' type='xs:int'/> <xs:element minOccurs='0' name='name' type='xs:string'/> </xs:sequence> </xs:complexType> </xs:schema> </types> <message name='ApplicationService_processResponse'> <part name='return' type='xsd:string'></part> </message> <message name='ApplicationService_process'> <part name='arg0' type='tns:po'></part> </message> <portType name='ApplicationService'> <operation name='process' parameterOrder='arg0'> <input message='tns:ApplicationService_process'></input> <output message='tns:ApplicationService_processResponse'></output> </operation> </portType> <binding name='ApplicationServiceBinding' type='tns:ApplicationService'> <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> <operation name='process'> <soap:operation soapAction=''/> <input> <soap:body namespace='http://cvicse.com/' use='literal'/> </input> <output> <soap:body namespace='http://cvicse.com/' use='literal'/> </output> </operation> </binding> <service name='ApplicationServiceService'> <port binding='tns:ApplicationServiceBinding' name='ApplicationServicePort'> <soap:address location='http://192.168.168.188:8080/application/applicationESB'/> </port> </service> </definitions> I use JBoss AS 4.2.0 GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056273#4056273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056273 From do-not-reply at jboss.com Thu Jun 21 03:46:01 2007 From: do-not-reply at jboss.com (Christy) Date: Thu, 21 Jun 2007 03:46:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem deploying web service Message-ID: <18698143.1182411961323.JavaMail.jboss@colo-br-02.atl.jboss.com> Realy nobody knows about this priblem? It's very important for me! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056303#4056303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056303 From do-not-reply at jboss.com Thu Jun 21 03:54:08 2007 From: do-not-reply at jboss.com (griff7023) Date: Thu, 21 Jun 2007 03:54:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem deploying web service Message-ID: <4774781.1182412448954.JavaMail.jboss@colo-br-02.atl.jboss.com> If you were to be a little more specific someone might be able to help. How are you deploying it as a .war, an exploded war, a .ear, etc.? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056309#4056309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056309 From do-not-reply at jboss.com Thu Jun 21 05:43:26 2007 From: do-not-reply at jboss.com (Christy) Date: Thu, 21 Jun 2007 05:43:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem deploying web service Message-ID: <10821998.1182419006108.JavaMail.jboss@colo-br-02.atl.jboss.com> What do you mean by saying "more specific"? I'm deploying it as a .war. Here is the code of web-service: import javax.jws.WebService; import javax.jws.WebMethod; import javax.jws.soap.SOAPBinding; @WebService @SOAPBinding(style = SOAPBinding.Style.RPC) public class WSJaxws { @WebMethod public String hello(String param){ String res = ""; res = "Hello "+param; return res; } } So I have only java code and web.xml file. When I start jboss it deploys this web-service and I here: http://localhost:8080/jbossws/services I have WSDL file. So everything seems to be fine. But when I restart jboss the web service dessapeares! So I need to rewrite web.xml file (before deploying I had one web.xml, but after deploying jboss changed it, but I know that i is normal). And if I rewrite web.xml as it was before first deploying my web service appeares! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056356#4056356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056356 From do-not-reply at jboss.com Thu Jun 21 06:05:18 2007 From: do-not-reply at jboss.com (hannes.koller) Date: Thu, 21 Jun 2007 06:05:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <9665583.1182420318934.JavaMail.jboss@colo-br-02.atl.jboss.com> I tried to post this in JIRA but it told me I dont have permission to comment on the issue so here it goes: I am experiencing the same problem described by original Reporter: Subclass information gets lost when the SOAP message is created....but not always.. if the class contains a variable of JAXBElement then the inheritance seems to work correctly for all attributes in the class. Example (constructed to explain my point, sorry if not 100% correct but the WSDL I am really dealing with is quite huge). | | | | | | | | | Note that the minOccurrs="0" together with nillable="true" in someElement will cause wsconsume to create the JAXBElement<..> variable i was talking about: | public class SomeType{ | | @XmlElementRef(name = "someElement", namespace = "http://some.namespace.com", type = JAXBElement.class) | protected JAXBElement someElement; | @XmlElement(required = true, nillable = true) | protected ClassB classB; | .... | In this example inheritance for the classB Attribute works as expected. Whereas if I alter the wsdl and set the minOccurrs of someElement to 1 thus having wsconsume create the following class: | public class SomeType{ | | @XmlElement(required=true, nillable=true) | protected SomeElement someElement; | @XmlElement(required = true, nillable = true) | protected ClassB classB; | ... | | then inheritance on classB breaks. Not sure why this is happening, but I thought this observation might help to track down the cause of this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056371#4056371 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056371 From do-not-reply at jboss.com Thu Jun 21 06:41:38 2007 From: do-not-reply at jboss.com (griff7023) Date: Thu, 21 Jun 2007 06:41:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem deploying web service Message-ID: <10392801.1182422498563.JavaMail.jboss@colo-br-02.atl.jboss.com> The re-writing of the web.xml file is normal but it usually only causes an issue if you deploy the web service as an exploded war (a directory). I haven't ever seen any issues when deploying the web service as a war file (a zip file). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056393#4056393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056393 From do-not-reply at jboss.com Thu Jun 21 08:07:48 2007 From: do-not-reply at jboss.com (Christy) Date: Thu, 21 Jun 2007 08:07:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem deploying web service Message-ID: <30892305.1182427668466.JavaMail.jboss@colo-br-02.atl.jboss.com> Thank you very much!!!!! You helped me so! This was my mistake! I was deploying web service as an exploded war. Now I deplpyed it as a .war and everything works fine! Thank you a lot!!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056440#4056440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056440 From do-not-reply at jboss.com Thu Jun 21 08:19:03 2007 From: do-not-reply at jboss.com (smangan) Date: Thu, 21 Jun 2007 08:19:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - UnfiledMetaData classLoader Message-ID: <17138695.1182428343919.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using a plugin environment on the client that provides classloader separation for each plugin. This leads to a problem in the UnfiledMetaData class where it stores the context classloader when it is created. My web service interface is coming from a different plugin, thus a different ClassLoader. When attempting to load the interface class, the UnfiledMetaData is using its stored ClassLoader instead of the current context ClassLoader. Could someone please tell me what reasoning is for storing the classloader in the UnfiledMetaData object, and is there some way to get the correct ClassLoader into the UnfiledMetaData? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056448#4056448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056448 From do-not-reply at jboss.com Thu Jun 21 08:55:36 2007 From: do-not-reply at jboss.com (poyge394) Date: Thu, 21 Jun 2007 08:55:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wsconsume binding Message-ID: <26626297.1182430536696.JavaMail.jboss@colo-br-02.atl.jboss.com> I whant that wsconsume tool generate JAX-RPC mapping file to specify how the types in the WSDL are mapped to the Java types. is it possible to that with wsconsume tool. i see that i cand sen in -b option with a binding file, but dont understand how to use it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056461#4056461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056461 From do-not-reply at jboss.com Thu Jun 21 09:24:42 2007 From: do-not-reply at jboss.com (fambad) Date: Thu, 21 Jun 2007 09:24:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <29473092.1182432282273.JavaMail.jboss@colo-br-02.atl.jboss.com> I tried to create an own JAXBElement as you described. But I am getting errors when I deploy it. First I create an ObjectFactory for "someElement": | @XmlRegistry | class ObjectFactory { | | @XmlElementDecl(scope=getClassBResponse.class, name="someElement", namespace="http://some.namespace.com") | JAXBElement createSomeElement(String s) { | return new JAXBElement(new QName("someElement"), String.class, s); | } | } | Then I defined the JAXBElement in my response class | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "getClassBResponse", namespace="http://mstrauch.examples.ws/", propOrder = { "data", "someElement" }) | public class getClassBResponse { | | @XmlElementRef(name = "someElement", namespace = "http://some.namespace.com", type = JAXBElement.class) | protected JAXBElement someElement; | | @XmlElement(required = true, nillable = true) | protected ClassB data; | | public getClassBResponse() { | } | | public ClassB getData() { | return data; | } | | public void setData(ClassB data) { | this.data = data; | } | | } | During deployment I am getting a ClassCastException: org.jboss.deployment.DeploymentException: Cannot start service endpoint; - nested throwable: (java.lang.ClassCastException: mstrauch.examples.ws.jaxws.GetClassCAsClassBResponse$JaxbAccessorM_getReturn _setReturn_mstrauch_examples_ws_types_ClassB) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:101) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: java.lang.ClassCastException: mstrauch.examples.ws.jaxws.GetClassCAsClassBResponse$JaxbAccessorM_getReturn_setReturn_mstrauch_examples_ws_types_ClassB at com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.instanciate(OptimizedAccessorFactory.java:151) at com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:96) at com.sun.xml.bind.v2.runtime.reflect.Accessor$GetterSetterReflection.optimize(Accessor.java:308) at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.(SingleElementNodeProperty.java:53) at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at com.sun.xml.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:88) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.(ClassBeanInfoImpl.java:135) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:404) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:246) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210) at javax.xml.bind.ContextFinder.find(ContextFinder.java:368) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522) at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:67) at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:54) at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:470) at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:469) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:516) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:502) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:490) at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:429) at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:192) at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:112) at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:646) at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:140) at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) ... 28 more So what can I do? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056482#4056482 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056482 From do-not-reply at jboss.com Thu Jun 21 10:14:36 2007 From: do-not-reply at jboss.com (hannes.koller) Date: Thu, 21 Jun 2007 10:14:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <8724461.1182435276572.JavaMail.jboss@colo-br-02.atl.jboss.com> Hmm interesting. As I said I started with a wsdl file and used wsconsume to create the Java Classes and annotations. I have not touched the Java classes or the ObjectFactory manually. When I find the time I will try to create a complete, minimal example. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056522#4056522 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056522 From do-not-reply at jboss.com Thu Jun 21 12:12:51 2007 From: do-not-reply at jboss.com (djayakaran) Date: Thu, 21 Jun 2007 12:12:51 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem Accessing Web Service Message-ID: <11475762.1182442371731.JavaMail.jboss@colo-br-02.atl.jboss.com> Here's the code I wrote to invoke the web service: { CurrencyForm form = null; CurrencyWSService svc = null; form = populateCurrencyForm(); // Souce, target currencies svc = new CurrencyWSService(); CurrencyWS currencyWS = svc.getCurrencyWSPort(); System.out.println(form); form = currencyWS.convertCurrency(form); System.out.println(form); } The exception is thrown at the getCurrencyWSPort() call. Here's my Service Endpoint Interface (SEI): @WebService(name = "CurrencyWS", targetNamespace = "http://currencyconverter.ws/") public interface CurrencyWS { @WebMethod @WebResult(targetNamespace = "") @RequestWrapper(localName = "convertCurrency", targetNamespace = "http://currencyconverter.ws/", className = "ws.currencyconverter.ConvertCurrency") @ResponseWrapper(localName = "convertCurrencyResponse", targetNamespace = "http://currencyconverter.ws/", className = "ws.currencyconverter.ConvertCurrencyResponse") public CurrencyForm convertCurrency(@WebParam(name = "arg0", targetNamespace = "") CurrencyForm arg0); } I seem to have the necessary @WebService annotation, yet the JBoss container throws the exception (see my previous posting). Any thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056580#4056580 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056580 From do-not-reply at jboss.com Thu Jun 21 16:40:35 2007 From: do-not-reply at jboss.com (Maffewl) Date: Thu, 21 Jun 2007 16:40:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - SimpleTypes not creating classes with wsconsume Message-ID: <25482179.1182458435637.JavaMail.jboss@colo-br-02.atl.jboss.com> When I use the wsconsume tool on my wsdl, It seems that while my ComplexType declarations generate classes, however my SimpleType ones do not. previously, when using wsdl2java. I would get classes generated on these simple types for example: | | ... | | | Value Meaning | ------------------ | eng English | fra French | | | | | | | | | ... | | would generate a LanguageCode class when using wsdl2java. However, using wsconsume, this class is not created. Any thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056658#4056658 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056658 From do-not-reply at jboss.com Thu Jun 21 17:05:23 2007 From: do-not-reply at jboss.com (Maffewl) Date: Thu, 21 Jun 2007 17:05:23 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SimpleTypes not creating classes with wsconsume Message-ID: <11325775.1182459923549.JavaMail.jboss@colo-br-02.atl.jboss.com> my assumption that it did not generate all simple types was incorrect, in fact it DID even generate the LanguageCode class, it doesnt hoever generate this one: | | | | | | | | | | | | | any reason for that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056664#4056664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056664 From do-not-reply at jboss.com Fri Jun 22 03:07:07 2007 From: do-not-reply at jboss.com (last_deceneu) Date: Fri, 22 Jun 2007 03:07:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - SOAP Responce does not populate namespace prefix Message-ID: <10490411.1182496027590.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello! I'm developing a RPC web service using annotations and a .net client. The problem is that response attribute xsi:type="dtBaseCommand" does not contain namespace ns prefix for used schema, it should be xsi:type="ns:dtBaseCommand" (response is created correct for simple types). And on .net client xml soap processor crashes because does not now where is located that type and to instantiate it I'm using jboss 4.2GA Is any way to force soap response to use namespace prefix? The soap response is: | | | | | | CMD3_COMMAND | | | | | And schema for objects is: | | | | | | | | | | | | | | | Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056742#4056742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056742 From do-not-reply at jboss.com Fri Jun 22 03:17:44 2007 From: do-not-reply at jboss.com (fambad) Date: Fri, 22 Jun 2007 03:17:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <421222.1182496664010.JavaMail.jboss@colo-br-02.atl.jboss.com> I have testet a little bit more and now I have a little example that I can deploy. I also startet with the wsdl file and used wsconsume to create the java classes and annotation. Then I copied these classes in my project and so the deployment was successful. But when I access the deployed webservice I am getting a ClassCastException during the request. Below I list my classes: ClassA | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "classA", propOrder = { | "propA" | }) | public class ClassA { | | private String propA; | | public ClassA() { | } | | public String getPropA() { | return propA; | } | | public void setPropA(String propA) { | this.propA = propA; | } | | } | ClassB | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "classB", propOrder = { | "propB" | }) | public class ClassB extends ClassA { | private String propB; | public ClassB() { | } | | public String getPropB() { | return propB; | } | | public void setPropB(String propB) { | this.propB = propB; | } | } | ClassC | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "classC", propOrder = { | "propC" | }) | public class ClassC extends ClassB { | | private String propC; | public ClassC() { | } | | public String getPropC() { | return propC; | } | | public void setPropC(String propC) { | this.propC = propC; | } | } | GetClassBResponse | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "getClassBResponse", propOrder = { | "someElement", | "data" | }) | public class GetClassBResponse { | | @XmlElementRef(name = "someElement", type = JAXBElement.class) | protected JAXBElement someElement; | @XmlElement(required = true, nillable = true) | protected ClassB data; | | public JAXBElement getSomeElement() { | return someElement; | } | | public void setSomeElement(JAXBElement value) { | this.someElement = ((JAXBElement ) value); | } | | public ClassB getData() { | return data; | } | | public void setData(ClassB value) { | this.data = value; | } | } | SampleWSWithDocument_Bare | @WebService() | @SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.BARE ) | public class SampleWSWithDocument_Bare { | | public SampleWSWithDocument_Bare() { | } | | @WebMethod() | public GetClassBResponse getClassCAsClassB() { | System.out.print("getClassCAsClassB"); | ClassC classC= new ClassC(); | classC.setPropA("propA"); | classC.setPropB("propB"); | classC.setPropC("propC"); | | GetClassBResponse resp = new GetClassBResponse(); | resp.setData(classC); | | ObjectFactory fact = new ObjectFactory(); | resp.setSomeElement(fact.createGetClassBResponseSomeElement("Test")); | return resp; | } | } | ObjectFactory | @XmlRegistry | public class ObjectFactory { | | private final static QName _GetClassCAsClassBResponse_QNAME = new QName("http://ws.examples.mstrauch/", "getClassCAsClassBResponse"); | private final static QName _GetClassBResponseSomeElement_QNAME = new QName("http://ws.examples.mstrauch/", "someElement"); | | public ObjectFactory() { | } | | public ClassA createClassA() { | return new ClassA(); | } | | public ClassC createClassC() { | return new ClassC(); | } | | public ClassB createClassB() { | return new ClassB(); | } | | public GetClassBResponse createGetClassBResponse() { | return new GetClassBResponse(); | } | | @XmlElementDecl(namespace = "http://ws.examples.mstrauch/", name = "getClassCAsClassBResponse") | public JAXBElement createGetClassCAsClassBResponse(GetClassBResponse value) { | return new JAXBElement(_GetClassCAsClassBResponse_QNAME, GetClassBResponse.class, null, value); | } | | @XmlElementDecl(namespace = "http://ws.examples.mstrauch/", name = "someElement", scope = GetClassBResponse.class) | public JAXBElement createGetClassBResponseSomeElement(String value) { | return new JAXBElement(_GetClassBResponseSomeElement_QNAME, String.class, GetClassBResponse.class, value); | } | } | Now I get follow error message during request. 08:59:41,554 ERROR [SOAPFaultHelperJAXWS] SOAP request exception javax.xml.soap.SOAPException: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:68) at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:120) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:197) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64) ... 29 more 08:59:41,632 ERROR [SOAPFaultHelperJAXWS] Error creating SOAPFault message javax.xml.soap.SOAPException: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:77) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:234) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:164) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:623) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:229) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:73) ... 28 more 08:59:41,632 ERROR [AbstractServiceEndpointServlet] Error processing web service request javax.xml.ws.WebServiceException: Cannot create SOAPFault message for: javax.xml.soap.SOAPException: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:172) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:623) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:229) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 08:59:41,632 ERROR [[SampleWSWithDocument_Bare]] Servlet.service() for servlet SampleWSWithDocument_Bare threw exception javax.xml.ws.WebServiceException: Cannot create SOAPFault message for: javax.xml.soap.SOAPException: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:172) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:623) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:229) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056746#4056746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056746 From do-not-reply at jboss.com Fri Jun 22 03:48:55 2007 From: do-not-reply at jboss.com (mr_d) Date: Fri, 22 Jun 2007 03:48:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - MTOM + WS Security = problem Message-ID: <4400584.1182498535107.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, Has anyone tried to have a web service with mtom *and* ws security activated? I did some tests with a web service as an ejb3 stateless bean and a Java standalone client (using the client parts of JbossWS): mtom only works, ws-security only works. But when I enable both, I get an exception: javax.xml.ws.soap.SOAPFaultException: Endpoint {http://foo.org/mtom}ServiceImpl does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData If I inspect the network communication, the client seems to use ws-security and put all the data as an encrypted envelope. There is no binary attachment anymore. On the server side, it seems that ws-security cannot be enabled with mtom, as the exception suggests. Maybe the two standards are not compatible to work together. I didn't found any information that says: no, no, no don't use mtom with ws-security. Thanks in advance for any enlightenment, Let me know if my description is not clear enough, best regards, :oD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056751#4056751 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056751 From do-not-reply at jboss.com Fri Jun 22 04:00:44 2007 From: do-not-reply at jboss.com (davideling) Date: Fri, 22 Jun 2007 04:00:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <15883072.1182499244997.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, i did it, and i got the attachment inlined in the soap body encrypted (is it right?). Be sure you annotated the service implementation class | @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING) | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | public class ServiceCipheredSignedImpl implements | ServiceCipheredSigned { | | // Bla bla ... | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056754#4056754 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056754 From do-not-reply at jboss.com Fri Jun 22 04:06:48 2007 From: do-not-reply at jboss.com (floefliep) Date: Fri, 22 Jun 2007 04:06:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: charset encoding problem with the jsr181pojo sample : ec Message-ID: <20435404.1182499608821.JavaMail.jboss@colo-br-02.atl.jboss.com> I've been debugging for hours on this one and eventually tracked the problem down, which I posted on the JIRA: http://jira.jboss.org/jira/browse/JBWS-1716 A workaround UTF-8 fix can be downloaded there for version 1.2.1GA of JBossWS. Setting the system property file.encoding may not work when you have an application which relies on platform-default file encoding. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056756#4056756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056756 From do-not-reply at jboss.com Fri Jun 22 05:07:58 2007 From: do-not-reply at jboss.com (hannes.koller) Date: Fri, 22 Jun 2007 05:07:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <13097007.1182503278589.JavaMail.jboss@colo-br-02.atl.jboss.com> Ok I have managed to create a simple example of the behavior. Please note that I am pretty new to webservices and JBossWS (started using it a few days ago) so sorry if something is overly complicated. Feedback is highly appreciated. I am using JBoss 4.2.0.GA and java version "1.5.0_08" I started with the following WSDL (I have modified an echo tutorial I found on the web so please dont be confused by the namespace and other irregularities): | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have an A->B->C Class Hierarchy here, and a BResponse Complex Type which consists of a "B" and a "Something". Note the "minOccurs=1 maxOccurs=1 nillable=true " . If I throw the file at wsconsume it creates a number of classes. The BResponse Class looks like this: | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "BResponse", propOrder = { | "something", | "b" | }) | public class BResponse { | | @XmlElement(required = true, nillable = true) | protected Something something; | @XmlElement(required = true, nillable = true) | protected B b; | ....} | I have written a very simple Server: | @javax.jws.WebService(endpointInterface="echo.GetB", serviceName="GetBService", targetNamespace="http://echo/", portName="GetBPort" ) | public class DummyGetB implements GetB { | | public BResponse getB() { | | BResponse response = new BResponse(); | | C c = new C(); | c.setArg0("1"); | c.setArg1("2"); | c.setArg2("3"); | | response.setB(c); | | return response; | } | | } | and a Client: | public class Client { | | public static void main(String[] args) throws Exception { | GetBService getB = new GetBService(new URL("http://127.0.0.1:8080/server?wsdl"),new QName("http://echo/", "GetBService")); | | GetB getBPort = getB.getGetBPort(); | BResponse bResponse = getBPort.getB(); | | System.out.println(bResponse.getB().getClass()); | B b = bResponse.getB(); | System.out.println(b.getArg0()); | System.out.println(b.getArg1()); | C c = (C)bResponse.getB(); | System.out.println(c.getArg2()); | } | If I try this example I get: | class echo.B | 1 | 2 | Exception in thread "main" java.lang.ClassCastException: echo.B | at at.ac.arsenal.Client.main(Client.java:53) | Only a "B" gets transmitted, although it should be a "C" Now, to get the behavior I was talking about change the minOccurrs parameter of something element of BResponse to 0: | .............. | | | | | | | ................ | Then rerun wsconsume. The generated BResponse class now looks like this. Notice the JAXBElement type of variable something; | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "BResponse", propOrder = { | "something", | "b" | }) | public class BResponse { | | @XmlElementRef(name = "something", type = JAXBElement.class) | protected JAXBElement something; | @XmlElement(required = true, nillable = true) | protected B b; | I Recompile and Redeploy the server then rerun the Client. The output is now: | class echo.C | 1 | 2 | 3 | now C gets transmitted and the arg2 property has the correct value. As I said before this is of course no solution to the original problem, but I think it might be useful in tracking down the source of it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056777#4056777 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056777 From do-not-reply at jboss.com Fri Jun 22 05:38:07 2007 From: do-not-reply at jboss.com (hannes.koller) Date: Fri, 22 Jun 2007 05:38:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance and JBossWS Message-ID: <16808419.1182505087845.JavaMail.jboss@colo-br-02.atl.jboss.com> Here are the generated XML fragments (read from the JBoss log): Incorrect Behavior (B Transmitted) | | | | 1 | 2 | | | Correct Behavior(C Transmitted) | | | 1 | 2 | 3 | | | Perhaps that helps :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056789#4056789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056789 From do-not-reply at jboss.com Fri Jun 22 09:18:44 2007 From: do-not-reply at jboss.com (Christy) Date: Fri, 22 Jun 2007 09:18:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Jbossws client: java.lang.IncompatibleClassChangeError Message-ID: <6734547.1182518324058.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! Can somebody help me please? I wrote a simple client using jbossws. I've generated necessary files using wsconsume. Here is the code of my client: public class ClientJaxWS { public String getCall() { String res = ""; WSJaxwsService service = new WSJaxwsService(); WSJaxws port = service.getWSJaxwsPort(); res = port.hello("it is me"); System.out.println("res = " + res); return res; } } But when I try to run my client I have next eror: java.lang.IncompatibleClassChangeError at client.ws.jaxws.ClientJaxWS.getCall(ClientJaxWS.java:13) at org.apache.jsp.index_jsp._jspService(index_jsp.java:63) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Does anybody know what is the problem and what is the reason? Maybe someone has working examples? Thank you in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056864#4056864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056864 From do-not-reply at jboss.com Fri Jun 22 11:32:27 2007 From: do-not-reply at jboss.com (mr_d) Date: Fri, 22 Jun 2007 11:32:27 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <567334.1182526347629.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello davideling, Thanks for your reply, My annotations on my service implementation are: | @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING) | @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle = SOAPBinding.ParameterStyle.BARE) | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | as suggested in http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#MTOM.2FXOP. If I try your annotations (without @SOAPBinding) I have the same exception: | javax.xml.ws.soap.SOAPFaultException: Endpoint {http://foo.org/mtom}ServiceImpl does not contain | operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData | Now, the weird part: If I disable ws security on the client part, it works (even if on the server side I have @EndpointConfig(configName = "Standard WSSecurity Endpoint")). As I said on my first post, when I activate mtom and ws-security, it seems that only mtom works, so if my client send an encrypted soap message, the server will not know how to handle it and will throws the exception. You said, you've got the attachment inlined. I don't know what a soap message looks like using mtom + ws security, but mtom is supposed to use multi parts isn't it? So, are you sure that ws security has not disable mtom? Well, maybe I need to dig more information :oD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056930#4056930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056930 From do-not-reply at jboss.com Fri Jun 22 11:51:06 2007 From: do-not-reply at jboss.com (davideling) Date: Fri, 22 Jun 2007 11:51:06 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <18134686.1182527466494.JavaMail.jboss@colo-br-02.atl.jboss.com> Ehm... sorry my last reply was only a code snippet... Service implementation | @WebService(endpointInterface="serviceJBossCipheredSigned.ServiceJBossCipheredSigned", | portName="ServiceJBossCipheredSignedSOAP", | serviceName="ServiceJBossCipheredSigned" | ) | @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING) | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | public class ServiceJBossCipheredSignedImpl implements | ServiceJBossCipheredSigned { | // bla bla ... | } | Service configuration (jboss-wsse-service.xml): | | WEB-INF/wsse.keystore | jbossws | WEB-INF/wsse.truststore | jbossws | | | | | | | | | | | Client implementation: | public void testInvocation() throws Exception { | | // 1) Service | Service service = Service.create( | new File("wsdl/mywsdl.wsdl").toURL(), | new QName("http://serviceJBossCipheredSigned/", | "ServiceJBossCipheredSigned") | ); | | // Configuration file WS-Security | ((ServiceExt) service).setSecurityConfig( | "META-INF/jboss-wsse-client.xml"); | | // 2) Port Creation | ServiceJBossCipheredSigned port = (ServiceJBossCipheredSigned) | service.getPort( | new QName("http://serviceJBossCipheredSigned/", | "ServiceJBossCipheredSignedSOAP"), | ServiceJBossCipheredSigned.class); | | // Enable MTOM | SOAPBinding binding = | (SOAPBinding) ((BindingProvider) port).getBinding(); | binding.setMTOMEnabled(true); | | // Enable WS-Security on port | ((StubExt) port).setConfigName("Standard WSSecurity Client"); | | // Set endpoint address | Map reqContext = | ((BindingProvider)port).getRequestContext(); | reqContext.put( | BindingProvider.ENDPOINT_ADDRESS_PROPERTY, | "http://bla bla" | ); | | // Set username e password | reqContext.put(Stub.USERNAME_PROPERTY, "myUsername"); | reqContext.put(Stub.PASSWORD_PROPERTY, "myPassword"); | | ... bla bla and invocation | | ); | Client configuration | | | META-INF/wsse.keystore | jbossws | META-INF/wsse.truststore | jbossws | | | | | | | | | | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056935#4056935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056935 From do-not-reply at jboss.com Fri Jun 22 14:54:34 2007 From: do-not-reply at jboss.com (J2EEUser) Date: Fri, 22 Jun 2007 14:54:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jb0ss4.2.0, JAX-WS2.0 deployment exception Message-ID: <2812370.1182538474912.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am trying JAX-WS2.0 sample deployment on JBoss4.2.0. I am getting the following deplyment exception: Cannot start service endpoint; - nested throwable: ========= (org.jboss.ws.WSException: {http://www.test.com}arg0 is not a valid property on class fromwsdl.server.AddNumbers) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:101) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) ============= sun-jaxws.xml ======= ====== web.xml ======== fromwsdl fromwsdl com.sun.xml.ws.transport.http.servlet.WSServletContextListener JAX-WS endpoint - fromwsdl fromwsdl AddNumbersPort fromwsdl.server.AddNumbersImpl 1 AddNumbersPort /addnumbers 60 ======== Anyone had this issue? I have to solve this ASAP to develop actual web service implementations. Can anyone please help me in solving this? THanks in advance. RR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056989#4056989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056989 From do-not-reply at jboss.com Fri Jun 22 16:25:48 2007 From: do-not-reply at jboss.com (walbar) Date: Fri, 22 Jun 2007 16:25:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Spring + JBossWS best practice Message-ID: <7260872.1182543948610.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm using JBoss 4.0.5, EJB3 and Spring. My system offers and consumes web services. Initially I started consuming WS via Axis, but since I want to offer EJB3 style web services and Axis is not compatible with JBossWS, I have to move my ws clients implementations to jbossws. Anyway, I would like to keep my Spring-way style when consuming WS, so, any suggestion of how to implement this clients in a Spring-style using JBossWS? Thanks for your answers, Walbar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057012#4057012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057012 From do-not-reply at jboss.com Mon Jun 25 02:14:25 2007 From: do-not-reply at jboss.com (patel_123) Date: Mon, 25 Jun 2007 02:14:25 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Caused by: org.jboss.ws.WSException: Cannot obtain java type Message-ID: <15970027.1182752065271.JavaMail.jboss@colo-br-02.atl.jboss.com> hi I am exposing my EJB3 components as web services. WSDL document is generated correctly. But when my client application tries to access the webservice it throws the following exception, Caused by: org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://wb1-329:8080}validateUser at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:451) at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaDataInternal(JSR109ClientMetaDataBuilder.java:208) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:126) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82) at org.jboss.ws.jaxrpc.ServiceImpl.(ServiceImpl.java:96) at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157) at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128) at client.UserBean.loginUser(UserBean.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126) please help me in resolving this error View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057241#4057241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057241 From do-not-reply at jboss.com Mon Jun 25 05:45:46 2007 From: do-not-reply at jboss.com (patel_123) Date: Mon, 25 Jun 2007 05:45:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBoss 4.0.5 and JBoss 4.2 CR1 plus JBossWS 1.2 - Does it Message-ID: <11011454.1182764746811.JavaMail.jboss@colo-br-02.atl.jboss.com> i am getting following error can anybody tell what would be cause, Caused by: org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://wb1-329:8080}validateUser at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:451) at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaDataInternal(JSR109ClientMetaDataBuilder.java:208) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:126) at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82) at org.jboss.ws.jaxrpc.ServiceImpl.(ServiceImpl.java:96) at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157) at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128) at client.UserBean.loginUser(UserBean.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126) thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057275#4057275 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057275 From do-not-reply at jboss.com Mon Jun 25 07:55:53 2007 From: do-not-reply at jboss.com (richard_opalka) Date: Mon, 25 Jun 2007 07:55:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <27707461.1182772553629.JavaMail.jboss@colo-br-02.atl.jboss.com> Maybe the two standards are not compatible to work together. I didn't found any information that says: no, no, no don't use mtom with ws-security. Hi mr_d, MTOM + WS-Security are fully compatible standards. MTOM is a new attachment approach and was designed with WS security in mind. Before MTOM e.g. using standard WS attachments or SWA ref attachments, users were unable to use these attachments in conjunction with WS Security. With MTOM you can ;-) Rio View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057309#4057309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057309 From do-not-reply at jboss.com Mon Jun 25 08:24:05 2007 From: do-not-reply at jboss.com (davideling) Date: Mon, 25 Jun 2007 08:24:05 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <26825896.1182774245745.JavaMail.jboss@colo-br-02.atl.jboss.com> Ok, but have the MTOM attachment to be inlined or not when WS-Security signature or encryption is activated? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057316#4057316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057316 From do-not-reply at jboss.com Mon Jun 25 09:10:07 2007 From: do-not-reply at jboss.com (mr_d) Date: Mon, 25 Jun 2007 09:10:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <32624529.1182777007607.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, Thanks for your answers, @richard_opalka: I agree, they are compatible, so to use attachments with WS Security, MTOM is the only and right way. @davideling: I have the same config. As I said on my first post, mtom only works, and ws security only also works. Are you sure that your encrypted soap envelope is created using mtom? Can you post one of your soap messages? And also the parameters of the exposed method or the wsdl file? I tried to get some soap message examples where mtom + ws security are enabled. I found two: -http://wso2.org/files/rampart-tute.pdf [page 81] -http://msdn2.microsoft.com/en-US/library/aa738574.aspx[bottom of the page] In these two message, we can see that: -Content-Type contains "multipart/related" and "type="application/xop+xml" -In the body of the soap message, there is a "xop:Include" element -In the body of the soap message, there is a "CipherData" and a "CipherValue" element -The attachment is in an encrypted mime part The two first points are the proof that mtom is enabled. The last ones indicate that ws security is active too. Im trying to achieve this kind of message with JbossWS. So far, no luck. :oD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057334#4057334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057334 From do-not-reply at jboss.com Mon Jun 25 09:37:08 2007 From: do-not-reply at jboss.com (davideling) Date: Mon, 25 Jun 2007 09:37:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <27534118.1182778628682.JavaMail.jboss@colo-br-02.atl.jboss.com> Thank you for your links mr_d, they are very interesting. Now I'm sure that my Web Services behaviour is not correct :-( . Request Headers | POST /servizioJBossCipheredSigned/ServizioJBossCipheredSigned?datatype=JBossWSMessage HTTP/1.1 | | Authorization: Basic bXlVc2VybmFtZTpteVBhc3N3b3Jk | | SOAPAction: "" | | Content-Type: text/xml; charset=UTF-8 | | JBoss-Remoting-Version: 22 | | User-Agent: JBossRemoting - 2.2.0 SP4 (Bluto) | | Host: 127.0.0.1:8181 | | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 | | Connection: keep-alive | | Content-Length: 503592 | Response Headers | HTTP/1.1 200 OK | | Server: Apache-Coyote/1.1 | | X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5 | | Content-Type: text/xml;charset=UTF-8 | | Transfer-Encoding: chunked | | Date: Mon, 25 Jun 2007 13:22:57 GMT | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057348#4057348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057348 From do-not-reply at jboss.com Mon Jun 25 09:56:01 2007 From: do-not-reply at jboss.com (davideling) Date: Mon, 25 Jun 2007 09:56:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <21291874.1182779761701.JavaMail.jboss@colo-br-02.atl.jboss.com> Exposed interface method | @WebMethod | @WebResult(name="responseMessage") | public ResponseMessage eleaborateMessage( | @WebParam(name="requestMessage") | RequestMessage message); | Request bean | public class RequestMessage implements Serializable { | | ... | | private DataHandler attachment; | | @XmlMimeType("application/pdf") | public DataHandler getAttachment() { | return attachment; | } | | public void setAttachment(DataHandler attachment) { | this.attachment = attachment; | } | | ... | | } | The attachment arrive correctly to destination... but it's not an attachment! ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057357#4057357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057357 From do-not-reply at jboss.com Mon Jun 25 10:02:12 2007 From: do-not-reply at jboss.com (leo5abi) Date: Mon, 25 Jun 2007 10:02:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Elements sorted in Ascending order in WSDL Message-ID: <9335533.1182780132190.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello there, new beginner in JBOSSWS. I went through the Getting started guide release 5 from JBOSS and developed a Small web service. Details: EJB: I have an entity bean that selects data from a view in HSQLDB with columns as Contract, Newdate, Company (all varchar) On top of entity bean i have a session bean that i use to access all records in a view (findAll()) using EJB ql. I have deployed the ejb - works fine Now i try to develop a webservice to access the VIEW (using the startup guide). Now when i run the wstool the WSDL file i get has elemnts in Ascending order of the name i.e element name="company" nillable="true" type="string" element name="contract" nillable="true" type="string" element name="newdate" nillable="true" type="string" whereas i was expecting it to be in order same as column in the view element name="contract" nillable="true" type="string" element name="newdate" nillable="true" type="string" element name="company" nillable="true" type="string" deployment of ws goes fine Now when i run my client and try to print contract, i get company name which mean that data is correct but element name is wrong Help needed what should i do to correct my problem so that the data for contract comes under element contract? /Amit View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057360#4057360 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057360 From do-not-reply at jboss.com Mon Jun 25 11:20:06 2007 From: do-not-reply at jboss.com (djayakaran) Date: Mon, 25 Jun 2007 11:20:06 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem Accessing Web Service Message-ID: <31428829.1182784806458.JavaMail.jboss@colo-br-02.atl.jboss.com> I've tried everything short of looking into JBoss's source code to see why it's throwing the exception: Here's a portion of the call stack in the exception: javax.xml.ws.WebServiceException: SEI is missing @WebService annotation: interface ws.currencyconverter.CurrencyWS at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.assertSEIConstraints(ServiceDelegateImpl.java:287) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:180) at javax.xml.ws.Service.getPort(Service.java:116) at ws.currencyconverter.CurrencyWSService.getCurrencyWSPort(CurrencyWSService.java:54) at commands.ConvertCurrencyCommand.invokeWebService(ConvertCurrencyCommand.java:76) at commands.ConvertCurrencyCommand.execute(ConvertCurrencyCommand.java:59) at web.CurrencyConverterServlet.process(CurrencyConverterServlet.java:52) Can someone help? If you think you can help but need more info, please reply and I'll post any additional info needed. Thanks, David View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057401#4057401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057401 From do-not-reply at jboss.com Mon Jun 25 19:37:22 2007 From: do-not-reply at jboss.com (axstevens) Date: Mon, 25 Jun 2007 19:37:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: change HTTP status code in a WS fault Message-ID: <14319374.1182814642798.JavaMail.jboss@colo-br-02.atl.jboss.com> Something along the following lines if you can configure in a filter. But to a previous posters point. How do you get a filter configured when @WebService is a Session Bean, nice example in user guide is for POJO. I guess use HTTP request/response context properties in SOAPHandler? Haven't looked to see if they are popuated yet. But anyway kind of problemattic with a lot of servlet filter resources already written for authentication, etc. public class AdobeStatusFilter implements Filter { | Logger log = Logger.getLogger(AdobeStatusFilter.class); | private FilterConfig filterConfig = null; | | public void init(FilterConfig filterConfig) throws ServletException { | this.filterConfig = filterConfig; | } | | public void doFilter(ServletRequest req, ServletResponse resp, FilterChain chain) throws IOException, ServletException { | AdobeResponseWrapper wrapper = new AdobeResponseWrapper((HttpServletResponse) resp); | HttpServletResponse response = (HttpServletResponse)resp; | chain.doFilter(req, wrapper); | } | | public void destroy() { | this.filterConfig = null; | } | | } public class AdobeResponseWrapper extends HttpServletResponseWrapper { | | private int statusCode; | public AdobeResponseWrapper(HttpServletResponse response) { | super(response); | } | public int getStatus() { | return statusCode; | } | public void sendError(int errorCode) throws IOException { | this.statusCode = adjust(errorCode); | super.sendError(this.statusCode); | } | public void sendError(int errorCode, String errorMessage) throws IOException { | this.statusCode = adjust(errorCode); | super.sendError(this.statusCode, errorMessage); | } | public void setStatus(int statusCode) { | this.statusCode = adjust(statusCode); | super.setStatus(this.statusCode); | } | public void setStatus(int statusCode, String message) { | this.statusCode = adjust(statusCode); | super.setStatus(this.statusCode, message); | } | | private int adjust(int errorCode) { | return errorCode == HttpServletResponse.SC_INTERNAL_SERVER_ERROR ? | HttpServletResponse.SC_OK : errorCode; | } | | | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057524#4057524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057524 From do-not-reply at jboss.com Tue Jun 26 03:19:01 2007 From: do-not-reply at jboss.com (richard_opalka) Date: Tue, 26 Jun 2007 03:19:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <25374117.1182842341258.JavaMail.jboss@colo-br-02.atl.jboss.com> "davideling" wrote : Ok, | but have the MTOM attachment to be inlined or not | when WS-Security signature or encryption is activated? | | Thanks | MTOM attachments do not need to be inlined. For example Microsoft Indigo and some other Java stacks (I don't know if JBossWS too) provide some kind of "MTOM SAAJ Text Element", which contains just MIME attachment id as its content (when you're sniffing the wire communcation). However from SOAP stack point of view when some other SAAJ handler that is in the handler chain tries to read the content of this special text element, it will obtain attachment binary data encoded in base64 canonical format instead of the attachment id. However on the wire it goes as the MIME attachment. This has also some performance consequences. For example if application sends MTOM in the form of MIME attachment and there's some handler in the handler chain that needs to work with this MTOM attachment content (e.g. WSSecurity SAAJ handler), this attachment must be encoded to base64 canonical format and that value is returned to the requestor. When processing really big attachments this fact causes real performance issues. Rio View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057567#4057567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057567 From do-not-reply at jboss.com Tue Jun 26 03:37:46 2007 From: do-not-reply at jboss.com (davideling) Date: Tue, 26 Jun 2007 03:37:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <18600165.1182843466170.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello Rio, i agree with You. Do You know how to develop a JBossWS Web Service with both attachment and WS-Security encryption? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057570#4057570 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057570 From do-not-reply at jboss.com Tue Jun 26 04:32:38 2007 From: do-not-reply at jboss.com (leo5abi) Date: Tue, 26 Jun 2007 04:32:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Jbossws and .net Message-ID: <906665.1182846758793.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, Can i call JBOSS web service developed using JBOSSWS from a .NET Client. IF Yes, any link to a tutorial or example will be highly appreciated. I have developed a JBOSSWS app and currently calling it from a java client using RPC. How can i trace the SOAP message? I am running the webservice and client locally on windows(so ethereal can't sniff it) Is there any JBOSSWS tolls which can sniff the messages or any log level which can print detail soap message /Amit View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057588#4057588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057588 From do-not-reply at jboss.com Tue Jun 26 04:39:51 2007 From: do-not-reply at jboss.com (davideling) Date: Tue, 26 Jun 2007 04:39:51 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jbossws and .net Message-ID: <31755166.1182847192003.JavaMail.jboss@colo-br-02.atl.jboss.com> I develop on Linux. I use Wireshark (ex ethereal) sometimes, but I usually sniff SOAP messages with apache tcpmon http://ws.apache.org/commons/tcpmon/ Bye View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057590#4057590 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057590 From do-not-reply at jboss.com Tue Jun 26 06:15:34 2007 From: do-not-reply at jboss.com (hypnosat7) Date: Tue, 26 Jun 2007 06:15:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WS and rules Message-ID: <24749041.1182852934453.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, How can we call Drools as a Web Service ? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057629#4057629 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057629 From do-not-reply at jboss.com Tue Jun 26 06:27:38 2007 From: do-not-reply at jboss.com (richard_opalka) Date: Tue, 26 Jun 2007 06:27:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jbossws and .net Message-ID: <935198.1182853658973.JavaMail.jboss@colo-br-02.atl.jboss.com> "leo5abi" wrote : | | Can i call JBOSS web service developed using JBOSSWS from a .NET Client. | IF Yes, any link to a tutorial or example will be highly appreciated. | | Of course you can. Take a look to Microsoft Indigo or WSE (I don't know which one Microsoft SOAP stack are you using) and take a look how to write your application from WSDL contract. They refer to it as Contract Based Approach in their documentation. Rio View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057634#4057634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057634 From do-not-reply at jboss.com Tue Jun 26 06:52:18 2007 From: do-not-reply at jboss.com (davideling) Date: Tue, 26 Jun 2007 06:52:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <24455967.1182855138317.JavaMail.jboss@colo-br-02.atl.jboss.com> This time I'm trying a simpler example MTOM/WS-Security onl with username and password In my service client, if I comment out // ((StubExt) port).setConfigName("Standard WSSecurity Client"); I get MTOM work correctly | POST /servizioJBossWSSEAttachment/ServizioWSSEAttachment?datatype=JBossWSMessage HTTP/1.1 | Authorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3Jk | SOAPAction: "" | Content-Type: multipart/related; type="application/xop+xml"; start=""; | start-info="text/xml"; | boundary="----=_Part_0_31571602.1182853646985" | JBoss-Remoting-Version: 22 | User-Agent: JBossRemoting - 2.2.0 SP4 (Bluto) | Host: localhost:8181 | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 | Connection: keep-alive | Content-Length: 453280 | | | ------=_Part_0_31571602.1182853646985 | Content-Type: application/xop+xml; type="text/xml" | Content-Transfer-Encoding: 8bit | Content-ID: | | DavideLing | ------=_Part_0_31571602.1182853646985 | Content-Type: application/octet-stream | Content-Transfer-Encoding: binary | Content-Id: | | %PDF-1.4 | blablabla... | But if I enable WS-Security MTOM doesn't work any more. The client doesn't send a multipart related message, but inserts the xop:include tag with the attachment reference. I use JBoss 4.2.0 GA, JDK 1.5.0_12 on Linux 32 bit | POST /servizioJBossWSSEAttachment/ServizioWSSEAttachment?datatype=JBossWSMessage HTTP/1.1 | Authorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3Jk | SOAPAction: "" | Content-Type: text/xml; charset=UTF-8 | JBoss-Remoting-Version: 22 | User-Agent: JBossRemoting - 2.2.0 SP4 (Bluto) | Host: localhost:8181 | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 | Connection: keep-alive | Content-Length: 828 | | | | | | myusername | mypassword | | | | | | | | Davide | Ling | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057646#4057646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057646 From do-not-reply at jboss.com Tue Jun 26 08:32:03 2007 From: do-not-reply at jboss.com (sdwfxsf) Date: Tue, 26 Jun 2007 08:32:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How to return List? Message-ID: <30911653.1182861123907.JavaMail.jboss@colo-br-02.atl.jboss.com> I develop the web service programme use java in both server and client. I use the annotation to expose the method as service.There's a method in server which return a List type.I use the tool named wsconsume to generate the code of client.It generated the ArrayList class of itself and the return type of the mapping method is this ArrayList,but the ArrayList contains nothing.When I invoke this method,it returned an object with nothing.And I also change this ArrayList to java.util.ArrayList,but get nothing too.So I want to ask if the server return a list type,how should I get the result.Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057688#4057688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057688 From do-not-reply at jboss.com Tue Jun 26 08:37:04 2007 From: do-not-reply at jboss.com (patel_123) Date: Tue, 26 Jun 2007 08:37:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - javax.naming.NameNotFoundException: service not bound Message-ID: <24547542.1182861424847.JavaMail.jboss@colo-br-02.atl.jboss.com> hi i am trying to access web services using JNDI lookup.I am using JBoss app server. this is my client code snippet ctx=new InitialContext(); //customerSessionRemote remote=(customerSessionRemote)ctx.lookup("customer/remote"); Service service=(Service)ctx.lookup("java:comp/env/service/CustomerRegisteration"); try { EndpointInterface port = (EndpointInterface)service.getPort(EndpointInterface.class); String user=port.validateUser(getUserName(), getPassword()); System.out.println(user); } catch (ServiceException e) { // TODO Auto-generated catch block e.printStackTrace(); } } catch (NamingException e) { // TODO Auto-generated catch block e.printStackTrace(); } but i am getting following error, javax.naming.NameNotFoundException: service not bound 17:55:56,468 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) 17:55:56,468 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) 17:55:56,468 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:543) 17:55:56,468 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:267) 17:55:56,468 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:270) 17:55:56,468 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) 17:55:56,484 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) 17:55:56,484 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) 17:55:56,484 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351) 17:55:56,484 ERROR [STDERR] at client.UserBean.loginUser(UserBean.java:125) 17:55:56,484 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 17:55:56,484 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 17:55:56,484 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 17:55:56,484 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 17:55:56,484 ERROR [STDERR] at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126) 17:55:56,484 ERROR [STDERR] at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72) 17:55:56,484 ERROR [STDERR] at javax.faces.component.UICommand.broadcast(UICommand.java:312) 17:55:56,484 ERROR [STDERR] at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267) 17:55:56,484 ERROR [STDERR] at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381) 17:55:56,484 ERROR [STDERR] at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75) 17:55:56,484 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) 17:55:56,484 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90) 17:55:56,484 ERROR [STDERR] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 17:55:56,484 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) 17:55:56,484 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) 17:55:56,484 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 17:55:56,484 ERROR [STDERR] at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 17:55:56,484 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 17:55:56,484 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 17:55:56,484 ERROR [STDERR] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 17:55:56,484 ERROR [STDERR] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 17:55:56,484 ERROR [STDERR] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) 17:55:56,484 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) please help me in resolving this View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057692#4057692 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057692 From do-not-reply at jboss.com Tue Jun 26 08:40:37 2007 From: do-not-reply at jboss.com (richard_opalka) Date: Tue, 26 Jun 2007 08:40:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <11040931.1182861637222.JavaMail.jboss@colo-br-02.atl.jboss.com> "davideling" wrote : | But if I enable WS-Security MTOM doesn't work any more. | The client doesn't send a multipart related message, | but inserts the xop:include tag with the attachment reference. | | I use JBoss 4.2.0 GA, JDK 1.5.0_12 on Linux 32 bit | Hi davideling, I don't know JBossWS stack very well yet but according to the attachments you've posted I can see that both MTOM and WSSecurity handlers when activated create buggy message. Probably MTOM handler is the first one in the handler chain and it created SOAP message with attachment and set message type to MULTIPART/RELATED, but next handler in the chain, i.e. WSSecurity handler, changed message type from MULTIPART/RELATED to simple SOAP message. But I'm just guessing. What about debugging JBossWS source code? Did you try it? Rio View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057698#4057698 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057698 From do-not-reply at jboss.com Tue Jun 26 09:45:40 2007 From: do-not-reply at jboss.com (davideling) Date: Tue, 26 Jun 2007 09:45:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <21866580.1182865540230.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm sorry Rio, I'm at work now and I can't look JBossWS sources now. All I can do now is look at client log4j logs. If I enable WS-Security I can see this where I can find two times ...HEADER={SOAPAction="", Content-Type=text/xml... | ... | DEBUG main org.jboss.remoting.MicroRemoteClientInvoker - org.jboss.remoting.transport.http.HTTPClientInvoker at 1922f46 connecting | DEBUG main org.jboss.remoting.MicroRemoteClientInvoker - org.jboss.remoting.transport.http.HTTPClientInvoker at 1922f46 connected | DEBUG main org.jboss.ws.core.client.RemotingConnectionImpl - Remoting metadata: {http.basic.password=mypassword, http.basic.username=myusername, HEADER={SOAPAction="", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true} | DEBUG main org.jboss.remoting.transport.http.HTTPClientInvoker - Setting request header with SOAPAction : "" | DEBUG main org.jboss.remoting.transport.http.HTTPClientInvoker - Setting request header with Content-Type : text/xml; charset=UTF-8 | DEBUG main org.jboss.ws.core.soap.SOAPContentElement - MTOM enabled: Restore XOP data | DEBUG main org.jboss.ws.extensions.xop.XOPContext - Replace base64 representation on element [xmlName=inputMessage] | DEBUG main org.jboss.ws.extensions.xop.jaxrpc.XOPMarshallerImpl - serialize: [xmlName=attachment] | DEBUG main org.jboss.ws.core.soap.attachment.CIDGenerator - generateFromName: attachment-37b4f42c-7f38-43b1-b905-9e5d3a3b08c8 at ws.jboss.org | DEBUG main org.jboss.ws.extensions.xop.jaxrpc.XOPMarshallerImpl - Created attachment part attachment-37b4f42c-7f38-43b1-b905-9e5d3a3b08c8 at ws.jboss.org, with content-type application/octet-stream | DEBUG main org.jboss.ws.extensions.xop.XOPContext - Restored xop:Include element on [xmlName=attachment] | DEBUG main org.jboss.ws.core.soap.SOAPMessageUnMarshaller - getMimeHeaders from: {X-Powered-By=[Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5], ResponseCodeMessage=OK, http.basic.password=mypassword, Date=[Tue, 26 Jun 2007 13:23:19 GMT], http.basic.username=myusername, Content-Type=[text/xml;charset=UTF-8], Server=[Apache-Coyote/1.1], HEADER={SOAPAction="", Content-Type=text/xml; charset=UTF-8}, Transfer-Encoding=[chunked], NoThrowOnError=true, ResponseCode=200} | DEBUG main org.jboss.ws.core.soap.MessageFactoryImpl - createMessage: [contentType=text/xml; charset=UTF-8] | Instead If I disable WS-Security the Content-Type is correct (and type too) | ... | DEBUG main org.jboss.remoting.MicroRemoteClientInvoker - org.jboss.remoting.transport.http.HTTPClientInvoker at 82751 connected | DEBUG main org.jboss.ws.core.client.RemotingConnectionImpl - Remoting metadata: {http.basic.password=mypassword, http.basic.username=myusername, HEADER={SOAPAction="", Content-Type=multipart/related; type="application/xop+xml"; start=""; | | start-info="text/xml"; | | boundary="----=_Part_0_7896086.1182865340817"}, NoThrowOnError=true} | DEBUG main org.jboss.remoting.transport.http.HTTPClientInvoker - Setting request header with SOAPAction : "" | DEBUG main org.jboss.remoting.transport.http.HTTPClientInvoker - Setting request header with Content-Type : multipart/related; type="application/xop+xml"; start=""; | | start-info="text/xml"; | | boundary="----=_Part_0_7896086.1182865340817" | DEBUG main org.jboss.ws.core.soap.SOAPMessageUnMarshaller - getMimeHeaders from: {Connection=[close], X-Powered-By=[Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5], ResponseCodeMessage=Internal Server Error, http.basic.password=mypassword, Date=[Tue, 26 Jun 2007 13:42:21 GMT], http.basic.username=myusername, Content-Type=[text/xml;charset=UTF-8], Server=[Apache-Coyote/1.1], HEADER={SOAPAction="", Content-Type=multipart/related; type="application/xop+xml"; start=""; | | start-info="text/xml"; | | boundary="----=_Part_0_7896086.1182865340817"}, Transfer-Encoding=[chunked], NoThrowOnError=true, ResponseCode=500} | DEBUG main org.jboss.ws.core.soap.MessageFactoryImpl - createMessage: [contentType=text/xml; charset=UTF-8] | ... | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057717#4057717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057717 From do-not-reply at jboss.com Wed Jun 27 03:47:17 2007 From: do-not-reply at jboss.com (pufferfish) Date: Wed, 27 Jun 2007 03:47:17 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK Message-ID: <14902029.1182930437167.JavaMail.jboss@colo-br-02.atl.jboss.com> Please check this out. http://thesmallpotato.blogspot.com/2007/06/jdk-16-jboss-420-ejb3-web-service-axis2.html Using JDK6 and JBoss 4.2.0GA and it works for me... Good luck guys View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057993#4057993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057993 From do-not-reply at jboss.com Wed Jun 27 03:49:15 2007 From: do-not-reply at jboss.com (pufferfish) Date: Wed, 27 Jun 2007 03:49:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK Message-ID: <29563864.1182930555755.JavaMail.jboss@colo-br-02.atl.jboss.com> Please check this out. http://thesmallpotato.blogspot.com/2007/06/jdk-16-jboss-420-ejb3-web-service-axis2.html Using JDK6 and JBoss 4.2.0GA and it works for me... Good luck guys View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057994#4057994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057994 From do-not-reply at jboss.com Wed Jun 27 04:15:04 2007 From: do-not-reply at jboss.com (mr_d) Date: Wed, 27 Jun 2007 04:15:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <27025575.1182932104276.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello! Thanks for your answers, "richard_opalka" wrote : MTOM attachments do not need to be inlined. I agree, but if mtom is used and it is inlined, I don't see the point of using mtom: we can have the binary parameter inlined like the others. I thought that one of the advantages of mtom was to use xop which describes how to package binary data as an attachment. @davideling I have exactly the same config as you, same Jboss version and JbossWS version. I have also a method with a bean which contains a DataHandler (annoted). But no luck, I get always the same exception. javax.xml.ws.soap.SOAPFaultException: Endpoint {http://foo.org/mtom}ServiceImpl does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData But this problem doesn't change the main problem: to use mtom + ws security with jbossws. I will take a look to the sources when I got time. :oD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058001#4058001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058001 From do-not-reply at jboss.com Wed Jun 27 04:32:36 2007 From: do-not-reply at jboss.com (richard_opalka) Date: Wed, 27 Jun 2007 04:32:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <1173014.1182933156644.JavaMail.jboss@colo-br-02.atl.jboss.com> "mr_d" wrote : | I agree, but if mtom is used and it is inlined, I don't see the point of using mtom: we can have the binary parameter inlined like the others. I thought that one of the advantages of mtom was to use xop which describes how to package binary data as an attachment. @mr_d Well MTOM can be inlined or not. If you're dealing with small attachments, such as < 5k images or other binary data I don't see the problem if the MTOM attachments are inlined. If you're dealing with bigger attachments then I agree inlined MTOM attachmetns are not good for you. But it depends on the SOAP stack how it will deal with MTOM attachments. For example, some SOAP stacks are configured the following way: * if attachment size is lesser than some preconfigured size then MTOM attachment is inlined * if attachment size is greater than some preconfigured size then MTOM attachment is sent as MIME part. Isn't this your problem? Rio View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058006#4058006 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058006 From do-not-reply at jboss.com Wed Jun 27 06:14:26 2007 From: do-not-reply at jboss.com (mr_d) Date: Wed, 27 Jun 2007 06:14:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: MTOM + WS Security = problem Message-ID: <7124429.1182939266373.JavaMail.jboss@colo-br-02.atl.jboss.com> "richard_opalka" wrote : | * if attachment size is lesser than some preconfigured size then MTOM attachment is inlined | * if attachment size is greater than some preconfigured size then MTOM attachment is sent as MIME part. | Thank you for this explanation, Yes, Im working with larger file size such as 1-2MB. So, my problem is to use correctly mtom + ws security with jbossws. :oD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058059#4058059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058059 From do-not-reply at jboss.com Wed Jun 27 06:54:17 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Wed, 27 Jun 2007 06:54:17 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Jboss 4.2.0 and SQL Server Message-ID: <10277253.1182941657355.JavaMail.jboss@colo-br-02.atl.jboss.com> i am running a ejb3 aplication on jboss 4.2.0. It worked fine, but i've added new entities unreleated with the old ones and it raises next exception. Can anyone help me? 11:58:35,632 WARN [JDBCExceptionReporter] SQL Error: 208, SQLState: 42S02 11:58:35,632 ERROR [JDBCExceptionReporter] [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]El nombre de objeto 'usuario_concesion' no es v?lido. 11:58:35,632 WARN [JDBCExceptionReporter] SQL Error: 16945, SQLState: HY000 11:58:35,632 ERROR [JDBCExceptionReporter] [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]El cursor no ha sido declarado. 12:01:41,798 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57df8d:759:4682264b:cf invoked while multiple threads active within it. 12:01:41,798 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57df8d:759:4682264b:cf aborting with 1 threads active! 12:45:44,181 ERROR [LazyInitializationException] failed to lazily initialize a collection of role: com.satdatatelecom.satdataweb.model.usuario.ejb.UsuarioEJB.concesiones, no session or session was closed org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.satdatatelecom.satdataweb.model.usuario.ejb.UsuarioEJB.concesiones, no session or session was closed at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358) at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:343) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:483) at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.finders.FindUsuarioAction.execute(FindUsuarioAction.java:31) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058075#4058075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058075 From do-not-reply at jboss.com Wed Jun 27 08:53:41 2007 From: do-not-reply at jboss.com (davideling) Date: Wed, 27 Jun 2007 08:53:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.0 and SQL Server Message-ID: <2205739.1182948821498.JavaMail.jboss@colo-br-02.atl.jboss.com> Your problem is Hibernate related. When you load a persistent object it's related objects are lazily loaded. That is these objects aren't actually loaded, but will be loaded only when you try to access them. The problem take place when you access to lazily loaded object proxy when it's owner session is terminated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058158#4058158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058158 From do-not-reply at jboss.com Wed Jun 27 10:19:26 2007 From: do-not-reply at jboss.com (rohstoffmond) Date: Wed, 27 Jun 2007 10:19:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBoss WSSecurity and .Net Client Message-ID: <7536784.1182953966198.JavaMail.jboss@colo-br-02.atl.jboss.com> I've tried a lot to interop between .Net (C#) Client using WSE 3.0 and Jboss 4.2.0 Webservices secured with WSSecurity (Signing and encrypting the webservices). But still it doesn't work... So if anybody has solved this problem, or knows where I can find documentation/help please let me know... WSE 3.0 is no requirement, so any (proprietary) solution is ok as well View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058208#4058208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058208 From do-not-reply at jboss.com Wed Jun 27 11:29:47 2007 From: do-not-reply at jboss.com (florian79) Date: Wed, 27 Jun 2007 11:29:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: advice needed Message-ID: <26733248.1182958187665.JavaMail.jboss@colo-br-02.atl.jboss.com> I have the same problem by using an javascript/AJAX client. That is the xml, that I send to the webservice: | | and that is the xml of the response: | env:ServerUnsupported content type: application/x-www-form-urlencoded | | what is the meaning of this Exception: "Unsupported content type: application/x-www-form-urlencoded" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058252#4058252 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058252 From do-not-reply at jboss.com Wed Jun 27 13:31:41 2007 From: do-not-reply at jboss.com (chlong) Date: Wed, 27 Jun 2007 13:31:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - disabling wsdl publication Message-ID: <17123365.1182965501777.JavaMail.jboss@colo-br-02.atl.jboss.com> I am currently running a fresh install of JBoss 4.2.0. I am using JBossWS with EJB3 for web services. I have reviewed the WebContext annotation, but it does not appear to provide a way to suppress the publication of the wsdl on server startup (only allows me to secure it). I understand the wsdl can be secured, but would like it not to be published at all in our production environment. Is this possible? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058343#4058343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058343 From do-not-reply at jboss.com Thu Jun 28 02:43:44 2007 From: do-not-reply at jboss.com (mengyi) Date: Thu, 28 Jun 2007 02:43:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - help on web services feasibility study.. Message-ID: <10609229.1183013024359.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, I am new to both web services and jboss ...... Basically, ideally, i would like to have things work as follows:- Parties: P1. Third party Web Services Provider running on .NET P2. J2EE 1.4 Application running on JBOSS (v4.20), which consumes services from P1 and provides services for P3 P3. J2SE RCP clients Security: X.509 certificate based authentication, signature over https for all interactions. So, what exactly do a need for P2 and P3??? I suppose JBossWS should work for P2, but unfortunately both quick start and user guide links are not working, at least today... http://jbws.dyndns.org/mediawiki/index.php/Quick_Start http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide My main doubts is on P3, is there any readily available api that supports WS-security? any comments or recommendations are welcomed. thanks a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058559#4058559 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058559 From do-not-reply at jboss.com Thu Jun 28 04:45:48 2007 From: do-not-reply at jboss.com (sashaxiv) Date: Thu, 28 Jun 2007 04:45:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.0 and SQL Server Message-ID: <14643018.1183020348194.JavaMail.jboss@colo-br-02.atl.jboss.com> i can't understand. I've debug the aplication with jboss ide to see the variable values. The entity usuario has a List of concesiones. When i run with debug i could see the value of this list and i was ok, it has the list of Concesiones i wanted but it crashes when calling the getList method (com.sun.jdi.InvocationException occurred invoking method) and after it jboss crashes .10:36:36,147 ERROR [LazyInitializationException] illegal access to loading collection | org.hibernate.LazyInitializationException: illegal access to loading collection | at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) | at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) | at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:483) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.finders.FindUsuarioAction.execute(FindUsuarioAction.java:31) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.LoginUsuarioAction.execute(LoginUsuarioAction.java:65) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.UsuarioFacadeEJB.loginUsuarioVO(UsuarioFacadeEJB.java:198) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | 10:36:38,022 ERROR [LazyInitializationException] illegal access to loading collection | org.hibernate.LazyInitializationException: illegal access to loading collection | at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) | at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) | at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:483) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.finders.FindUsuarioAction.execute(FindUsuarioAction.java:31) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.LoginUsuarioAction.execute(LoginUsuarioAction.java:65) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.UsuarioFacadeEJB.loginUsuarioVO(UsuarioFacadeEJB.java:198) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | 10:36:40,272 ERROR [LazyInitializationException] illegal access to loading collection | org.hibernate.LazyInitializationException: illegal access to loading collection | at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) | at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) | at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:483) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.finders.FindUsuarioAction.execute(FindUsuarioAction.java:31) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.LoginUsuarioAction.execute(LoginUsuarioAction.java:65) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.UsuarioFacadeEJB.loginUsuarioVO(UsuarioFacadeEJB.java:198) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | 10:41:02,966 ERROR [LazyInitializationException] illegal access to loading collection | org.hibernate.LazyInitializationException: illegal access to loading collection | at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) | at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) | at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:483) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.finders.FindUsuarioAction.execute(FindUsuarioAction.java:31) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.actions.LoginUsuarioAction.execute(LoginUsuarioAction.java:65) | at com.satdatatelecom.satdataweb.model.usuariofachada.ejb.UsuarioFacadeEJB.loginUsuarioVO(UsuarioFacadeEJB.java:198) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | 10:41:34,293 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57df8d:11bc:46836fca:53 invoked while multiple threads active within it. | 10:41:34,293 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57df8d:11bc:46836fca:53 aborting with 1 threads active! | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058607#4058607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058607 From do-not-reply at jboss.com Thu Jun 28 23:53:57 2007 From: do-not-reply at jboss.com (nagmca) Date: Thu, 28 Jun 2007 23:53:57 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Web service works in 4.0.2 but not in 4.0.5 Message-ID: <11377500.1183089237491.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a document oriented web service which is working fine in 4.0.2. When I deploy this in 4.0.5 , I am not seeing any problems in the console and it says webservice is deployed. If I goto localhost:8080/jbossws/services, I am seeing my webservices as registered. But If I try to view the web service then getting 403 Access to the requested resource has been denied. What would be the problem? Why am I not able to see the wsdl file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058999#4058999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058999 From do-not-reply at jboss.com Fri Jun 29 00:40:56 2007 From: do-not-reply at jboss.com (rickcr) Date: Fri, 29 Jun 2007 00:40:56 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Accessing jaxws web service gives error complaining about no Message-ID: <32787620.1183092056428.JavaMail.jboss@colo-br-02.atl.jboss.com> This is driving me nuts. I have installed jbossws on jboss (both on 4.0.5 and 4.2). I deploy my ear and the webservice is created and I can access the wsdl. I then use wsconsume to create some stubs. For now, I'm just trying to test this from a client running on the same server, so I thought I'd only need the generated Service stub. I call it from my client as: | SpecProcessorService specService = new SpecProcessorService(); | SpecProcessor specProcessor = specService.getSpecProcessorPort(); | //... | It errors out on trying to get the Port... | 00:27:39,375 ERROR [SpecProcessClient] Error in SpecProcessClient client: | org.jboss.ws.WSException: Cannot load java type: net.learntechnology.sample.ejb.slsb.jaxws.ProcessSpec | at org.jboss.ws.metadata.umdm.ParameterMetaData.getJavaType(ParameterMetaData.java:275) | ... | Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: net.learntechnology.sample.ejb.slsb.jaxws.ProcessSpec | ... What I don't even get is why it's complaining about not being able to find: net.learntechnology.sample.ejb.slsb.jaxws.ProcessSpec I don't even have a package by that name. I have packages that start with net.learntechnology.sample.ejb.slsb but nothing with jaxws.ProcessSpec I'm really stumped here. Any idea what I'm doing wrong? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059002#4059002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059002 From do-not-reply at jboss.com Fri Jun 29 06:11:30 2007 From: do-not-reply at jboss.com (patel_123) Date: Fri, 29 Jun 2007 06:11:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - problem with web method returning list Message-ID: <10656474.1183111890176.JavaMail.jboss@colo-br-02.atl.jboss.com> hi I am exposing ejb components as webservice.Initially i exposed one method as web method,that returns String.This works fine.Next i tried another method which returns array of objects.This leads to following error.... Caused by: javax.xml.rpc.JAXRPCException: org.jboss.xb.binding.JBossXBValueFormatException: Java value for XSD boolean type expected to be an instance of java.lang.Boolean or java.lang.Number. But the value is of type java.util.ArrayList at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:986) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:171) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) at org.jboss.ws.soap.SAAJElementWriter.printInternal(SAAJElementWriter.java:163) at org.jboss.ws.soap.SAAJElementWriter.print(SAAJElementWriter.java:142) at org.jboss.ws.soap.SAAJElementWriter.printSOAPElement(SAAJElementWriter.java:91) at org.jboss.ws.server.ServiceEndpoint.postProcessResponse(ServiceEndpoint.java:280) ... 25 more Caused by: org.jboss.xb.binding.JBossXBValueFormatException: Java value for XSD boolean type expected to be an instance of java.lang.Boolean or java.lang.Number. But the value is of type java.util.ArrayList at org.jboss.xb.binding.SimpleTypeBindings.marshal(SimpleTypeBindings.java:1120) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalCharacters(MarshallerImpl.java:995) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalSimpleType(MarshallerImpl.java:471) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementType(MarshallerImpl.java:415) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(MarshallerImpl.java:331) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOccurence(MarshallerImpl.java:311) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(MarshallerImpl.java:730) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroupSequence(MarshallerImpl.java:920) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroup(MarshallerImpl.java:860) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(MarshallerImpl.java:641) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalComplexType(MarshallerImpl.java:608) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementType(MarshallerImpl.java:419) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(MarshallerImpl.java:331) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOccurence(MarshallerImpl.java:311) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshallInternal(MarshallerImpl.java:210) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshal(MarshallerImpl.java:168) at org.jboss.ws.jaxb.JBossXBMarshallerImpl.marshal(JBossXBMarshallerImpl.java:146) at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer.java:107) at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElement.java:157) at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:817) at org.jboss.ws.soap.SOAPContentElement.handleMTOMTransitions(SOAPContentElement.java:1015) at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:968) ... 33 more could any body tell me what went wrong? in the wsdl doc, - its taking type as boolean but actaully it should be of type list.... i dont know where i went wrong....please anybody help me View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059090#4059090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059090 From do-not-reply at jboss.com Fri Jun 29 10:35:38 2007 From: do-not-reply at jboss.com (mmoura) Date: Fri, 29 Jun 2007 10:35:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Web Service Client : Could not transmit message Message-ID: <32111218.1183127738970.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm getting the same error in JBoss 4.0.5. Have you ever got to solve this problem? In a few words I'm trying to consume a web service hosted in what looks like to be a .NET server from a client running in JBoss 4.0.5. The same client running from a Java stand-alone application runs fine, with no transport errors. I'm able to receive a SOAP response with no problems. So the issue resides in the client web app. By the way, both the stand-alone and the web apps use the same code to build and send the soap messages. The only difference is that the web client used JNDI to retrieve the service interface. The client sends two different types of message to the server. One of them is small and runs fine. The other one sends a byte array and is quite big. That's the one that fails, returning a HTTP 400 - Bad request. Looking at the SOAP request message I could see that it was not being well formated by the JAX-RPC client. Please look at the bold Binario attribute below (it should be a Hex coded string - again, it works fine outside of JBoss - I'm not posting the correct message here): | | | | | | | | CN=AC CertiSign SRF, OU=Secretaria da Receita Federal - SRF, O=ICP-Brasil, C=BR | da2bac79587b4129976d42d04c29aec89fc972d0 | 2007-06-28-03:00 | 10:55:48.000-03:00 | | | 1164.0 | 0.0 | | | | | | Here's the stack trace (similar to the one posted above): | br.com.certisign.ws.receita.client.exceptions.ServiceFailureException: br.com.certisign.ws.receita.client.exceptions.WSException: java.rmi.RemoteException: Call invocation failed: Could not transmit message; nested exception is: | javax.xml.soap.SOAPException: Could not transmit message | at br.com.certisign.ws.receita.client.control.ReceitaWSClientServlet.sendLCR(ReceitaWSClientServlet.java:298) | at br.com.certisign.ws.receita.client.control.ReceitaWSClientServlet.init(ReceitaWSClientServlet.java:179) | at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) | at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) | at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3951) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4225) | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) | at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) | at org.jboss.web.WebModule.startModule(WebModule.java:83) | at org.jboss.web.WebModule.startService(WebModule.java:61) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy38.start(Unknown Source) | at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy39.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: br.com.certisign.ws.receita.client.exceptions.WSException: java.rmi.RemoteException: Call invocation failed: Could not transmit message; nested exception is: | javax.xml.soap.SOAPException: Could not transmit message | at br.com.certisign.ws.receita.client.ws.ReceitaWSClient.sendMessageACLista(ReceitaWSClient.java:32) | at br.com.certisign.ws.receita.client.control.ReceitaWSClientServlet.sendLCR(ReceitaWSClientServlet.java:284) | ... 92 more | Caused by: java.rmi.RemoteException: Call invocation failed: Could not transmit message; nested exception is: | javax.xml.soap.SOAPException: Could not transmit message | at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:718) | at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) | at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) | at $Proxy55.recebeLista(Unknown Source) | at br.com.certisign.ws.receita.client.ws.ReceitaWSClient.sendMessageACLista(ReceitaWSClient.java:25) | ... 93 more | Caused by: javax.xml.soap.SOAPException: Could not transmit message | at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:204) | at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:687) | ... 97 more | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:201) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81) | at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) | at org.jboss.remoting.Client.invoke(Client.java:525) | at org.jboss.remoting.Client.invoke(Client.java:488) | at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189) | ... 98 more | Caused by: org.jboss.ws.WSException: Invalid HTTP server response [400] - Bad Request | at org.jboss.ws.binding.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:73) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175) | ... 103 more | My web.xml follows: ReceitaWSClientServlet ReceitaWSClientServlet br.com.certisign.ws.receita.client.control.ReceitaWSClientServlet propertiesFile WEB-INF/config/client.properties javax.xml.soap.MessageFactory com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl 1 ReceitaWSClientServlet /ReceitaWSClientServlet/* 30 index.jsp index.html index.htm services/ReceitaWSServer br.com.certisign.ws.receita.lcr.LCRReceber WEB-INF/lcrreceber.wsdl WEB-INF/jaxrpc-mapping.xml br.com.certisign.ws.receita.lcr.LCRReceberSoap | | | I tried to deploy the same app in JBoss 4.2.0 and got an exception: | | | org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.kernel.spi.registry.KernelRegistryEntryNotFoundException: Entry not found with name ServiceRefHandler) | | | | I did not manage to configure the right Handler in the web.xml file. I tried something like the code below but it did not work: | | | | | Service Ref Handler | | org.jboss.ws.core.jaxws.client.ServiceRefHandlerJAXWS | | | | | | | I'd like to have the app running in 4.0.5. | | I can send you more information if necessary. | | Any help will be greatly appreciated! | | Thanks, | Marcel | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059204#4059204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059204 From do-not-reply at jboss.com Fri Jun 29 17:20:26 2007 From: do-not-reply at jboss.com (asarubbi) Date: Fri, 29 Jun 2007 17:20:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Web Service Client : Could not transmit message Message-ID: <17323563.1183152026031.JavaMail.jboss@colo-br-02.atl.jboss.com> solved. not using JWSDP but JBossWS. drop me a line if you want samples. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059338#4059338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059338 From do-not-reply at jboss.com Fri Jun 29 17:39:12 2007 From: do-not-reply at jboss.com (mmoura) Date: Fri, 29 Jun 2007 17:39:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Web Service Client : Could not transmit message Message-ID: <17544143.1183153152858.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for your response. Somehow I am not able to contact you through the forum. I was only able to get your user id. Can you send a note to the following temp e-mail? mmmm.rj at gmail dot com We can go on from there if you don't mind. Thanks again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059341#4059341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059341 From do-not-reply at jboss.com Sat Jun 30 05:25:37 2007 From: do-not-reply at jboss.com (kkarthikeyankrr) Date: Sat, 30 Jun 2007 05:25:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Intercepting SOAP message Message-ID: <32185067.1183195537822.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi , This is karthick and i'm new to webservices.Can anyone tell me how to intercept the SOAP message in server and client side.I have done the SOAP message intercepting at server side by using handler.In this I have mentioned some information in my service.But I dont want like this I want to intercept with the help of deployment descriptor.I have downloaded many examples from net.so plz dont give me the link.Plz tel me whether I have to create the separate WSDD file for this or otherwise I can use my web.xml to configure those details(about handlers)? Then tell me where I have to keep that wsdd file. My personal id:kkarthikeyankrr at gmail.com Thanks&Regards Karthick View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059366#4059366 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059366 From do-not-reply at jboss.com Sat Jun 30 09:24:38 2007 From: do-not-reply at jboss.com (rickcr) Date: Sat, 30 Jun 2007 09:24:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Accessing jaxws web service gives error complaining abou Message-ID: <17699681.1183209878280.JavaMail.jboss@colo-br-02.atl.jboss.com> I figured out the problem even though the errors being thrown didn't really help. For some reason, if I start the process of calling my webserivce from a bean annotated as JMX component, the webservice call does not work. If I start the call from say a Servlet everything is fine. Not sure why I can't use a JMX component though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059380#4059380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059380