From do-not-reply at jboss.com Tue Feb 3 10:16:35 2009 From: do-not-reply at jboss.com (jhalliday) Date: Tue, 3 Feb 2009 10:16:35 -0500 (EST) Subject: [jbossws-users] [JBossWS] - mysterious vanishing Service21 Message-ID: <31484255.1233674195101.JavaMail.jboss@colo-br-02.atl.jboss.com> In JBossAS branch5x the class javax.xml.ws.Service21 seems to have vanished from jbossws-native-jaxws-ext.jar Was this intentional? It's broken things that work fine on AS 5.0.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206588#4206588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206588 From do-not-reply at jboss.com Tue Feb 3 10:38:57 2009 From: do-not-reply at jboss.com (skajotde) Date: Tue, 3 Feb 2009 10:38:57 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WeFault and throws declaration Message-ID: <22262305.1233675537567.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I have that structure @WebFault public class BaseAppException { | ExceptionXBVO getFaultInfo() { ...} | } | | @WebFault public class OtherAppException extends BaseAppException { | ExceptionXBVO getFaultInfo() { super.getFa...} | } | | public interface IServiceOne { | @WebMethod public String one(@WebParam("xxx" xxx) throws BaseAppException; | } | | @WebService [...other annotations...] public class SerwiceOne implements IServiceOne { | @WebMethod public String one(@WebParam("xxx" xxx) throws BaseAppException { | throw new OtherAppException("info"); | } | } | | If web service declare BaseAppException but method throws OtherAppException which inherit on it. Should JBoss WS throw SOAPFaultException or OtherAppException or BaseAppException ? I think best solution is to catch OtherAppException by client but in my config is catched SOAPFaultException. When I add OtherAppException to throws declaration then is works as excepted. Does JBoss WS require adding to throws decalarion all possible exception, iheritance doesn't enough ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206608#4206608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206608 From do-not-reply at jboss.com Tue Feb 3 12:05:04 2009 From: do-not-reply at jboss.com (klogube) Date: Tue, 3 Feb 2009 12:05:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Webservice deployment error: Endpoint already registered Message-ID: <30529413.1233680705012.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, Greetings. I need you ppl help to solve my Java Webservices deployment issue. I am developing Java WS through Jdeveloper11g and trying to deploy the WS.WAR in to JBOSS 4.2.3GA server from Jdeveloper11g. But getting error when I am restarting the server after deployment. Below is the error --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo at a99914c8 { url=file:/opt/jboss-4.2.3.GA/server/default/deploy/Testing-SampleWebServices-context-root.war } deployer: MBeanProxyExt[jboss.web:service=WebServer] status: Deployment FAILED reason: Endpoint already registered: jboss.ws:context=Testing-SampleWebServices-context-root,endpoint=DateTestingWSSoapHttpPort state: FAILED watch: file:/opt/jboss-4.2.3.GA/server/default/deploy/Testing-SampleWebServices-context-root.war altDD: null lastDeployed: 1233678646914 lastModified: 1233678644000 Help me to solve this "Endpoint already registered" error, which is stop our development completely and our project is in production stage and cant able to make progress due to this error. Due to this error we couldn't able to create the client application for our Web service. (Note: I can able to see the list of WS's deployed in to JBOSS under: http://localhost:8080/jbossws/services which display the Endpoint name and address. But cant able to access the URL.) Thanks in advance klogube View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206650#4206650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206650 From do-not-reply at jboss.com Tue Feb 3 12:38:13 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Tue, 3 Feb 2009 12:38:13 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Should @EJB work in Pojo's deployed as a WebService? Message-ID: <17297085.1233682693300.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a pojo which is being deployed as a servlet in a war file. The goal is to expose the pojo as a WS endpoint (Metro endpoint actually). If I add any J2EE annotations (@EJB or @Resource) they come back as null. Is the expectation that Pojos deployed should be able to use these annotations? -- bk View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206671#4206671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206671 From do-not-reply at jboss.com Tue Feb 3 13:37:22 2009 From: do-not-reply at jboss.com (PeterJ) Date: Tue, 3 Feb 2009 13:37:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Should @EJB work in Pojo's deployed as a WebService? Message-ID: <2450145.1233686242260.JavaMail.jboss@colo-br-02.atl.jboss.com> Which version of JBoss AS? I don't think that those annotations are supported until JBoss AS 5.0.0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206692#4206692 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206692 From do-not-reply at jboss.com Tue Feb 3 14:09:52 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Tue, 3 Feb 2009 14:09:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Should @EJB work in Pojo's deployed as a WebService? Message-ID: <7517503.1233688192614.JavaMail.jboss@colo-br-02.atl.jboss.com> I am running this in JBoos 5.0, Using JbossWS-Metro 3.0.5 as the web container. In addition, I have updated the web.xml as described at the end of this post: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=143277 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206701#4206701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206701 From do-not-reply at jboss.com Wed Feb 4 01:25:38 2009 From: do-not-reply at jboss.com (goveasr) Date: Wed, 4 Feb 2009 01:25:38 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBWS-2208- Failing to deploy WS containing binding objects t Message-ID: <19379705.1233728738518.JavaMail.jboss@colo-br-02.atl.jboss.com> We are using Jboss 4.2.3.GA and currently facing with the ERROR referenced in the above BUG report. Is there any alternative to this issue or any workaround or patch from Jboss. Thanks Rohan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206794#4206794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206794 From do-not-reply at jboss.com Wed Feb 4 06:23:08 2009 From: do-not-reply at jboss.com (skajotde) Date: Wed, 4 Feb 2009 06:23:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WeFault and throws declaration Message-ID: <6489192.1233746588199.JavaMail.jboss@colo-br-02.atl.jboss.com> I see that in 3.0.3.GA Tag in svn there is code void org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processWebMethod which add fault metadata from declaring exceptions. | // Add faults | for (Class exClass : method.getExceptionTypes()) | if (!RemoteException.class.isAssignableFrom(exClass)) | addFault(opMetaData, exClass); I'm reading JSR-224 but dont see what spec talk about this situation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206882#4206882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206882 From do-not-reply at jboss.com Wed Feb 4 08:58:23 2009 From: do-not-reply at jboss.com (mfueser) Date: Wed, 4 Feb 2009 08:58:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: MTOM enabled webservice, no access to base64 fields / no Message-ID: <30956482.1233755903947.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! That was the problem: @XmlElement(name = "Document") The generated code didn??t annotate the namespace for the document-element. This topic can be closed now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206973#4206973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206973 From do-not-reply at jboss.com Wed Feb 4 11:37:06 2009 From: do-not-reply at jboss.com (jorgemoralespou_2) Date: Wed, 4 Feb 2009 11:37:06 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Propagate an attachment when using JBossWS as service proxy Message-ID: <24474854.1233765426470.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I know that probably the name of the topic is misleading, but my english is not as good as I would like. I'm using JBossWS native 3.0.4 to make a service that acts as a proxy to access the same service in another server, but performing some policies. I want to proxy a service that supports attachments, and I have made an northbound handler to get the attachment, and then setting the attachment in a southbound handler. The problem is how can I propagate this attachment from the northbound hadler to the southbound handler. I know probably this has nothing to do with JBossWS, but probably you people using JBossWS has had this same issue before. I'm thinking of something like a Context that can be attached in the northbound, with the attachment, and freeing it in the southbound handler if message is propagated, or in the northbound handler if an error has ocurred before getting to this handler. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207055#4207055 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207055 From do-not-reply at jboss.com Thu Feb 5 11:19:11 2009 From: do-not-reply at jboss.com (redCar) Date: Thu, 5 Feb 2009 11:19:11 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Webservice Timeout Message-ID: <3675683.1233850751211.JavaMail.jboss@colo-br-02.atl.jboss.com> Hallo, I want to enlarge the JBoss-WS timeout for my application. I use the WS from JBoss 5.0.0 GA After getting the port with: | org.opentrafficsystems.ots2.OTS2WebServices m_port = service.getOTS2WebSoapServices(); | I set the timeout: | ((BindingProvider) m_port).getRequestContext().put("org.jboss.ws.timeout", 1000 * 60 * 30); | But after 5 Minutes I get this exception: javax.xml.ws.soap.SOAPFaultException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active! | at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171) | at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94) | at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240) | at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) | at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103) | at $Proxy32.tConnect(Unknown Source) | How can I enlarge the WS-Timeout? Thanks, Werner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207421#4207421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207421 From do-not-reply at jboss.com Fri Feb 6 03:32:48 2009 From: do-not-reply at jboss.com (redCar) Date: Fri, 6 Feb 2009 03:32:48 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Webservice Timeout Message-ID: <24923520.1233909168306.JavaMail.jboss@colo-br-02.atl.jboss.com> Good morning, for my project I need to enlarge the server timeout. Is it possible to enlarge it, and where can I do this? Thanks, Werner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207604#4207604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207604 From do-not-reply at jboss.com Fri Feb 6 04:55:44 2009 From: do-not-reply at jboss.com (chawax) Date: Fri, 6 Feb 2009 04:55:44 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Only JBoss AS support ? Message-ID: <13958012.1233914144651.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, A simple question but I can't find a clear answer to it ... Can I use JBossWS on any JEE application servers (Tomcat, Websphere, ... ) ? Or is it supported only on JBoss AS ? Regards, Olivier View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207632#4207632 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207632 From do-not-reply at jboss.com Fri Feb 6 12:16:41 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Fri, 6 Feb 2009 12:16:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Native versus Metro Message-ID: <28073266.1233940601438.JavaMail.jboss@colo-br-02.atl.jboss.com> Is there an up2date version of this: http://wiki.apache.org/ws/StackComparison I have some services which work under Native, but not under Metro. I am very interested in WCF integration.. and some of the items listed here (tcp transport) would be very important. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207793#4207793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207793 From do-not-reply at jboss.com Fri Feb 6 17:01:13 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Fri, 6 Feb 2009 17:01:13 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Class cast excpetion with an RM client Message-ID: <23470161.1233957673880.JavaMail.jboss@colo-br-02.atl.jboss.com> I am attempting to test a RM client as a stand alone jar file using JbossWS-native against a service which is deployed in a Jboss 5.0 container. I have a simple client which I generated using wsconsume. I am following the directions from http://jbossws.jboss.org/mediawiki/index.php?title=WS_Reliable_Messaging and am adding the Addressing and RM Handlers to the client port. When I run (with only jars from $JBOSS_HOME/client on my classpath) I get the following exception: javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.ws.handler.SOAPMessageContextImpl cannot be cast to org.jboss.ws.core.CommonMessageContext at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnRequest(ClientSOAPHandlerTube.java:168) at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:100) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) at com.sun.xml.ws.client.Stub.process(Stub.java:235) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103) at $Proxy27.runAction(Unknown Source) I appear to be doing the same code as the samples. Are thee other examples I could look at? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207869#4207869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207869 From do-not-reply at jboss.com Sat Feb 7 05:29:46 2009 From: do-not-reply at jboss.com (skajotde) Date: Sat, 7 Feb 2009 05:29:46 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Redeploy Endpoint already registered Message-ID: <30795898.1234002586791.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all! Problem like here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=135099 and not solved.h Case: When deploying application occurs problem like ClassNotFoundException, next I remove ear so all beans should be undeployed but seems not all. When repair ear and copying it to deploy dir JBoss again deploy this app (redeploy) and while deploying module jws with JBossWs services is problem anonymous wrote : 11:07:39,018 ERROR [MainDeployer] Could not start deployment: file:/systemYYY/jboss-developerski/server/developerski01/tmp/deploy/tmp454525987406062238920-systemYYY-xxx-jee-1.0-SNAPSHOT.ear-contents/ystemYYY-xxx-jws-1.0-SNAPSHOT.jar | java.lang.IllegalStateException: Endpoint already registered: jboss.ws:context=jws/xxx,endpoint=SerwisyXxxRoleJWS I think JWS beans should be fully undeployed on first deploy when catch ClassCastException. It is bug ? JBoss 4.2.3 GA JBossWS Version: jbossws-native-3.0.3.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207914#4207914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207914 From do-not-reply at jboss.com Sat Feb 7 05:31:55 2009 From: do-not-reply at jboss.com (skajotde) Date: Sat, 7 Feb 2009 05:31:55 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Redeploy Endpoint already registered Message-ID: <32830159.1234002715651.JavaMail.jboss@colo-br-02.atl.jboss.com> Question from mentioned post "Do the errors you get somehow influence the deploy/undeploy?" Yes, these errors fails redeploy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207915#4207915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207915 From do-not-reply at jboss.com Sun Feb 8 06:18:41 2009 From: do-not-reply at jboss.com (Andrechan) Date: Sun, 8 Feb 2009 06:18:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Errors Web Service Client Message-ID: <9215189.1234091921632.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All Could you please help me? I'm a new bie of Web Services I've created an EJB3 application and transformed a session bean into a web service. I've tested everything and it works. Then I've generated a simple Web Service Client using eclipse (develop client) I've created this class public class test { | | | public static void main(String[] args) { | | NavigatoreBeanProxy pp = new NavigatoreBeanProxy(); | | try { | pp.setPosition(10, 40, 34); | } catch (RemoteException e) { | | | e.printStackTrace(); | } And it gives the following error if run as a java application: | AxisFault | faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException | faultSubcode: | faultString: org.xml.sax.SAXParseException: Premature end of file. | faultActor: | faultNode: | faultDetail: | {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: Premature end of file. | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) | at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1411) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1058) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) | at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) | at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) | at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) | at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) | at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) | at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) | at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) | at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) | at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) | 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 session.NavigatoreBeanBindingStub.setPosition(NavigatoreBeanBindingStub.java:403) | at session.NavigatoreBeanProxy.setPosition(NavigatoreBeanProxy.java:80) | at session.test.main(test.java:15) | | {http://xml.apache.org/axis/}hostname:admin-836482f5f | | org.xml.sax.SAXParseException: Premature end of file. | at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) | at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) | at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) | at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) | 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 session.NavigatoreBeanBindingStub.setPosition(NavigatoreBeanBindingStub.java:403) | at session.NavigatoreBeanProxy.setPosition(NavigatoreBeanProxy.java:80) | at session.test.main(test.java:15) | Caused by: org.xml.sax.SAXParseException: Premature end of file. | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) | at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1411) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1058) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) | at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) | at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) | at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) | at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) | at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) | at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) | at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) | ... 11 more | Instead this other error if run on the server Jboss 4.2 11:58:16,062 INFO [Server] Starting JBoss (MX MicroKernel)... | 11:58:16,078 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) | 11:58:16,078 INFO [Server] Home Dir: C:\Programmi\jboss-4.2.2.GA | 11:58:16,078 INFO [Server] Home URL: file:/C:/Programmi/jboss-4.2.2.GA/ | 11:58:16,078 INFO [Server] Patch URL: null | 11:58:16,078 INFO [Server] Server Name: default | 11:58:16,078 INFO [Server] Server Home Dir: C:\Programmi\jboss-4.2.2.GA\server\default | 11:58:16,078 INFO [Server] Server Home URL: file:/C:/Programmi/jboss-4.2.2.GA/server/default/ | 11:58:16,078 INFO [Server] Server Log Dir: C:\Programmi\jboss-4.2.2.GA\server\default\log | 11:58:16,078 INFO [Server] Server Temp Dir: C:\Programmi\jboss-4.2.2.GA\server\default\tmp | 11:58:16,078 INFO [Server] Root Deployment Filename: jboss-service.xml | 11:58:17,109 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc. | 11:58:17,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b23,Sun Microsystems Inc. | 11:58:17,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 | 11:58:18,218 INFO [Server] Core system initialized | 11:58:20,500 INFO [WebService] Using RMI server codebase: http://localhost:8083/ | 11:58:20,500 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml | 11:58:22,281 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. | 11:58:22,281 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer | 11:58:22,500 INFO [TransactionManagerService] Starting recovery manager | 11:58:22,609 INFO [TransactionManagerService] Recovery manager started | 11:58:22,609 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference | 11:58:24,890 INFO [EJB3Deployer] Starting java:comp multiplexer | 11:58:25,218 INFO [STDOUT] no object for null | 11:58:25,218 INFO [STDOUT] no object for null | 11:58:25,234 INFO [STDOUT] no object for null | 11:58:25,234 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType | 11:58:25,250 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType | 11:58:26,890 INFO [NativeServerConfig] JBoss Web Services - Native | 11:58:26,890 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837) | 11:58:27,796 INFO [Embedded] Catalina naming disabled | 11:58:27,968 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\eclipse\jre\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/eclipse/jre/bin/client;C:/eclipse/jre/bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programmi\ATI Technologies\ATI.ACE\Core-Static;C:\Programmi\File comuni\Adobe\AGL;C:\Sun\SDK\bin | 11:58:28,000 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 | 11:58:28,015 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 | 11:58:28,015 INFO [Catalina] Initialization processed in 210 ms | 11:58:28,015 INFO [StandardService] Starting service jboss.web | 11:58:28,015 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA | 11:58:28,046 INFO [Catalina] Server startup in 30 ms | 11:58:28,218 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/ | 11:58:29,015 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/ | 11:58:29,140 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/ | 11:58:29,234 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ | 11:58:29,937 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/ | 11:58:30,375 INFO [MailService] Mail Service bound to java:/Mail | 11:58:30,656 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar | 11:58:30,687 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar | 11:58:30,718 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar | 11:58:30,750 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar | 11:58:30,796 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar | 11:58:30,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar | 11:58:31,046 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar | 11:58:31,046 INFO [QuartzResourceAdapter] start quartz!!! | 11:58:31,109 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main | 11:58:31,125 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. | 11:58:31,125 INFO [RAMJobStore] RAMJobStore initialized. | 11:58:31,125 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' | 11:58:31,125 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 | 11:58:31,125 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. | 11:58:31,390 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' | 11:58:31,453 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' | 11:58:32,765 INFO [A] Bound to JNDI name: queue/A | 11:58:32,765 INFO [B] Bound to JNDI name: queue/B | 11:58:32,765 INFO [C] Bound to JNDI name: queue/C | 11:58:32,781 INFO [D] Bound to JNDI name: queue/D | 11:58:32,781 INFO [ex] Bound to JNDI name: queue/ex | 11:58:32,812 INFO [testTopic] Bound to JNDI name: topic/testTopic | 11:58:32,812 INFO [securedTopic] Bound to JNDI name: topic/securedTopic | 11:58:32,812 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic | 11:58:32,812 INFO [testQueue] Bound to JNDI name: queue/testQueue | 11:58:32,843 INFO [UILServerILService] JBossMQ UIL service available at : localhost/127.0.0.1:8093 | 11:58:33,187 INFO [DLQ] Bound to JNDI name: queue/DLQ | 11:58:33,375 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment | 11:58:33,375 INFO [JmxKernelAbstraction] installing MBean: persistence.units:jar=WSNav.jar,unitName=WSNavDB with dependencies: | 11:58:33,375 INFO [JmxKernelAbstraction] jboss.jca:name=DefaultDS,service=DataSourceBinding | 11:58:33,375 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:jar=WSNav.jar,unitName=WSNavDB | 11:58:33,390 INFO [Version] Hibernate EntityManager 3.2.1.GA | 11:58:33,406 INFO [Version] Hibernate Annotations 3.2.1.GA | 11:58:33,421 INFO [Environment] Hibernate 3.2.4.sp1 | 11:58:33,421 INFO [Environment] hibernate.properties not found | 11:58:33,421 INFO [Environment] Bytecode provider name : javassist | 11:58:33,421 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling | 11:58:33,546 INFO [Ejb3Configuration] found EJB3 Entity bean: entity.Position | 11:58:33,546 INFO [Ejb3Configuration] found EJB3 Entity bean: entity.User | 11:58:33,562 INFO [Configuration] Reading mappings from resource : META-INF/orm.xml | 11:58:33,578 INFO [Ejb3Configuration] [PersistenceUnit: WSNavDB] no META-INF/orm.xml found | 11:58:33,609 INFO [AnnotationBinder] Binding entity from annotated class: entity.Position | 11:58:33,640 INFO [EntityBinder] Bind entity entity.Position on table positions | 11:58:33,671 INFO [AnnotationBinder] Binding entity from annotated class: entity.User | 11:58:33,671 INFO [EntityBinder] Bind entity entity.User on table users | 11:58:34,046 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider | 11:58:34,046 INFO [InjectedDataSourceConnectionProvider] Using provided datasource | 11:58:34,046 INFO [SettingsFactory] RDBMS: MySQL, version: 5.0.67-community-nt | 11:58:34,046 INFO [SettingsFactory] JDBC driver: MySQL-AB JDBC Driver, version: mysql-connector-java-5.0.8 ( Revision: ${svn.Revision} ) | 11:58:34,062 INFO [Dialect] Using dialect: org.hibernate.dialect.MySQLDialect | 11:58:34,062 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory | 11:58:34,078 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup | 11:58:34,078 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup | 11:58:34,078 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled | 11:58:34,078 INFO [SettingsFactory] Automatic session close at end of transaction: disabled | 11:58:34,078 INFO [SettingsFactory] JDBC batch size: 15 | 11:58:34,078 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled | 11:58:34,078 INFO [SettingsFactory] Scrollable result sets: enabled | 11:58:34,078 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): enabled | 11:58:34,078 INFO [SettingsFactory] Connection release mode: auto | 11:58:34,078 INFO [SettingsFactory] Maximum outer join fetch depth: 2 | 11:58:34,078 INFO [SettingsFactory] Default batch fetch size: 1 | 11:58:34,078 INFO [SettingsFactory] Generate SQL with comments: disabled | 11:58:34,078 INFO [SettingsFactory] Order SQL updates by primary key: disabled | 11:58:34,078 INFO [SettingsFactory] Order SQL inserts for batching: disabled | 11:58:34,078 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory | 11:58:34,078 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory | 11:58:34,078 INFO [SettingsFactory] Query language substitutions: {} | 11:58:34,078 INFO [SettingsFactory] JPA-QL strict compliance: enabled | 11:58:34,078 INFO [SettingsFactory] Second-level cache: enabled | 11:58:34,078 INFO [SettingsFactory] Query cache: disabled | 11:58:34,078 INFO [SettingsFactory] Cache provider: org.hibernate.cache.HashtableCacheProvider | 11:58:34,078 INFO [SettingsFactory] Optimize cache for minimal puts: disabled | 11:58:34,078 INFO [SettingsFactory] Cache region prefix: WSNav_jar,WSNavDB | 11:58:34,078 INFO [SettingsFactory] Structured second-level cache entries: disabled | 11:58:34,078 INFO [SettingsFactory] Statistics: disabled | 11:58:34,078 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled | 11:58:34,078 INFO [SettingsFactory] Default entity-mode: pojo | 11:58:34,078 INFO [SettingsFactory] Named query checking : enabled | 11:58:34,109 INFO [SessionFactoryImpl] building session factory | 11:58:34,265 INFO [SessionFactoryObjectFactory] Factory name: persistence.units:jar=WSNav.jar,unitName=WSNavDB | 11:58:34,265 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} | 11:58:34,265 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.units:jar=WSNav.jar,unitName=WSNavDB | 11:58:34,328 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext | 11:58:34,328 INFO [SchemaUpdate] Running hbm2ddl schema update | 11:58:34,328 INFO [SchemaUpdate] fetching database metadata | 11:58:34,328 INFO [SchemaUpdate] updating schema | 11:58:34,406 INFO [TableMetadata] table found: defaultds.positions | 11:58:34,406 INFO [TableMetadata] columns: [timeinserted, longitudine, latitudine, idutente] | 11:58:34,406 INFO [TableMetadata] foreign keys: [fk_posizioni_1] | 11:58:34,406 INFO [TableMetadata] indexes: [primary] | 11:58:34,437 INFO [TableMetadata] table found: defaultds.users | 11:58:34,437 INFO [TableMetadata] columns: [name, idutente] | 11:58:34,437 INFO [TableMetadata] foreign keys: [] | 11:58:34,437 INFO [TableMetadata] indexes: [primary] | 11:58:34,437 INFO [SchemaUpdate] schema update complete | 11:58:34,437 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} | 11:58:34,484 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer | 11:58:34,484 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=WSNav.jar,name=ManageUserBean,service=EJB3 with dependencies: | 11:58:34,484 INFO [JmxKernelAbstraction] persistence.units:jar=WSNav.jar,unitName=WSNavDB | 11:58:34,609 INFO [EJBContainer] STARTED EJB: session.ManageUserBean ejbName: ManageUserBean | 11:58:34,671 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer | 11:58:34,671 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=WSNav.jar,name=NavigatoreBean,service=EJB3 with dependencies: | 11:58:34,671 INFO [JmxKernelAbstraction] persistence.units:jar=WSNav.jar,unitName=WSNavDB | 11:58:34,687 INFO [EJBContainer] STARTED EJB: session.NavigatoreBean ejbName: NavigatoreBean | 11:58:34,687 INFO [EJB3Deployer] Deployed: file:/C:/Programmi/jboss-4.2.2.GA/server/default/deploy/WSNav.jar/ | 11:58:34,781 INFO [DefaultEndpointRegistry] register: jboss.ws:context=WSNav,endpoint=NavigatoreBean | 11:58:36,093 INFO [WSDLFilePublisher] WSDL published to: file:/C:/Programmi/jboss-4.2.2.GA/server/default/data/wsdl/WSNav.jar/NavigatoreBeanService49847.wsdl | 11:58:36,218 INFO [TomcatDeployer] deploy, ctxPath=/WSNav, warUrl=.../tmp/deploy/WSNav.jar49846.war/ | 11:58:36,296 INFO [TomcatDeployer] deploy, ctxPath=/WSNavClient, warUrl=.../deploy/WSNavClient.war/ | 11:58:36,437 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ | 11:58:36,609 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 | 11:58:36,625 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 | 11:58:36,625 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 20s:532ms | 11:58:44,843 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:207) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | 11:58:44,843 ERROR [RequestHandlerImpl] Error processing web service request | org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at org.jboss.ws.WSException.rethrow(WSException.java:68) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:310) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | ... 22 more | 11:58:44,859 ERROR [[NavigatoreBean]] Servlet.service() for servlet NavigatoreBean threw exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | 12:14:31,062 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:207) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | 12:14:31,062 ERROR [RequestHandlerImpl] Error processing web service request | org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at org.jboss.ws.WSException.rethrow(WSException.java:68) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:310) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | ... 22 more | 12:14:31,062 ERROR [[NavigatoreBean]] Servlet.service() for servlet NavigatoreBean threw exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:430) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | Have you got any idea? I'm using Axis 1 and Jboss 4.2.2 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207985#4207985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207985 From do-not-reply at jboss.com Mon Feb 9 13:42:30 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Mon, 9 Feb 2009 13:42:30 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class cast excpetion with an RM client Message-ID: <700741.1234204950312.JavaMail.jboss@colo-br-02.atl.jboss.com> OK.. I had not used the wsrunclient.sh in the JBOSS_HOM/bin directory. Using this script, instead of my own script, allowed me to get past this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208238#4208238 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208238 From do-not-reply at jboss.com Mon Feb 9 17:31:56 2009 From: do-not-reply at jboss.com (sunilbabu) Date: Mon, 9 Feb 2009 17:31:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - wsclient: javax.xml.ws.soap.SOAPFaultException on jboss-4.2. Message-ID: <11082927.1234218716156.JavaMail.jboss@colo-br-02.atl.jboss.com> I am getting the following exception when I try to call a WS from jboss-4.2.3.GA server, but if I call the same WS from jboss-4.2.0.CR2 it works fine and return the response. 2009-02-09 16:47:53,866 ERROR [STDERR] saveTransactionToACS: java.io.IOException: HTTP/1.1 protocol error: bad chunk | 2009-02-09 16:47:53,867 INFO [STDOUT] javax.xml.ws.soap.SOAPFaultException: java.io.IOException: HTTP/1.1 protocol error: bad chunk | 2009-02-09 16:47:53,867 INFO [STDOUT] at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72) | 2009-02-09 16:47:53,867 INFO [STDOUT] at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) | 2009-02-09 16:47:53,868 INFO [STDOUT] at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579) | 2009-02-09 16:47:53,868 INFO [STDOUT] at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) | 2009-02-09 16:47:53,868 INFO [STDOUT] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) | 2009-02-09 16:47:53,868 INFO [STDOUT] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) | 2009-02-09 16:47:53,868 INFO [STDOUT] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) | 2009-02-09 16:47:53,868 INFO [STDOUT] at $Proxy159.sendPaymentDetails(Unknown Source) | 2009-02-09 16:47:53,868 INFO [STDOUT] at com.payease.eos.acs.AcsFacadeBeans.saveTransactionToACS(AcsFacadeBeans.java:299) | 2009-02-09 16:47:53,868 INFO [STDOUT] at com.payease.eos.acs.AcsFacadeBeans.saveTest(AcsFacadeBeans.java:275) | 2009-02-09 16:47:53,868 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 2009-02-09 16:47:53,868 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 2009-02-09 16:47:53,868 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 2009-02-09 16:47:53,869 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | 2009-02-09 16:47:53,869 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) | 2009-02-09 16:47:53,870 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) | 2009-02-09 16:47:53,871 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406) | 2009-02-09 16:47:53,872 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208300#4208300 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208300 From do-not-reply at jboss.com Mon Feb 9 21:57:53 2009 From: do-not-reply at jboss.com (saavyone) Date: Mon, 9 Feb 2009 21:57:53 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: ant tests errors: NoClassDefFoundError: org/jboss/wsf/te Message-ID: <28304698.1234234673651.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm having a similar problem finding org.jboss.ws.core.jaxws.handler.GenericSOAPHandler.java. I did find another class named the same, doing basically the same, but in a different test package and therefore, not the one I want. It looks like it's a very useful class to extend, but seems to be removed from the latest distribution. In jbossws-native-core.jar there is org.jboss.ws.core.jaxws.handler.*, but no Generic*. In JBoss ESB there is a jbossws-client.jar that has nearly all the same classes as jbossws-native-core.jar, but it DOES have org.jboss.ws.core.jaxws.handler.GenericSOAPHandler plus two more Generic*Handler. This is all very confusing! I don't have a solution, just adding my $.02 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208341#4208341 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208341 From do-not-reply at jboss.com Tue Feb 10 04:03:12 2009 From: do-not-reply at jboss.com (hifi) Date: Tue, 10 Feb 2009 04:03:12 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Performance problem with Jbossws client Message-ID: <2954121.1234256592816.JavaMail.jboss@colo-br-02.atl.jboss.com> I have similar problem with poor jboss performance. I tried a simple example with 2 library sets - let's call them jboss & sun | | jboss: | | | jboss-jaxrpc.jar | | jboss-jaxws.jar | | jboss-saaj.jar | | | | sun: | | | jaxb-xjc.jar | | jaxws-api.jar | | jaxws-rt_sun.jar | | jsr181-api.jar | | saaj-api.jar | | saaj-impl.jar | | stax-1.2.0.jar | | stax-ex.jar | | streambuffer.jar | | | | common libraries : | | | activation.jar | | commons-logging.jar | | concurrent.jar | | ebaycalls.jar | | javassist.jar | | jaxb-api.jar | | jaxb-impl.jar | | jboss-common.jar | | jboss-remoting.jar | | jboss-xml-binding.jar | | jbossws-client.jar | | jbossws-common.jar | | jbossws-spi.jar | | jsr173_api.jar | | log4j.jar | | mail.jar | | policy.jar | | wsdl4j-1.6.2.jar | | xercesImpl.jar | | | | With common+sun_libs the initial call takes 8.2sec and consumes 34MB | With common+jboss_libs it takes 60sec and consumes 150MB | | Does anyone have an idea what's going on? Why the JBoss WS implementation is so slow? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208406#4208406 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208406 From do-not-reply at jboss.com Tue Feb 10 04:29:11 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 04:29:11 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Performance problem with Jbossws client Message-ID: <23297114.1234258151663.JavaMail.jboss@colo-br-02.atl.jboss.com> Profiling would probably help in understanding what's happing there. When wsdl contracts with huge type models are involved, the port creation can be quite time consuming because a lot of classes are created. Perhaps you could evaluate re-using the port instance once it has been created. In case you're seeing different performance between the first invocation and following ones, instead, please refer to http://jbossws.jboss.org/mediawiki/index.php?title=Tuning. Finally, regarding the library comparison, I'd say also try using recent version of jbossws (from the libs names I'd say you're using old ones). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208416#4208416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208416 From do-not-reply at jboss.com Tue Feb 10 04:43:54 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Tue, 10 Feb 2009 04:43:54 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WebServices logging Message-ID: <29441512.1234259034995.JavaMail.jboss@colo-br-02.atl.jboss.com> We are using JBOSS 4.2.2 GA. We expose all our services as WEB Services and our client application inturn consumes them. Now, we need to log the Request and response objects for the web service calls. CAn we do it using log4j logging available in JBOSS. Searching the forums and articles, found that we can have a separate appender. But what package we have to refer, for web service calls? It must be some JBOSS package where the web service is first taken in for processing? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208420#4208420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208420 From do-not-reply at jboss.com Tue Feb 10 05:11:09 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 10 Feb 2009 05:11:09 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Webservice Timeout Message-ID: <11620977.1234260669514.JavaMail.jboss@colo-br-02.atl.jboss.com> It's JBossWeb (Tomcat) server configuration file you're looking for. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208435#4208435 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208435 From do-not-reply at jboss.com Tue Feb 10 05:11:55 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 10 Feb 2009 05:11:55 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Only JBoss AS support ? Message-ID: <23815222.1234260716008.JavaMail.jboss@colo-br-02.atl.jboss.com> It's tested and supported only on JBossAS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208436#4208436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208436 From do-not-reply at jboss.com Tue Feb 10 05:13:36 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 10 Feb 2009 05:13:36 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Native versus Metro Message-ID: <3386203.1234260816057.JavaMail.jboss@colo-br-02.atl.jboss.com> No, there's no up2date version of the aforementioned document. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208438#4208438 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208438 From do-not-reply at jboss.com Tue Feb 10 05:19:59 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 10 Feb 2009 05:19:59 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Redeploy Endpoint already registered Message-ID: <2972718.1234261199266.JavaMail.jboss@colo-br-02.atl.jboss.com> This should be fixed with latest JBossWS 3.0.5 release. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208446#4208446 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208446 From do-not-reply at jboss.com Tue Feb 10 05:39:24 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 05:39:24 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: ant tests errors: NoClassDefFoundError: org/jboss/wsf/te Message-ID: <17729373.1234262364972.JavaMail.jboss@colo-br-02.atl.jboss.com> https://jira.jboss.org/jira/browse/JBWS-2524 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208459#4208459 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208459 From do-not-reply at jboss.com Tue Feb 10 05:49:50 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 05:49:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <10456284.1234262990546.JavaMail.jboss@colo-br-02.atl.jboss.com> http://jbossws.jboss.org/mediawiki/index.php?title=Log4J View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208465#4208465 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208465 From do-not-reply at jboss.com Tue Feb 10 05:55:37 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 05:55:37 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: mysterious vanishing Service21 Message-ID: <13388565.1234263337869.JavaMail.jboss@colo-br-02.atl.jboss.com> This has been fixed, branch5x now has JBossWS 3.1.0.CR2 including those deprecated classes. Thanks for pointing this out. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208471#4208471 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208471 From do-not-reply at jboss.com Tue Feb 10 05:57:01 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 05:57:01 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Webservice deployment error: Endpoint already registered Message-ID: <30895622.1234263421402.JavaMail.jboss@colo-br-02.atl.jboss.com> http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208446#4208446 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208472#4208472 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208472 From do-not-reply at jboss.com Tue Feb 10 06:38:29 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 06:38:29 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Should @EJB work in Pojo's deployed as a WebService? Message-ID: <20827382.1234265909177.JavaMail.jboss@colo-br-02.atl.jboss.com> This most probably falls under this issue: https://jira.jboss.org/jira/browse/JBWS-2074 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208493#4208493 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208493 From do-not-reply at jboss.com Tue Feb 10 06:50:07 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 06:50:07 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WeFault and throws declaration Message-ID: <16436002.1234266607335.JavaMail.jboss@colo-br-02.atl.jboss.com> That's in JAXWS 2.1 spec, section 3.7. Btw the upcoming 3.1.0 jbossws version will also treat RuntimeException the same way because of the spec conformance requirement. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208499#4208499 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208499 From do-not-reply at jboss.com Tue Feb 10 07:22:15 2009 From: do-not-reply at jboss.com (nbmenon) Date: Tue, 10 Feb 2009 07:22:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Jboss SOAPElementSerializer error Message-ID: <17439154.1234268535756.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using Jboss 4.2.3 and trying to invoke BPEL process which has a decision service(a web service). I get the following error. ---------------------------------------------------------------------------------- ERROR [RequestHandlerImpl] Error processing web service request org.jboss.ws.WSException: org.jboss.xb.binding.JBossXBRuntimeException: Failed to find read method or field for property 'resultList' in class org.jboss.ws.core .soap.SOAPBodyElementDoc at org.jboss.ws.WSException.rethrow(WSException.java:68) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand lerImpl.java:325) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl .java:201) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request HandlerImpl.java:134) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java :84) ....... Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to find read method or field for property 'resultList' in class org.jboss.ws.core.soap.SOAPBodyElementDoc at org.jboss.xb.binding.introspection.ClassInfo.getFieldInfo(ClassInfo.j ava:82) at org.jboss.xb.binding.introspection.FieldInfo.getFieldInfo(FieldInfo.j ava:155) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.getJavaValue(M arshallerImpl.java:1267) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.getChildren(Ma rshallerImpl.java:1257)..... ------------------------------------------------------------------------ We fixed this issue by introducing the piece of code as below in eagerInitializeTypes method in EndpointMetaData.java ----------------------------------------------------------------------------- else if(javaTypeName.equals("javax.xml.soap.SOAPElement")) { typeMapping.register(javaType, xmlType, new SOAPElementSerializerFactory(), new SOAPElementDeserializerFactory()); } ------------------------------------------------------------------------------------ we are working on porting Oracle SOA Suite on to Jboss 4.2.3 for a customer. Kindly let us know how to check this fix in and or is there any other workaround to get over this issue? Thank you. Nirmal View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208513#4208513 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208513 From do-not-reply at jboss.com Tue Feb 10 08:02:28 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Tue, 10 Feb 2009 08:02:28 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Native versus Metro Message-ID: <32248171.1234270948596.JavaMail.jboss@colo-br-02.atl.jboss.com> OK.. thanks! From what I can see... both Native and Metro have good adoption of the soap/http transport and for the WSIT stack on top of that. However, if I want to look at non http or JMS, then Metro seems to be the choice. Am I missing something? Thanks again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208537#4208537 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208537 From do-not-reply at jboss.com Tue Feb 10 08:18:22 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 08:18:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: What could cause a null Endpoint? Message-ID: <22073020.1234271902638.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, could you please show us the structure of your deployment (iow, where is the referenced bean actually declared). I'd like to add a testcase like this to the jbossws-cxf testsuite, to try reproducing your issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208544#4208544 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208544 From do-not-reply at jboss.com Tue Feb 10 08:28:22 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 08:28:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBossWS JAX-WS question using stateful Message-ID: <18250433.1234272502808.JavaMail.jboss@colo-br-02.atl.jboss.com> @javax.xml.ws.soap.Addressing will be supported starting from JBossWS-Native 3.1.0.GA, that's scheduled for the end of February 2009. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208550#4208550 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208550 From do-not-reply at jboss.com Tue Feb 10 09:56:06 2009 From: do-not-reply at jboss.com (redCar) Date: Tue, 10 Feb 2009 09:56:06 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Webservice Timeout Message-ID: <28773437.1234277766799.JavaMail.jboss@colo-br-02.atl.jboss.com> Hallo Richard, the Tomcat timeout it was not. Because of the message that the transaction is not active, I have increased the transaction timeout in the file: server/.../deploy/transaction-jboss-beans.xml I don't know if I can have disadvantages with this setting. The new value is 300000. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208604#4208604 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208604 From do-not-reply at jboss.com Tue Feb 10 10:07:54 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 10 Feb 2009 10:07:54 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Webservice Timeout Message-ID: <17446469.1234278474719.JavaMail.jboss@colo-br-02.atl.jboss.com> Yes, you need to configure the transaction timeout on the server as you did. Consider that value is in seconds, thus 300000 might be really too much. Perhaps you can better estimate the maximum tx length you might expect and set that value accordingly. Also consider taking a look at the transaction project forum for this kind of issues. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208613#4208613 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208613 From do-not-reply at jboss.com Tue Feb 10 13:21:43 2009 From: do-not-reply at jboss.com (sukhdesi) Date: Tue, 10 Feb 2009 13:21:43 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBOSSWS client get disconnected after web service consumptio Message-ID: <19138280.1234290103964.JavaMail.jboss@colo-br-02.atl.jboss.com> I have written a web service consume application in jbossws that invokes web services running in gSOAP/C++. Client server model is:- [jbossws based client]------------>[gSOAP based server] After the web service consumption complete, client sends socket disconnect and connection goes away. I want underlying TCP socket connection to persist forever. How can we achieve this? Is there any configuration at jbossws side? I am using jboss 4.2.3, in this HTTP1.1 automatically using keep-alive. Any hint is highly appreciated. Best Regards Sukhdev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208699#4208699 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208699 From do-not-reply at jboss.com Tue Feb 10 14:13:48 2009 From: do-not-reply at jboss.com (skajotde) Date: Tue, 10 Feb 2009 14:13:48 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Redeploy Endpoint already registered Message-ID: <799353.1234293228344.JavaMail.jboss@colo-br-02.atl.jboss.com> "richard.opalka at jboss.com" wrote : This should be fixed with latest JBossWS 3.0.5 release. Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208715#4208715 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208715 From do-not-reply at jboss.com Wed Feb 11 00:48:59 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 11 Feb 2009 00:48:59 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <5925185.1234331339763.JavaMail.jboss@colo-br-02.atl.jboss.com> It Works.. Thanks a lot.. I had been beating the bush around for the past 5 days... You saved my work Thanks again for your instant reply. regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208828#4208828 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208828 From do-not-reply at jboss.com Wed Feb 11 09:12:23 2009 From: do-not-reply at jboss.com (marko14) Date: Wed, 11 Feb 2009 09:12:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - connect to SSL WebService problem Message-ID: <23114034.1234361543048.JavaMail.jboss@colo-br-02.atl.jboss.com> When i'm trying connect to SSL Web Service i get error: javax.xml.ws.soap.SOAPFaultException: WS Security Error : 182001 I'm using jboss 4.2.3 GA and i've created soap client with jaxws-ri 2.1.3 tool. Does anybody know why i get this exception? Is it configuration fault or wrong, unvalid certificate? Full stack trace: javax.xml.ws.soap.SOAPFaultException: WS Security Error : 182001 | org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72) | org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) | org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579) | org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) | org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) | org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) | org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) | $Proxy89.getBillingHierarchy(Unknown Source) | org.apache.jsp.tibcoClient_jsp._jspService(tibcoClient_jsp.java:148) | org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) | javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) | org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) | org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) | javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209048#4209048 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209048 From do-not-reply at jboss.com Wed Feb 11 09:17:32 2009 From: do-not-reply at jboss.com (nbmenon) Date: Wed, 11 Feb 2009 09:17:32 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Custom Serializer in Jboss 4.2.3 Message-ID: <5548386.1234361852182.JavaMail.jboss@colo-br-02.atl.jboss.com> Can I use a custom serializer in jboss 4.2.3? If yes, where do i specify it ? Is there an equivalent of ws4ee-deployment.xml in jboss 4.2.3 ? Please let me know. Thank you. Nirmal View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209052#4209052 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209052 From do-not-reply at jboss.com Wed Feb 11 09:38:51 2009 From: do-not-reply at jboss.com (hannes.koller) Date: Wed, 11 Feb 2009 09:38:51 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Receiving Compressed WebService Requests Message-ID: <29958042.1234363131337.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I have built a simple JAX-WS WebService (on JBoss 4.2.3.GA) which is supposed to receive a rather large data structure from clients. In order to speed up the transmission I would like the clients of my service to use http compressed requests. I have tried using SoapUI to test the service. As long as I turn off request compression in SoapUI everything works fine. When I set Request compression to "GZIP" or "DEFLATE" I get the following error from JBoss: | 14:35:33,042 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | org.jboss.ws.core.CommonSOAPFaultException: org.xml.sax.SAXParseException: Content is not allowed in prolog. | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:93) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:280) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:182) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | It appears that the request is not uncompressed before it is forwarded to the SAX Parser. I am wondering how I can tell JBoss to run compressed requests through gzip before passing them to the SAX Parser? Or is it possible to write a custom HttpConnectionHandler in order to perform request decompression? I would be most thankful for any pointers you can give me. TIA :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209073#4209073 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209073 From do-not-reply at jboss.com Wed Feb 11 10:46:49 2009 From: do-not-reply at jboss.com (fghj5678) Date: Wed, 11 Feb 2009 10:46:49 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Problem with inheritance - JbossWS Message-ID: <20820722.1234367209644.JavaMail.jboss@colo-br-02.atl.jboss.com> I have problem to get inheritance in a WS to work. I've tried a small example on these env: Windows XP SP2 Jboss AS 4.2.2 GA , 4.2.3 (and also JBoss eap 4.3) I'm trying to do a request to server with a parameter that contains a inherited class. Class testEnv contains class testAAA, and class testBBB inherits testAAA. So when I put testBBB in testEnv and sends it to the WS I'm supposed to get testBBB from testEnv on the server - but I only get a testAAA! Classes used in my example: | @WebService | public interface TestWS { | | public String test(TestEnv testEnv); | } | | | @Stateless | @WebService(name = "TestWSService", serviceName = "TestWSService") | @Remote(TestWS.class) | public class TestWSImpl implements TestWS { | | public String test(TestEnv testEnv) { | if (testEnv.getTestAAA() instanceof TestAAA) { | return "WRONG, should not end up here"; | } else if (testEnv.getTestAAA() instanceof TestBBB) { | return "CORRECT"; | } | return "ERROR.."; | } | | | public class TestEnv implements Serializable { | | private static final long serialVersionUID = 1L; | | TestAAA testAAA; | | public TestAAA getTestAAA() { | return testAAA; | } | | public void setTestAAA(TestAAA testAAA) { | this.testAAA = testAAA; | } | } | | @XmlSeeAlso({TestBBB.class}) | public class TestAAA implements Serializable { | | private static final long serialVersionUID = 1L; | | int a = 1; | } | | public class TestBBB extends TestAAA implements Serializable { | | private static final long serialVersionUID = 1L; | | int b = 2; | } | | Then I've tried both with SoupUI and a generated ws-client - but I always get a testAAA instead of testBBB. example from ws-client: | ... | TestWSService testWS = ts.getTestWSServicePort(); | TestBBB testBBB = new TestBBB(); | TestEnv testEnv = new TestEnv(); | testEnv.setTestAAA(testBBB); | String s = testWS.test(testEnv); | ... | I also have logged the http soap request and it looks ok (with xsi:type for the inherited class), here is the parameter: | | This is from the generated wsdl: (which have a correct "extension base=..") | | | | | | | | | | | | | | | | | | | | | Any help would be appreciated! Mats. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209119#4209119 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209119 From do-not-reply at jboss.com Wed Feb 11 14:11:30 2009 From: do-not-reply at jboss.com (ecbdc) Date: Wed, 11 Feb 2009 14:11:30 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak Message-ID: <15108271.1234379490490.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Marlboro, were you able to resolve the issue by upgrading to JBoss 5.0? I'm having a similar issue w/ the web services memory leak. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209206#4209206 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209206 From do-not-reply at jboss.com Thu Feb 12 00:49:54 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Thu, 12 Feb 2009 00:49:54 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WS-Security on POJO Endpoint Message-ID: <5978104.1234417794236.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am trying to implement WS-Security on a POJO Endpoint using JBOSS WS. I want to use the UserName token authentication. This is already a Jira Issue with 3.0.5 (https://jira.jboss.org/jira/browse/JBWS-1999) and since I saw the Jira Issue as resolved, I got the latest code from the site and built the Web Service stack and tried to implement it. I am implementing based on this http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131719&postdays=0&postorder=asc&start=0 But while deploying the Web Service the endpoint configuration is shown as Standard Endpoint in the logs . Shouldn't it be Standard WSSecurity Endpoint. Given below is the excerpt from log. | ServerEndpointMetaData: | type=JAXWS | qname={http://www.test.com/WF/Framework/AWFUtilityService}AWFUtilityServicePortTypePort | id=jboss.ws:context=TestUtility,endpoint=AWFUtilityService | address=http://127.0.0.1:8180/TestUtility/AWFUtilityService | binding=http://schemas.xmlsoap.org/wsdl/soap/http | linkName=AWFUtilityService | implName=com.test.wf.framework.awfutilityservice.AWFUtilityServiceImpl | seiName=com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType | serviceMode=null | portComponentName=null | contextRoot=/TestUtility | urlPattern=/AWFUtilityService | configFile=META-INF/standard-jaxws-endpoint-config.xml | configName=Standard Endpoint | authMethod=null | transportGuarantee=null | secureWSDLAccess=false | properties={} | Now I run the client and the SOAP Message is properly built using the wsse:security headers, but at the server side its throwing a class cast exception 2009-02-11 20:12:52,153 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=UTF-8] | 2009-02-11 20:12:52,247 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding | 2009-02-11 20:12:52,247 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception | java.lang.ClassCastException: org.jboss.ws.core.soap.EnvelopeBuilderDOM | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:278) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) | at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) | 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) | Here is my Web Service and the server side config files. | @WebService(name="AWFUtilityServicePortType", serviceName = "AWFUtilityService", targetNamespace = "http://www.test.com/WF/Framework/AWFUtilityService", | endpointInterface = "com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType" | ) | @EndpointConfig(configFile="META-INF/standard-jaxws-endpoint-config.xml", configName = "Standard WSSecurity Endpoint") | | public class AWFUtilityServiceImpl implements AWFUtilityServicePortType { | | public String getCorrelationID(String CorrelationID) | throws GetCorrelationIDFault | { | String strCorrValue = Calendar.getInstance().getTime().toString(); | return CorrelationID + "_" + strCorrValue; | } | | } | Server config file jboss-wsse-server.xml | | | | | | | | | | | | | | | | | | | | jboss-web.xml | | | | | | java:/jaas/JBossWS | /TestUtility | | | Please help why this service is not getting deployed as a WS Security Endpoint. Do I need to enable it some where ? Or is it that the latest code doesn't contain the fix? Thanks in Advance. Dhanush View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209342#4209342 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209342 From do-not-reply at jboss.com Thu Feb 12 01:52:11 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Thu, 12 Feb 2009 01:52:11 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <15470885.1234421531903.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Now all webservices are logged to a file as xml. We need to log in a MySQL database. I used JDBCAppender and the configuration is as shown But in the database, i get only debug and info, not the Traces from MessageTrace class Why? regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209358#4209358 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209358 From do-not-reply at jboss.com Thu Feb 12 03:31:43 2009 From: do-not-reply at jboss.com (gambellid) Date: Thu, 12 Feb 2009 03:31:43 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: schemavalidation: fault not returned to calling client Message-ID: <17620239.1234427503278.JavaMail.jboss@colo-br-02.atl.jboss.com> I have the same problem. Anyone know if this is the correct behavoiur and how is it possible to intercept the exception from the server side and send some fault code to the client? I'm searching over all forum but no solution is explained, help me please. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209376#4209376 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209376 From do-not-reply at jboss.com Thu Feb 12 05:29:15 2009 From: do-not-reply at jboss.com (dimar1975) Date: Thu, 12 Feb 2009 05:29:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Is it possible to inject a Datasource in a JBoss WS ? Message-ID: <32124416.1234434555243.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all ! I have posted this question in the persistence forum yesterday, but I had no luck. Meybe this forum is more appropriate: so I'm trying to inject a Datasource in a Webservice.... @WebService(name = "CalculatorWS", targetNamespace = "http://webservice_calc/calculator") | public class CalculatorWS | { | @Resource(mappedName="java:/OracleDS") | DataSource datasource; | | @WebMethod | public Person calculate(Object obj) { | System.out.println("Datasource is " + datasource; // NULL !! | // ..... | } | } | | | The Datasource injected is null in the method calculate..... so I have tried to get the datasource with the InitialContext DataSource ds = (DataSource)new InitialContext().lookup("java:/OracleDS"); | | Connection conn = null; | try { | | conn = ds.getConnection(); | System.out.println("Connection with initial context" +conn); | } | | and the Connection is correctly retrieved. Do I miss something to make it work also with injection ??? The AS I0m using is JBoss 5.0 GA but I have tested also with 4.2 and it doesn't work too. :-( Thanks a lot Marco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209416#4209416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209416 From do-not-reply at jboss.com Thu Feb 12 08:38:32 2009 From: do-not-reply at jboss.com (andre.rieck@hansemerkur.de) Date: Thu, 12 Feb 2009 08:38:32 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JAXB Annotations are beeing ignored Message-ID: <24267614.1234445912614.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, i've build a Web-Service enabled StatelessSession Bean with JAXB annotated classes as Result-Types. @Stateless @Remote(MyBusinessInterface.class) @WebService(name="MyBusinessService") public class MyBusinessServiceBean implements MyBusinessInterface // from MyBusinessInterface @WebMethod public MyResultType getResult() { .... } ... } @XmlAccessorType(XmlAccessType.FIELD) @XmlType(name="ResultType") public class MyResultType implements Serializable { @XmlElement(name="anElement") protected List myElements; ... getters and setters ... } Unfortunately the JAXB-Annotations are ignored when generating the wsdl ! I used wsprovide and also tried just to deploying the the EAR with the @WebService-annotated bean. In both cases the JAXB-Annotations do not seem to have any effect. I would very much appreciate any hint on what might be wrong here. Thanks a lot :-) !! Andr?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209496#4209496 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209496 From do-not-reply at jboss.com Thu Feb 12 09:07:05 2009 From: do-not-reply at jboss.com (fghj5678) Date: Thu, 12 Feb 2009 09:07:05 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance - JbossWS Message-ID: <16230613.1234447625278.JavaMail.jboss@colo-br-02.atl.jboss.com> And the test was done with JDK 1.5.0_05 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209507#4209507 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209507 From do-not-reply at jboss.com Thu Feb 12 10:40:08 2009 From: do-not-reply at jboss.com (PeterJ) Date: Thu, 12 Feb 2009 10:40:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <15538096.1234453208750.JavaMail.jboss@colo-br-02.atl.jboss.com> Try adding to the category. P.S. When posting XML text or source code, please enclose the text in UBBCode "code" tags - you can do this by selecting the text and clicking the Code button above the editor window. Also, click the Preview button to ensure that the formatting is correct and the XML text shows up before posting. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209588#4209588 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209588 From do-not-reply at jboss.com Fri Feb 13 00:01:32 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Fri, 13 Feb 2009 00:01:32 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <12656790.1234501292952.JavaMail.jboss@colo-br-02.atl.jboss.com> I have already given that | | | | | | | | | | | | The same category works if it is for a file appender Pls help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209760#4209760 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209760 From do-not-reply at jboss.com Fri Feb 13 03:20:27 2009 From: do-not-reply at jboss.com (hifi) Date: Fri, 13 Feb 2009 03:20:27 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Performance problem with Jbossws client Message-ID: <11945069.1234513227532.JavaMail.jboss@colo-br-02.atl.jboss.com> I tested it with latest 3.0.5GA. It seems it's not a bug but just annoying way of working. Debugging it showed that the eagerInitialize() is the evil. It's not a fun to wait 60 seconds for the first call to the eBay SDK. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209789#4209789 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209789 From do-not-reply at jboss.com Fri Feb 13 04:20:28 2009 From: do-not-reply at jboss.com (getaceres) Date: Fri, 13 Feb 2009 04:20:28 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Optimizing deployment Message-ID: <7477180.1234516829031.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I'm developing a set of web services which accept and return data based on a standard. I have the standard schema and I have generated the JAXB elements jar file. Now, I have some web services (like 6 and it's growing) and they all use the same jar file with the bindings. They are EJB3 services and they are packaged in the same jar. The problem is that, when I deploy that jar, it takes a lot of time to deploy the services. Looking at the debug, I see that JBoss is generating JAXB classes again (or it seems) but it is completely innecessary as most of the classes are already in the classpath in that jar file that I've provided. I have deployed my services in Glassfish before and it takes only a few seconds to deploy, while in JBoss it takes more than one minute. Is there a way to tell JBoss WS to use the already generated classes or to provide it the necessary artifacts so it doesn't generate it every time? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209813#4209813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209813 From do-not-reply at jboss.com Fri Feb 13 09:00:25 2009 From: do-not-reply at jboss.com (ZeMagik) Date: Fri, 13 Feb 2009 09:00:25 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m Message-ID: <13259682.1234533625603.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, My conf : Windows XP JDK 1.5.0_14 JBoss AS 5.0.0 GA I get this "java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage" with my junit tests runned from ant. I checked that : - JBoss is the jdk5-compiled version - I compile Junit tests with the JDK5 and I launched Junit with all the JBoss libraries in the classpath : lib/endorsed, common and client. - To be sure, I removed all occurence of JDK and JRE 6.0 from my computer. If you have any clue... Thanks for your help. Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209892#4209892 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209892 From do-not-reply at jboss.com Fri Feb 13 11:33:49 2009 From: do-not-reply at jboss.com (PeterJ) Date: Fri, 13 Feb 2009 11:33:49 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m Message-ID: <3798815.1234542829237.JavaMail.jboss@colo-br-02.atl.jboss.com> Do you have CLASSPATH set globally? Or you can try this. Add "-verbose:class" to the JAVA_OPTS in run.conf. This option prints each class loaded and the JAR it was loaded from. This should help you locate the stray JAXB JAR file that is being picked up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209965#4209965 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209965 From do-not-reply at jboss.com Sun Feb 15 15:54:55 2009 From: do-not-reply at jboss.com (adavey) Date: Sun, 15 Feb 2009 15:54:55 -0500 (EST) Subject: [jbossws-users] [JBossWS] - De-serialising axis-ws4ee SOAP message Message-ID: <10375989.1234731295336.JavaMail.jboss@colo-br-02.atl.jboss.com> We have a axis web service running on JBoss4.0.3SP1 that we wish to call from another service running on JBoss4.2.3 and JBossWS 3.0.5. We are able to consume the wsdl file and call the service method that returns an array of Objects. However, when the message is de-serialised we end up with a List of size 0. We intercepted the SOAP message returned and it contains 37 objects. If we call the same method using the axis library everything works as expected and we get an array containing 37 objects. Any help would be appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210192#4210192 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210192 From do-not-reply at jboss.com Mon Feb 16 01:01:55 2009 From: do-not-reply at jboss.com (venukb) Date: Mon, 16 Feb 2009 01:01:55 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Not able to build Jboss 3.0.5 Native from source Message-ID: <13127551.1234764115936.JavaMail.jboss@colo-br-02.atl.jboss.com> I set the JDK home and the jboss home in the profiles in xml and ran - ant deploy-jboss423 saaj module builds fine jaxrpc module builds fine jax-ws modules builds fine jax-ws-ext module throws the following error jbossws-native-src-dist/modules/jaxws-ext/src/main/java/javax/xml/ws/Service21.java:[145,36] delegate has private access in javax.xml.ws.Service jbossws-native-src-dist/modules/jaxws-ext/src/main/java/javax/xml/ws/Service21.java:[222,33] delegate has private access in javax.xml.ws.Service The delegate is referred in many other lines in the same source file and same message is printed for every such occurence. Is this a problem with the source? Or is it a problem with my settings? (I am new to maven) Thanks, -- Venu View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210215#4210215 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210215 From do-not-reply at jboss.com Mon Feb 16 13:18:45 2009 From: do-not-reply at jboss.com (torf) Date: Mon, 16 Feb 2009 13:18:45 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: problem in generating a wsdl file with wstool Message-ID: <3102935.1234808325706.JavaMail.jboss@colo-br-02.atl.jboss.com> Maybe tools.jar (from the JDK) is missing in the classpath. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210461#4210461 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210461 From do-not-reply at jboss.com Mon Feb 16 18:24:07 2009 From: do-not-reply at jboss.com (ericcart) Date: Mon, 16 Feb 2009 18:24:07 -0500 (EST) Subject: [jbossws-users] [JBossWS] - jbossws-metro-3.0.5.GA Installer Bug Message-ID: <18506206.1234826647191.JavaMail.jboss@colo-br-02.atl.jboss.com> I deployed jbossws-metro-3.0.5.GA at JBoss 4.3.0.GA_CP01 (ant deploy-jboss422). I begun to receive "javax.xml.ws.WebServiceException: Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: org.jboss.ws.core.jaxws.spi.ProviderImpl" at my ws client. So, I traced the problem to production/lib/jboss-jaxws.jar and roduction/lib/jjboss-saaj.jar After I removed the libraries, everything went back to normal. Do you need a bug filled at Jira ? Thanks, Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210544#4210544 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210544 From do-not-reply at jboss.com Tue Feb 17 02:10:41 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 17 Feb 2009 02:10:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: jbossws-metro-3.0.5.GA Installer Bug Message-ID: <20511231.1234854641384.JavaMail.jboss@colo-br-02.atl.jboss.com> Try 'ant deploy-jboss424' command instead View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210580#4210580 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210580 From do-not-reply at jboss.com Tue Feb 17 03:54:08 2009 From: do-not-reply at jboss.com (deberlin) Date: Tue, 17 Feb 2009 03:54:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Error installing WebService in JAXRPCMetaDataBuilder Message-ID: <30899937.1234860848139.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello! We have a web service ejb2.1 with ejb endpoint running on JBoss5.0.0.GA with JBossWS 3.0.5.GA and JDK 1.6. On JBoss 4.x works fine. The web service artifacts generated with jwsdp-1.6. The following error occurs: 16:48:10,706 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270 | Med.jar/META-INF/wsdl/medws.xsd | 16:48:10,753 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270 | Med.jar/META-INF/wsdl/ws.xsd | 16:48:10,862 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270 | Med.jar/META-INF/wsdl/medws.xsd | 16:48:10,925 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270 | Med.jar/META-INF/wsdl/ws.xsd | 16:48:11,112 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/D:/jboss5/server/default/deploy/270Med.jar st | ate=PreReal mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/D:/jboss5/server/default/deploy/270Med.jar | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) | at org.jboss.Main.boot(Main.java:209) | at org.jboss.Main$1.run(Main.java:547) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.IllegalArgumentException: Could not determine variable name for element: result | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processOutputDocElement(JAXRPCMetaDataBuilder.java:801) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:898) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:212) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:218) | at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:59) | at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129) | at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:75) | at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) | at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:112) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) | ... 18 more The webservice.xml: | | | | | MEDWSService | META-INF/wsdl/medws.wsdl | META-INF/server-mapping.xml | | MEDWSServicePort | impl:MEDWSServicePort | de.gsd.amasys.server.modules.med.ws.MEDWSService | | MEDWS | | | | | The ejb-jar.xml: | | | | | MEDWS | MEDWS | de.gsd.amasys.server.modules.med.sessions.MEDWSHome | de.gsd.amasys.server.modules.med.sessions.MEDWSRemote | de.gsd.amasys.server.modules.med.ws.MEDWSService | de.gsd.amasys.server.modules.med.sessions.MEDWSBean | Stateless | Container | | SAP DB Datenbank | jdbc/SAPDBDS | javax.sql.DataSource | Container | | | | | | The jboss.xml: | | | | | | | MEDWS | Med/MEDWS | Med/MEDWSLocal | | MEDWSServicePort | /wsmed/MEDWSServicePort | | | jdbc/SAPDBDS | java:/SAPDBDS | | | | | | The META-INF contains: META-INF/wsdl/medws.wsdl | META-INF/wsdl/medws.xsd | META-INF/wsdl/ws.xsd | META-INF/ejb-jar.xml | META-INF/jboss.xml | META-INF/server-mapping.xml <- generated JAXB file | META-INF/webservice.xml | Any help would be appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210597#4210597 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210597 From do-not-reply at jboss.com Tue Feb 17 05:26:25 2009 From: do-not-reply at jboss.com (ericcart) Date: Tue, 17 Feb 2009 05:26:25 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: jbossws-metro-3.0.5.GA Installer Bug Message-ID: <30097019.1234866385624.JavaMail.jboss@colo-br-02.atl.jboss.com> It've already tried it. It fails with several: 07:24:12,477 ERROR [MainDeployer] Could not create deployment: file:/home/anibal/05_bin/jbdevstudio/jboss-eap/jboss-as/server/production/deploy/httpha-invoker.sar/invoker.war/ java.lang.NoSuchMethodError: org.jboss.metadata.WebMetaData.getServletParams(Ljava/lang/String;)Ljava/util/Map; at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getEndpointBeans(JAXWSDeployerHookPreJSE.java:133) at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:103) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:85) at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:77) 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) So, I downgraded 'til 422. Thanks, Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210625#4210625 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210625 From do-not-reply at jboss.com Tue Feb 17 11:01:22 2009 From: do-not-reply at jboss.com (dscottp) Date: Tue, 17 Feb 2009 11:01:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - how to exclude the 'Header' element from my Soap Client requ Message-ID: <27915175.1234886482950.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi guys, I'm working with a Web Service breaks when you have an empty header element. I won't be able to get the service fixed unfortunately. Is there any way I can exclude the empty header from my request? Basically, the JbossWS client is generating the envelope: | | | | | bar | | | | and I would like to generate this instead: | | | | bar | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210740#4210740 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210740 From do-not-reply at jboss.com Tue Feb 17 11:53:15 2009 From: do-not-reply at jboss.com (ailing.qin) Date: Tue, 17 Feb 2009 11:53:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - how to do the schema validation for incoming message in jbos Message-ID: <23501525.1234889595437.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I use jbossws-native-2.0.1.SP2_CP04 and JBoss (MX MicroKernel) [4.3.0.GA_CP03] for deploy my project, I need to do schema validation (like annotation @schemavalidation since jboss-native 3.0.1 ) . How can I do ? Thanks for your help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210768#4210768 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210768 From do-not-reply at jboss.com Wed Feb 18 09:31:26 2009 From: do-not-reply at jboss.com (adinn) Date: Wed, 18 Feb 2009 09:31:26 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Using Lists of String in WSDL-first JaxWS service Message-ID: <26842961.1234967486409.JavaMail.jboss@colo-br-02.atl.jboss.com> I am developing a JaxWS-based test service which supports scripting of various actions in the server. So, the service provides a single WebMethod which takes a list of command strings and returns a list of result strings. I defined this using the following WSDL: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I generated the Java code from this and obtained the following types | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "commandsType", propOrder = { | "commandList" | }) | public class CommandsType { | @XmlList | @XmlElement(required = true) | protected List commandList; | public List getCommandList() { | if (commandList == null) { | commandList = new ArrayList(); | } | return this.commandList; | } | } | | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "resultsType", propOrder = { | "resultList" | }) | public class ResultsType { | @XmlList | @XmlElement(required = true) | protected List resultList; | public List getResultList() { | if (resultList == null) { | resultList = new ArrayList(); | } | return this.resultList; | } | } | The server interface was generated as follows: | @WebService(name = "XTSServiceTestPortType", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated") | @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) | public interface XTSServiceTestPortType { | @WebMethod | @WebResult(name = "results", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated", partName = "results") | public ResultsType serve( | @WebParam(name = "commands", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated", partName = "commands") | CommandsType commands); | } | This works fine for a whole load of cases where I supply a series of string commands and get one or more strings as a reply. However, I found to my surprise a case where the results gets mangled. One of my command types contains the single command "subtransaction" which causes the server to start a subordinate transaction and return a transaction id. I call it as follows | commands = new CommandsType(); | commands.getCommandList().add("subtransaction"); | | try { | results = port.serve(commands); | } catch (Exception e) { | exception = e; | } | On the server side I obtain a CommandsType containing a list with the single String element "subtransaction" as expected. The code which returns the result is as follows: | result = new ResultsType(); | resultsList = result.getResultsList() | String id = newTx.toString(); | resultsList.add(id); | return resultsList; | When I look at resultsList it contains a single String soemthing like this "AtomicTransactionIdentifier: urn:-53ef7d93:9592:499c0a00:ec". Now, going back to the client the value returned from the call to port.serve(commands) is a ResultsType whose ResultsList contains two strings, "AtomicTransactionIdentifier:" and "urn:-53ef7d93:9592". In my debugger I stepped up out of the server implementation method from the return statement up to the point where the returned value was encoded into a SOAPMessage and printed the message to System.out. The result was as follows: | 13:54:22,795 INFO [STDOUT] AtomicTransactionIdentifier: urn:-53ef7d93:9592:499c0a00:ec | It looks like the message text representation of the SOAP element corresponding to field resultsList of type List is encoded by printing the text of each String separated by spaces inside tags and decoded by reading back in the space-separated character sequences found between these tags. This appears to ignore the presence of spaces embedded in any of the Strings. That's not exactly what I would call robust :-). Firstly, is this a WS issue or a JaxB issue? Secondly, can I get round this by using a more sophiisticated schema or do I have to resort to registering my own encode/decode callbacks with JaxB? I realise I could avoid the problem by making sure my Strings don't contain spaces but I'd prefer to implement a more usable service. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211101#4211101 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211101 From do-not-reply at jboss.com Wed Feb 18 14:16:17 2009 From: do-not-reply at jboss.com (gang.yang) Date: Wed, 18 Feb 2009 14:16:17 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Accessing from SOAP Handler Message-ID: <19635895.1234984577605.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm trying to develop a generic SOAP handler that can be configured to use with different WebService services. I need to pass into the handler service specific config data, such as config file name. I tried to configure this generic handler with a Web-based WS service and defined the in web.xml. Even though I was not able to inject field into the handler class, I WAS able to look it up using JNDI. However, I could not do this with an EJB3-based WS service. I defined the in ejb-jar.xml. But I could not inject the field into the handler or the EJB bean itelf. Nor could I look it up using JNDI. I'm using JBoss 4.2.2 and I could not even see the resource in the JNDIView. Is this a bug? Does anyone have any more info or experience in this area? Thanks, Gang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211249#4211249 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211249 From do-not-reply at jboss.com Wed Feb 18 14:20:08 2009 From: do-not-reply at jboss.com (gang.yang) Date: Wed, 18 Feb 2009 14:20:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Accessing from SOAP Handler Message-ID: <4785644.1234984808714.JavaMail.jboss@colo-br-02.atl.jboss.com> Be aware: somehow the "\" in my original post was stripped during the posting process. This post is about not being able to access "\", which is defined in ejb-jar.xml of an EJB-based WS service, from the associated SOAP handler. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211251#4211251 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211251 From do-not-reply at jboss.com Wed Feb 18 15:08:44 2009 From: do-not-reply at jboss.com (samyers) Date: Wed, 18 Feb 2009 15:08:44 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WS methods with same name in different WS classes => unexpec Message-ID: <30080617.1234987724360.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm new to JbossWS and getting unexpected generated WSDLs from my simple test WebService classes when the classes (deployed in the same WAR) share common WebMethod names. I'm using JBossWS native version 3.0.4.GA in jboss-5.0.0.GA-jdk6. In both WebService classes there are two methods, methodOne and methodTwo. In the TestOneWeb class both methods return Integers, in the TestTwoWeb class both methods return Strings. The WSDL for TestOneWeb looks fine, but in the WSDL for TestTwoWeb both method return ints when they should return strings. Any help or suggestions are appreciated. -- Steve TestOneWeb.java: | package com.ep.ff.web.endpoint.test; | | import javax.jws.WebMethod; | import javax.jws.WebService; | | import org.apache.log4j.Logger; | | @WebService | public class TestOneWeb | { | private static Logger logger = Logger.getLogger(TestOneWeb.class); | | @WebMethod | public Integer methodOne(String number) | { | return new Integer(number); | } | | @WebMethod | public Integer methodTwo(String number) | { | return new Integer(number); | } | } | TestTwoWeb.java: | package com.ep.ff.web.endpoint.test; | | import javax.jws.WebMethod; | import javax.jws.WebService; | | import org.apache.log4j.Logger; | | @WebService | public class TestTwoWeb | { | private static Logger logger = Logger.getLogger(TestTwoWeb.class); | | @WebMethod | public String methodOne(String number) | { | return number; | } | | @WebMethod | public String methodTwo(String number) | { | return number; | } | } | web.xml: | | | | web-test | | | TestOneWeb | com.ep.ff.web.endpoint.test.TestOneWeb | | | TestOneWeb | /ws/TestOne | | | | TestTwoWeb | com.ep.ff.web.endpoint.test.TestTwoWeb | | | TestTwoWeb | /ws/TestTwo | | | http://localhost:8080/web-test/ws/TestOne?wsdl : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://localhost:8080/web-test/ws/TestTwo?wsdl : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211253#4211253 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211253 From do-not-reply at jboss.com Thu Feb 19 11:28:31 2009 From: do-not-reply at jboss.com (ailing.qin) Date: Thu, 19 Feb 2009 11:28:31 -0500 (EST) Subject: [jbossws-users] [JBossWS] - schema validation in JBossWS 2.0.GA Message-ID: <8530142.1235060912643.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I need do schema validation (like annotation @SchemaValidation since jbossws 3.0) in my project with Jbossws-native-2.0.1.SP2 and Jboss 4.3.0.GA_CP03 without update Jbossws. How can I do? Any help would be appreciated. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211541#4211541 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211541 From do-not-reply at jboss.com Sat Feb 21 12:08:52 2009 From: do-not-reply at jboss.com (neosamurai) Date: Sat, 21 Feb 2009 12:08:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Web Service Client : Could not transmit message Message-ID: <14953991.1235236132078.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi i have the same problem can u please let me know the fix.... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212037#4212037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212037 From mike.saavedra at SirsiDynix.com Mon Feb 23 13:10:08 2009 From: mike.saavedra at SirsiDynix.com (Mike Saavedra) Date: Mon, 23 Feb 2009 11:10:08 -0700 Subject: [jbossws-users] explicit headers when code first Message-ID: <49A2E680.3050504@sirsidynix.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090223/ae969bd7/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: sdLogo.jpg Type: image/jpeg Size: 2165 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090223/ae969bd7/attachment.jpg From do-not-reply at jboss.com Mon Feb 23 14:57:54 2009 From: do-not-reply at jboss.com (lbolanos) Date: Mon, 23 Feb 2009 14:57:54 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Error unmarshalling anytype with complexType Message-ID: <21473199.1235419074655.JavaMail.jboss@colo-br-02.atl.jboss.com> Greetings! I'm using Jboss.4.2.3 I want to receive the process event with hashtable with Objects like String, Integer or QueryVO. I have this interface @WebMethod(operationName = "process", action = "http://com.sns.bas.dbenabler.web.jmsws/action/processIn") public DoneMessage process(Hashtable listParameter ) { } @WebMethod(operationName = "dummy", action = "http://com.sns.bas.dbenabler.web.jmsws/action/processIn") public QueryVO dummy(QueryVO arg1) { } All is ok when i send String or Integer. But when the client send a QueryVO the JAXBContext does not found the QName("queryVO","","") because it is searching for QName("queryVO","http://com.hds.eihv./DBEnabler","ns3") This is the what the client send: VO select There is a way to include a (QName, Class) to JAXBContext ? How can i ride this problem? Thanks in advance Leo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212412#4212412 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212412 From do-not-reply at jboss.com Mon Feb 23 15:11:07 2009 From: do-not-reply at jboss.com (lbolanos) Date: Mon, 23 Feb 2009 15:11:07 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Error unmarshalling anytype with complexType Message-ID: <5074867.1235419867971.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry... my first time :( I'm using Jboss.4.2.3 I have this interface @WebMethod(operationName = "process", action = "http://com.sns.bas.dbenabler.web.jmsws/action/processIn") public DoneMessage process(Hashtable listParameter ) { } @WebMethod(operationName = "dummy", action = "http://com.sns.bas.dbenabler.web.jmsws/action/processIn") public QueryVO dummy(QueryVO arg1) { } I want the hashtable receive any Objects like String, Integer or QueryVO. All is ok when i send String or Integer. But when the client send a QueryVO the JAXBContext does not found the QName("queryVO","","") because it is searching for QName("queryVO","http://com.hds.eihv./DBEnabler","ns3") This is the what the client send: | | VO | | | | select | | | There is a way to include a (QName, Class) to JAXBContext ? How can i ride this problem? Thanks in advance Leo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212413#4212413 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212413 From do-not-reply at jboss.com Mon Feb 23 17:23:21 2009 From: do-not-reply at jboss.com (dmoses48) Date: Mon, 23 Feb 2009 17:23:21 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBoss WS dependencies Message-ID: <9991090.1235427801794.JavaMail.jboss@colo-br-02.atl.jboss.com> I can't seem to find all the dependencies for JBossWS. I can deploy it in the server/default, but it crashes in server/web or server/minimal. I want the most minimal deployment so I'd like a list of it's dependencies. Where might I find this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212439#4212439 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212439 From do-not-reply at jboss.com Mon Feb 23 17:33:41 2009 From: do-not-reply at jboss.com (dmoses48) Date: Mon, 23 Feb 2009 17:33:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS dependencies Message-ID: <7755989.1235428421704.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry didn't include much information. Deploying jbossws 3.0.5 into jboss 500 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212440#4212440 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212440 From do-not-reply at jboss.com Mon Feb 23 17:34:14 2009 From: do-not-reply at jboss.com (PeterJ) Date: Mon, 23 Feb 2009 17:34:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS dependencies Message-ID: <14777192.1235428454499.JavaMail.jboss@colo-br-02.atl.jboss.com> You cannot deploy a web service in 'minimal' or 'web', neither of those configurations contains the JBossWS service. You need to deploy to 'all' or 'default'. If you don't care about clustering, use 'default'. It is easier to remove from 'default' services that you don't want than to add to 'web' services that you need. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212441#4212441 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212441 From do-not-reply at jboss.com Mon Feb 23 17:36:27 2009 From: do-not-reply at jboss.com (PeterJ) Date: Mon, 23 Feb 2009 17:36:27 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS dependencies Message-ID: <22389120.1235428587746.JavaMail.jboss@colo-br-02.atl.jboss.com> Looks like you posted your second item the same time I posted my reply. I didn't know you were attempting to install JBossWS 3.0.5, I thought you were trying to deploy a web service. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212442#4212442 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212442 From do-not-reply at jboss.com Mon Feb 23 22:01:44 2009 From: do-not-reply at jboss.com (JeremyGood) Date: Mon, 23 Feb 2009 22:01:44 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Error installing WebService in JAXRPCMetaDataBuilder Message-ID: <1727462.1235444504669.JavaMail.jboss@colo-br-02.atl.jboss.com> I have been having this problem all day. Yesterday, I was able to get this all working, but I must have changed something because now I get this error whenever I attempt to add a new Seam Project (via eclipse): 18:57:45,162 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/Program%20Files/Java/jboss/jboss-5.0.0.GA/server/default/deploy/newest-ear.ear/ state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: Error deploying newest-ejb.jar: failed to initialize bean container View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212487#4212487 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212487 From do-not-reply at jboss.com Tue Feb 24 00:49:11 2009 From: do-not-reply at jboss.com (Grid.Qian) Date: Tue, 24 Feb 2009 00:49:11 -0500 (EST) Subject: [jbossws-users] [JBossWS] - 'the command is too long' when run wsprovide.bat Message-ID: <31087481.1235454551710.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, I met a problem when I run wsprovide.bat in command line like this: wsprovide -w -k -c a.jar:b.jar:c.jar:d.jar.....xx.jar org.test.Testservice Then a error occured: the command is too long. I know this is caused by I set many too jars into '-c'. But I need add many jars into '-c'. How can I fix it? o, btw, the wsprovider.bat is from jboss as 4.2 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212500#4212500 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212500 From do-not-reply at jboss.com Tue Feb 24 03:35:42 2009 From: do-not-reply at jboss.com (deberlin) Date: Tue, 24 Feb 2009 03:35:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Error installing WebService in JAXRPCMetaDataBuilder Message-ID: <33145570.1235464542687.JavaMail.jboss@colo-br-02.atl.jboss.com> Which modifications in ejb2.x are necessary to run? Regards! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212528#4212528 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212528 From do-not-reply at jboss.com Tue Feb 24 11:06:15 2009 From: do-not-reply at jboss.com (PeterJ) Date: Tue, 24 Feb 2009 11:06:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: 'the command is too long' when run wsprovide.bat Message-ID: <8075050.1235491575248.JavaMail.jboss@colo-br-02.atl.jboss.com> Try placing the command into a *.bat file and run the bat file. I think this has something to do with the input handler for Command Prompt and putting the command into a *.bat file might get around it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212661#4212661 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212661 From do-not-reply at jboss.com Tue Feb 24 12:37:01 2009 From: do-not-reply at jboss.com (dmoses48) Date: Tue, 24 Feb 2009 12:37:01 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS dependencies Message-ID: <29523212.1235497021935.JavaMail.jboss@colo-br-02.atl.jboss.com> Ok, it appears you can use the web server that comes with jboss500 and you need to add the ejb deployer from default and it works for me. (jbossws depends on EJB2xDeployer) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212686#4212686 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212686 From do-not-reply at jboss.com Wed Feb 25 02:56:58 2009 From: do-not-reply at jboss.com (toma25) Date: Wed, 25 Feb 2009 02:56:58 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Webservice problem with base64 data when upgrading to JBoss Message-ID: <17235776.1235548618186.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, This is a long one du to config files... I'm running a upgrade from JBoss 4.0.5 to 4.2.3 The system I work with have a legacy webservice. It is based on J2EE webservices 1.1. It has a SLSB (EJB2) as endpoint. The WSDL file points out a schema (XSD-file) file for the definition of the parameters to the webservice. And there is a mapping file which maps to the schema. The problem: For starters, the service works in JBoss 4.0.5. In 4.2.3 it works perfectly fine for except for a attachment element, the base64 data doesn't convert properly into a byte array. Changing it to string works fine, so there is no problem with typos, it just won't convert into a byte array. Has anyone had a similar problem when upgrading from 4.0.5 to 4.2.3? If i remove an attachments from the call, it works fine, but if I have one, if fails with: org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to | parse source: Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding at 1f1804d({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType) | at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:250) | at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97) | at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:141) | at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:85) | at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:173) | at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263) | at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115) | at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135) | at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:82) | at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.getMBeanInvocation(InvocationHandlerEJB21.java:169) | at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 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:182) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | Caused by: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: | Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding at 1369863({http://foo/newsws/t | ypes}attachment, type={http://foo/newsws/types}AttachmentElementType) | at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:111) | at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:62) | at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60) | at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180) | ... 36 more | Caused by: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: Failed to resolve target property type on or | g.jboss.xb.binding.sunday.unmarshalling.ElementBinding at 1369863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType) | at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:65) | at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:103) | ... 39 more | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve target property type on org.jboss.xb.binding.sun | day.unmarshalling.ElementBinding at 1369863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}Attach | mentElementType) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:179) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126) | at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:61) | ... 40 more | Caused by: org.jboss.ws.WSException: Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding at 1369 | 863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType) | at org.jboss.ws.extensions.xop.jaxrpc.JBossXBContentAdapter.beforeSetParent(JBossXBContentAdapter.java:115) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1005) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:246) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:296) | at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) | at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:175) | ... 42 more this is the webservices.xml | FooService | META-INF/wsdl/FooService.wsdl | META-INF/FooService-mapping.xml | | FooService | FooServicePort | com.foo.FooServiceEndpoint | | FooServiceBean | | | | >From the foo.xsd | | Attachment data. When submitting, contains the attachment itself. | | | | | | The filename of the attachment | | | | | The URL from which the attachment can be downloaded. Not used when submitting news. | | | | | The MIME type of the attached file | | | | | >From FooService-mapping.xml | foo.MessageElementType | typeNS:MessageElementType | complexType | | category | category | | | type | type | | | headline | headline | | | body | body | | | attachment | attachment | | | field | field | | And Attachment.java looks like this: public class AttachmentElementType | { | | protected java.lang.String filename; | | protected java.net.URI href; | | protected java.lang.String mimeType; | | protected byte[] _value; | public AttachmentElementType(){} | | public AttachmentElementType(java.lang.String filename, java.net.URI href, java.lang.String mimeType, byte[] _value){ | this.filename=filename; | this.href=href; | this.mimeType=mimeType; | this._value=_value; | } | public java.lang.String getFilename() { return filename ;} | | public void setFilename(java.lang.String filename){ this.filename=filename; } | | public java.net.URI getHref() { return href ;} | | public void setHref(java.net.URI href){ this.href=href; } | | public java.lang.String getMimeType() { return mimeType ;} | | public void setMimeType(java.lang.String mimeType){ this.mimeType=mimeType; } | | public byte[] get_value() { return _value ;} | | public void set_value(byte[] _value){ this._value=_value; } | | } View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212824#4212824 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212824 From do-not-reply at jboss.com Wed Feb 25 12:47:40 2009 From: do-not-reply at jboss.com (jej2003) Date: Wed, 25 Feb 2009 12:47:40 -0500 (EST) Subject: [jbossws-users] [JBossWS] - RestEasy Client Framework Message-ID: <9163582.1235584060522.JavaMail.jboss@colo-br-02.atl.jboss.com> I am trying to follow the guide that is here http://www.jboss.org/community/docs/DOC-11746 and while trying to implement the client I can't import org.resteasy.plugins.client.httpclient.ProxyFactory; Where is this located? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213108#4213108 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213108 From do-not-reply at jboss.com Wed Feb 25 17:39:04 2009 From: do-not-reply at jboss.com (gang.yang) Date: Wed, 25 Feb 2009 17:39:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: resource injection in WS handler not working in jboss JA Message-ID: <26867582.1235601544166.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I also hit this problem now, which is a blocking one since I can not pass in any info to the handler w/o this capability. According the JAX-WS spec, you should also be able to lookup up the names defined by the associated Java EE component using JNDI from the handler. I tried that. It worked for handlers that is configure for the Web container. But it did not work for handlers that is configure for the EJB3 container. So I'm really dead in the water since we use EJB3 annotated WS endpoint. I understand that the fix for the resource injection is targeted for JBossWS 3.1.1. But could there be a fix for the JNDI lookup not working earlier? Or should I create a trouble report for the JNDI? Thanks, Gang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213196#4213196 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213196 From do-not-reply at jboss.com Thu Feb 26 06:09:07 2009 From: do-not-reply at jboss.com (mounir-aboud) Date: Thu, 26 Feb 2009 06:09:07 -0500 (EST) Subject: [jbossws-users] [JBossWS] - XML Message Message-ID: <31508374.1235646547631.JavaMail.jboss@colo-br-02.atl.jboss.com> i want to ask how to get the sent document i im using document literal and how to sent this document View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213290#4213290 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213290 From do-not-reply at jboss.com Thu Feb 26 10:59:17 2009 From: do-not-reply at jboss.com (jej2003) Date: Thu, 26 Feb 2009 10:59:17 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: RestEasy Client Framework Message-ID: <9275541.1235663957820.JavaMail.jboss@colo-br-02.atl.jboss.com> for anyone interested it is at import org.jboss.resteasy.client.ProxyFactory; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213417#4213417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213417 From do-not-reply at jboss.com Thu Feb 26 12:08:57 2009 From: do-not-reply at jboss.com (ailing.qin) Date: Thu, 26 Feb 2009 12:08:57 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: schema validation in JBossWS 2.0.GA Message-ID: <30639345.1235668137416.JavaMail.jboss@colo-br-02.atl.jboss.com> I find the solution, 1. create a file of handler chaine 2.use @HandlerChain for add the file in the class endpoint impl 3. create the class implements SOAPHandler View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213458#4213458 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213458 From do-not-reply at jboss.com Fri Feb 27 15:51:40 2009 From: do-not-reply at jboss.com (jej2003) Date: Fri, 27 Feb 2009 15:51:40 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Could not find MessageBodyWriter for class java.util.List an Message-ID: <16258217.1235767900474.JavaMail.jboss@colo-br-02.atl.jboss.com> Has anyone had any experience with getting the java.util.List multipart support working as described at http://bill.burkecentral.com/2008/10/23/jax-rs-multipart-support-with-resteasy/ ? When running the Client Framework I get the following: Exception in thread "main" java.lang.RuntimeException: Could not find MessageBodyWriter for class java.util.List and mediaType multipart/mixed | at org.jboss.resteasy.client.core.MessageBodyParameterMarshaller.getMessageBodyWriter(MessageBodyParameterMarshaller.java:59) | at org.jboss.resteasy.client.core.MessageBodyParameterMarshaller.buildRequest(MessageBodyParameterMarshaller.java:48) | at org.jboss.resteasy.client.core.WebRequestIntializer.setHeadersAndRequestBody(WebRequestIntializer.java:43) | at org.jboss.resteasy.client.core.ClientInvoker.initBaseMethod(ClientInvoker.java:107) | at org.jboss.resteasy.client.core.ClientInvoker.invoke(ClientInvoker.java:67) | at org.jboss.resteasy.client.core.ClientProxy.invoke(ClientProxy.java:47) I see the provider being loaded (or at least what I would assume is the provider) | ... | 78 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in provider org.jboss.resteasy.plugins.providers.multipart.ListMultipartReader | 78 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in provider org.jboss.resteasy.plugins.providers.multipart.MultipartFormDataReader | 78 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in provider org.jboss.resteasy.plugins.providers.multipart.MapMultipartFormDataReader | 94 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in providerorg.jboss.resteasy.plugins.providers.multipart.MultipartWriter | 94 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in providerorg.jboss.resteasy.plugins.providers.multipart.MultipartFormDataWriter | 94 [main] INFO org.jboss.resteasy.plugins.providers - Adding built in providerorg.jboss.resteasy.plugins.providers.multipart.ListMultipartWriter | ... | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213863#4213863 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213863 From do-not-reply at jboss.com Sat Feb 28 00:01:53 2009 From: do-not-reply at jboss.com (glen_s) Date: Sat, 28 Feb 2009 00:01:53 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Use of JAX-RPC in JBoss 4.2.3 Message-ID: <21624117.1235797313372.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a web app running on JBoss AS 4.2.3, default server configuration. I need to write a web service client that can talk to a soap encoded web service. I know that JBossWS does not support soap encoding, so I am struggling to find a workaround. >From my research I'm lead to believe that JAX-RPC is the one library that does support soap encoding, so have tried using a (JWSDP) wscompile produced client in JBoss 4.2.3. When I include the JWSDP compatible JARs[1] in the lib directory of my EAR, and my client code calls into the wscompile produced stub, the stub calls into (JWSDP) StreamingSender class and ultimately throws a ClassCastException: | 1. java.lang.ClassCastException: org.jboss.ws.core.soap.SOAPMessageImpl | 2. at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231) | 3. at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324) | How can I make JAX-RPC work on JBoss 4.2.3? Is it possible to manipulate the set of JARs from JWSDP that I am including[1] in my web app to make JAX-RPC (supporting soap encoding) work on JBoss 4.2.3? If no-one can offer the silver-bullet answer as to how to make JAX-RPC work on JBoss 4.2.3, maybe one of the following ideas will ring true with someone who can at least point me in the right direction to pursue. Might I: * *Somehow* configure JBossWS to "play nice" with JAX-RPC so that JAX-RPC can be used as my web service library | * Change the class loader configuration to allow the JAX-RPC (and associated JWSDP) JAR files to work in my web app | * Remove the JBossWS module from the default configuration, and somehow just use JAX-RPC JARs from my web app rather than being loaded as a JBoss service (although I have concerns that the JAX-RPC dependant JARs from JWSDP would still conflict with other XML related JARs in JBoss AS) | * Switch to some other web service client library that supports soap encoding (that I'm not aware of) that can be configured to run on JBoss AS 4.2.3 | | I am relatively new to JBoss, so if one of the above ideas strikes you as ludicrous (just doesn't make sense), I apologize. | | Thank you, | Glen Scott | | [1]The jars from JWSDP 1.6 I included in my EAR's lib are: activation.jar, commons-beanutils.jar, commons-collections.jar, commons-digester.jar, commons-logging.jar, dom.jar, jaas.jar, jax-qname.jar, jaxp-api.jar, jaxrpc-api.jar, jaxrpc-impl.jar, jaxrpc-spi.jar, mail.jar, namespace.jar, relaxngDatatype.jar, saaj-api.jar, saaj-impl.jar, sax.jar, xercesImpl.jar, xsdlib.jar | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213909#4213909 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213909