As I figured out, a very old version of jaxb-impl.jar was being loaded by
jboss. JAXBContextImpl class didn't have that method in that version.
Upgrading jboss to 4.2.3 and copying jaxb-api.jar from lib to its endorsed
directory solved my problem.
Thanks Benu.
--
View this message in context:
h
Thanks for you answer Daniel,
Attachment I need to send is different for each WS method invocation (it
is like an additional merthod argument). Are interceptors designed for such
use? What about synchronisation etc.
--
Roderic
2009/3/31 Daniel Kulp
>
> It's definitely doable with an Inte
I understand where you are coming from and I've posted in gSOAP's forums as
well to ask about some hints regarding this problem since gSOAP is suppose
to be fully compliant with the MTOM standard for transferring files. Is
there any other C++ SOAP client that you would recommend?
I thought perhaps
Hi,
I am using CXF 2.2 to expose the same service supporting both SOAP and
REST-based invocations with the help of JAX-WS and JAX-RS. My beans.xml is
attached.
http://www.nabble.com/file/p22818039/beans.xml beans.xml
When I invoke the service using REST client, I get a successful response,
but
Java InputStream <> C++ InputStream (assuming the latter exists). Your way
of thinking still seems strange:
"successfully developed a C++ client for a Java service that uses MTOM"
should not be the issue. The real question should be: "successfully
developed a C++ client for a web service that us
Right. So in order to use the Java service's upload method, I have to
provide a DataHandler object (that references a file) and from what I
understand, DataHandler is just a wrapper for an InputStream. So if I were
to construct my own DataHandler class in C++ and pass an input stream to the
Java Se
In the handleMessage() method of an interceptor what is the best way to
determine the direction of the message flow?
There are a bunch of interceptors that query the exchange to see if there is an
out message, but is that reliable on the client-side? On the client-side won't
there still be an o
I think you're approaching the problem the wrong way. The Java DataHandler
class, when being used from the web service provider, would not have any
clue what programming language the client is written in. It's just XML (and
a MIME attachment) over the wire. So I think you would need to go to so
Next dumb question... is it possible to do top-down development with
existing classes?
I have some classes which are shared between client and server. Is it
possible to tell wsdl2java to use/augement the existing classes?
-- bk
Daniel Kulp wrote:
On Tue March 31 2009 5:03:59 am Eoghan Glynn wrote:
Well, WS-Addressing version 2005/08 is already supported by CXF, and is
default version used on the wire and the native version used internally in
the stack.
Its only in the special case of WS-A used in conjunction with WS-RM
This is more of a jaxb question, but I have a class like this:
class Foo {
Object attribute ;
}
I have a webService who returns type Foo. If I pass in an ArrayList to
the value of attribute, I get an exception which says:
javax.xml.bind.JAXBException: class java.util.ArrayList nor any
Hmmm really good input back to the Sun folks... Any idea of how to get
them to take notice?
Also, could the Geronimo dependencies be refactored and renamed in
some generic manner? This may sound like alot of work for just naming
sake... I have folks that get nervous when they see a JAR or other
r
On Tue March 31 2009 11:32:35 am nicolas de loof wrote:
> Hi
> is there any reason CXF uses geronimo specs as dependencies and not
> standard javax.xml ones ?
> They are now available in http://download.java.net/maven/2/javax/ with
> Apache compatible licensing AFAIK
Other than the fact that I ref
Hello, I have a CXF service running for transferring files that I would
like to be consumed by a C++ client. Currently I am looking at gSOAP to
implement the client side but before I start, is there any known way of
using DataHandler to transfer files from a Java service to a non-Java
client? I'v
It's definitely doable with an Interceptor. If you want to write an
interceptor (not hard) that runs in an early phase (like user_logical), then
you can do it. The interceptor's handleMessage call would look something
like:
message.getInterceptorChain().add(new AttachmentOutIntercep
On Tue March 31 2009 5:03:59 am Eoghan Glynn wrote:
> Well, WS-Addressing version 2005/08 is already supported by CXF, and is
> default version used on the wire and the native version used internally in
> the stack.
> Its only in the special case of WS-A used in conjunction with WS-RM that we
> fal
OK. Now fixed on trunk. Will be in tonights snapshots.
Dan
On Tue March 31 2009 9:12:43 am Vassilis Virvilis wrote:
> On Tuesday 31 March 2009, Vassilis Virvilis wrote:
> > [java] at
> > java.awt.EventDispatchThread.run(EventDispatchThread.java:110) [java]
> > Caused by: java.lang.R
at happens when I remove geronimo activation
>
> [java] INFO:
> com.biovista.acgt.client.LiteratureMiningServiceClient:()
> com.biovista.acgt.client.LiteratureMiningServiceClient 1.2 build
> 20090331-0849 [java] INFO: com.biovista.lib.Net:getProxyClient() Cr
This one should now be fixed. It would be great if you can try tomorrows
snapshots (will deploy overnight) to double check. Thanks for catching it.
Dan
On Tue March 31 2009 2:47:52 am Vassilis Virvilis wrote:
> On Friday 27 March 2009, Daniel Kulp wrote:
> > > 1) Why I do need geronimo-jax
great! Thanks a lot!
Priscille.
Sergey Beryozkin a écrit :
Hi
I fixed it on Friday evening but could not merge so merged only
today...Arrays can now be supported for all the parameter types
(query, path, header, etc)There's no need to register a
ParameterHandler for say String[] or Long
Hello,
is it possible to disable multiple file WSDL (imports tag) from Aegis
on-the-fly WSDL generation and allow only one file WSDL (like in XFIRE or
JAX-RS)?
On Tuesday 31 March 2009, Vassilis Virvilis wrote:
> [java] at
> java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
> [java] Caused by: java.lang.RuntimeException: Could not find conduit
> initiator for transport http://schemas.xmlsoap.org/soap/http
> [java] at
Hi
I think it's an interesting idea, bean properties have no '.' thus using a '.' as an indicator should work. The procedure in charge
of handling this extension will become more complicated, possibly recursive, but it looks like it's quite realistic to make it
support queries with nested param
Well, WS-Addressing version 2005/08 is already supported by CXF, and is
default version used on the wire and the native version used internally in
the stack.
Its only in the special case of WS-A used in conjunction with WS-RM that we
fallback to the older WS-A version 2004/08. This is because the W
Hi Dan,
Daniel Kulp wrote:
Ah. Didn't realize this was a "java first" thing producing that wsdl. The
JIRA item just really mentioned running wsdl2java on the wsdl.
Sorry I forgot to mention that in the subject. But yes, this is a java
first service.
Hmmm Any chance of getting the
Your approach is "close". If you stored it on the exchange
(message.getExchange()) and retrieved it from there, that would be available
on the out.
You MAY be able to do this just on the out:
message.getExchange().getInMessage().get("HTTP.REQUEST");
Dan
On Mon March 30 2009 10:21:45 pm Mo
On Tue March 31 2009 12:04:05 am Gabo Manuel wrote:
> Hi Dan,
>
> I saw your latest comments re the jira. Would that mean that CXF has a
> problem generating the WSDL properly? Or is there an annotation I should
> fix?
Ah. Didn't realize this was a "java first" thing producing that wsdl. The
Hi Daniel,
Thanks for the answers.
I provided backtrace for the jar dependencies you requested in other mails
On Friday 27 March 2009, Daniel Kulp wrote:
>
> > 2) Is Aegis based on JAXB or is this is meaningless
> > question? Can I have aegis without the jaxb stuff?
>
> No. We use JAXB inte
28 matches
Mail list logo
