Re: ws-security under tomcat

Ok so i ended up reading the source for the WSHandlerConstants and WSConstants classes to figure out the xml config i needed for my server, and have basic username/password authentication going. anyone interested can have a look at my code at:

Specifying port for the example server

Hello, can I change the port of the standalone http server? I would like to run two servers on one machine. Thanks -- Lukas Zapletal http://lukas.zapletalovi.com

suggestion: package some test classes in a 'mock' jar?

I'm about to borrow AbstractCXFTest and a subclass or two to set up test of my own service. It occurs to me that you all could package a jar file with the contents of org.apache.cxf.test and the generally useful pieces of AbstractAegisTest. Spring does something like this with the 'mock' jar, no?

RE: Specifying port for the example server

If you're creating multiple services off the embedded http server, just pass the port in the url. If it's different it will automatically listen off of that port for that endpoint. -Original Message- From: Lukas Zapletal [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 6:45 AM

Aegis and exceptions

I find that my exception classes are collapsing into SoapFault. What am I missing? java.lang.Exception: Unexpected exception, expectedcom.basistech.rnm.index.NameIndexException but wasorg.apache.cxf.binding.soap.SoapFault at

RE: Getting the HTTP server off the bus

I think it would be helpful on a wiki... -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 8:55 PM To: cxf-user@incubator.apache.org Subject: RE: Getting the HTTP server off the bus Well, you can ignore the first paragraph. The rest of my

RE: Wrong number of Arguments Error

Every time I send this with a code zip attached it is bounced as spam, so I'll try to send you the code zip offline. This is a java first case. What we are doing is hooking up applications that are completely internal, so the wsdl is not so much of a concern per se for this application because

RE: Specifying port for the example server

Hi Lukas, You just need set the endpoint address with different port, Here are the example, if you publish service with jaxws api: Object implementor = new GreeterImpl(); String address1 = http://localhost:9000/SoapContext/GreeterPort;; Endpoint.publish(address,

RE: Getting the HTTP server off the bus

Done. Here is the URL http://cwiki.apache.org/confluence/display/CXF20DOC/Standalone+HTTP+Transport -Original Message- From: Clough, Samuel (USPC.PRG.Atlanta) [mailto:[EMAIL PROTECTED] Sent: Tue 7/17/2007 20:39 To: cxf-user@incubator.apache.org Subject: RE: Getting the HTTP server off

RE: Getting the HTTP server off the bus

I added some comments and cleaned out some grit. -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 9:38 AM To: cxf-user@incubator.apache.org Subject: RE: Getting the HTTP server off the bus Done. Here is the URL

Re: Issues with cxf.xml using spring and simple front end.

Thanks! that worked. When you are updating the wiki, you may want to check the sample xml file also. On 7/16/07, Willem Jiang [EMAIL PROTECTED] wrote: Here is a litter trick for the endpoint address setting with using servlet transport. I will update wiki for it. Because of CXFServlet can't

@WebFault, I think there's a mistake on the Wiki

http://cwiki.apache.org/CXF20DOC/developing-a-service.html This page states that @WebFault goes on methods. However, it looks to me as if @WebFault only goes on exception classes. The page could also use an example. XFire had a whole discussion about faults, which doesn't seem to have

How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)

Hi all, I am an xfire user who is used to the xfire services.xml. I am now porting the services.xml to cxf.xml and have it working for a simple 'Hello World' case. I have a requirement to refer to beans defined else where in the cxf.xml. XFire used to let me do this using the # convention.

RE: Java 1.4

IMHO, yes. -Original Message- From: Christopher Moesel [mailto:[EMAIL PROTECTED] Sent: 17 July 2007 14:11 To: cxf-user@incubator.apache.org Subject: RE: Java 1.4 Thanks for the extra info, Roman. I was going based on a snippet in the XFire Migration Guide on the WIKI:

RE: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)

I think you could try to use the endpoint's attribute implementor. It should be workable with the # convention. Here is an example for it jaxws:endpoint id=endpoint1 implementor=#HelloService address=/services/Greeter1/ Willem -Original Message- From: Jacob

Configuring interceptors using annotations

Is there support for configuring interceptors using annotations? I'm looking for something like the org.codehaus.xfire.annotations.InHandlers and org.codehaus.xfire.annotations.OutHandlers class where were present in XFire. I'm thinking of writing similar annotations and want to make sure that

Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)

Hi Willem, I believe I am using version CXF incubator 2.0. The simple.xsd does not support implementor as an attribute. It does support implementor as an element. But it needs child elements. Should I be using a different version (snapshot) of CXF? Thanks, Jacob On 7/17/07, Jiang, Ning

RE: Access to MessageContext in the implementations. (XFire to CXF question)

Hi Jacob, I'm not sure how to do this without annotations. With annotations, you would do this the JAX-WS approved way, by adding this to your service implementation class: @Resource private WebServiceContext context; Then you could use the WebServiceContext object to get the message

Re: Wrong number of Arguments Error

Samuel, I managed to track this down. It's a bug in the DepthXMLStreamReader that isn't getting the END_ELEMENT events lined up correctly in the Aegis binding.Thus, while reading the first object, it's sucking in all the rest of the data so it doesn't deserialize the second parameter.

RE: How to enable mtom on the embedded server?

Hi Samuel, Have you looked at the MTOM documentation in the user guide? http://cwiki.apache.org/CXF20DOC/mtom.html If so, then what information is missing (or incorrect) that you need? -Chris -Original Message- From: Clough, Samuel (USPC.PRG.Atlanta) [mailto:[EMAIL PROTECTED] Sent:

Re: Wrong number of Arguments Error

My fix is committed. You would need to rebuild the common/common stuff. The aegis binding was OK, it's just the XMLDepthStreamReader thing from common-utilities that it used was a problem. Dan On Tuesday 17 July 2007 11:52, Clough, Samuel (USPC.PRG.Atlanta) wrote: Wow, thanks for

RE: How to enable mtom on the embedded server?

I have looked at that doc. I was trying to see if there was a simple setting like what Xfire had that would activate it on byte[] property. We're doing Java first dev since all the services here are in house and nothing uses Annotations right now for the services, so I was trying to do it without

Re: Java 1.4

On Tuesday 17 July 2007 08:49, Roelofsen, Roman wrote: With retrotranslator you only solve language problems like - generics - annotations - etc But CXF also uses new classes introduced in Java5, existing classes got new methods, etc. So the bigger problem is running CXF with a Java4

RE: Java 1.4

I tried. Retrotranslater maps thinks like - Annotation API - StringBuilder - StringBuffer But NOT - java.util.Properties.loadFromXML - and hundreds of other methods - and hundreds of new classes I got it working by using Apache Harmony to override/add the missing classes etc. In addition,

Re: Using CXF

Can you show me what your web.xml and whole cxf.xml look like? How are you importing the CXF bean definitions? Thanks, - Dan On 7/16/07, Jacob Marcus [EMAIL PROTECTED] wrote: Thanks Dan. That worked. from the cxf.xml I would like to refer to a bean defined else where like, simple:server

Re: suggestion: package some test classes in a 'mock' jar?

On Tuesday 17 July 2007 06:55, Benson Margulies wrote: I'm about to borrow AbstractCXFTest and a subclass or two to set up test of my own service. It occurs to me that you all could package a jar file with the contents of org.apache.cxf.test and the generally useful pieces of

Re: @WebFault, I think there's a mistake on the Wiki

Thanks I fixed this. Which discussion are you referring to? If you are using the JAX-WS frontend, you do need to use @WebFault. If you're using the simple frontend, things *should* work without the @WebFault annotation. Regards, - Dan On 7/17/07, Benson Margulies [EMAIL PROTECTED] wrote:

Re: Configuring interceptors using annotations

Hi Zarar, It'd be great if you could file a feature request in JIRA for this though: http://issues.apache.org/jira/browse/CXF Thanks, - Dan On 7/17/07, Andrea Smyth [EMAIL PROTECTED] wrote: Hi Zarar, As part of its JAXWS implementation CXF supports the @javax.jws.HandlerChain annotation for

Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)

With the simple frontend its called a serviceBean: simple:server id=Test address=/hello serviceBean=#helloService serviceClass=com.test.Hello /simple:server Cheers, - Dan On 7/17/07, Jacob Marcus [EMAIL PROTECTED] wrote: Hi Willem, I believe I am using version CXF incubator 2.0. The

RE: Aegis tests and exceptions ...

Dan, Reading the code of 2.0, I see no evidence of any client-side code capable of taking a soap fault and turning it into a custom exception class. The two interceptors I see (the 1.1 and 1.2 versions) both end up throwing the CXF-specific SoapFault class. What am I missing? --benson

RE: @WebFault, I think there's a mistake on the Wiki

At some risk of redundancy: Step 1: set up Aegis+JAX-WS environment with some exceptions on the service interface (and of course implementation). Step 2: observe that WSDL seems plausible. Step 3: run unit test. The throw is org.apache.cxf.binding.soap.SoapFault, not any of mine. Step 4: In a

Re: Configuring interceptors using annotations

Hi Dan, I've created the JIRA: http://issues.apache.org/jira/browse/CXF-803 Thanks, Zarar Dan Diephouse wrote: Hi Zarar, It'd be great if you could file a feature request in JIRA for this though: http://issues.apache.org/jira/browse/CXF Thanks, - Dan On 7/17/07, Andrea Smyth

Re: Using Local Transport for JUnit Tests

Hi Christopher - If you are using maven you need to add this dependency: dependency groupIdorg.apache.cxf/groupId artifactIdcxf-rt-transports-http-jetty/artifactId version${cxf.version}/version /dependency If your not using maven just add that jar to your application

RE: attempting HelloWorld service, getting NULL return value

Hi Marty, as you said, you've examined the message flowing between client and client and it is correct, in this case, must be sth wrong with your client. You may want to send us your client code, so that we can take a quick look to see what happened there. Thanks, Jervis -Original

shell scripts tools versus cygwin

Java2wsdl (the shell script) does not react well to being run from a cygwin shell. It ends up with the wrong path separators. If this isn't in the queue, I'll post a JIRA with a patch.

java2wsdl from ant

I know that ant tasks are pending. Until then, I tried to roll my own. And I crashed with a complaint that cxf.xml was not found in classpath. What jar file is supposed to contain it for this purpose?

java2wsdl rejects class that is acceptable to the aegis universe

Is there something special I have to do to run java2wsdl for an aegis environment? As it is, I get a very mysterious rejection letter until I ask for -verbose, and then I get the following... org.apache.cxf.bus.spring.BusApplicationContext getConfigResources [java] INFO: Could not find the

Re: How to enable mtom on the embedded server?

Hi Samuel, javax.xml.ws.soap.SOAPBinding is class from jax-ws api, so you need make your service jaxws compatible add jaxws BindingType annotation into your TestServiceImpl @BindingType (value = SoapBinding.SOAP11HTTP_MTOM_BINDING) And use JaxWsServerFactoryBean instead of ServerFactoryBean to

Re: Using Local Transport for JUnit Tests

Here is another way to add the LocalTransport by adding these in your spring.xml instead of including META-INF/cxf/cxf-extension-local.xml bean class=org.apache.cxf.transport.local.LocalTransportFactory lazy-init=false property name=transportIds list

Re: java2wsdl from ant

java2wsdl/wsdl2java ant tasks was in the trunk, i checked in days ago, but you have to build by your own, it's in /trunk/tools/anttask Let me know if you have any problems with it. James I know that ant tasks are pending. Until then, I tried to roll my own. And I crashed with a complaint that

Re: java2wsdl rejects class that is acceptable to the aegis universe

Hi Benson, Would you please append your java class? From the exception, it seems your class method are bare mode so that java2wsdl load jaxb to process your method parameter type class, but unfortunately, this type class has two properties with same name, which is illegal for jaxb. As you