I found that the bug is fixed in cxf 2.0.1
Liu, Jervis wrote:
>
> BTW, this is similar to a discussion we had before [1]. I.e., which method
> annotation is supposed to take effect, the annotation in impl class or the
> annotation in SEI.
>
> [1].
> http://mail-archives.apache.org/mod_mbox/in
Abid,
Judging from the stack trace, it looks like there is a problem in the
processing of the "-p" parameter. Any chance you could remove that
param real quick and see if it at least generates some code and doesn't
error out?
If it does work, you could work around it by creating a jaxws
cu
On Wednesday 15 August 2007, Jason Rosenberg wrote:
> I am interested in trying to create some complex xsd types, using code
> first development
>
> So far, I've seen how to do some things, like create enums by using
> the @XmlEnum annotation, etc
>
> What i haven't come accross is a way to
Instead of thinking about 'required', concentrate on min-occurs?
Aegis does this quite nicely.
And if you want to set a general policy of treating zero-cardinality as
evil (which I do, to avoid spurious arrays behind all the strings) you
can set an option.
I'm sure that there's a spring equival
Honestly, I don't think there's an easy way. I just grepped through the
JAX-WS spec and the JSR181 spec and neither spec mentions anything about
it. When we move to JAX-WS 2.1, we might be able to add support for
@XmlElement(required=true). Right now, we don't support any of the
JAXB a
I use soapscope, but it's not free.
> -Original Message-
> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 17, 2007 4:49 PM
> To: cxf-user@incubator.apache.org
> Cc: Daniel Dienhardt
> Subject: Re: Problems consuming rpc literal service
>
>
> Daniel,
>
> On Friday 17
Daniel,
On Friday 17 August 2007, Daniel Dienhardt wrote:
> afaik Axis 1.3 is used to produce this service, and I managed to
> consume it with this library. But I will send your reply to the
> provider of this ws. Can you recommend some tool to check the
> compliance of SOAP-Messages?
No idea on
Hi Benson,
In my project I have something like:
And this gets generated into:
@XmlElements({
@XmlElement(name = "Color", namespace = "http://myco.com/types";,
required = true, type = ColorType.class),
@XmlElement(name = "Sound", namespace = "http://myco.com/types";,
required = tr
Hi,
If I wsdl2java with a schema with a 'choice' element, what shows up in
the Java code? I know, I could try an experiment, but I imagine that
someone reading this could tell me in 20 seconds or so.
--benson
Hi,
I am trying to build a generic server using Provider. But I
want to make the WSDL metadata, wsdlLocation, serviceName, portName,
etc. to be user configurable, without having to re-compile the Provider
with new WebServiceProvider annotations for every new WSDL.
I thought I'd be able to do thi
Daniel,
Thanks for your reply.
I should have been more explicit. I am using the default DOCUMENT style.
Furthermore, I got my question completely backwards. :P The real question
(given that all non-primitive parameters are marked "minOccurs=0" as you
mention below, how do I mark these parameter
Corey,
On Friday 17 August 2007, Corey Puffalt wrote:
> I'm doing Java-first development using CXF and JAX-WS annotations and
> I'm trying to figure out how to mark some of my method parameters as
> optional (nillable). Does anyone know if this is possible? It seems
> like a strange oversight s
All...
I'm doing Java-first development using CXF and JAX-WS annotations and I'm
trying to figure out how to mark some of my method parameters as optional
(nillable). Does anyone know if this is possible? It seems like a strange
oversight so I'm guessing I'm just missing something obvious.
Than
Ok now it works, but here's the thing:
I switched to unwrapped mode. This time it's throwing me this:
INFO: URIParameterInterceptor handle message on path [/employees/33] with
content-type [null]
2007-08-17 08:46:25 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has th
Alright, according to this:
http://forum.java.sun.com/thread.jspa?threadID=597048&messageID=3171352
It seems that the
com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl is a
working solution, and by using that MessageFactory I am indeed getting
a different error.
So that's wher
Hi there ,
Any hints for solving this problem ?
Thanks in advance ,
Stefan
On 8/16/07, Stefan Alexandrescu <[EMAIL PROTECTED]> wrote:
>
> Hi Dan ,
> I will attach all the configurations files . They are actually the same
> with the examples files .
> what else can I verify ?
> Thanks in ad
So I take it sun saaj should work.
Then, can you explain the error I get bellow? I can see in my log that
my web service operation was invoked successfuly, but somehow things
go avry when the result of the operation is to be returned/transmitted
back to the caller:
12:57:21,940 DEBUG [HandlerPipe
Neither java.sql.Timestamp nor HashMap are supported by JAXB. A common practice
is abstracting data from unsupported types to a supported JAVA types or to user
defined POJOs. For example, Timestamp can be represented as a String, and if
you know HashMap is used as HashMap, you can write a class
Hi Ade,
CXF has tested on Jboss 4.0.x in release. We can do work on Jboss 4.2.x if you
need. Could you raise a JIRA?
Thanks
Jeff
- Original Message -
From: "Adrian Trenaman" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 17, 2007 6:03 PM
Subject: JCA demo raises java.lang.UnsupportedOper
Hi,
Has anyone experienced any problems deploying the JCA adaptor into JBoss? I
was experiencing problems and have reproduced with the demo in
samples/integration/jca/hello_world. When the servlet invokes on the proxy,
we get:
java.lang.UnsupportedOperationException: setProperty must be ove
Hi
This is a known issue, CXF does not support to generate code like that
(generate wsdl from code and then generate codes from wsdl ), we discussed
it with CXF team guys, it will be fixed once CXF supports that use case.
Thanks
Denny
blacksheep wrote:
>
> Hi Denny,
>
> The other point that
Sun's SAAJ impl should be ok. CXF has been using Sun's SAAJ as default since
CXF's inception.
> -Original Message-
> From: Christian Vest Hansen [mailto:[EMAIL PROTECTED]
> Sent: 2007年8月17日 17:12
> To: cxf-user@incubator.apache.org
> Subject: Re: Unable to create message factory for SOAP
I stuck that in a JSP file and added an import.
When I run that it gives a root complaint much like the one in my previous mail:
javax.xml.soap.SOAPException: Unable to create message factory for
SOAP: org.jboss.ws.core.soap.MessageFactoryImpl
javax.xml.soap.MessageFactory.newInstance(Unk
Hi Dan,
Not at all :-)
I see what you're saying, and thinking of it like that makes sense. If I
have to specify customisations, then its not really dynamic at all then is
it? And the whole point of what i'm doing is to be dynamic with it.
Ok then, as I need to point cxf at a variety of random
Hi Dan,
thanks for help. No offence, but I switched back to XFire 1.2.6 and
everything works fine now!
Best regards,
Abid
Dan Diephouse schrieb:
Hi Abid,
I'm not very good with German, but I think the problem is that you have a
undeclared prefix somewhere. Can you attach your WSDL?
- Dan
Thanks for your help,
afaik Axis 1.3 is used to produce this service, and I managed to consume
it with this library. But I will send your reply to the provider of this
ws. Can you recommend some tool to check the compliance of SOAP-Messages?
Daniel
Daniel Kulp schrieb:
Daniel,
That SOAP m
It looks like my problem was related to a missing SOA plugin file.
Since I was also having problems with the SOA perspective wasn't coming
up as an option any more, I reinstalled the jar files. That seemed to
fix the last of my problems. Everything appears to be working smoothly
now.
-Orig
Hi Denny,
The other point that I was uncomfortable with the plugin was generating the
implementation and client classes. They were not compatible with the
interface's method definitions. One sample might explain the problem:
One of my interface's method:
@WebResult(targetNamespace="http://servic
28 matches
Mail list logo
