Sven,
I take it the "moving around" occurs in custom interceptors? You can
definitely do your own Hibernate session management in interceptors. I did
it myself before I groked AOP and @Transactional. In fact, I think I
plagiarized the crux of it from OpenSessionInViewInterceptor. Just be sure
you
For the first issue, yes, I would say the errors should have separate
namespaces even if they mean the same thing--if you're doing WSDL-first
each of their WSDL's should have separate target namespaces anyway.
For the second issue, this article[1] has both a wsdl-defined fault and
a generic SOAPFa
Hi all,
I realize something similar was just asked but still some of my issues are not
solved.
My SOAP service may throw a few exceptions and as far as I understand, these
Exception object will be converted automatically by CFX. I created a java
client with wsdl2java and I can see the Exceptio
Yeah, JAX-RS was my specific need. Thank you both for your assistance.
On Thu, 2008-07-17 at 14:22 +0100, Sergey Beryozkin wrote:
> I'm wondering is it a question about JAX-RS by any chance ?
> Just in case it is :-) ('Response' is mentioned in the original mail) here's
> the info on how to do
Hi all,
there must be a more elegant solution to an issue I have right now. I am using
CXF to expose a SOAP-based interface to our data layer. This means in my spring
config, I got bith Hibernate setup and also cxf. So calls would come in, hit
the SOAP interface and the service implementations
The soap message is wrong for an rpc/lit response.
The element should be:
Per RPC/Lit rules, the part accessors come from the part names in the
message/parts of the wsdl. They are also supposed to be unqualified
per wsi-bp rules (although some older toolkits do qualify them so our
RPC
We have implemented a CXF client from a counterparty-supplied WSDL.
As we call one operation, we get back a response containing valid
business messages.
However, the RPCInInterceptor throws an exception because it "could not
find matching RPC/Literal part".
We have checked the response, and it con
Glen,
The reason I didn't pull it into the 2.0.x branch is that it
technically is a binary incompatible change. The WSS4JOutIntercptor
moves from the POST_PROTOCOL phase to the PRE_PROTOCOL phase with it's
internal interceptor going into the POST_PROTOCOL. Thus, if a user
has an inte
> Depends on the business logic. :-)If the business logic is doing
> all kinds of database lookups, transforms, etc..., that percentage
> would go up.If it's just: return "hello " + arg1;
> the percentage is obviously very small.
In these tests it is literally just "hello".
-O
On Jul 17, 2008, at 11:17 AM, David Soroko wrote:
Perhaps I should explain why I think this is an interesting question.
Imagine two frameworks: framework10 and framework100. During
performance
testing it is observed that on a given hardware framwork10 supports up
to 10 requests per second (
Perhaps I should explain why I think this is an interesting question.
Imagine two frameworks: framework10 and framework100. During performance
testing it is observed that on a given hardware framwork10 supports up
to 10 requests per second (rps) with a "good enough" response time at
which point t
Hi,
I am currently working on a creating custom conduit that asynchronously
receives messages.
In the current implementation of Client &
org.apache.cxf.endpoint.ClientImpl - consumers of a conduit the
assumption
seems to be that invoke() is a synchronous operation as the javadoc
clearly stat
Work has been started to get the WTP stuff to support CXF/JAX-WS a bit
better. One of the IONA folks have posted a short video of it "in action":
http://open.iona.com/forums/thread.jspa?threadID=331&tstart=0
(might need to register/login to see it, not really sure)
Definitely take a look at
No, it looks like you need to turn chunking off when using them.
See:
http://cwiki.apache.org/CXF20DOC/client-http-transport-including-ssl-support.html
Dan
On Jul 16, 2008, at 4:12 PM, Mert Çalışkan wrote:
getting read-timeouts on soap11 and soap12 bindings :/
looks like provider doesnt s
I'm wondering is it a question about JAX-RS by any chance ?
Just in case it is :-) ('Response' is mentioned in the original mail) here's
the info on how to do it in JAX-RS :
1. throw unchecked JAX-RS WebApplicationException, by initializing it
with an xml-based Response
2. Throw whatever custom
Dan, if you wouldn't mind adding the SAAJ handler to the one WSS4J In/Out
Interceptor (one of those two) in the 2.0.x branch where it is missing (the
other one in 2.0.x has it), we can remove this distracting moving part
entirely from the CXF WS-Security documentation. I'll happily do the doc
upd
Hi!
I'm new to cxf. At the moment I try to generate a wsdl from an existing
java class via a maven plugin. It seems that everything works fine,
except the targetNamespace I defined in my pom.xml was not transferred
to the wsdl. What is wrong?
Here is the part of my pom.xml:
In both cases, the easiest thing to do would probably to put an
interceptor early in the FaultOut chain that pulls the Fault/
Exception out of the chain and replaces it with a SoapFault that
you've built up with your needed codes and such.
In the second case, you could subclass our invoke
Looking at the code, it looks like Aegis only reads mtom if mtom is
enabled on the databinding. JAXB is different. It will always read
MTOM, but only write mtom if mtom is enabled.
The simplest thing to do is when you create your AegisDatabinding
object, call the setMtomEnabled(true)
2008/7/17 Daniel Kulp <[EMAIL PROTECTED]>:
>
>
> Just add another dependency like:
>
>
> org.apache.cxf
> cxf-rt-javascript
> ${cxf.version}
>
>
>
> That should be it. maven should then add that to the package and it should
> be automatically picked up.
Brilliant, thanks, works now. Maven is
On Jul 17, 2008, at 12:40 AM, Glen Mazza wrote:
If you're using CXF 2.1+, be sure *not* to add the SAAJ handlers as
you're
doing below. That's only a 2.0.x thing.
Actually, it's not a big deal if you do add them. It's smart enough
to check if its needed or not.
Dan
Also, you *mi
Just add another dependency like:
org.apache.cxf
cxf-rt-javascript
${cxf.version}
That should be it. maven should then add that to the package and it
should be automatically picked up.
Dan
On Jul 17, 2008, at 3:47 AM, Andrew Clegg wrote:
2008/7/16 Daniel Kulp <[EMAIL PROTECTED]
Hello
Is it possible to get JAX-WS + Aegis + MTOM working? So far I was unable
to achieve such configuration. Example (as a client I used SoapUI 2.0.2):
WEB-INF/web.xml:
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://j
2008/7/16 Daniel Kulp <[EMAIL PROTECTED]>:
>
> Well, couple questions:
> 1) Are you using a 2.1.x version of CXF or 2.0.x? The javascript stuff
> is only in 2.1.x.
2.1.1
> 2) In your war or tomcat setup, are you using the big CXF bundle jar or
> individual modules? If using modules, is the
24 matches
Mail list logo
