From do-not-reply at jboss.com Sat Aug 1 00:56:55 2009
From: do-not-reply at jboss.com (krishnaroopa)
Date: Sat, 1 Aug 2009 00:56:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting ClassCast Exception in case
of malformed webserv
Message-ID: <19379480.1249102615678.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Though we are getting the same exception,. I have checked the response returned, the xml is valid. But could not found out why this exception occurs,.
AS you said, it is scheduled for 3.2.1, we have our deliverables by 15th. Is there any work around?
Thanks
KRS
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247371#4247371
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247371
From do-not-reply at jboss.com Sat Aug 1 01:42:50 2009
From: do-not-reply at jboss.com (krishnaroopa)
Date: Sat, 1 Aug 2009 01:42:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Class Cast Exception inconsistently
Message-ID: <3417026.1249105370927.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi
We are using JBOSS 4.2.3 , JBOSSWS Native 3.1.0 with WS-Addressing enabled. WS tracing enabled.
We have an architecture like this.
Web services -- servlets -- JSP pages (uses GWT)
When multiple web methods are called in a JSP page, it throws the Classcast exception.
anonymous wrote :
| javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.mobax.signage.ws.RemoveDeviceResponse cannot be cast to com.mobax.signage.ws.GetDeviceResponseResponse
| at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
| at $Proxy103.removeDevice(Unknown Source)
| at com.mobax.mashup.webserviceconsumer.SignageServiceConsumer.removeDevices(SignageServiceConsumer.java:264)
| at com.mobax.mashup.responsebuilder.EnablerResponseParser.removeDevice(EnablerResponseParser.java:1489)
| at com.mobax.mashup.servlet.signage.RemoveDevice.processRequest(RemoveDevice.java:60)
| at com.mobax.mashup.servlet.signage.RemoveDevice.doGet(RemoveDevice.java:88)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
| 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)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247373#4247373
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247373
From do-not-reply at jboss.com Sat Aug 1 03:18:14 2009
From: do-not-reply at jboss.com (krishnaroopa)
Date: Sat, 1 Aug 2009 03:18:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception inconsistently
Message-ID: <33140926.1249111094124.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi
What will be WS stack default with JBOSS 4.2.3 ?
For implementing WS-addressing, we deployed native 3.1.0 on top of it
Now, we are getting classcastexception in web service invocation since the jbossws native 3.1.0?
regards
KRS
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247376#4247376
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247376
From do-not-reply at jboss.com Mon Aug 3 03:20:55 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 3 Aug 2009 03:20:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: String being escaped
Message-ID: <28953540.1249284055896.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
If there's CDATA section, then there's no need to escape characters.
If you don't like current begavior, provide simple test case, patch and we'll incorporate it to our product ;)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247491#4247491
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247491
From do-not-reply at jboss.com Mon Aug 3 11:15:44 2009
From: do-not-reply at jboss.com (erili)
Date: Mon, 3 Aug 2009 11:15:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak
Message-ID: <4923459.1249312544816.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello!
We are running into the same problem. The JVM runs out of memory and heap analysis shows huge HashSets containing entries like "JBossWS_..._20342.xsd". Following the path to GC root shows that resourceBlackList in the unified classloader holds references to these hashmaps.
We are running JBoss AS 4.2.2.GA with JBossWS 3.0.1-native-2.0.4.GA and cannot upgrade to JBoss AS 5, so more information on this problem would be greatly appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247639#4247639
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247639
From do-not-reply at jboss.com Mon Aug 3 11:59:16 2009
From: do-not-reply at jboss.com (creaturita)
Date: Mon, 3 Aug 2009 11:59:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Caused by:
java.lang.ClassCastException: com.sun.xml.bind.v2
Message-ID: <5369133.1249315156692.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello everyone,
I have a JBoss 4.2.3 with jdk6v14. I have installed Metro on it. I can publish webservices (ejb 3 style) and webpages (jsf+facelets+richfaces) correctly, but when I call a webservice in the page I get the following exception:
[2009/08/03 17:05:30] -- ERROR -- org.ajax4jsf.webapp.BaseXMLFilter -- Exception in the filter chain
javax.servlet.ServletException: La ejecuci??n del Servlet lanz?? una excepci??n
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
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)
Caused by: java.lang.ExceptionInInitializerError
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:107)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy158.obtenerVademecum(Unknown Source)
at es.indra.peissmu.presentacion.casos.version.delegate.ServicioVersionVademecumDelegate.getObtenerVademecum(ServicioVersionVademecumDelegate.java:49)
at es.indra.peismu.presentacion.casos.cargaNomenclator.view.CargaNomenclatorManagedBean.ObtenerVersion(CargaNomenclatorManagedBean.java:178)
at es.indra.peismu.presentacion.casos.cargaNomenclator.view.CargaNomenclatorManagedBean.(CargaNomenclatorManagedBean.java:120
at sun.reflect.NativeCons
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ewInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at java.beans.Beans.instantiate(Beans.java:204)
at java.beans.Beans.instantiate(Beans.java:48)
at com.sun.faces.config.ManagedBeanFactoryImpl.newInstance(ManagedBeanFactoryImpl.java:269)
at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:510)
at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:82)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:62)
at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:45)
at org.apache.el.parser.AstValue.getValue(AstValue.java:86)
at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
at javax.faces.component.UIOutput.getValue(UIOutput.java:176)
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:100)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:290)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:216)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:847)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:893)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:827)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:883)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:889)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:243)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
... 23 more
Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.internal.bind.api.JAXBRIContext
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.(SOAPFaultBuilder.java:533)
... 65 more
I suppose it is a library mix failure, but I can not find the solution . Any ideas?
Thanks in advance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247647#4247647
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247647
From do-not-reply at jboss.com Tue Aug 4 06:16:50 2009
From: do-not-reply at jboss.com (fsciascia)
Date: Tue, 4 Aug 2009 06:16:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ws-addressing: use of annotations
@Stateful @WebService @Add
Message-ID: <18565750.1249381010716.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello!
it's possible to use @Addressing annotation (javax.xml.ws.soap.Addressing) (jboss4.2.3 + jbossWS 3.1).
I use also security and webservices annotations(everything works).
What I want to do is to build a stateful secure web service with ejb3, without working with descriptors if possible
thanks
francesco
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247804#4247804
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247804
From do-not-reply at jboss.com Tue Aug 4 07:42:34 2009
From: do-not-reply at jboss.com (iou_paul)
Date: Tue, 4 Aug 2009 07:42:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WebMethod call problem
Message-ID: <11144686.1249386154628.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I'm trying to make a call from a desktop client to a webservice method running on JBoss 5.1.0. It connects to the webservice, but when calling the webmethod I got the following error:
On the client side:
javax.xml.ws.WebServiceException: java.lang.NullPointerException
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:176)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:86)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy22.fileUp(Unknown Source)
at ro.datagroup.verlinkung.upload.webservice.TestProcess.testEJBWebService(TestProcess.java:75)
at ro.datagroup.verlinkung.upload.webservice.TestProcess.main(TestProcess.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
Caused by: java.lang.NullPointerException
at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.getProperty(XMLStreamWriterImpl.java:426)
at com.sun.xml.ws.util.xml.XMLStreamWriterFilter.getProperty(XMLStreamWriterFilter.java:139)
at com.sun.xml.ws.streaming.XMLStreamWriterUtil.getOutputStream(XMLStreamWriterUtil.java:77)
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:313)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
at com.sun.xml.ws.encoding.MtomCodec.encode(MtomCodec.java:158)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:142)
... 18 more
On server side:
ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-0.0.0.0-8080-1) SOAP request exception
ClientAbortException: java.net.SocketException: Connection reset
at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:342)
at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:420)
at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:364)
at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:193)
at java.io.FilterInputStream.read(FilterInputStream.java:116)
at java.io.PushbackInputStream.read(PushbackInputStream.java:169)
at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.fullRead(BoundaryDelimitedInputStream.java:144)
at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:191)
at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:312)
at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:286)
at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:119)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:241)
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:717)
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:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
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:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:745)
at org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:775)
at org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:245)
at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:276)
at org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:132)
at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:704)
at org.apache.coyote.Request.doRead(Request.java:428)
at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:332)
... 38 more
I get the same problem regardless the webmethod signature or content.
The weird thing is that the same client & ws code actually works on an older application.
Can anybody give me a hint about what is or might be the problem?!?
Thanks,
Paul.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247829#4247829
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247829
From do-not-reply at jboss.com Tue Aug 4 09:45:36 2009
From: do-not-reply at jboss.com (karypid)
Date: Tue, 4 Aug 2009 09:45:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException: Cannot obtain
operation meta data
Message-ID: <24119636.1249393536122.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I'm trying to create a web service client with WS-RM enabled, that will work with a WebLogic 10gR3 service. When I run the client I get:
***********************
| Create Web Service Client...
| Create Web Service...
| Call Web Service Operation...
| Exception in thread "main" org.jboss.ws.extensions.wsrm.api.RMException: Unable to create WSRM sequence
| at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:573)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:168)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy14.deliver(Unknown Source)
| at cmr.messaging.clientsample.ClientSample.main(ClientSample.java:23)
| Caused by: org.jboss.ws.WSException: Cannot obtain operation meta data for: {http://docs.oasis-open.org/ws-rx/wsrm/200702}CreateSequence
| at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:201)
| at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:182)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:295)
| at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:559)
| ... 4 more
Any pointers as to what is going wrong? I use the following configuration for the client:
|
|
|
| Standard Anonymous WSRM Client
|
|
|
|
|
|
| ##SOAP11_HTTP
|
| WSAddressing Handler
| org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler
|
|
|
| WSRM Handler
| org.jboss.ws.extensions.wsrm.jaxws.RMClientHandler
|
|
|
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247865#4247865
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247865
From do-not-reply at jboss.com Tue Aug 4 11:22:24 2009
From: do-not-reply at jboss.com (meetoblivion)
Date: Tue, 4 Aug 2009 11:22:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Two classes have the same XML type name
when deploying clien
Message-ID: <29365567.1249399344994.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
This may have more to do with how our test/dev environment is setup, but I am in the process of developing some web services to act as a facade to direct database access from our external site (mostly for writes). When I deploy both the client (war) and server (ejb jar) on the same box, I get the below errors in my stack trace:
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}signupProperties". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SignupProperties
| at protected java.util.List com.coat.web.services.sweeps.SweepsSignup.properties
| at com.coat.web.services.sweeps.SweepsSignup
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SignupProperties
| at public com.coat.web.services.sweeps.SignupProperties com.coat.web.services.sweeps.ObjectFactory.createSignupProperties()
| at com.coat.web.services.sweeps.ObjectFactory
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}sweepsSignup". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsSignup
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsSignup
| at public com.coat.web.services.sweeps.SweepsSignup com.coat.web.services.sweeps.ObjectFactory.createSweepsSignup()
| at com.coat.web.services.sweeps.ObjectFactory
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}SweepsException". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsException
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsException
| at public com.coat.web.services.sweeps.SweepsException com.coat.web.services.sweeps.ObjectFactory.createSweepsException()
| at com.coat.web.services.sweeps.ObjectFactory
Now, I think it's because both client and server are on the same machine. I used wsconsume to generate the WS client stubs. Is the correct work around to use a different package?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247907#4247907
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247907
From do-not-reply at jboss.com Tue Aug 4 19:24:09 2009
From: do-not-reply at jboss.com (meetoblivion)
Date: Tue, 4 Aug 2009 19:24:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Two classes have the same XML type
name when deploying c
Message-ID: <17456609.1249428249629.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
so a small update.
i did confirm that the issue is only present when the client and server are the same box. even if both are deployed to both boxes, issue does not present itself as long as i ensure that the request comes from server1 and goes to server2.
changing the package name did not fix anything, and i don't think it's right to try to change the namespace based on this. any ideas?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247999#4247999
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247999
From do-not-reply at jboss.com Wed Aug 5 08:04:20 2009
From: do-not-reply at jboss.com (delicjapatrycja)
Date: Wed, 5 Aug 2009 08:04:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wsconsume and implementing interface
top-down
Message-ID: <10808791.1249473860161.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi
(It's my first post, I was trying to find something about my problem but I couldn't )
I have some problem with deploy my Jax WS Web service.
I'm trying to do this using top-down method - wsconsume. When I generate java classes from WSDL which I have written before, I get one which is the interface.
How should I implement it ?
How should I write the web.xml ? which class name should I write inside tags ?
If i write the generated class name, how jax-ws knows where (in which java class) is implementing class ?
If I write the class name inside, which impelements generated interface, I can't deploy the web service. (maybe I do something wrong?)
part of Service class generated by Jax-WS:
| // [...]
| @WebService(name = "XXXService", targetNamespace = "http://xxx.com/XXX/ws")
| public interface XXXService {
|
|
| /**
| *
| * @param in
| * @return
| * returns int
| * @throws Method1FaultMsg
| */
| @WebMethod
| @WebResult(name = "out", targetNamespace = "")
| @RequestWrapper(localName = "method1", targetNamespace = "http://xxx.com/XXX/ws", className = "com.xxx.xxx.ws.Method1")
| @ResponseWrapper(localName = "method1Response", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1Response")
| public int method1(
| @WebParam(name = "in", targetNamespace = "")
| int in)
| throws Method1FaultMsg
| ;
| // [...]
|
|
My implementation class:
|
| public class XXXServiceImpl implements com.xxx.xxx.ws.XXXService {
|
|
| @WebMethod
| @WebResult(name = "out", targetNamespace = "")
| @RequestWrapper(localName = "method1", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1")
| @ResponseWrapper(localName = "method1Response", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1Response")
| public int method1(int in) throws Method1FaultMsg
| {
| try
| {
| return in*2;
| }
| catch(Exception e)
| {
| new Method1FaultMsg("Server Exception", new ServerException(), e);
| }
| return in;
| }
|
|
Any tips?
Anyway, sorry for my English :/
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248099#4248099
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248099
From do-not-reply at jboss.com Wed Aug 5 10:59:50 2009
From: do-not-reply at jboss.com (erili)
Date: Wed, 5 Aug 2009 10:59:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak
Message-ID: <24359794.1249484390729.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I found a poller method in our code that created new instances of WS client objects in the poller method. Even though these were not retained they apparently added data to the classloader's (unifiedclassloader3) resourceBlackList.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248167#4248167
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248167
From do-not-reply at jboss.com Thu Aug 6 07:32:27 2009
From: do-not-reply at jboss.com (meetoblivion)
Date: Thu, 6 Aug 2009 07:32:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume and implementing
interface top-down
Message-ID: <28973682.1249558347957.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
i think you may have your implementation strategies mixed up.
if you're using wsconsume, it assumes that you've already written the webservice, and wsconsume helps create the client interface.
if you're using wsprovide, it assumes you've written the WSDL and need to generate the server side stubs.
Why fits your scenario better?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248436#4248436
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248436
From postmaster at lists.jboss.org Sat Aug 8 10:27:35 2009
From: postmaster at lists.jboss.org (Automatic Email Delivery Software)
Date: Sat, 8 Aug 2009 22:27:35 +0800
Subject: [jbossws-users] Delivery failed
Message-ID: <200908081427.n78ER408028065@lists01.dmz-a.mwc.hst.phx2.redhat.com>
Your message was undeliverable due to the following reason:
Your message could not be delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.
Your message could not be delivered within 3 days:
Server 123.255.139.86 is not responding.
The following recipients did not receive this message:
Please reply to postmaster at lists.jboss.org
if you feel this message to be in error.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Message.com
Type: application/octet-stream
Size: 28864 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090808/6393b597/attachment.obj
From do-not-reply at jboss.com Tue Aug 11 13:07:31 2009
From: do-not-reply at jboss.com (magacho)
Date: Tue, 11 Aug 2009 13:07:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem in a WSclient (JBoss 4.2.3)
to connect .NET serv
Message-ID: <17538959.1250010451538.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
The [404] is the answer from our partner, when he got a transfer-encoding: chunked for protection agains Deny os service attacs, he returns 404 as an answer.
The fact is that depending on the context (EJB or WS) the code (Soap Request) works in two diferent ways.
| WS
| POST /virtual/wsi/cap.asmx HTTP/1.1
| SOAPAction: "http://qqcoisa.com.br/GetAuthorized"
| Content-Type: text/xml; charset=UTF-8
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.2.SP8
| Host: ecommerce.redecard.com.br
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Content-Length: 860
|
| JNDI Remote / Local
| POST /virtual/ws/cap.asmx HTTP/1.1
| SOAPAction: "http://qqcoisa.com.br/GetAuthorized"
| Content-Type: text/xml; charset=UTF-8
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.2.SP8
| Host: ecommerce.redecard.com.br
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Transfer-Encoding: chunked
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249057#4249057
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249057
From do-not-reply at jboss.com Wed Aug 12 08:48:43 2009
From: do-not-reply at jboss.com (konstt2000)
Date: Wed, 12 Aug 2009 08:48:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem deploy WS (ClassFormatError)
Message-ID: <6813465.1250081323102.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I have a project java and compile it with ANT. When deploy the war (with his web.xml, etc) gives me a error.
| 14:23:19,852 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-soa-p.4.3.0/jboss-as_SOA/server/default/deploy/WebServiceGde.war
| java.lang.ClassFormatError: Method "getDescripcion" in class es/ree/gde/webservice/logica/WebServiceGde has illegal signature "ourceFile"
| at java.lang.ClassLoader.defineClass1(Native Method)
| at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
| at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
| at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
| at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
| at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getEndpointBeans(JAXWSDeployerHookPreJSE.java:145)
| at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:104)
| at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87)
| at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy46.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
|
If I believe a project web in eclipse and deploy the webservice works fine.
I believe
I believe that the classes are not compiled well. In addition they occupy differently the .class that I compile that those that eclipse generates. ??????????
I work with JDK1.5 and JBOSS.4.3
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249211#4249211
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249211
From do-not-reply at jboss.com Wed Aug 12 12:20:32 2009
From: do-not-reply at jboss.com (hstang)
Date: Wed, 12 Aug 2009 12:20:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Is it possible to set timeout on the
server instead of clien
Message-ID: <3906541.1250094032092.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi everyone,
I searched the forums here and I noticed that other developers are inserting the kind of code:
| BindingProvider provider = (BindingProvider) somePort;
| provider.getRequestContext().put("org.jboss.ws.timeout", 120);
|
to configure the timeout for the client.
But is there a way to set the default timeout setting on the JBossWS side so that *any* potential web service client(outside of java) can assume a default timeout setting?
I'm trying to implement a long-running-web-service that could take a long time to finish (possibly 10 minutes?) and I would like to hold that connection long enough so that a response will get back the client.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249269#4249269
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249269
From do-not-reply at jboss.com Wed Aug 12 12:50:35 2009
From: do-not-reply at jboss.com (monkeyden)
Date: Wed, 12 Aug 2009 12:50:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Endpoint registration
Message-ID: <9584867.1250095835523.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I have an endpoint, in my ejb jar file, deployed to JBoss 4.2.2GA. I can see the bean is being deployed but I see nothing about the endpoint registration, like I do all the portal services. I also see the portal services endpoints at the services URL http://localhost:8080/jbossws/services but not mine. Is there something else I need to do to get it to register? Perhaps a cfg file in the ear? I am using the first example from Java Web Services: Up and Running
Interface
| @WebService
| @SOAPBinding(style = Style.RPC) // more on this later
| public interface TimeServer {
| @WebMethod String getTimeAsString();
| @WebMethod long getTimeAsElapsed();
| }
|
Impl
@WebService(endpointInterface = "com.symcare.ids.services.TimeServer")
| public class TimeServerImpl implements TimeServer {
| public String getTimeAsString() { return new Date().toString(); }
| public long getTimeAsElapsed() { return new Date().getTime(); }
| }
|
Thanks!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249274#4249274
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249274
From do-not-reply at jboss.com Wed Aug 12 14:01:24 2009
From: do-not-reply at jboss.com (monkeyden)
Date: Wed, 12 Aug 2009 14:01:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Endpoint registration
Message-ID: <4193990.1250100084376.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
The above deployment was in an ear file. I tried it according to the JBossWS documentation and had no mention of the service in the server log. I packaged the the impl and the interface in a jar file and deployed it to the "deploy" directory as directed in:
anonymous wrote : Simply wrap up the service implementation class, the endpoint interface and any custom data types in a JAR and drop them in the deploy directory. No additional deployment descriptors required.
|
Anyone have an idea?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249285#4249285
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249285
From do-not-reply at jboss.com Thu Aug 13 03:46:23 2009
From: do-not-reply at jboss.com (spinder)
Date: Thu, 13 Aug 2009 03:46:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - portable JAXWS deployment
example/steps? bottom up...
Message-ID: <24961529.1250149583486.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi all,
Are there any examples of how to create portable JAXWS deployment? On http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools, in the bottom-up section, there is mention of creating portable JAXWS deployments. How does this work?
My problem: I have a number of session beans that are being exposed each as separate wsdls and server startup has slowed quite a bit. I'd like to tell JbossWs to stop regenerating the wsdl interfaces dynamically as the back end beans are considered frozen now.
Will creating portable JAXWS deployments help here? Are there any examples that will stop JbossWS from dynamically recompiling/rechecking wsdls each time the server is startup? Is there a better solution?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249330#4249330
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249330
From do-not-reply at jboss.com Thu Aug 13 05:45:51 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Thu, 13 Aug 2009 05:45:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: portable JAXWS deployment
example/steps? bottom up...
Message-ID: <25517517.1250156751042.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Running wsprovide offline and including the generated classes as well as the wsdl contract in the deployed archive (be sure it's correctly referenced in the @WebService) might save some time as less processing is required to perform the deployment.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249354#4249354
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249354
From do-not-reply at jboss.com Thu Aug 13 06:01:22 2009
From: do-not-reply at jboss.com (Till Dreier)
Date: Thu, 13 Aug 2009 06:01:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Printing Service with thread unsave
drivers
Message-ID: <20202085.1250157682048.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
We are developing a label printing webservice for our company.
The service gets the data from the request and creates a label with jasper. This is working fine. After that we want to print out the label and here we have the problem that the driver is not thread save. If we have some parallel requests the application crashes.
So I want to ask you if there is a solution how to make this working? We have now made the printing method singleton, this is working but not really performant. And we created a queuing thread for every printer but this is also not working because the printers are using the same driver. So there must be a solution with multiple processes.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249361#4249361
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249361
From do-not-reply at jboss.com Thu Aug 13 14:20:49 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 13 Aug 2009 14:20:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Printing Service with thread unsave
drivers
Message-ID: <24885769.1250187649807.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
How about doing the printing from a Message-Driven Bean (MDB). Have your web service send the label information to a queue and have one MDB per printer reading from the queue (probably same source code, but deployed multiple times - once per printer - each with its own config). Then your web service does not have to wait for the label to print before responding - the print request is asynchronous.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249505#4249505
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249505
From do-not-reply at jboss.com Fri Aug 14 04:09:26 2009
From: do-not-reply at jboss.com (Till Dreier)
Date: Fri, 14 Aug 2009 04:09:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Printing Service with thread unsave
drivers
Message-ID: <27399936.1250237366838.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Thank You for your response.
This could be a good solution, but i think there is still a problem with the printer driver dll which is not working in a multi thread application.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249587#4249587
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249587
From do-not-reply at jboss.com Mon Aug 17 10:17:26 2009
From: do-not-reply at jboss.com (fejesjoco)
Date: Mon, 17 Aug 2009 10:17:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - webservive form-like authentication
Message-ID: <27075233.1250518646999.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I would like to create a JBossWS webservice with a very specific authentication scheme, it's like securing a webservice like a website with form authentication. We want a login(...) webmethod (or several of them). When a client calls it and the authentication succeeds, we store that information (username, roles) in the session. All other webmethods would be declaratively secured like with @RolesAllowed. I haven't implemented anything yet, I'm only planning now.
I believe that in the endpoint class, I can get a @Resource WebServiceContext, and after that, in the login(...) method I can get the MessageContext, and then the HttpServletRequest, and then the HttpSession. This login(...) method is unsecured, so anyone can call it, we log them in and the client automatically receive a session cookie.
What I don't know how to do is this: I want JBoss to ask me before every webservice method invocation who the currently logged in user/Principal is and what roles they have. In this callback I would look at the session and return to JBoss the information that the login method stores in the session. So if I wanted to call WebServiceContext.getUserPrincipal, the principal would appear there, somehow magically, because there's no setUserPrincipal. And I believe that once a Principal is associated to the current request (or maybe the session, automatically), the @RolesAllowed annotation would work as expected.
Is there any extension point that lets me do this? So far I've only come up with some poor workarounds. I think I could create a GenericSOAPHandler, it knows what I want: it does execute before every request and it does have access to the session in the function handleInbound(MessageContext msgContext). I could throw an exception from there if the session is empty, but that's far from role-based security. Or, naturally, I have access to the session in all of the webmethods, so I could call an isInRole function at the start of every method, but that's much worse than doing the same thing declaratively.
I have no doubt that associating a principal+roles with a session is the only viable way for me. So is it possible? Please don't suggest WS-Security or basic authentication or things like that, requirements say we can't use that, it has to be with sessions+cookies (we're porting the server from .NET, yay, but the clients will have to stay the same).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249952#4249952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249952
From do-not-reply at jboss.com Mon Aug 17 10:21:02 2009
From: do-not-reply at jboss.com (fejesjoco)
Date: Mon, 17 Aug 2009 10:21:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: webservive form-like authentication
Message-ID: <14411059.1250518862770.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
One more thing, the application server is running JBoss 4.2.3 and JBossWS 3.0.5, although if there's no other way, I might be able to convince management to upgrade.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249953#4249953
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249953
From do-not-reply at jboss.com Mon Aug 17 10:47:48 2009
From: do-not-reply at jboss.com (fejesjoco)
Date: Mon, 17 Aug 2009 10:47:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: webservive form-like authentication
Message-ID: <9457754.1250520468979.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Alternatively, if I can't get JBoss to ask me who the currently logged in user is, can I explicitly tell it, like in a GenericSOAPHandler, xxx.yyy.setPrincipal()? Or where can I find information about a requests processing order? For example it would be good to know if session state is established BEFORE checking the @RolesAllowed declarative security.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249969#4249969
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249969
From postmaster at lists.jboss.org Tue Aug 18 03:15:35 2009
From: postmaster at lists.jboss.org (The Post Office)
Date: Tue, 18 Aug 2009 12:45:35 +0530
Subject: [jbossws-users] Jbossws-users@lists.jboss.org
Message-ID: <200908180712.n7I7CsGb010362@lists01.dmz-a.mwc.hst.phx2.redhat.com>
The original message was received at Tue, 18 Aug 2009 12:45:35 +0530 from 190.53.221.26
----- The following addresses had permanent fatal errors -----
jbossws-users at lists.jboss.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mail.zip
Type: application/octet-stream
Size: 29258 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090818/df881612/attachment.obj
From do-not-reply at jboss.com Tue Aug 18 06:14:54 2009
From: do-not-reply at jboss.com (sbutt)
Date: Tue, 18 Aug 2009 06:14:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss WS-Eventing vs JMS-Topic
Message-ID: <21256390.1250590494137.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi there,
I'm planning to implement a data-mining/analysis application (using WS-Eventing framework), which would get some data from a number of third party providers and analyse it.
I'm assuming my analysis application would be an Event Consumer (sink) WS-Client, which would subscribe to Event Producer(source), responsible for third party data providers? Do you think my understanding is correct at this stage?
Actually, my scenario is that I have a number of clients to whom we're sending some requests and in return getting some response. So in nut-shell what i'm looking for is a kind of analysis application, through which I can monitor what was sent to which client and what I got in response(success, error, warning etc etc).
So do you think that with the help of WS-Eventing framework I can take care of the above scenario?
Secondly, I have also read about JMS-Notification framework similarly based upon Producer-Subscriber design pattern. So can anybody suggest, which one is more robust and beneficial over the other?
One good reason I can think about WS-Eventing framework is that the communication is going to be in the form of SOAP, so Event-Consumer endpoint can be implemented in any language be it php, c#, asp etc etc.
In-case of JMS-Notification, it is going to be Java dependent. Is this assumption true and what other reasons there can be to give preference to WS-Eventing over JMS-Notification?
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250117#4250117
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250117
From do-not-reply at jboss.com Tue Aug 18 06:17:45 2009
From: do-not-reply at jboss.com (sbutt)
Date: Tue, 18 Aug 2009 06:17:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss WS-Eventing vs JMS-Topic
Message-ID: <28106439.1250590665591.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Sorry for the type in my previous message, from JMS-Notification i meant JMS-Topic framework.
"sbutt" wrote : Hi there,
| I'm planning to implement a data-mining/analysis application (using WS-Eventing framework), which would get some data from a number of third party providers and analyse it.
|
| I'm assuming my analysis application would be an Event Consumer (sink) WS-Client, which would subscribe to Event Producer(source), responsible for third party data providers? Do you think my understanding is correct at this stage?
|
| Actually, my scenario is that I have a number of clients to whom we're sending some requests and in return getting some response. So in nut-shell what i'm looking for is a kind of analysis application, through which I can monitor what was sent to which client and what I got in response(success, error, warning etc etc).
|
| So do you think that with the help of WS-Eventing framework I can take care of the above scenario?
|
| Secondly, I have also read about JMS-Notification framework similarly based upon Producer-Subscriber design pattern. So can anybody suggest, which one is more robust and beneficial over the other?
|
| One good reason I can think about WS-Eventing framework is that the communication is going to be in the form of SOAP, so Event-Consumer endpoint can be implemented in any language be it php, c#, asp etc etc.
|
| In-case of JMS-Notification, it is going to be Java dependent. Is this assumption true and what other reasons there can be to give preference to WS-Eventing over JMS-Notification?
|
| Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250120#4250120
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250120
From do-not-reply at jboss.com Tue Aug 18 09:54:00 2009
From: do-not-reply at jboss.com (lucastoledo)
Date: Tue, 18 Aug 2009 09:54:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain wsdl service
Message-ID: <24917787.1250603640130.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi there, I am running jboss-4.2.1.GA and I am encountering the exact problem.
I followed the instruction posted in the last reply (copying - jaxb-api.jar - jboss-jaxws.jar - jboss-saaj.jar from client\ to lib\endorsed\ ) and it caused a new type of problem.
Here is the log error:
| 14:31:22,046 ERROR [JmsServerSession] Unexpected error delivering message org.jboss.mq.SpyObjectMess
| age {
| Header {
| jmsDestination : QUEUE.AsyncPlugin
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:6-12506022817341
| jmsTimeStamp : 1250602281734
| jmsCorrelationID: null
| jmsReplyTo : null
| jmsType : null
| jmsRedelivered : false
| jmsProperties : {}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:6
| }
| }
| javax.ejb.EJBTransactionRolledbackException: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245)
| at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
| at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
| at $Proxy154.onMessage(Unknown Source)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
| at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
| at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
| at org.jboss.mq.SpySession.run(SpySession.java:323)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.RuntimeException: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:174)
| at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
| ... 17 more
| Caused by: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47)
| at javax.xml.ws.spi.Provider.provider(Provider.java:91)
| at javax.xml.ws.Service.(Service.java:83)
| at com.abm_uk.imswebservice.CurrentCrimesRequest_Service.(CurrentCrimesRequest_Service.java:42)
| at com.beatSystems.nottsPolice.crime.myCrime.CurrentCrimesUtility.getService(CurrentCrimesUtility.java:48)
| at com.beatSystems.mobaq.backend.notts.crime.configuration.CrimeConfigurationManager.getCurrentCrimesClient(CrimeConfigurationManager.java:277)
| at com.beatSystems.mobaq.backend.notts.crime.plugins.NottsMyCurrentCrimesUploadPlugin.processUpload(NottsMyCurrentCrimesUploadPlugin.java:55)
| at com.beatSystems.mobaq.core.plugin.GenericUploadPlugin.handle(GenericUploadPlugin.java:17)
| at com.beatSystems.mobaq.core.bean.PluginHandlerListenerBean.handle(PluginHandlerListenerBean.java:55)
| at com.beatSystems.mobaq.core.bean.PluginHandlerListenerBean.onMessage(PluginHandlerListenerBean.java:45)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
| ... 24 more
|
Has anyone encounter a similar problem as a result of these changes?
Thanks in advance for replies.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250190#4250190
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250190
From do-not-reply at jboss.com Tue Aug 18 12:14:21 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 18 Aug 2009 12:14:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain wsdl service
Message-ID: <9126967.1250612061665.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Is this on the client side? Looks like a JAR file is missing from the classpath. The missing class is in client/jboss-common-client.jar and client/jbossall-client.jar in 4.2.3 (I don't have a copy of 4.2.1 handy to check there).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250230#4250230
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250230
From do-not-reply at jboss.com Tue Aug 18 14:10:05 2009
From: do-not-reply at jboss.com (monkeyden)
Date: Tue, 18 Aug 2009 14:10:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Endpoint registration
Message-ID: <14862320.1250619005081.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I was able to get the endpoint registered when deployed in it's own jar file, but I'm not able to deploy it when it's lives within my ejb jar inside the ear file. I would imagine the solution is simple but I have yet to track it down. Suggestions are greatly appreciated.
Thanks
P.S.
Is this forum still active or should I be asking somewhere else?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250245#4250245
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250245
From do-not-reply at jboss.com Wed Aug 19 00:36:02 2009
From: do-not-reply at jboss.com (anoop10)
Date: Wed, 19 Aug 2009 00:36:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error:
org.jboss.util.NotImplementedException: getTextConten
Message-ID: <14549716.1250656562785.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I was trying to write a SOAP client program using Servlet. When the service method called, I am getting the following error.
16:05:02,236 ERROR [STDERR] org.jboss.util.NotImplementedException: getTextContent
16:05:02,237 ERROR [STDERR] at org.jboss.ws.core.soap.NodeImpl.getTextContent(NodeImpl.java:611)
16:05:02,237 ERROR [STDERR] at org.mobicents.slee.resource.http.LdapSearchServlet.service(LdapSearchServlet.java:85)
16:05:02,237 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
16:05:02,237 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:05:02,238 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
16:05:02,240 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
16:05:02,240 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
16:05:02,240 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
16:05:02,240 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
16:05:02,240 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
The code I have written in Servelt is
SOAPMessage responseSM = connection.call(sm, endpoint);
SOAPPart soapPart = responseSM.getSOAPPart();
SOAPEnvelope soapEnv = soapPart.getEnvelope();
SOAPBody soapBody = soapEnv.getBody();
out.println(soapBody.getFirstChild().getFirstChild().getTextContent());
I am using the above code to print value of a text node and getting the above exception on runtime.
I am using JBOSS 4.2.3GA and JDK 1.6.
Please help me to solve this issue.
Thanks
Anoop
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250290#4250290
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250290
From do-not-reply at jboss.com Wed Aug 19 02:22:41 2009
From: do-not-reply at jboss.com (anoop10)
Date: Wed, 19 Aug 2009 02:22:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: DOM API on SOAPElementImpl causes
NotImplementedExceptio
Message-ID: <19585139.1250662961819.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I am facing the same issue. Will you please help me to solve this issue.
Note: I have posted this issue in the following link.
http://jboss.org//index.html?module=bb&op=viewtopic&p=4250290
Thanks
Anoop
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250295#4250295
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250295
From do-not-reply at jboss.com Wed Aug 19 06:45:38 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 19 Aug 2009 06:45:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Endpoint registration
Message-ID: <1067357.1250678738881.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Have a look at the eardeployment sample in the jbossws testsuite, it does what you're trying to do.
The forum is still active, but you might not get a lot of replies in this period of the year ;-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250354#4250354
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250354
From do-not-reply at jboss.com Wed Aug 19 10:39:49 2009
From: do-not-reply at jboss.com (jse)
Date: Wed, 19 Aug 2009 10:39:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem installing
jbossws-native-3.1.1.GA onto jboss-4.2.3.
Message-ID: <14595448.1250692789785.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi
I have a problem with my installation of jbossws 3.1.1 over the top of jboss 4.2.3.GA. I get this error:
| 2009-08-19 14:53:36,920 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/app/jboss-4.2.3.GA/server/fred/tmp/deploy/tmp32687FRED.ear-contents/FRED.war
| java.lang.IllegalStateException: Failed to load org.jboss.wsf.spi.invocation.WebServiceContextFactory: org.jboss.wsf.container.jboss42.WebServiceContextFactoryImpl
| at org.jboss.wsf.spi.util.ServiceLoader.loadFromServices(ServiceLoader.java:97)
| ...
| lots of lines
| ...
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.lang.NoClassDefFoundError: org/jboss/wsf/spi/invocation/WebServiceContextEJB
| at java.lang.Class.getDeclaredConstructors0(Native Method)
| at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
| at java.lang.Class.getConstructor0(Unknown Source)
| at java.lang.Class.newInstance0(Unknown Source)
| at java.lang.Class.newInstance(Unknown Source)
| at org.jboss.wsf.spi.util.ServiceLoader.loadFromServices(ServiceLoader.java:92)
|
Looking at the jbossws-native-3.1.1.GA binary distribution it appears that there is no class org.jboss.wsf.spi.invocation.WebServiceContextEJB. It is not contained within jbossws-spi.jar.... although jbossws-native-core.jar does contain org.jboss.wsf.stack.jbws.WebServiceContextEJB
I can see this class in the jbossws-spi.jar for a jboss 4.2.3 that has not been "upgraded" with jbossws-native-3.1.1
The classes in FRED.war were built using the ws*.bat scripts/code that shipped with the jbossws shipped with Jboss 4.2.3.GA. Not sure if this is relevant.
Any advice gratefully received.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250417#4250417
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250417
From do-not-reply at jboss.com Wed Aug 19 11:54:29 2009
From: do-not-reply at jboss.com (ivan.stefanov)
Date: Wed, 19 Aug 2009 11:54:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JAX-WS Web Service Authentication
(NTLM) against a MS CRM Se
Message-ID: <32476192.1250697269225.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello everybody,
I am currently developing a jboss web service client, which is supposed to connect to a web service on a Microsoft CRM Dynamics (I hope I've got the name right) instance, running on an Internet Information Server. The service itself and the relevant data types are defined in a what appears to be a standard CrmServiceWsdl.aspx file.
I've generated the Java classes with the /bin/wsconsume.bat tool in the JBoss folder. We have many times used this tool successfully, when programming JBoss web services and clients for them. Everything seemed nice and well, the client easily connected (including HTTP BASIC authentication) and sent what looked like a correct request to a dummy JBoss web service which I wrote for testing purposes. The problems appeared when we tried the real thing, namely connecting to the MS CRM web service. The IIS Server has the "Windows Intergrated Security" authentication activated, which is supposed to be NTLM.
First I have tried doing HTTP Basic, as the IIS was also supposed to support it:
| url = new java.net.URL(InfondsParameter.CRMWebServiceUrlCreateUpdateTask.get(em));
|
| CrmTaskServiceSoap port = (new CrmTaskService(url, new QName("http://schemas.microsoft.com/crm/2007/WebServices", "CrmService")))
| .getCrmTaskServiceSoap();
| ((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "username");
| ((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "password");
|
This didn't work and I kept getting the "javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set" error message plus debug messages (my own) telling me the WSDL could not be reached.
Then I decided to aim for the NTLM authentication. Following advice I found on many (non official) sources in Internet, I wrote the following:
| static class MyAuthenticator extends Authenticator {
|
| private String user;
| private String pass;
|
| public MyAuthenticator(String user, String pass) {
| this.user = user;
| this.pass = pass;
| }
|
| public PasswordAuthentication getPasswordAuthentication() {
| return (new PasswordAuthentication(kuser, kpass.toCharArray()));
| }
| }
|
| public static void callCreateTask()
|
| Authenticator.setDefault(new MyAuthenticator("username", "password"));
|
| url = new java.net.URL(InfondsParameter.CRMWebServiceUrlCreateUpdateTask.get(em));
|
| CrmTaskServiceSoap port = (new CrmTaskService(url, new QName("http://schemas.microsoft.com/crm/2007/WebServices", "CrmService")))
| .getCrmTaskServiceSoap();
|
| ...
|
| String ret = port.create(ent);
| }
|
Now the WSDL seems to get reached and consumed, but at the last row I still get a "org.jboss.ws.WSException: Invalid HTTP server response [401] - Unauthorized". The port.create(ent) statement is just calling the "create" operation, defined in the WSDL, with the argument being an entity, also as defined in the WSDL.
I really fail to grasp what is going wrong. As far as I know, Java is supposed to support NTLM Authentication "off the shelf" through the Authenticator class and it obviously does some work, as the WSDL residing on the IIS could be opened and read. However, the call to the service itself could not be authorised. I've found some references to a CrmAuthenticationToken having to be set, but neither my CrmTaskService (which is the standard CrmService), nor CrmTaskServiceSoap (which is the proxy of the service) has been generated with a possibility to set Credentials or AuthenticationToken.
Has anyone had exprience with interfacing the Microsoft CRM Web Services? Any advice, insight or ideas are welcome!
Thank you in advance!
Best regards,
Ivan Stefanov
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250438#4250438
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250438
From do-not-reply at jboss.com Wed Aug 19 11:57:54 2009
From: do-not-reply at jboss.com (ksinno)
Date: Wed, 19 Aug 2009 11:57:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: ...Port does not contain operation
meta data for: {http:
Message-ID: <104970.1250697474366.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
Any updates on this issue ? Has anyone been able to solve it ?
I'm using JBoss 5.1.0 and I get this problem. (SOAPFaultException... Port does not contain operation meta data for EncryptedData... )
Also what is the key for this issue on Jira ?
thanks!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250439#4250439
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250439
From do-not-reply at jboss.com Wed Aug 19 14:47:40 2009
From: do-not-reply at jboss.com (sinjem)
Date: Wed, 19 Aug 2009 14:47:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 5.0.1.GA Native Maven2
Eclipse POM dependencies: d
Message-ID: <24549201.1250707660256.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
So I'll respond to my own post just in case anyone else runs into a similar problem. I finally figured out the dependency that allows me to reference JBoss from within an Eclipse workspace and run my deployed web service on a local JBoss Runtime Server.
You'll need the following dependency in your pom.xml file:
| org.jboss.jbossas
| jboss-as-main
| 5.0.1.GA
| provided
|
By adding this dependency I was able to call my mavenized JEE web service, bundled in an ear (as a war with an associated ejb.jar) all deployed to an Eclipse JBoss Runtime with nothing on my project classpath other than the JDK and Maven references.
Hope this helps any one else who is struggling with something similar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250459#4250459
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250459
From do-not-reply at jboss.com Wed Aug 19 18:57:34 2009
From: do-not-reply at jboss.com (preddy1104@gmail.com)
Date: Wed, 19 Aug 2009 18:57:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Incomplete Deployment when EJB turn
into webservices
Message-ID: <11100260.1250722654541.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I am facing the same problem, did you find any solution?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250510#4250510
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250510
From do-not-reply at jboss.com Wed Aug 19 19:15:53 2009
From: do-not-reply at jboss.com (preddy1104@gmail.com)
Date: Wed, 19 Aug 2009 19:15:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error deploying web services
Message-ID: <10548960.1250723753176.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
While deploying web service module the following exception is thrown. If the session bean is not marked for web services then the bean deploys without any problem.
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:jndiName=MySEI,service=EJB
State: FAILED
Reason: java.lang.NoSuchMethodException: Not found in bean class: public abstract void javax.ejb.EJBObject.remove() throws java.rmi.RemoteException,javax.ejb.RemoveException
Thanks in advance!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250512#4250512
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250512
From do-not-reply at jboss.com Thu Aug 20 06:20:55 2009
From: do-not-reply at jboss.com (thrustsream)
Date: Thu, 20 Aug 2009 06:20:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceException: Unable to load
Provider
Message-ID: <19348866.1250763655967.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
"gsekar" wrote : https://jira.jboss.org/jira/browse/JBPAPP-941
|
| This fixed the same issue I was having. I didnt have to remove or copy any jars
I have replaced the jar files, as you mentioned,, still i see the same error
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250573#4250573
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250573
From do-not-reply at jboss.com Thu Aug 20 06:34:15 2009
From: do-not-reply at jboss.com (sridhar1985)
Date: Thu, 20 Aug 2009 06:34:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Failed to create a new SAX parser
Message-ID: <926032.1250764455603.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I have switched from Jboss 4.2.2 to JBoss 5.1.0 GA.
While deploying my workspace i am getting the error "Failed to create a new SAX parser"
I am using xmlparserv2.jar. i can't delete this bcoz i need it in my workspace.
Even i tried by adding jboss-classloading.xml in WEB-INF folder with the following code
Still i am getting same error with some more.
Plz help me out. Thanks in advance.
A.Sridhar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250578#4250578
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250578
From do-not-reply at jboss.com Thu Aug 20 06:36:40 2009
From: do-not-reply at jboss.com (thrustsream)
Date: Thu, 20 Aug 2009 06:36:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceException: Unable to load
Provider
Message-ID: <23560448.1250764600847.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I use jboss 4.0.5
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250580#4250580
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250580
From do-not-reply at jboss.com Thu Aug 20 07:53:28 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Thu, 20 Aug 2009 07:53:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Where can I find jbwse.xsd
Message-ID: <25596077.1250769208311.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Greetings all,
I am trying to create a simple WS-Eventing prototype and I cannot locate jbwse.xsd. Anyone know where I can find it?
Earnie!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250610#4250610
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250610
From do-not-reply at jboss.com Thu Aug 20 08:06:13 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 20 Aug 2009 08:06:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can I find jbwse.xsd
Message-ID: <12352973.1250769973327.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
You're looking for eventing_200408.xsd, you should find it in jbossws-native-core.jar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250614#4250614
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250614
From do-not-reply at jboss.com Thu Aug 20 08:18:23 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Thu, 20 Aug 2009 08:18:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can I find jbwse.xsd
Message-ID: <17196578.1250770703334.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Thanks Richard.
I find an eventing.xsd in jbossws-native-core.jar. What about the associated wsdl? I am using JBoss 5.0.1 is that makes a difference. Also, should I need to include the .xsd and .wsdl in my jar when I deploy?
Earnie!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250621#4250621
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250621
From do-not-reply at jboss.com Thu Aug 20 08:51:26 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 20 Aug 2009 08:51:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can I find jbwse.xsd
Message-ID: <28701186.1250772686356.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
See our samples and docs to see how to use WS-Eventing properly.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250629#4250629
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250629
From do-not-reply at jboss.com Thu Aug 20 08:55:30 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Thu, 20 Aug 2009 08:55:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Where can I find jbwse.xsd
Message-ID: <4929585.1250772930413.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Specifically which sample? And I have looked at the User Guide and still find I have these questions.
Earnie!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250630#4250630
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250630
From do-not-reply at jboss.com Thu Aug 20 10:28:05 2009
From: do-not-reply at jboss.com (monkeyden)
Date: Thu, 20 Aug 2009 10:28:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Endpoint registration
Message-ID: <9090636.1250778485236.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Are there any special files or configuration needed to get it to deploy in an ear? I have looked at the testsuite example as well as the "seam bay" example and have found no differences at all. These are the very same SEI and impl files, which deployed just fine in its own independent jar file.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250659#4250659
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250659
From do-not-reply at jboss.com Thu Aug 20 11:06:51 2009
From: do-not-reply at jboss.com (hnqoliveira)
Date: Thu, 20 Aug 2009 11:06:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Receiving Compressed WebService
Requests
Message-ID: <18144693.1250780811802.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I nedd help too for the same problem ... I am a five days searching the solution.
thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250676#4250676
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250676
From do-not-reply at jboss.com Thu Aug 20 11:43:53 2009
From: do-not-reply at jboss.com (alexb413)
Date: Thu, 20 Aug 2009 11:43:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Enabling HTTPS for runtime generated
WSDL
Message-ID: <6786012.1250783033295.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello,
I'm trying to enable HTTPS for WSDLs that are generated using the annotations in the java file, rather than through a static XML file. So, the application is just an ear file that is deployed on JBoss.
I can do this via @WebContext(transportGuarantee="CONFIDENTIAL") but this means that we need to change the source code, check-in and rebuild, everytime we want to enable/disable HTTPS.
I was wondering if its possible to do this through a web.xml file, that would work in parallel with the annotations in the source code, just for the transport-guarantee part. The problem is, this application is just an ear file, so it doesn't have it's own directory in JBoss with it's own config files. Is there anyway to do this?
Thanks in advance,
Alex
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250693#4250693
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250693
From do-not-reply at jboss.com Thu Aug 20 15:34:01 2009
From: do-not-reply at jboss.com (rk_jboss)
Date: Thu, 20 Aug 2009 15:34:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting NotImplementedException for
NodeImpl.getTextContent(
Message-ID: <27532003.1250796841642.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I'm getting org.jboss.util.NotImplementedException, when SAML api internally calls
org.jboss.ws.core.soap.NodeImpl.getTextContent() method. I'm using jboss-5.0.0.GA
with jbossws-native-3.1.2.GA.
Looks like jbossws implementation does not support some of the DOM API's.
Just I'm wondering, is there any alternative ways to make it work. Pls can you update me
if jboss has any tentative plans to implement those methods.Its a show stopper for me.
I really appreciate your response.
I'm copying the exception stacktrace.
| org.jboss.util.NotImplementedException: getTextContent
| at org.jboss.ws.core.soap.NodeImpl.getTextContent(NodeImpl.java:618)
| at org.opensaml.xml.util.XMLHelper.getXSIType(XMLHelper.java:111)
| at org.opensaml.xml.io.UnmarshallerFactory.getUnmarshaller(UnmarshallerFactory.java:77)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:300)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:120)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:317)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:120)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:317)
| at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:120)
| at com.mycompany.xxx.AssertionValidatorHandler.handleMessage(AssertionValidatorHandler.java:111)
| at com.mycompany.xxx.AssertionValidatorHandler.handleMessage(AssertionValidatorHandler.java:1)
| at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:293)
| at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:138)
| at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:197)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:498)
| 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:109)
| 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:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
| 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:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
|
Thanks,
Ram
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250732#4250732
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250732
From do-not-reply at jboss.com Fri Aug 21 06:55:52 2009
From: do-not-reply at jboss.com (jayblanc54)
Date: Fri, 21 Aug 2009 06:55:52 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services] - Re: Implementing WS-Security
Usename Token Profile Authentic
Message-ID: <23870983.1250852152933.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Thanks alessio, setting StubExt.PROPERTY_AUTH_TYPE works fine.
I have also a problem with SoapUI Digest which always give me an Invalid User.
for exemple : using kermit/thefrog, the generated request for SoapUI is :
|
|
|
|
| kermit
| a4QMImbwZWY5ofgqZQK7SqkWF9M=
| bEC2QeCam1oBnj+wpGBPQw==
| 2009-08-21T10:47:42.580Z
|
|
|
|
|
|
|
|
Whereas the generated request for the same credentials using the jboss endorsed JAX-WS 2.1 client is :
|
|
|
|
| 2009-08-21T10:49:48.298Z
| 2009-08-21T10:54:48.298Z
|
|
| kermit
| oOxvxKABFwsUfCvOpjE+GfyrQJs=
| NXS4XKiKBe9eaJdiAjtCG23A1e3w3wZ9j38POOu4Dvg=
| 2009-08-21T10:49:48.289Z
|
|
|
|
|
|
|
|
I don't understand why the SoapUI client is not able to authenticate using the same configuration...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250851#4250851
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250851
From do-not-reply at jboss.com Fri Aug 21 09:13:56 2009
From: do-not-reply at jboss.com (ksinno)
Date: Fri, 21 Aug 2009 09:13:56 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services] - Re: ...Port does not contain
operation meta data for: {http:
Message-ID: <422674.1250860436714.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
JBoss processes the HandlerTypes in the following order for JAXWS:
POST
ENDPOINT
PRE
Since the POST handler needs to parse some information from the soap message to identify the ENDPOINT handler chain to call, you should do your decrypting at the level of the POST handler.
To do this, you can annotate your webservice class with @EndpointConfig and define your post handlers in the file standard-jaxws-endpoint-config.xml under META-INF
Alternatively, to stay independent from JBoss specific code (ie no dependency to JBoss), you do the below configuration at the level of the deployment descriptors, by modifying the file standard-jaxws-endpoint-config.xml under [JBOSS_HOME]\server\[type]\deployers\jbossws.deployer\META-INF (path differs for JBoss 4.3 ... but same file name) and adding your post-handler chain (example below).
| Murex Security Handlers
|
|
| ##SOAP11_HTTP
|
| My Security Handler
| package.security.MySecurityClass
|
|
|
|
The Config-name you create should be referenced in your web.xml file inside your war file such as the following:
| jbossws-config-name
| My Security Handler
|
Cheers.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250884#4250884
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250884
From do-not-reply at jboss.com Mon Aug 24 08:13:40 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Mon, 24 Aug 2009 08:13:40 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: How to implement
WS-Eventing
Message-ID: <28436744.1251116020190.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Joe,
You ever figure this out? I am stuck also. Chap 16 just isn't clear on a number of issues.
Earnie!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251175#4251175
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251175
From do-not-reply at jboss.com Mon Aug 24 15:42:04 2009
From: do-not-reply at jboss.com (wuyanbo)
Date: Mon, 24 Aug 2009 15:42:04 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - regarding message
types in bottom-up service generation
Message-ID: <22746465.1251142924132.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
I am learning web service using jboss 5 and jbossws as runtime. I have created a POJO which is quoted below:
| @WebService
| public class HelloWorld {
|
| @WebMethod
| public String sayHello(@WebParam(name="name") String name) {
| return "Hello, " + name;
| }
| }
|
The problem is when i deployed the service into jboss, at runtime, the wsdl file generated contains complex type definitions for the parameter and return value. I expected xsd:string as message type, but it wasn't so. Can anybody be kind to tell me why this happens and how to avoid it? Thanks
Here is the wsdl file generated:
| -
| -
| -
|
|
| -
| -
|
|
|
| -
| -
|
|
|
|
|
| -
|
|
| -
|
|
| -
| -
|
|
|
|
| -
|
| -
|
| -
|
|
| -
|
|
| -
| -
|
|
|
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251282#4251282
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251282
From do-not-reply at jboss.com Tue Aug 25 06:18:28 2009
From: do-not-reply at jboss.com (vinothkumar)
Date: Tue, 25 Aug 2009 06:18:28 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Getting Classcast
Exception Inconsistently on WSAddressing I
Message-ID: <20907373.1251195508212.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello all,
We are using JBOSS 4.2.3 with JBOSSWS Native 3.1.0 deployed.
We had implemented WSAddressing for Our Services as per the Steps given in the link : http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide.
This WSAddressing implementation works fine without any issues if we give a single hit to the Services from the client for a given time. But if we have multiple simultaneous hits, we are getting the Classcast Exception inconsistently.
We had done the following changes in Client,
Service service = Service.create(wsdlURL, serviceName);
| port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
| BindingProvider bindingProvider = (BindingProvider)port1;
|
| List customHandlerChain = new ArrayList();
| customHandlerChain.add(new ClientHandler());
| customHandlerChain.add(new WSAddressingClientHandler());
| bindingProvider.getBinding().setHandlerChain(customHandlerChain);
The Exception that we are getting is,
javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.mobax.signage.ws.RemoveDeviceResponse cannot be cast to com.mobax.signage.ws.GetDeviceResponseResponse
| at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
| at $Proxy103.removeDevice(Unknown Source)
| at com.mobax.mashup.webserviceconsumer.SignageServiceConsumer.removeDevices(SignageServiceConsumer.java:264)
| at com.mobax.mashup.responsebuilder.EnablerResponseParser.removeDevice(EnablerResponseParser.java:1489)
| at com.mobax.mashup.servlet.signage.RemoveDevice.processRequest(RemoveDevice.java:60)
| at com.mobax.mashup.servlet.signage.RemoveDevice.doGet(RemoveDevice.java:88)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
| 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)
As per Our understanding,
We are invoking the method port1.getDeviceResponse(). Before receiving the response for this request, we are invoking another method port1.removeDevice(). The Proxy seems to be waiting for the Response for the second request removeDevice(). When it receives the Response for the first request getDeviceResponse(), the proxy tries to parse this response assuming that this response belongs to the Second request, thus Resulting in Classcast Exception.
We would like to know whether anybody have Successfully implemented the WSAddressing in their Services without having any issues.
Interestingly, we had find out a WORKAROUND for this issue. The workaround is to generate the following code for every Request. i.e., before calling any Requests, if we generate the following proxy every time newly, then the Exception does not Occurs.
| port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
| BindingProvider bindingProvider = (BindingProvider)port1;
|
| List customHandlerChain = new ArrayList();
| customHandlerChain.add(new ClientHandler());
| customHandlerChain.add(new WSAddressingClientHandler());
| bindingProvider.getBinding().setHandlerChain(customHandlerChain);
Does anybody have any idea on this? We are not getting enough responses on our previous posts for this issue. So I had opened a new thread and provided more information on this issue.
Thanks for reading this long post.
Regards,
Vinoth Kumar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251412#4251412
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251412
From do-not-reply at jboss.com Tue Aug 25 07:14:40 2009
From: do-not-reply at jboss.com (vinothkumar)
Date: Tue, 25 Aug 2009 07:14:40 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Getting warning while
deploying the WSAddressing Enabled Ser
Message-ID: <22449563.1251198880072.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hello all,
We are using JBOSS 4.2.3 with JBOSSWS Native 3.1.0 deployed.
We had implemented the WSAddressing for our Services as per the Steps given in the link http://www.jboss.org/community/wiki/JBossWS-NativeWS-AddressingTutorial
when we deploy the war file, we are getting the following warning.
| 16:33:30,434 WARN [WSDL11Reader] UsingAddressing extensibility element not supported yet.
| 16:33:31,145 WARN [WSDL11Reader] UsingAddressing extensibility element not supported yet.
Is there anything missing in our implementation?. Is there something need to be configured?
Thanks,
Vinoth Kumar.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251426#4251426
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251426
From do-not-reply at jboss.com Tue Aug 25 08:01:40 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Tue, 25 Aug 2009 08:01:40 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Working WS-Eventing
example
Message-ID: <2439926.1251201700907.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Does anyone have a working example of WS-Eventing they would be willing to share? I have been through the user guide and the source code but I am still missing something.
Thanks in advance for any and all help.
Earnie!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251448#4251448
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251448
From do-not-reply at jboss.com Wed Aug 26 16:55:35 2009
From: do-not-reply at jboss.com (ramk5101)
Date: Wed, 26 Aug 2009 16:55:35 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - proxy server tunneling
https connection to backend jboss as
Message-ID: <15981274.1251320135613.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Our jboss application server is fronted by a proxy server.when a request comes in over ssl, the proxy terminates ssl and passes http to jboss.Since the End point address is generated dynamically the end point url is using http protocol ,but our proxy server allows only https protocol.Is there any configuration change that we can make so dynamically genrated protocol is https.
thanks
So we basically need a way to publish secure urls while still declaring the service as non-secure.
I tried setting below in jboss-beans.xml :
is there a solution for the above problem.
thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251906#4251906
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251906
From do-not-reply at jboss.com Thu Aug 27 02:35:25 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 27 Aug 2009 02:35:25 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: proxy server
tunneling https connection to backend jboss
Message-ID: <14781331.1251354925975.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Is your endpoint EJB or POJO?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251958#4251958
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251958
From do-not-reply at jboss.com Thu Aug 27 02:36:25 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 27 Aug 2009 02:36:25 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: proxy server
tunneling https connection to backend jboss
Message-ID: <11904586.1251354985076.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
And do you use static WSDLs or it is generated for you on demand?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251959#4251959
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251959
From do-not-reply at jboss.com Thu Aug 27 05:45:11 2009
From: do-not-reply at jboss.com (erasmomarciano)
Date: Thu, 27 Aug 2009 05:45:11 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Help
org.jboss.web.tomcat.security.SecurityAssociationValve
Message-ID: <28818565.1251366311928.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
With a monitoring tool of java , i saw that there is a method
anonymous wrote :
| void org.jboss.web.tomcat.security.SecurityAssociationValve.invoke()
|
that has been invoked many times.
The time of answer is too high indeed.
Everyone can help me?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252012#4252012
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252012
From do-not-reply at jboss.com Thu Aug 27 07:27:28 2009
From: do-not-reply at jboss.com (seamyong)
Date: Thu, 27 Aug 2009 07:27:28 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Cannot change the
context root for web service
Message-ID: <21247774.1251372448520.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi all,
I would like to seek for help how to change the context root for the webservices. From my http://localhost:8080/jbossws/services, two wsdl[s] are shown with the following URL.
1.**************************************************************
Endpoint Name jboss.ws:context=amslogin-amslogin, endpoint=WSUserServiceImpl
Endpoint Address http://AMS-WS-007:8180/amslogin-amslogin/WSUserServiceImpl?wsdl
***************************************************************
2.************************************************************
Endpoint Name jboss.ws:context=amslogin,endpoint=WSUserService
Endpoint Address http://AMS-WS-007:8180/amslogin/ws/WSUserService?wsdl
*************************************************************
However, only the first link works; the second cant be accessed. The following error messages showed whenever i tried to run my web applicaton.
*************************************************************
Exceptions:
*************************************************************
org.jboss.ws.WSException: Cannot obtain config: SOAP Request Handler
at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:148)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:704)
at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigNameInternal(EndpointMetaData.java:695)
at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigName(EndpointMetaData.java:679)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.processEndpointConfig(JAXWSServerMetaDataBuilder.java:76)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:137)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
19:07:01,500 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Helps are needed!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252035#4252035
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252035
From do-not-reply at jboss.com Thu Aug 27 17:20:06 2009
From: do-not-reply at jboss.com (yonghongb)
Date: Thu, 27 Aug 2009 17:20:06 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Jboss and Jboss WS jar
files conflict
Message-ID: <32579323.1251408006791.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
We are using jboss and jboss ws for our one application. We are facing jar files conflict.
We have our other apps jar files , jboss and jboss ws jar files.
Some of them are duplicated/triplicate. Even the order can case problem.
Any idea how to figure out ?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252150#4252150
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252150
From do-not-reply at jboss.com Fri Aug 28 06:18:29 2009
From: do-not-reply at jboss.com (lucastoledo)
Date: Fri, 28 Aug 2009 06:18:29 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Cannot obtain wsdl
service
Message-ID: <24781407.1251454709636.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi there,
I have reverted the changes that led to this error and it workss
Maybe a reason for it is that I modified WSDL_URL to point to actual WSDL in file system instead of using an http URL path.
Thanks PeterJ for your reply.
Regards,
Lucas
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252270#4252270
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252270
From do-not-reply at jboss.com Fri Aug 28 06:57:52 2009
From: do-not-reply at jboss.com (stata)
Date: Fri, 28 Aug 2009 06:57:52 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Overriding wsdl4j.jar
that comes with JBoss
Message-ID: <24744077.1251457072909.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi,
My application uses a wsdl4j.jar but JBoss also has a wsdl4j.jar in default\deployers\jbossws.deployer. I want it to pick up classes from my application's wsdl4j.jar. I used the following configuration in jboss-web.xml:
com.ibm:archive=wsdl4j.jar
java2ParentDelegation=false
Also I tried adding a classpath entry in jboss-service.xml but none of these approaches work. If I remove the jar that comes with JBoss, my application works fine, but I don't want to do that. Is there some way out?
Thanks in advance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252283#4252283
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252283
From do-not-reply at jboss.com Fri Aug 28 07:01:23 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 28 Aug 2009 07:01:23 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JBossWS 3.2.0.GA
released
Message-ID: <16892326.1251457283738.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I'm happy to announce the release of JBossWS-Native 3.2.0 GA.
For a list of the new features, improvements and bug fixes, please refer the release notes available here:
http://labs.jboss.com/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.2.0.GA.txt
The supported target containers for this release are JBoss 5.0.0.GA, JBoss 5.0.1.GA and JBoss 5.1.0.GA.
The binaries, including the samples can be obtained here:
http://labs.jboss.com/jbossws/downloads/
Installation instructions can be found here:
http://www.jboss.org/community/wiki/JBossWS
To get started please have a look at the Quick Start and User Guide:
http://www.jboss.org/community/wiki/JBossWS-QuickStart
http://www.jboss.org/community/wiki/JBossWS-UserGuide
Many thanks to the team and contributors making this release possible.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252285#4252285
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252285
From do-not-reply at jboss.com Fri Aug 28 12:29:11 2009
From: do-not-reply at jboss.com (donakalz)
Date: Fri, 28 Aug 2009 12:29:11 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - vfs problems with
jboss web service
Message-ID: <12115529.1251476951458.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Hi Everyone.
I get a very strange error when I try to deploy my ear application. I use the following versions of software:
JBoss AS 5.0.0GA
seam 2.1.2GA
Richfaces 3.3.1GA
JBossWS 3.2.0GA
My ear is organized as follows:
Soko-ear
|-----------> soko-beans
|-----------> soko-web
soko-beans consissts of my EJBs and I use seam as the component model. Without any web service file in soko-beans, the ear gets deployed and the application is browsable. But if I create a POJO, annotate it @WebService (and its methods with @WebMethod) ....and effectively signal to seam and jboss that I need a webservice deployed, the ear never gets successfully deployed. Below is the stack trace of the errors I get. It seems to be something with vfs...Please if any of you knows what the problem might be, kindly post comments.
| 13:17:41,453 INFO [TomcatDeployment] deploy, ctxPath=/soko-web/ui, vfsUrl=soko-ear.ear/soko-beans.jar
| 13:17:41,578 WARN [config] Unable to process deployment descriptor for context '/soko-web/ui'
| 13:17:42,421 ERROR [Digester] End event threw exception
| java.lang.NoSuchMethodException: No such accessible method: addResource() on object: org.ajax4jsf.resource.ResourceBuilderImpl
| at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:278)
| at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:217)
| at org.apache.commons.digester.Rule.end(Rule.java:253)
| at org.apache.commons.digester.Digester.endElement(Digester.java:1332)
| at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.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.apache.commons.digester.Digester.parse(Digester.java:1887)
| at org.ajax4jsf.resource.ResourceBuilderImpl.registerConfig(ResourceBuilderImpl.java:209)
| at org.ajax4jsf.resource.ResourceBuilderImpl.registerResources(ResourceBuilderImpl.java:153)
| at org.ajax4jsf.resource.ResourceBuilderImpl.init(ResourceBuilderImpl.java:224)
| at org.ajax4jsf.renderkit.ChameleonRenderKitFactory.(ChameleonRenderKitFactory.java:62)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
| at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:519)
| at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:405)
| at javax.faces.FactoryFinder.access$400(FactoryFinder.java:135)
| at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:717)
| at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
| at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:186)
| at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:131)
| at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
| at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
| at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:75)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| 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:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy36.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
| 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.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.start(ServiceController.java:460)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| 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.doInstallParentFirst(DeployersImpl.java:1178)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
| 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)
| 13:17:42,437 ERROR [[/soko-web/ui]] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
| com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! No such accessible method: addResource() on object: org.ajax4jsf.resource.ResourceBuilderImpl
| at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:213)
| at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
| at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:75)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| 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:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy36.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
| 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.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.start(ServiceController.java:460)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| 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.doInstallParentFirst(DeployersImpl.java:1178)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
| 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.NoSuchMethodException: No such accessible method: addResource() on object: org.ajax4jsf.resource.ResourceBuilderImpl
| at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:278)
| at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:217)
| at org.apache.commons.digester.Rule.end(Rule.java:253)
| at org.apache.commons.digester.Digester.endElement(Digester.java:1332)
| at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.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.apache.commons.digester.Digester.parse(Digester.java:1887)
| at org.ajax4jsf.resource.ResourceBuilderImpl.registerConfig(ResourceBuilderImpl.java:209)
| at org.ajax4jsf.resource.ResourceBuilderImpl.registerResources(ResourceBuilderImpl.java:153)
| at org.ajax4jsf.resource.ResourceBuilderImpl.init(ResourceBuilderImpl.java:224)
| at org.ajax4jsf.renderkit.ChameleonRenderKitFactory.(ChameleonRenderKitFactory.java:62)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
| at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:519)
| at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:405)
| at javax.faces.FactoryFinder.access$400(FactoryFinder.java:135)
| at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:717)
| at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
| at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:186)
| at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:131)
| at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
| ... 61 more
| 13:17:42,437 ERROR [StandardContext] Error listenerStart
| 13:17:42,437 ERROR [StandardContext] Context [/soko-web/ui] startup failed due to previous errors
| 13:17:42,531 ERROR [AbstractKernelController] Error installing to Start: name=jboss.web.deployment:war=/soko-web/ui state=Create mode=Manual requiredState=Installed
| org.jboss.deployers.spi.DeploymentException: URL vfsfile:/C:/Soko/jbdevstudio/jboss-eap/jboss-5.0.0.GA/server/default/deploy/soko-ear.ear/soko-beans.jar/ deployment failed
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:388)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| 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:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy36.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
| 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.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.start(ServiceController.java:460)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| 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.doInstallParentFirst(DeployersImpl.java:1178)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
| 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)
| 13:17:42,546 INFO [TomcatDeployment] undeploy, ctxPath=/soko-web, vfsUrl=soko-ear.ear/soko-web.war
| 13:17:42,609 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=soko-web/ui,endpoint=SokoService
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252362#4252362
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252362
From do-not-reply at jboss.com Fri Aug 28 19:28:33 2009
From: do-not-reply at jboss.com (karmst)
Date: Fri, 28 Aug 2009 19:28:33 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - running 'ant tests'
with 3.2.0.GA fails
Message-ID: <27205675.1251502113207.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I have installed 3.2.0.GA on top of jBoss 5.1.0.GA, and have bound it to address 192.168.174.144, so not localhost.
However, when I run 'ant tests' as the 2nd part of the install procedure, I get an error in the build:
[junit] Executing command: /opt/jboss/jboss-5.1.0.GA/bin/wsrunclient.sh junit.textui.TestRunner org.jboss.test.ws.jaxws.samples.webmethod.WebMethodTestCase
[junit] Process input stream:
[junit] Process error stream:
[junit] .E.E.E.E
[junit] Time: 0.749
[junit] There were 4 errors:
[junit] 1) testLegalAccess(org.jboss.test.ws.jaxws.samples.webmethod.WebMethodTestCase)org.jboss.ws.metadata.wsdl.WSDLException: Cannot connect to: http://localhost:8080/jaxws-samples-webmethod/TestService?wsdl
The build reports:
org.jboss.test.ws.jaxws.smoke.tools.WSRunClientTestCase FAILED
org.jboss.test.ws.management.recording.MemoryBufferRecorderTestCase FAILED
Any help would be appreciated.
The top of the build looks fine, and I know the variables are set correctly:
init:
[echo] integration.target=jboss510
tests-prepare:
[echo]
[echo] -----------------------------------------------
[echo] jboss.home = /opt/jboss/jboss-5.1.0.GA
[echo] excludesfile = /opt/jboss/jbossws-native-bin-dist/tests/resources/test-excludes-jboss510.txt
[echo] java.home = /usr/java/jdk1.6.0_12/jre
[echo] jboss.bind = 192.168.174.144
[echo] -----------------------------------------------
Thanks, Keith
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252409#4252409
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252409
From do-not-reply at jboss.com Sat Aug 29 11:51:46 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Sat, 29 Aug 2009 11:51:46 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: regarding message
types in bottom-up service generation
Message-ID: <8718377.1251561106934.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
Try adding this annotation to your class:
import javax.jws.soap.SOAPBinding;
...
@SOAPBinding(style=SOAPBinding.Style.RPC)
By default, the DOC binding style is used which yields complex types. The RPC style should yield simple types.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252450#4252450
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252450
From do-not-reply at jboss.com Mon Aug 31 12:55:19 2009
From: do-not-reply at jboss.com (cavani)
Date: Mon, 31 Aug 2009 12:55:19 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - CXF and Native issue
with Encryptation (no wsu:Id for Body)
Message-ID: <30488174.1251737719940.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>
I was using Native for server (EJB) and client (Java SE / jax-ws dipatch mainly) with encryptation but without signing.
Recently, I rewrote just the client with CXF using the same approach (dispatch), but an issue break me!
Without signing, WSS4J (used by CXF for encrypting) didn't set 'wsu:Id' for 'body' tag and Native reject the message (in class RequireTargetableOperation).
Commenting the test where Native require 'wsu:Id' in RequireTargetableOperation makes CXF encrypted message acceptable and correct.
Using signing makes WSS4J set 'wsu:Id' for 'body' tag, so no issues this way.
I don't know if this issue is a CXF (WSS4J) issue or a Native issue, but here seems to be the right place to report.
(CXF 2.2.3 and Native 3.0.5/JBoss 4.2.3 or Native 3.1.2/JBoss 5.1)
Thanks,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252675#4252675
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252675