Well, I have researched this one now and am stuck again. I'm confused about
the following:
1. The "real" WSDL is secured behind SSL. Given the SSL issues before, I'm
unable to generate the client stubs using the remote URL. So, I've stored
the WSDL to a local file and referenced that to generate
Hi All,
I have created cxf webservice client application.
When I deploy the applicaiton in WAS 6.1 and I have change the class loader
to "class loaded with application class loader first" and I have made change
in manifest file as "DisableIBMJAXWSEngine: true".
The application works properly exc
Hi dkulp ,
Thanks for suggestion.
I am not using any spring stuff.
Is there any way to do webseal security using java code where we can
directly point to the wsdl url?
Regards
Saravanan Ramamoorthy
dkulp wrote:
>
> On Wed February 10 2010 9:54:27 am SaravananRamamoorthy wrote:
>> Hi All,
>>
This is extremely strange. I have no idea what would cause that. :-( And
not having a windows box, not really something I can debug. Can I ask for
some help from you in debugging this or at least coming up with a reproducible
case?
1) Is there any way you could test it without the WS-
cipherSuites are ok.
I made the suggested changes (cleaned up the cipher filter and put the
key/trust stores in the current directory. No love.
Interestingly, after my original post, I found another post that had success
essentially commenting out everything but the main tlsClientParameters
ele
I'm not really sure what's happening. Can you check the Client Hello token
sent and make sure the cipher suites that are being sent to the server are OK?
You cipherSuitesFilter thing looks a bit strange, but it just may be the mail
client doing something. Normally, they would look like:
I'd be ok changing the default if it would be more interopable.
Please file a JIRA with a patch. :-)
Dan
On Wed February 10 2010 11:15:46 am Michel Decima wrote:
> Hello,
>
> We are facing exactly the same issue here : third-party server unable to
> handle
> attachment sent by MTOM producer
On Wed February 10 2010 9:54:27 am SaravananRamamoorthy wrote:
> Hi All,
>
> How can we access the webservice running behind the webseal where the
> credentials have to be specified when calling the webservice wsdl url?
If you still want to pursue this, in the spring config, you can specify a
ht
Honestly, you may just need to turn off chunking. When you say "smaller
request succeeds", do you mean under 4096? If so, we automatically don't
chunk for messages that small and just send a content-length header.
Dan
On Wed February 10 2010 9:56:31 am Jim Talbut wrote:
> Hi,
>
> I don't
On Wed February 10 2010 11:46:01 am James Avery wrote:
> We're using CXF in stand-alone mode (i.e. with the standard CXF embedded
> Jetty factories, engines, etc.).
>
> We see various 'shutdown', 'stop', and 'start' methods on the engine
> classes, the Bus class, etc. What's the proper method of
Well, outbound wouldn't have a "RECEIVE" phase. :-)
Depending on what you want to do, a SETUP phase or PREPARE_SEND or PRE_STREAM
or similar.
You can see the phases defined:
http://svn.apache.org/repos/asf/cxf/trunk/rt/core/src/main/java/org/apache/cxf/phase/PhaseManagerImpl.java
Dan
On W
I've never seen this at all.
Most likely the "runnable" that is stuck on the executor, or the executor
itself, is not recording the thead context classloader or similar. Do you
have control over the creation of that runnable? (I've never looked at the
procrun stuff) If so, could you grab
CXF 2.2.4 client trying to access an Axis2 soap web service over SSL
I can't get my CXF client to get past the SSL handshake, but the sample
Axis2 client from the web service developer works fine. Here's my config:
Thanks Daniel, I'll try that. For now unfortunately, I have to continue
to use cxf 2.1.3
Thanks
Jorge
On Tue, 2010-02-09 at 15:27 -0500, Daniel Kulp wrote:
> On Mon February 8 2010 10:40:25 am jsari...@gmail.com wrote:
> > Hi,
> >
> > I'm new with CXF. I'm using version 2.1.3. When I try to use
Karthik,
Once upon a time, we had an active contributor to CXF who was working
toward JAX-RPC support. He wrote code to support SOAP-encoded
representation in the Aegis data binding. Sadly, he got too busy with
his real job, and never finished.
There is no plan to work on this. If someone comes t
Hi
thanks for the clarification. I does look like a release-time issue which caused configadmin and fileinstall being shipped, unless
David or Eoghan have done it intentionally ?
paxweb issue : I'm wondering, should paxweb be patched so that it checks first if another HttpService is already av
Hi,
I implemented a basic web service (standalone, embedded into jetty, Java
1.6.0_18 , CXF 2.2.6) and now want to deploy it as a Windows service.
To this end I'm trying to use procrun/commons daemon to install and run
the windows service, which then calls out to a Java class that launches
the web
Hi,
See the Response tag
> S.B DOSGI RI does not ship the above two modules
Response : In the distribution single-bundle-1.1, I found in the folder "lib"
the two bundles "org.apache.felix.configadmin-1.0.10.jar" and
"org.apache.felix.fileinstall-1.0.0.jar". For the first bundle I saw the
mani
18 matches
Mail list logo
