Re: JUnit test with local transport failing to find hibernate session
Hi Gilles, I just committed a quick fix for the issue of the CXF local transport direct dispatch model [CXF-1107]. You can try it by using the truck version or waiting few days for the next 2.0.3 snapshot. Willem. Willem Jiang wrote: Hi, I can reproduce the error, it definitely is a CXF local transport bug. I will investigate it later today. Willem. Gilles Durys wrote: Willem Jiang wrote: Hi, Which CXF version are you using? Can you access the service with http transport? I just checked the code in the trunk XMLStreamWriter xtw = message.getContent(XMLStreamWriter.class); * xtw.setPrefix(soapVersion.getPrefix(), soapVersion.getNamespace()); I guess the NPE is came from xtw, but I have no idea why XMLStreamWriter.class is not set into the message. I gripped the code and found it should be set to the message by StaxOutInterceptor. Hi, I came back to this problem and for what I understand looking at LocalConduit.directDispatch, when using direct dispatch, no content is set on the message.
Re: Cannot run Maven java2wsdl goal
What's the version of cxf are you using? it's been changed to java2ws http://cwiki.apache.org/CXF20DOC/java-to-ws.html James Hi, I've been trying to use the Maven plugin but I'm getting this error. [INFO] Scanning for projects... [INFO] -- --- [INFO] Building FooProject Web Services Wrapper [INFO]task-segment: [package] [INFO] -- --- [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] 'java2wsdl' was specified in an execution, but not found in the plugin [INFO] -- [INFO] For more information, run Maven with the -e switch [INFO] -- [INFO] Total time: 1 second [INFO] Finished at: Thu Oct 11 13:40:06 CEST 2007 [INFO] Final Memory: 3M/5M [INFO] --
Re: Error deploying CXF 2.0.2 to WebSphere 6.1.0.5
Hi,
I am trying to deploy the java_first_spring_support sample war to the
WebSphere 6.1.0.0, I am using the WebSphere console to install the
Application, and it started successfully.
However, when I want to access the wsdl, it shows the Error 500, and I
look up the log file,
it shows java.lang.IncompatibleClassChangeError
com.ibm.ws.webcontainer.servlet.ServletInstance.service.
By the way, for the java_first_spring_support, I can see the
{http://spring.demo/}helloWorldImplPort; link when I access it through
http://localhost:9080/spring/services. (Note, I set the context root as
spring).
I am not sure how did you deploy the war, I am new to websphere, and
found its configuration is more complex than weblogic, jboss etc.
Can you test the java_first_spring_support sample on WebSphere to see if
you can started it successfully
Thanks
Jeff
Todd Pickford wrote:
I have created a simple service that runs fine with Tomcat, but gives
the following error when deploying to WebSphere. Has anyone seen this
or know how to fix it?
Spring Config:
bean id=misImpl
class=org.lds.platform.service.member.MemberInfoServiceImpl
/bean
jaxws:endpoint id=misTest
address=/MisService
implementorClass=org.lds.platform.service.member.MemberInfoService
implementor=#misImpl/
Error on WebSphere:
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'misTest': Invocation of init method
failed; nested exception is java.lang.VerifyError
Caused by: java.lang.VerifyError
at
com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.(RuntimeBuiltinLeafInfoImpl.java:186)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java :177)
at
com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.(RuntimeTypeInfoSetImpl.java:25)
at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:84)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet
(RuntimeModelBuilder.java:41)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:104)
at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.(RuntimeModelBuilder.java:49)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet
(JAXBContextImpl.java:372)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:236)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
at com.sun.xml.bind.v2.ContextFactory.createContext (ContextFactory.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
at javax.xml.bind.ContextFinder.find(ContextFinder.java :368)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at
org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding.java:377)
at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java :182)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:244)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel
(ReflectionServiceFactoryBean.java:272)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:146)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java
:89)
at
org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(AbstractEndpointFactory.java:83)
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:107)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create
(JaxWsServerFactoryBean.java:147)
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:287)
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:227)
at org.apache.cxf.jaxws.EndpointImpl.publish (EndpointImpl.java:179)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:340)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod
(AbstractAutowireCapableBeanFactory.java:1214)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1179)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:1145)
at
Re: WSDL not recognized by vs net
Spent a bunch of time playing with the JWS and JAXWS TCK's last night and digging though specs to figure out what can be done here. 1) For the simple frontend, I can definitely make the default parameters for all cases. 2) For jaxws, I can make the default parameters for MOST cases. There are one or two cases where I cannot, but they are edge cases. (Example: all the OUT parts are header=true. The resulting wrapper type is an empty complex type.) Anyway, I'm going to work on getting this committed today. Dan On Wednesday 10 October 2007, William Leung wrote: Very annoyance :((( After quite a few trys, I finally make HelloWorld worked with vs net (2005). just change these line in WDSL: ( wrapped DOC/LIT ) wsdl:message name=sayHiResponse wsdl:part element=tns:sayHiResponse name=result /wsdl:part /wsdl:message after change the name from result to parameters vs net recognized the WSDL, and string hello.sayHi(string) is finally available. Anyone could tell me why? William Leung wrote: I am testing CXF and sadlly found that our method parameters and returns are not recognized in vs net. VS NET recongnized the sayHi function as --- sayHi ( sayHi As sayHi ) As sayHiResponse it should be --- sayHi ( arg0 As string) as string When I change the wsdl manually from xsd:element name=sayHi type=tns:sayHi/ xsd:complexType name=sayHi xsd:sequence xsd:element minOccurs=0 name=arg0 type=xsd:string/ /xsd:sequence /xsd:complexType to xsd:element xsd:complexType xsd:sequence xsd:element minOccurs=0 name=arg0 type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element It worked, but I have no idea how could I make this changes without switch to wsdl first (I dont want to, I have just too many methods to export) Any help will be very appreciated -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: Cannot run Maven java2wsdl goal
Hello James, I'm using Apache CXF 2.0.2. Here's an extract from my pom.xml plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration encodingUTF-8/encoding source1.5/source target1.5/target showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration /plugin plugin groupIdorg.apache.cxf/groupId artifactIdcxf-codegen-plugin/artifactId version2.0-incubator-M1/version dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-rt-frontend-jaxws/artifactId version2.0/version /dependency /dependencies executions execution idgenerate-wsdl/id phaseprocess-classes/phase configuration classNamefoo.myClass/className /configuration goals goaljava2ws/goal /goals /execution /executions /plugin 2007/10/11, James Mao [EMAIL PROTECTED]: What's the version of cxf are you using? it's been changed to java2ws http://cwiki.apache.org/CXF20DOC/java-to-ws.html James Hi, I've been trying to use the Maven plugin but I'm getting this error. [INFO] Scanning for projects... [INFO] -- --- [INFO] Building FooProject Web Services Wrapper [INFO]task-segment: [package] [INFO] -- --- [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] 'java2wsdl' was specified in an execution, but not found in the plugin [INFO] -- [INFO] For more information, run Maven with the -e switch [INFO] -- [INFO] Total time: 1 second [INFO] Finished at: Thu Oct 11 13:40:06 CEST 2007 [INFO] Final Memory: 3M/5M [INFO] --
Best practices with min/max occurs/nillable and JAXB
Fellow users: When using JAXB code-first, how much do people worry about the irritation of Java strings mapping to arrays? That is: String foo: Turns into an array of 0 or 1 strings, to account for the possibility of null versus versus foobar. One can clean this up with XmlElement. My question is, how often do people bother?
Re: Best practices with min/max occurs/nillable and JAXB
On Thursday 11 October 2007, Benson Margulies wrote: Fellow users: When using JAXB code-first, how much do people worry about the irritation of Java strings mapping to arrays? Well, I personally don't consider minOccurs=0 maxOccurs=1 to be an array. That's and optional element, not an array.Thus, IMO, it isn't an irritation as it's not an array. None of the standard JAVA toolkits would map such a construct to an Array. Dan That is: String foo: Turns into an array of 0 or 1 strings, to account for the possibility of null versus versus foobar. One can clean this up with XmlElement. My question is, how often do people bother? -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: Problem with Exception Handling: Premature end of file.
What version of CXF are you using?There were a few bugs logged for 2.0 and 2.0.1 that were fixed in 2.0.2: https://issues.apache.org/jira/browse/CXF-926 https://issues.apache.org/jira/browse/CXF-1028 There currently is a bug in the SNAPSHOTS that is causing nothing to be written back to the client (empty HTTP response) in some very rare situations that I'm fixing right now. Dan On Thursday 11 October 2007, [EMAIL PROTECTED] wrote: Hi all, I have got a problem with exception handling within cxf: If I throw a runtime exception in my web service, the client gets an SOAPFaultException and everything is fine. But when I throw a normal exception I get the following stacktrace. It seems that cxf is not able map my exception to the response. What could be the reason for my problem? Thank in advance, Marc java.lang.Exception: Unexpected exception, expectedMyException but wasjavax.xml.ws.soap.SOAPFaultException at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodR unner.java:91) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAnd AfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner .java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java: 45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(Tes tClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethods Runner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassR unner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAnd AfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52 ) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4T estReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution. java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote TestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote TestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestR unner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTest Runner.java:196) Caused by: javax.xml.ws.soap.SOAPFaultException: Error reading XMLStreamReader. at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:175 ) at $Proxy37.anlegenRisikoklasse(Unknown Source) at de.degussabank.wp2.RisikoklassenWebServiceTest.testAnlegenRisikoklasse KundeExistiertNicht(RisikoklassenWebServiceTest.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j ava:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMeth odRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodR unner.java:81) ... 14 more Caused by: org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader. at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleM essage(ReadHeadersInterceptor.java:187) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleM essage(ReadHeadersInterceptor.java:56) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercepto rChain.java:207) at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:395) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRe sponse(HTTPConduit.java:1932) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HT TPConduit.java:1790) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66 ) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:576) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndin gInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercepto rChain.java:207) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:254) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135 ) ... 22 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Premature end of file. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLSt reamReaderImpl.java:588) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XM LStreamReaderImpl.java:1219) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleM essage(ReadHeadersInterceptor.java:85) ... 35 more -- J. Daniel Kulp
RE: Best practices with min/max occurs/nillable and JAXB
I think that some toolkit I tried to use to build a client once-upon-a-time gave me an array, and I've been exhibiting allergic behavior ever since. -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 10:28 AM To: cxf-user@incubator.apache.org Cc: Benson Margulies Subject: Re: Best practices with min/max occurs/nillable and JAXB On Thursday 11 October 2007, Benson Margulies wrote: Fellow users: When using JAXB code-first, how much do people worry about the irritation of Java strings mapping to arrays? Well, I personally don't consider minOccurs=0 maxOccurs=1 to be an array. That's and optional element, not an array.Thus, IMO, it isn't an irritation as it's not an array. None of the standard JAVA toolkits would map such a construct to an Array. Dan That is: String foo: Turns into an array of 0 or 1 strings, to account for the possibility of null versus versus foobar. One can clean this up with XmlElement. My question is, how often do people bother? -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: Antwort: Re: Problem with Exception Handling: Premature end of file.
On Thursday 11 October 2007, [EMAIL PROTECTED] wrote: I am using Version 2.02. Should I upgrade to Snapshot? Nope. 2.0.2 should definitely be working (providing the code was generated with 2.0.2. Code generated with 2.0.1's wsdl2java will not work correctly).I guess I would need to see: 1) The tcpmon/wireshark/tcpdump/whatever of the request and response. 2) The wsdl 3) The actual Exception java object so I can see what it's trying to do. Dan Marc |-+--- | | | Daniel Kulp | | | [EMAIL PROTECTED]| | | g | | | | | 11.10.2007 16:37| | | Bitte antworten | | | an cxf-user | | |-+--- | --- | |An: cxf-user@incubator.apache.org || | Kopie: [EMAIL PROTECTED] | | Thema: Re: | Problem with Exception Handling: Premature end of file. || | --- | What version of CXF are you using?There were a few bugs logged for 2.0 and 2.0.1 that were fixed in 2.0.2: https://issues.apache.org/jira/browse/CXF-926 https://issues.apache.org/jira/browse/CXF-1028 There currently is a bug in the SNAPSHOTS that is causing nothing to be written back to the client (empty HTTP response) in some very rare situations that I'm fixing right now. Dan On Thursday 11 October 2007, [EMAIL PROTECTED] wrote: Hi all, I have got a problem with exception handling within cxf: If I throw a runtime exception in my web service, the client gets an SOAPFaultException and everything is fine. But when I throw a normal exception I get the following stacktrace. It seems that cxf is not able map my exception to the response. What could be the reason for my problem? Thank in advance, Marc java.lang.Exception: Unexpected exception, expectedMyException but wasjavax.xml.ws.soap.SOAPFaultException at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMetho dR unner.java:91) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeA nd AfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunn er .java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.jav a: 45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(T es tClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMetho ds Runner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClas sR unner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeA nd AfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java: 52 ) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit 4T estReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecutio n. java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remo te TestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remo te TestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTes tR unner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTe st Runner.java:196) Caused by: javax.xml.ws.soap.SOAPFaultException: Error reading XMLStreamReader. at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:1 75 ) at $Proxy37.anlegenRisikoklasse(Unknown Source) at de.degussabank.wp2.RisikoklassenWebServiceTest.testAnlegenRisikoklas se KundeExistiertNicht(RisikoklassenWebServiceTest.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl .j ava:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce ss orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMe th odRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMetho dR unner.java:81) ... 14 more Caused by: org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader. at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handl eM essage(ReadHeadersInterceptor.java:187) at
Re: deploy CXF web service in JBoss
Just simply put the war in the JBoss deploy folder, and then it would be working fine. -Jeff shaminda perera wrote: Hi all I need some help in deploying a CXF Web service in JBoss application server . Any pointers? Thanks
Message level service
Hi all,
i have an old service in axis that uses saaj to work on messages. Now i want
to migrate on CFX but i encounter some problems...
First step is make a service that works at message level with saaj. So i
need that avery message that point to
http://localhost:8080/CFX/myService/and/some/moreis catch by myService
service and some method handle it (something like handleMessage(SOAPMessage
message) )
To work at Message level i read something about @ServiceProvider but i don't
reach the goal...
i tryed with:
package org.openspcoop.pdd.services;
import java.rmi.RemoteException;
import java.util.Map;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.*;
@WebServiceProvider
@ServiceMode(value=javax.xml.ws.Service.Mode.MESSAGE)
public class RicezioneContenutiApplicativiWS {
public SOAPMessage invoke(SOAPMessage msg, MapString, Object ctxt)
throws
RemoteException {
return msg;
}
}
but it doesn't work, it gives this exception when invoking:
17:06:10,341 ERROR [STDERR] 11-ott-2007 17.06.10
org.apache.cxf.binding.http.interceptor.DispatchInterceptor handleMessage
INFO: Invoking POST on
17:06:10,344 ERROR [STDERR] 11-ott-2007 17.06.10
org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Invalid URL/Verb combination. Verb: POST
Path:
at
org.apache.cxf.binding.http.interceptor.DispatchInterceptor.handleMessage(DispatchInterceptor.java:74)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73)
at
org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140)
at
org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278)
at
org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
I deployed CFX into jboss with this web.xml:
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
web-app
context-param
param-namecontextConfigLocation/param-name
param-valueWEB-INF/openspcoop_beans.xml/param-value
/context-param
listener
listener-class
org.springframework.web.context.ContextLoaderListener
/listener-class
/listener
servlet
servlet-nameCXFServlet/servlet-name
display-nameCXF Servlet/display-name
servlet-class
org.apache.cxf.transport.servlet.CXFServlet
/servlet-class
Re: Cannot run Maven java2wsdl goal
plugin groupIdorg.apache.cxf/groupId artifactIdcxf-codegen-plugin/artifactId version2.0-incubator-M1/version dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-rt-frontend-jaxws/artifactId version2.0/version /dependency /dependencies Change both of those to 2.0.2-incubator and try again. goaljava2ws/goal Change to java2wsdl Dan On Thursday 11 October 2007, Nef Asus wrote: Hello James, I'm using Apache CXF 2.0.2. Here's an extract from my pom.xml plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration encodingUTF-8/encoding source1.5/source target1.5/target showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration /plugin plugin groupIdorg.apache.cxf/groupId artifactIdcxf-codegen-plugin/artifactId version2.0-incubator-M1/version dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-rt-frontend-jaxws/artifactId version2.0/version /dependency /dependencies executions execution idgenerate-wsdl/id phaseprocess-classes/phase configuration classNamefoo.myClass/className /configuration goals goaljava2ws/goal /goals /execution /executions /plugin 2007/10/11, James Mao [EMAIL PROTECTED]: What's the version of cxf are you using? it's been changed to java2ws http://cwiki.apache.org/CXF20DOC/java-to-ws.html James Hi, I've been trying to use the Maven plugin but I'm getting this error. [INFO] Scanning for projects... [INFO] -- --- [INFO] Building FooProject Web Services Wrapper [INFO]task-segment: [package] [INFO] -- --- [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] 'java2wsdl' was specified in an execution, but not found in the plugin [INFO] -- [INFO] For more information, run Maven with the -e switch [INFO] -- [INFO] Total time: 1 second [INFO] Finished at: Thu Oct 11 13:40:06 CEST 2007 [INFO] Final Memory: 3M/5M [INFO] -- -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: jetty logging when embedded
On Thursday 11 October 2007, Benson Margulies wrote: When CXF launches jetty, does it rearrange jetty's log across to j.u.l? Jetty uses slf4j so whichever slf4j-XXX.jar it finds on the classpath is the one that is used. We ship the slf4j-jdk14 jar which directs slf4j to use j.u.l. There is a slf4j-log4j jar that would direct it there. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: spring and qnames
Doing this would make the schema's not really match the API's. The APIs
specifically use QNames which is why the schema says xsd:qname. To
support this, we'd have to change the schema to be a xsd:string (or
string with a restriction with a pattern) which then no longer matches
the API's. Not a huge deal, but right now they are in sync.
Dan
On Thursday 11 October 2007, Sergey Beryozkin wrote:
JaxWS-RI supports an expanded form of QName :
endpoint service={http://ws.index.rnm.basistech.com}NameIndex;
port={http://ws.index.rnm.basistech.com}NameIndexPort2/
javax.xml.namespace.QName.toString() produces the expanded form too
and it makes the above form easy to use. This pattern can be also
enforced at a schema validation time.
Now that CXF already defines a serviceName be of QName type, not sure
if it would be feasible to introduce an alternative attribute like
@service and @port. If it were possible then the configuration would
get simplified quite a bit IMHO.
Existing @serviceName and @portName could be deprecated and supported
for a while too...
Cheers, Sergey
- Original Message -
From: Daniel Kulp [EMAIL PROTECTED]
To: cxf-user@incubator.apache.org
Cc: Benson Margulies [EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 11:01 PM
Subject: Re: spring and qnames
It should be something like:
jaxws:client serviceName=ns1:NameIndex
xmlns:ns1=http://ws.index.rnm.basistech.com;
address=${serviceUrl}/NameIndex
serviceClass=com.basistech.rnm.index.ws.NameIndexService
jaxws:dataBindingbean ref=.//jaxws:dataBinding/
/jaxws:client
Dan
On Wednesday 10 October 2007, Benson Margulies wrote:
Is there a way to express this with jaxws:? Whether or not, is
there an editor out there for QNames that reduces the noise level
of this?
bean id=rni-proxyFactory
class=org.apache.cxf.jaxws.JaxWsProxyFactoryBean
property name=serviceClass
value=com.basistech.rnm.index.ws.NameIndexService/
property name=serviceName
bean class=javax.xml.namespace.QName
constructor-arg value=http://ws.index.rnm.basistech.com/
constructor-arg value=NameIndex/
/bean
/property
property name=address value=${serviceUrl}/NameIndex/
property name=dataBinding ref=aegis-databinding/
/bean
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
Ireland
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: Error deploying CXF 2.0.2 to WebSphere 6.1.0.5
I installed the java_first_spring_support and got the same error as you did.
On 10/11/07, Jeff Yu [EMAIL PROTECTED] wrote:
Hi,
I am trying to deploy the java_first_spring_support sample war to the
WebSphere 6.1.0.0, I am using the WebSphere console to install the
Application, and it started successfully.
However, when I want to access the wsdl, it shows the Error 500, and I
look up the log file,
it shows java.lang.IncompatibleClassChangeError
com.ibm.ws.webcontainer.servlet.ServletInstance.service.
By the way, for the java_first_spring_support, I can see the
{http://spring.demo/}helloWorldImplPort; link when I access it through
http://localhost:9080/spring/services. (Note, I set the context root as
spring).
I am not sure how did you deploy the war, I am new to websphere, and
found its configuration is more complex than weblogic, jboss etc.
Can you test the java_first_spring_support sample on WebSphere to see if
you can started it successfully
Thanks
Jeff
Todd Pickford wrote:
I have created a simple service that runs fine with Tomcat, but gives
the following error when deploying to WebSphere. Has anyone seen this
or know how to fix it?
Spring Config:
bean id=misImpl
class=org.lds.platform.service.member.MemberInfoServiceImpl
/bean
jaxws:endpoint id=misTest
address=/MisService
implementorClass=org.lds.platform.service.member.MemberInfoService
implementor=#misImpl/
Error on WebSphere:
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'misTest': Invocation of init method
failed; nested exception is java.lang.VerifyError
Caused by: java.lang.VerifyError
at
com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.(RuntimeBuiltinLeafInfoImpl.java:186)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java :177)
at
com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.(RuntimeTypeInfoSetImpl.java:25)
at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:84)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet
(RuntimeModelBuilder.java:41)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:104)
at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.(RuntimeModelBuilder.java:49)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet
(JAXBContextImpl.java:372)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:236)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
at com.sun.xml.bind.v2.ContextFactory.createContext (ContextFactory.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
at javax.xml.bind.ContextFinder.find(ContextFinder.java :368)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at
org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding.java:377)
at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java :182)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:244)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel
(ReflectionServiceFactoryBean.java:272)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:146)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java
:89)
at
org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(AbstractEndpointFactory.java:83)
at
org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:107)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create
(JaxWsServerFactoryBean.java:147)
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:287)
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:227)
at org.apache.cxf.jaxws.EndpointImpl.publish (EndpointImpl.java:179)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:340)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod
(AbstractAutowireCapableBeanFactory.java:1214)
at
Re: Stacktrace, Why?
In addition, it can help to reduce your source code to the most minimum that replicates the error. Less for the reader to wade through / easier to spot errors that way. Glen Am Dienstag, den 09.10.2007, 09:41 -0400 schrieb Daniel Kulp: That stack trace points to you using the the Sun reference implementation of JAX-WS thats built into JDK 6. You aren't hitting CXF code at all. The classes: com.sun.xml.internal.ws.* are the JAX-WS stuff in JDK 6. Double check that CXF is properly on the classpath. Dan On Tuesday 09 October 2007, Mattas, Tony wrote: Can someone give me a clue as to why I'm getting this stack trace, I don't reference a class by that name ever.
JAXB and namespace prefixes
At least with CXF, the namespace prefixes for the wsdl:definition element ignore any @XmlNs mappings on the package-info.java of the package containing the SEI. Is this right?
Re: Error deploying CXF 2.0.2 to WebSphere 6.1.0.5
If you haven't been liberated yet, [EMAIL PROTECTED] might help or (worst case) [EMAIL PROTECTED] Glen Am Mittwoch, den 10.10.2007, 10:37 -0700 schrieb [EMAIL PROTECTED]: Someone please unsubscribe me from this mailing list. I tried atleast 10 times through unsubscribe mail id. It asked me to confirm unsubscription with reply but no use. I am still getting all these e-mails. Please help me out. Govind
RE: logging behavior of the client side
Metro also is a bit on the chatty side when generating a client. But our debugging page gives more info on setting logging levels: http://cwiki.apache.org/confluence/display/CXF20DOC/Debugging Glen Am Mittwoch, den 10.10.2007, 18:04 -0400 schrieb Benson Margulies: What do you think of turning those down to FINE? Should we log anything visibly when all is well by default? -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 6:04 PM To: cxf-user@incubator.apache.org Cc: Benson Margulies Subject: Re: logging behavior of the client side On Wednesday 10 October 2007, Benson Margulies wrote: When I run a simple junit test that uses a client created using spring configuration, I get some INFO level log traffic on the console. These messages seem a bit noisy. Or, maybe, the real question is who is setting j.u.l to operate at INFO? INFO is the default level for j.u.l if a configuration file isn't provided. Dan
Re: Message level service
I'm probably not understanding your entire question, but I think if
you're using SAAJ, that would mean you don't need to use a web service
framework--neither CXF nor anything else. (SAAJ has a SOAPConnection
object that will do what you want.) See here[1] for an example.
Glen
[1] http://users.skynet.be/pascalbotte/rcx-ws-doc/saajpost.htm
Am Donnerstag, den 11.10.2007, 08:13 -0700 schrieb Cencio:
Hi all,
i have an old service in axis that uses saaj to work on messages. Now i want
to migrate on CFX but i encounter some problems...
First step is make a service that works at message level with saaj. So i
need that avery message that point to
http://localhost:8080/CFX/myService/and/some/moreis catch by myService
service and some method handle it (something like handleMessage(SOAPMessage
message) )
To work at Message level i read something about @ServiceProvider but i don't
reach the goal...
i tryed with:
package org.openspcoop.pdd.services;
import java.rmi.RemoteException;
import java.util.Map;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.*;
@WebServiceProvider
@ServiceMode(value=javax.xml.ws.Service.Mode.MESSAGE)
public class RicezioneContenutiApplicativiWS {
public SOAPMessage invoke(SOAPMessage msg, MapString, Object ctxt)
throws
RemoteException {
return msg;
}
}
Re: Cannot run Maven java2wsdl goal
FYI, Cxf2.0.2 still using java2wsdl, so you dont' need to change the goal to java2ws If you're using latest trunk, you need to change to java2ws, CXF2.0.2 is the last version which using java2wsdl Besides, your version version2.0-incubator-M1/version is not correct Try the 2.0.2-incubator as DanK said Regards, James Hello James, I'm using Apache CXF 2.0.2. Here's an extract from my pom.xml plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration encodingUTF-8/encoding source1.5/source target1.5/target showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration /plugin plugin groupIdorg.apache.cxf/groupId artifactIdcxf-codegen-plugin/artifactId version2.0-incubator-M1/version dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-rt-frontend-jaxws/artifactId version2.0/version /dependency /dependencies executions execution idgenerate-wsdl/id phaseprocess-classes/phase configuration classNamefoo.myClass/className /configuration goals goaljava2ws/goal /goals /execution /executions /plugin 2007/10/11, James Mao [EMAIL PROTECTED]: What's the version of cxf are you using? it's been changed to java2ws http://cwiki.apache.org/CXF20DOC/java-to-ws.html James Hi, I've been trying to use the Maven plugin but I'm getting this error. [INFO] Scanning for projects... [INFO] -- --- [INFO] Building FooProject Web Services Wrapper [INFO]task-segment: [package] [INFO] -- --- [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] 'java2wsdl' was specified in an execution, but not found in the plugin [INFO] -- [INFO] For more information, run Maven with the -e switch [INFO] -- [INFO] Total time: 1 second [INFO] Finished at: Thu Oct 11 13:40:06 CEST 2007 [INFO] Final Memory: 3M/5M [INFO] --
RE: Message level service
JAX-WS Dispatch/Provider API should give you what you want. There is a sample
named jaxws_dispatch_provider in CXF distribution demonstrates how to write
dispatch/provider in CXF. The reason why you got that exception is because you
are using CXF HTTP binding in your configuration, which is the wrong. CXF HTTP
binding is supposed to be used for REST style services, not for SOAP services.
A configuration snippet like below should do the trick for you:
jaxws:endpoint
id=PD
implementor=org.openspcoop.pdd.services.RicezioneContenutiApplicativiWS
address=/PD /
Cheers,
Jervis
-Original Message-
From: Cencio [mailto:[EMAIL PROTECTED]
Sent: 2007?10?11? 23:13
To: cxf-user@incubator.apache.org
Subject: Message level service
Hi all,
i have an old service in axis that uses saaj to work on
messages. Now i want
to migrate on CFX but i encounter some problems...
First step is make a service that works at message level with
saaj. So i
need that avery message that point to
http://localhost:8080/CFX/myService/and/some/moreis catch
by myService
service and some method handle it (something like
handleMessage(SOAPMessage
message) )
To work at Message level i read something about
@ServiceProvider but i don't
reach the goal...
i tryed with:
package org.openspcoop.pdd.services;
import java.rmi.RemoteException;
import java.util.Map;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.*;
@WebServiceProvider
@ServiceMode(value=javax.xml.ws.Service.Mode.MESSAGE)
public class RicezioneContenutiApplicativiWS {
public SOAPMessage invoke(SOAPMessage msg, MapString,
Object ctxt) throws
RemoteException {
return msg;
}
}
but it doesn't work, it gives this exception when invoking:
17:06:10,341 ERROR [STDERR] 11-ott-2007 17.06.10
org.apache.cxf.binding.http.interceptor.DispatchInterceptor
handleMessage
INFO: Invoking POST on
17:06:10,344 ERROR [STDERR] 11-ott-2007 17.06.10
org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Invalid URL/Verb
combination. Verb: POST
Path:
at
org.apache.cxf.binding.http.interceptor.DispatchInterceptor.ha
ndleMessage(DispatchInterceptor.java:74)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIn
terceptorChain.java:207)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(Cha
inInitiationObserver.java:73)
at
org.apache.cxf.transport.servlet.ServletDestination.doMessage(
ServletDestination.java:79)
at
org.apache.cxf.transport.servlet.ServletController.invokeDesti
nation(ServletController.java:235)
at
org.apache.cxf.transport.servlet.ServletController.invoke(Serv
letController.java:140)
at
org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.
java:278)
at
org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.
java:256)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
er(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
cationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyH
eaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
er(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
cationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
rapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardC
ontextValve.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(
SecurityAssociationValve.java:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCont
extValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHost
Valve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
Valve.java:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(Cach
edConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
gineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdap
ter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Process
or.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHa
ndler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolT
cpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterS
