CXF web service with sw security - Why the wsdl doesn't demand the username/pwd?

2011-07-08 Thread liav.ezer
Hello, I've wrote a CXF based service & added ws security (wss4j 1.5.1) through Spring xml. This is the end point configuration:

Which Interceptor to choose to Cleanup WS-Policy namesapces within soap body child nodes?

2011-07-08 Thread mahesh
I have been able to clean up some of the prefix and namespaces using the public class PrintOutMsg extends AbstractSoapInterceptor { public PrintOutMsg() { super(Phase.USER_PROTOCOL); } But I have some namespaces related to WS-policy that are implemented at later stage. Is there

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread David Hoffer
Okay I'll look into that. Not sure if it matters but the PHP client is something like this: $client = new nusoap_client($wsdl, 'wsdl'); $var11 = $client->call('calc', array('WebInput' => $param1)); Note there is no mention of namespace here. Is there a simple way to configure this client to use

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread Daniel Kulp
On Friday, July 08, 2011 8:54:37 AM David Hoffer wrote: > Here is what CXF receives from the PHP client: > > INFO | jvm 1| 2011/07/08 04:22:03 | Payload: encoding="ISO-8859-1"?> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xml

Re: cxf-2.4.0 pattern match StaxTransformFeature?

2011-07-08 Thread Sergey Beryozkin
Hi On Fri, Jul 8, 2011 at 4:47 AM, cogitate wrote: > ok - just to close the loop . > what was happening is specific to cxf-2.4.0 and it's a bug that's been fixed > in cxf-2.4.1-SNAPSHOT as given below. > http://cxf.547215.n5.nabble.com/quot-Stream-is-closed-quot-Exception-when-upgrade-from-CXF-2-

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread Sergey Beryozkin
Hi On Fri, Jul 8, 2011 at 3:49 PM, David Hoffer wrote: > Hi Sergey, > > That example looks like its configuring the client to drop the > namespace.  What I need is the reverse, I need to configure the server > to not use a namespace.  I can't change the PHP client so I'm trying > to change the se

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread David Hoffer
Here is what CXF receives from the PHP client: INFO | jvm 1| 2011/07/08 04:22:03 | Payload: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encodin

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread David Hoffer
Hi Sergey, That example looks like its configuring the client to drop the namespace. What I need is the reverse, I need to configure the server to not use a namespace. I can't change the PHP client so I'm trying to change the server so that it works with existing PHP client code. (Apparently in

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread Daniel Kulp
On Friday, July 08, 2011 8:35:29 AM David Hoffer wrote: > I have some existing services developed and deployed with 2.1.2 using > the java first annotation approach (JAX-WS). After upgrading to 2.4.1 > existing PHP clients receive the following error: > > INFO | jvm 1| 2011/07/08 04:22:03 |

Re: Service differences when upgrading to 2.4.1

2011-07-08 Thread Sergey Beryozkin
Here you go: http://cxf.apache.org/docs/transformationfeature.html configure JAXWS endpoint to drop the namespace like this: {http://mynamespace}*:* where {http://mynamespace}* is a key, * is a value Cheers, Sergey On Fri, Jul 8, 2011 at 3:35 PM, David Hoffer wrote: > I have some existing se

Service differences when upgrading to 2.4.1

2011-07-08 Thread David Hoffer
I have some existing services developed and deployed with 2.1.2 using the java first annotation approach (JAX-WS).  After upgrading to 2.4.1 existing PHP clients receive the following error: INFO   | jvm 1    | 2011/07/08 04:22:03 | WARNING: Interceptor for {http://some_namespace/}IAPIService#{htt

RE: Client for rpc/encoded webservice

2011-07-08 Thread Zhemzhitsky Sergey
Hi Glen, Rather interesting solution. Thanks a lot for information. Best Regards, Sergey Zhemzhitsky -Original Message- From: Glen Mazza [mailto:gma...@talend.com] Sent: Wednesday, July 06, 2011 3:55 PM To: users@cxf.apache.org Subject: Re: Client for rpc/encoded webservice ...unless

Exception(Unexpected end of file from server) of CXF

2011-07-08 Thread xuhb
Recently I always encounter a "Unexpected end of file from server" Exception at CXF client side. it seems this exception is caused by the CXF Serverside has unexcepted release the http connection ; I tried some effort to to use a simple test case to regenerate such a exception; Following is