Minimal dependencies
Hello, I'm using CXF as shown in Building your cxf project with mavenhttp://cwiki.apache.org/CXF20DOC/building-your-cxf-project-with-maven.html and comparing to what is shown in A simple JAX-WS servicehttp://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html I noticed that, following the maven example I get 30 more libraries than in the simple one (50 on the maven configured project against 20 on the simple one, as the spring dependencies are said to be optional). So I'd like to know if there is a way to configure a maven project to get only the minimal dependency set to accomplish the same as in the simple example. (Better yet would be to know the minimal set for the client and the minimal for the server, if there would be any difference imagining that the client and server are separate projects). Regards, Oswaldo
Publishing services via Endpoint
Hi, Our application is a library that needs to publish extra services to support its functionality. Our library is initialized in the client application's main method and then starts publishing its services. Suppose we want to publish these services via the Endpoint.publish method. Question: could this interfere with the application's own services (if any)? I mean: would this just add our services to the already configured application services or is there something else to watch out for? Thanks Guy
Re: [Newbie] problem : No binding factory for namespace http://schemas.xmlsoap.org/wsdl/http/ registered
Hi Dan,
I'm using 2.0-incubator version as it was described in the maven doc
section (http://cwiki.apache.org/CXF20DOC/maven-integration-and-
plugin.html).
I will try using 2.0.2, or maybe the 2.0.3 if it is available (I was
cheking the roadmap, it was said that the 2.0.3 was waited for end of
october).
Thanks for the quick answer :)
Joel
Messages d´origine
De: Daniel Kulp [EMAIL PROTECTED]
Date: jeudi, novembre 8, 2007 10:19 pm
Objet: Re: [Newbie] problem : No binding factory for namespace
http://schemas.xmlsoap.org/wsdl/http/ registered
Joel,
What version of CXF are you using?I THINK this issue was fixed
in
2.0.2, but I'm not sure.
If you could try the 2.0.3 release candidate found at:
http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/dist/
That would be great.
Dan
On Thursday 08 November 2007, JoCosti wrote:
Hi all,
I'm working on a web service client migration from jax-rpc to
jax-ws
using cxf.
Everything was working fine with the jax-rpc client thus I know that
the ws is ok.
Note that this is a secure ws so the client must give a user/passwor
and having a trustStore (at least with jax-rpc, this was the way of
configuring security)
Ok, first thing done was to generate the client using
cxf-codegen-plugin maven plugin, well there was some strange
exception with message method annotated by @PostConstruct throws
exception when
invoked but since the code was generated I have continued ...
The ws client must be a secured one, after looking at some docs, I
have added a cxf.xml configuration file to set some
user/password (the
truststore is set programmatically).
here's the cxf.xml file used :
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec=http://cxf.apache.org/configuration/security;
xmlns:http=http://cxf.apache.org/transports/http/configuration;
xsi:schemaLocation=
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;
http:conduit
name={http://anpe.fr/DirectoryServices/}StructureServicesSoap.http-co
nduit http:authorization
sec:UserName_svc_ws_test/sec:UserName
sec:Passwordpassword/sec:Password
/http:authorization
http:tlsClientParameters
secureSocketProtocol=SSL/http:tlsClientParameters
/http:conduit
/beans
When running the ws client the following exception occurs:
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException
at org.apache.cxf.jaxws.ServiceImpl.getPort
(ServiceImpl.java:240)
at javax.xml.ws.Service.getPort(Service.java:94)
at
fr.anpe.directoryservices.StructureServices.getStructureServicesSoap
(StructureServices.java:59) at
fr.anpe.sapiens.services.structures.StructureServicesImpl.getStructureS
ervicesWebServiceProxy(StructureServicesImpl.java:189) at
fr.anpe.sapiens.services.structures.StructureServicesImpl.getMailAddres
s(StructureServicesImpl.java:84) at
fr.anpe.sapiens.services.structures.StructureServicesTest.testGetMailAd
dress(StructureServicesTest.java:51) 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 junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run
(JUnit3TestReference.java:128) at
org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38) at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:460) at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:673) at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:386) at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196) Caused by:
org.apache.cxf.service.factory.ServiceConstructionException at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.createEndpo
Re: schema validation
Hi Dan, Thanks for your help as always - looks like upgrading to 2.0.3 upgrading XMLSchema resolved this issue. The only issue I have with this now is with xsd:restriction - they are not annotated, not supported, so am forced to reference the wsdl, not big deal, this works I am however still having problems with the schema validation mtom. Its faily obvious why its breaking, however I would thought that there could be some iffing about butting around the mtom (attachement in/out interceptor).. i.e. before mtom'ing perform schema validation if enabled, and them remove mark as being validated... Or is it designed to work this way? dkulp wrote: Forgot to mention, 2.0.3 is being voted on now. You can download the release candidate from: http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/dist/ (That may fix your mtom validation issue as well, not really sure though) Dan On Thursday 08 November 2007, Daniel Kulp wrote: On Thursday 08 November 2007, Adrian C wrote: With jaxb if schema validation is turned on should validation work if the wsld is not defined for the webservice? Am seeing errors when I do this - I though that the schema/wsld could be generated from the classes? In theory, it should. I'm not sure how well tested it is though. I'd love to see any test cases if there is an issue. Also, definitely try with 2.0.3.We upgraded to a newer version of XmlSchema to fix SOME issues where the schema was losing some needed information. (such as whether a base64 thing was mtom enabled or not). Thus, 2.0.3 may fix some of the isssues. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog -- View this message in context: http://www.nabble.com/schema-validation-tf4770643.html#a13666392 Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAXWS WS Policy
Thanks for the reply James, maybe my understanding of this is incorrect, but I had hoped that by defining policy assertions for my endpoint (jaxws:endpoint) that these would be inserted into the served out wsld. The example seems to deal with a wsdl with the assertions already embedded, and these are picked up by the endpoint definition as they reference the service - i.e. from org.apache.hello_world_soap_http.SOAPService there is url = new URL(file:/C:/temp/apache-cxf-2.0.2-incubator/samples/ws_policy/wsdl/hello_world_addr_policy.wsdl); Is my understanding of this correct? What I would like is a more configuration way to add/remove policy assertions, for my endpoint. Thanks James Mao wrote: I've not been an expert on ws-*, but i just look at the samples in the cxf distribution, we do have a sample of ws-policy And we have doc on http://cwiki.apache.org/CXF20DOC/ws-support.html Don't know if it's sufficient James Is there a way to configure WSPolicy in the jaxws definition of a service in the same way as WS-Reliable Messaging? i.e. is it possible to have something like this: jaxws:features wsa:addressing / p:policies wsp:Policy wsam:Addressing xmlns:wsam=http://www.w3.org/2007/02/addressing/metadata; wsp:Policy / /wsam:Addressing /wsp:Policy /p:policies /jaxws:features Are there any examples of this? Thanks -- View this message in context: http://www.nabble.com/JAXWS---WS-Policy-tf4773036.html#a13666396 Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAXWS WS Policy
Hi Thanks for the reply James, maybe my understanding of this is incorrect, but I had hoped that by defining policy assertions for my endpoint (jaxws:endpoint) that these would be inserted into the served out wsld. +1. This is what shoud happen. As far as I'm aware no real WS-Policy work is happening in CXF but please stay tuned. Submitting a JIRA so that this issue (ensuring policy assertions with public visibility are inlined in the published wsdl) can be tracked would be great Cheers, Sergey The example seems to deal with a wsdl with the assertions already embedded, and these are picked up by the endpoint definition as they reference the service - i.e. from org.apache.hello_world_soap_http.SOAPService there is url = new URL(file:/C:/temp/apache-cxf-2.0.2-incubator/samples/ws_policy/wsdl/hello_world_addr_policy.wsdl); Is my understanding of this correct? What I would like is a more configuration way to add/remove policy assertions, for my endpoint. Thanks James Mao wrote: I've not been an expert on ws-*, but i just look at the samples in the cxf distribution, we do have a sample of ws-policy And we have doc on http://cwiki.apache.org/CXF20DOC/ws-support.html Don't know if it's sufficient James Is there a way to configure WSPolicy in the jaxws definition of a service in the same way as WS-Reliable Messaging? i.e. is it possible to have something like this: jaxws:features wsa:addressing / p:policies wsp:Policy wsam:Addressing xmlns:wsam=http://www.w3.org/2007/02/addressing/metadata; wsp:Policy / /wsam:Addressing /wsp:Policy /p:policies /jaxws:features Are there any examples of this? Thanks -- View this message in context: http://www.nabble.com/JAXWS---WS-Policy-tf4773036.html#a13666396 Sent from the cxf-user mailing list archive at Nabble.com. IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Enumeration problem
Hi,
Using CXF 2.0.2, I have a problem using CXF with a service which throws an
exception which contains an enumeration field. The WSDL is generated
correctly, and I use wsdl2java for generating client stubs. The WSDL shows
the following :
xs:simpleType name=fultyExceptionType
xs:restriction base=xs:string
xs:enumeration value=LILIAN_CONNECTION_FAILURE/
xs:enumeration value=INTERNAL_ERROR/
xs:enumeration value=IO_ERROR/
xs:enumeration value=UNKNOWN_CREATION_TEMPLATE/
xs:enumeration value=MISSING_PARAMETER/
xs:enumeration value=UNKNOWN_APPLICATION/
xs:enumeration value=QUERY_PARSE_ERROR/
xs:enumeration value=APPLICATION_ALREADY_EXISTS/
xs:enumeration value=INDEXATION_SESSION_NOT_ENDED/
xs:enumeration value=UNHANDLED_EXCEPTION/
xs:enumeration value=JDBC_CONNECTION_FAILURE/
/xs:restriction
/xs:simpleType
xs:complexType final=#all name=fultyExceptionTypeArray
xs:sequence
xs:element maxOccurs=unbounded minOccurs=0 name=item
nillable=true type=tns:fultyExceptionType/
/xs:sequence
/xs:complexType
The stubs also seem to be generated correctly, and FultyExceptionTypeArray
class is also generated. But at runtime, it fails with the following error :
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts
of IllegalAnnotationExceptions
Two classes have the same XML type name
{mycompany.com}fultyExceptionTypeArray. Use @XmlType.name and
@XmlType.namespace to assign different names to them.
this problem is related to the following location:
at com.mycompany.ws.FultyExceptionType[]
this problem is related to the following location:
at com.mycompany.ws.FultyExceptionTypeArray
There seems to be a conflict with the Array. Can't figure out what's
happening...
--
View this message in context:
http://www.nabble.com/Enumeration-problem-tf4777694.html#a13667022
Sent from the cxf-user mailing list archive at Nabble.com.
Monitoring CXF Webservices
Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
Re: newb question - JDOMException with aegis binding?
The dependencies list on http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html was what I was referring to. dkulp wrote: On Wednesday 07 November 2007, BrianP wrote: Thanks! Got it and it's working. Why is that not on the dependency list? What dependency list? It's in the dependencies for the aegis databinding pom so it should pull in. It's also shipped in our lib directory and is in the classpath entry of the manifest jar. Dan With that, it generated a bunch of foo.aegis.xml not found messages for each of the property types of the FullOrder, including the MultiString one. Is there a way to make it ignore most of the properties of my class except the ones I want to expose? Maybe I should start a new thread, since I'm past the JDOMException issue. Also, I went a couple steps further and got another NoClassDefFoundError, this time for jaxen. I found this jar, but it is also not on the dependencies list. You need jdom-1.0.jar. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog -- View this message in context: http://www.nabble.com/newb-question---JDOMException-with-aegis-binding--tf4767403.html#a13667433 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Monitoring CXF Webservices
Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony -- View this message in context: http://www.nabble.com/Monitoring-CXF-Webservices-tf4777853.html#a13667699 Sent from the cxf-user mailing list archive at Nabble.com.
RE: Monitoring CXF Webservices
That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony -- View this message in context: http://www.nabble.com/Monitoring-CXF-Webservices-tf4777853.html#a1366769 9 Sent from the cxf-user mailing list archive at Nabble.com.
RE: Gzip encoding
I've tried this and it doesn't seem to work. My config file is shown below. The
http-conf works fine but not the jaxws:client. I've tried uisng a features
instead of the inInterceptor but it makes no difference. The only time it works
is when I use the config at the bottom which adds the interceptor to the bus.
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:http-conf=http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xmlns:sec=http://cxf.apache.org/configuration/security;
xsi:schemaLocation=http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;
http-conf:conduit
name={http://datex2.eu/wsdl/clientPull/1_0}clientPullSoapEndPoint.http-conduit;
http-conf:client AcceptEncoding=gzip, deflate/
http-conf:authorization
sec:UserNameme/sec:UserName
sec:Passwordpassword/sec:Password
/http-conf:authorization
/http-conf:conduit
bean id=GZIPStream
class=com.atkinsglobal.mosaic.cxf.extensions.GZipInterceptor/
jaxws:client
name={http://datex2.eu/wsdl/clientPull/1_0}clientPullSoapEndPoint;
createdFromAPI=true
!-- jaxws:features
bean class=com.atkinsglobal.mosaic.cxf.extensions.GZipFeature/
/jaxws:features--
jaxws:inInterceptors
ref bean=GZIPStream/
/jaxws:inInterceptors
/jaxws:client
!-- We are adding the interceptors to the bus as we will have only one
endpoint/service/bus.
bean id=cxf class=org.apache.cxf.bus.CXFBusImpl
property name=inInterceptors
list
ref bean=GZIPStream/
/list
/property
property name=outInterceptors
list
ref bean=GZIPStream/
/list
/property
/bean
--
/beans
Richard Shaw
¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤
Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems
Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW
Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: [EMAIL PROTECTED]
www.atkinsglobal.com/its
-Original Message-
From: Liu, Jervis [mailto:[EMAIL PROTECTED]
Sent: 05 November 2007 03:03
To: cxf-user@incubator.apache.org
Cc: Shaw, Richard A
Subject: RE: Gzip encoding
Hi Shaw, you can configure your client side interceptors using feature. An
example can be found from dispatch system test:
\trunk\systests\src\test\java\org\apache\cxf\systest\dispatch\TestDispatchFeature.java
and client-config.xml.
Cheers,
Jervis
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 2007?11?3? 1:43
To: cxf-user@incubator.apache.org
Cc: Shaw, Richard A
Subject: Re: Gzip encoding
Hmm... not really sure how to add it to the dispatch style suff via
spring. Interesting.
That said, bus level might make sense if the interceptor was updated
to
handle the case where it's not gzip as well.
Basically, Accept-Encoding is a hint and the server may not respond
in
gzip form. Thus, the interceptor should check the request
header and
if the headers don't say it's gzipped, skip it.
The interceptor may also need to reset the Message.CONTENT_TYPE and
Message.ENCODING properties. Not really sure though.
Dan
On Friday 02 November 2007, Shaw, Richard A wrote:
In reply to my previous message I can see that there is an example
interceptor to GZIP. I've copied this but now I don't know
how to add
it to my dispatch call.
The example adds it to the bus, but I have other services on the bus
which are not using GZIP.
I've found an example that adds it to a jaxws:client but it needs a
serviceClass and I don't have one because I'm using the dispatch
interface.
Can anybody help. Ideally I'd like to add it to my spring
config. But
if I have to add it to my code I can live with that to get
it working.
Thanks
Richard Shaw
¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤
ø,¸¸,ø¤
Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems
Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW
Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: [EMAIL PROTECTED]
www.atkinsglobal.com/its
-Original Message-
From: Shaw, Richard A
Re: Gzip encoding
Hi Richard,
Which version of CXF do you use?
I think it probably is a bug of the JaxWsClientProxyFactoryBean.
Willem.
Shaw, Richard A wrote:
I've tried this and it doesn't seem to work. My config file is shown below. The
http-conf works fine but not the jaxws:client. I've tried uisng a features
instead of the inInterceptor but it makes no difference. The only time it works
is when I use the config at the bottom which adds the interceptor to the bus.
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:http-conf=http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xmlns:sec=http://cxf.apache.org/configuration/security;
xsi:schemaLocation=http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;
http-conf:conduit
name={http://datex2.eu/wsdl/clientPull/1_0}clientPullSoapEndPoint.http-conduit;
http-conf:client AcceptEncoding=gzip, deflate/
http-conf:authorization
sec:UserNameme/sec:UserName
sec:Passwordpassword/sec:Password
/http-conf:authorization
/http-conf:conduit
bean id=GZIPStream
class=com.atkinsglobal.mosaic.cxf.extensions.GZipInterceptor/
jaxws:client name={http://datex2.eu/wsdl/clientPull/1_0}clientPullSoapEndPoint;
createdFromAPI=true
!-- jaxws:features
bean class=com.atkinsglobal.mosaic.cxf.extensions.GZipFeature/
/jaxws:features--
jaxws:inInterceptors
ref bean=GZIPStream/
/jaxws:inInterceptors
/jaxws:client
!-- We are adding the interceptors to the bus as we will have only one endpoint/service/bus.
bean id=cxf class=org.apache.cxf.bus.CXFBusImpl
property name=inInterceptors
list
ref bean=GZIPStream/
/list
/property
property name=outInterceptors
list
ref bean=GZIPStream/
/list
/property
/bean
--
/beans
Richard Shaw
¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤
Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems
Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW
Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: [EMAIL PROTECTED]
www.atkinsglobal.com/its
-Original Message-
From: Liu, Jervis [mailto:[EMAIL PROTECTED]
Sent: 05 November 2007 03:03
To: cxf-user@incubator.apache.org
Cc: Shaw, Richard A
Subject: RE: Gzip encoding
Hi Shaw, you can configure your client side interceptors using feature. An
example can be found from dispatch system test:
\trunk\systests\src\test\java\org\apache\cxf\systest\dispatch\TestDispatchFeature.java
and client-config.xml.
Cheers,
Jervis
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 2007?11?3? 1:43
To: cxf-user@incubator.apache.org
Cc: Shaw, Richard A
Subject: Re: Gzip encoding
Hmm... not really sure how to add it to the dispatch style suff via
spring. Interesting.
That said, bus level might make sense if the interceptor was updated
to
handle the case where it's not gzip as well.
Basically, Accept-Encoding is a hint and the server may not respond
in
gzip form. Thus, the interceptor should check the request
header and
if the headers don't say it's gzipped, skip it.
The interceptor may also need to reset the Message.CONTENT_TYPE and
Message.ENCODING properties. Not really sure though.
Dan
On Friday 02 November 2007, Shaw, Richard A wrote:
In reply to my previous message I can see that there is an example
interceptor to GZIP. I've copied this but now I don't know
how to add
it to my dispatch call.
The example adds it to the bus, but I have other services on the bus
which are not using GZIP.
I've found an example that adds it to a jaxws:client but it needs a
serviceClass and I don't have one because I'm using the dispatch
interface.
Can anybody help. Ideally I'd like to add it to my spring
config. But
if I have to add it to my code I can live with that to get
it working.
Thanks
Richard Shaw
¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤
ø,¸¸,ø¤
Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems
Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW
Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740
Error calling simple JAX-WS service from Flex/Flash
I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but with a different address). Now I'm trying to connect to the service from a Flex/Flash client, and am getting the following errors (from the Tomcat log): Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) 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:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) ... 28 more I also noticed this error earlier in the log : Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Any idea what is going on? I searched this forum first and found another post where the poster mentioned that Flex uses RPC-style, and CXF is using doc/literal. Could that be the problem? I'm very new to developing with both Flex and CXF, so I'm assuming I'm missing something. Thanks -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13668742 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there BrianP wrote: I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but with a different address). Now I'm trying to connect to the service from a Flex/Flash client, and am getting the following errors (from the Tomcat log): Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) 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:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) ... 28 more I also noticed this error earlier in the log : Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Any idea what is going on? I searched this forum first and found another post where the poster mentioned that Flex uses RPC-style, and CXF is using doc/literal. Could that be the problem? I'm very new to developing with both Flex and CXF, so I'm assuming I'm missing something. Thanks -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13668997 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing And then a bit later in the log, I still have the '...geronimo-servlet... - jar not loaded' message If this problem is related, wouldn't that have caused a problem from the simple client as well? But that one worked. Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669130 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
are you sure its removed from the war your expanded web-inf/lib directory? I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing And then a bit later in the log, I still have the '...geronimo-servlet... - jar not loaded' message If this problem is related, wouldn't that have caused a problem from the simple client as well? But that one worked. Adrian C wrote: Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669191 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
My bad, I wasn't doing a 'clean' in my script so it was reloading it from a temp/build area. So it's gone now, and I'm left with INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault ... Caused by: java.lang.IllegalArgumentException 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) ... 28 more are you sure its removed from the war your expanded web-inf/lib directory? BrianP wrote: I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing And then a bit later in the log, I still have the '...geronimo-servlet... - jar not loaded' message If this problem is related, wouldn't that have caused a problem from the simple client as well? But that one worked. Adrian C wrote: Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669576 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
are you logging the messages in out and out of cxf - is the soap action/ws-addressing correct? BrianP wrote: I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but with a different address). Now I'm trying to connect to the service from a Flex/Flash client, and am getting the following errors (from the Tomcat log): Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) 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:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) ... 28 more I also noticed this error earlier in the log : Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Any idea what is going on? I searched this forum first and found another post where the poster mentioned that Flex uses RPC-style, and CXF is using doc/literal. Could that be the problem? I'm very new to developing with both Flex and CXF, so I'm assuming I'm missing something. Thanks -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669935 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
I wasn't logging, so I searched here on how to do that in the beans.xml and added jaxws:features bean class=org.apache.cxf.feature.LoggingFeature / /jaxws:features to my endpoint. This enabled the logging, which enabled me to see the entire message. When I saw that I immediately saw my problem. It was on the Flex side, I was using the wrong brackets in the mxml for the value to send, so it was sending 'fullOrderId.text' instead of the evaluation of that value into the int id. It's working now! Thanks much, Adrian! Adrian C wrote: are you logging the messages in out and out of cxf - is the soap action/ws-addressing correct? BrianP wrote: I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but with a different address). Now I'm trying to connect to the service from a Flex/Flash client, and am getting the following errors (from the Tomcat log): Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) 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:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) ... 28 more I also noticed this error earlier in the log : Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Any idea what is going on?
Extending Security Interceptors
I'm implementing a simple web service using Apache CXF where I have to authenticate a user based on username and password. This is straightforward and I have the service working using the WSS4F Interceptors. The next phase of the project is making the service able to choose from a list of auth dbs where it will get the encrypted password that WSS4J will then use to compare against the password sent in the SOAP header. In order to determine which DB to pull the auth data from, I'd like to add a new header to the SOAP message. The Interceptor/Callbackhandler should have access to this header and then use it to figure out which DB to connect to. If anyone has any tips on how to approach this using the CXF API, please let me know! Thanks! -- View this message in context: http://www.nabble.com/Extending-Security-Interceptors-tf4778795.html#a13670686 Sent from the cxf-user mailing list archive at Nabble.com.
RE: Monitoring CXF Webservices
Thank you for the tips! -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
Re: Default WSDL generated from annotated class has elementFormDefault=unqualified
I'm looking for the same ability to set elementFormDefault=qualified using the Java -- WSDL approach, has anyone found an answer to this? I'm using the most basic approach of JAX-WS / JAXB / annotations. Thanks, Rich Jon Mountjoy wrote: Hi, The default WSDL generated from my annotated classes seems to have elementFormDefault=unqualified While the result is perfectly valid, the service I'm integrating with dies when it gets unqualified element content. Is there a way to configure the server to generate qualified elements by default instead? Thanks Jon -- View this message in context: http://www.nabble.com/Default-WSDL-generated-from-annotated-class-has-elementFormDefault%3Dunqualified-tf4425777.html#a13677523 Sent from the cxf-user mailing list archive at Nabble.com.
