Hi Gilles,
I just committed a quick fix for the issue of the CXF local transport
direct dispatch model [CXF-1107].
You can try it by using the truck version or waiting few days for the
next 2.0.3 snapshot.
Willem.
Willem Jiang wrote:
Hi,
I can reproduce the error, it definitely is a CXF
What's the version of cxf are you using? it's been changed to java2ws
http://cwiki.apache.org/CXF20DOC/java-to-ws.html
James
Hi, I've been trying to use the Maven plugin but I'm getting this error.
[INFO] Scanning for projects...
[INFO]
Hi,
I am trying to deploy the java_first_spring_support sample war to the
WebSphere 6.1.0.0, I am using the WebSphere console to install the
Application, and it started successfully.
However, when I want to access the wsdl, it shows the Error 500, and I
look up the log file,
it shows
Spent a bunch of time playing with the JWS and JAXWS TCK's last night and
digging though specs to figure out what can be done here.
1) For the simple frontend, I can definitely make the
default parameters for all cases.
2) For jaxws, I can make the default parameters for MOST cases.
Hello James,
I'm using Apache CXF 2.0.2.
Here's an extract from my pom.xml
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
encodingUTF-8/encoding
Fellow users:
When using JAXB code-first, how much do people worry about the
irritation of Java strings mapping to arrays?
That is: String foo:
Turns into an array of 0 or 1 strings, to account for the possibility of
null versus versus foobar.
One can clean this up with
On Thursday 11 October 2007, Benson Margulies wrote:
Fellow users:
When using JAXB code-first, how much do people worry about the
irritation of Java strings mapping to arrays?
Well, I personally don't consider minOccurs=0 maxOccurs=1 to be an
array. That's and optional element, not an
What version of CXF are you using?There were a few bugs logged for
2.0 and 2.0.1 that were fixed in 2.0.2:
https://issues.apache.org/jira/browse/CXF-926
https://issues.apache.org/jira/browse/CXF-1028
There currently is a bug in the SNAPSHOTS that is causing nothing to be
written back to
I think that some toolkit I tried to use to build a client
once-upon-a-time gave me an array, and I've been exhibiting allergic
behavior ever since.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 11, 2007 10:28 AM
To:
On Thursday 11 October 2007, [EMAIL PROTECTED] wrote:
I am using Version 2.02. Should I upgrade to Snapshot?
Nope. 2.0.2 should definitely be working (providing the code was
generated with 2.0.2. Code generated with 2.0.1's wsdl2java will not
work correctly).I guess I would need to
Just simply put the war in the JBoss deploy folder, and then it would be
working fine.
-Jeff
shaminda perera wrote:
Hi all
I need some help in deploying a CXF Web service in JBoss application server
. Any pointers?
Thanks
Hi all,
i have an old service in axis that uses saaj to work on messages. Now i want
to migrate on CFX but i encounter some problems...
First step is make a service that works at message level with saaj. So i
need that avery message that point to
plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version2.0-incubator-M1/version
dependencies
dependency
groupIdorg.apache.cxf/groupId
On Thursday 11 October 2007, Benson Margulies wrote:
When CXF launches jetty, does it rearrange jetty's log across to
j.u.l?
Jetty uses slf4j so whichever slf4j-XXX.jar it finds on the classpath is
the one that is used. We ship the slf4j-jdk14 jar which directs slf4j
to use j.u.l. There
Doing this would make the schema's not really match the API's. The APIs
specifically use QNames which is why the schema says xsd:qname. To
support this, we'd have to change the schema to be a xsd:string (or
string with a restriction with a pattern) which then no longer matches
the API's.
I installed the java_first_spring_support and got the same error as you did.
On 10/11/07, Jeff Yu [EMAIL PROTECTED] wrote:
Hi,
I am trying to deploy the java_first_spring_support sample war to the
WebSphere 6.1.0.0, I am using the WebSphere console to install the
Application, and it started
In addition, it can help to reduce your source code to the most minimum
that replicates the error. Less for the reader to wade through / easier
to spot errors that way.
Glen
Am Dienstag, den 09.10.2007, 09:41 -0400 schrieb Daniel Kulp:
That stack trace points to you using the the Sun reference
At least with CXF, the namespace prefixes for the wsdl:definition
element ignore any @XmlNs mappings on the package-info.java of the
package containing the SEI.
Is this right?
If you haven't been liberated yet, [EMAIL PROTECTED] might help
or (worst case) [EMAIL PROTECTED]
Glen
Am Mittwoch, den 10.10.2007, 10:37 -0700 schrieb
[EMAIL PROTECTED]:
Someone please unsubscribe me from this mailing list. I tried atleast 10
times through unsubscribe mail id. It asked me to
Metro also is a bit on the chatty side when generating a client. But
our debugging page gives more info on setting logging levels:
http://cwiki.apache.org/confluence/display/CXF20DOC/Debugging
Glen
Am Mittwoch, den 10.10.2007, 18:04 -0400 schrieb Benson Margulies:
What do you think of turning
I'm probably not understanding your entire question, but I think if
you're using SAAJ, that would mean you don't need to use a web service
framework--neither CXF nor anything else. (SAAJ has a SOAPConnection
object that will do what you want.) See here[1] for an example.
Glen
[1]
FYI, Cxf2.0.2 still using java2wsdl, so you dont' need to change the
goal to java2ws
If you're using latest trunk, you need to change to java2ws, CXF2.0.2 is
the last version which using java2wsdl
Besides, your version
version2.0-incubator-M1/version
is not correct
Try the
2.0.2-incubator
JAX-WS Dispatch/Provider API should give you what you want. There is a sample
named jaxws_dispatch_provider in CXF distribution demonstrates how to write
dispatch/provider in CXF. The reason why you got that exception is because you
are using CXF HTTP binding in your configuration, which is the
23 matches
Mail list logo
