Hi,
I would like to reuse my xsd generated classes in different projects.
Therefore I would like to have a stand alone project which just contains the
xsd and generates the classes.
These classes should be put in my maven repository.
After that I would like to tell wsdl2java not to generate the j
ronanf wrote:
Thanks for that Dan,
Yes I am running CXF 2.0.3.
In the end my problem was I have an asm1*.jar in my build path (this is
needed for the version of Hibernate I'm running). But CXF requires asm2* or
asm3* as you pointed out.
I got around this by using the cglib-nodep JAR with Hibe
Hi
I'm not sure you can achive it with CXF-specific REST bindings but it's most
likely you can do it
(I hope pretty easily) with the CXF JAX-RS implementation.
Here's the way Servers and Server resources may look like. I belive there's no
need to specifically annotate ResultySet class in this c
Dan,
Sorry, I just spotted that there were some other response e-mails on
nabble.com's archive of this mailing list
(http://www.nabble.com/Problem-generating-WSDL-from-Java-API-with-
CXF-2.0.3-td15084730.html lists this thread) which I didn't actually
get. Not sure why. Were you asking for me to p
dkulp wrote:
>
>
> Hmm... That's not good. I more or less expected that to work. Not sure
> why it wouldn't be..
>
> Ok. Couple questions:
> 1) Are you throwing this from your impl, and interceptor, or a jaxws
> handler?
>
I'm throwing Exception inside my webService application code.
Hi,
What is the right way to call a secure web service that authenticates the
requests based on username token authentication in CXF ?
How can I accomplish this with Client Outbound Endpoint ?
Or should I implement my client ssing a web service client directly ?
Also can I use https connector
We are currently creating a Web Service using CXF configured with Spring
and Jax-ws annotations.
The web service runs on a server that is proxied (using Apache 2 httpd)
from an external URL to the internal URL.
So, the public URL of the WSDL is (for example) -
https://public.url/services/
I am sorry I shoud have post this message to mule forum.
blacksheep wrote:
>
> Hi,
>
> What is the right way to call a secure web service that authenticates the
> requests based on username token authentication in CXF ?
>
> How can I accomplish this with Client Outbound Endpoint ?
> Or shoul
Regarding target namespace and the elementFormDefault issues...
Interestingly the package-info.java approach doesn't seem to work.
Whilst this sets the default element form to qualified, each element is
then generated with the form="unqualified" attribute set. D'oh! I guess
I'll have to use the Xm
I tried to apply wsdl2java to the WSDL below. The WSDL operations
defined are both referring to the same type element as input message,
so the soap body are the same for both the messages. To solve this
collision, i added the soapAction to the binding, but the wsdl2java
seems to ignore it.
Hi Dan,
This worked very well! How can I do this on the client side?
Thanks!
Mayank
On 1/28/08, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> On Monday 28 January 2008, Mayank Thakore wrote:
> > Hi Daniel,
> >
> > Will BindingProvider.HTTP_PROTOCOL_HEADERS work for JMS also?
>
> With 2.0.4, yes. In
on server side i used the server response context...
i noticed that it only copies the jms message properties, not the
header... for the header server request context seems to work... but
anyway, i needed only the message properties.
how to get the context on the client side? i want to set jms
pro
Which option did you use?
you can use JAX-WS requstcontext and responsecontext to get the access
to JMS headers at client side.
Regards,
Ulhas Bhole
Mayank Thakore wrote:
Hi Dan,
This worked very well! How can I do this on the client side?
Thanks!
Mayank
On 1/28/08, Daniel Kulp <[EMAIL P
Better let us know the version of CXF you're using
James
On Jan 31, 2008 8:07 PM, Marco Piraccini <[EMAIL PROTECTED]> wrote:
> I tried to apply wsdl2java to the WSDL below. The WSDL operations
> defined are both referring to the same type element as input message,
> so the soap body are the sam
If you check the following system test it will show you how to use context.
http://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jms/JMSClientServerTest.java
Regards,
Ulhas Bhole
Mayank Thakore wrote:
on server side i used the server response conte
After a bit more research it seems that this error was because Weblogic is
trying to use it's own older version of JSR 181. So, I prepended
geronimo-ws-metadeta_2.0_spec-1.1.1.jar to the Weblogic classpath and am now
getting:
Jan 31, 2008 11:46:07 AM
org.apache.cxf.service.factory.ReflectionServ
Yeah, after reading the source code, I realized that the path resolution
happens in 2 phases. The first is the servelet selection based on the first
address.startsWith(path) match, and the second the score based match for the
URL once it gets into the servlet. Because of that overlapping URI pat
I found this guide on the CFX wiki, which confirms the issue is with WebLogic
overriding geronimo-ws-metadeta_2.0_spec-1.1.1.jar
http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-WebLogic
However, following their instructions I still get the QName error.
-Ben
chengas123 wrote
How about you put the jar file "xml-resolver-1.2.jar" in your webLogic
classpath?
(keep this
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
setting)
Or make sure CXF's jars in your classpath.
I agree that "Configuring the proxy" is not a good solution.
Hope this can help.
Unfortunately that does not work either. I get the stacktrace below.
I feel like I was closest overriding
geronimo-ws-metadeta_2.0_spec-1.1.1.jar:
http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-WebLogic
However, I then get the QName error. The wiki says in multiple places to
Hi
I've been using 2.0.3 with good success and I decided to upgrade to
2.0.4 this morning.
I'm having problem running my tests which are failing now with:
Testcase: test5SoapRemoting
(com.surgex.addresslookup.service.AddressLookupServiceIntegrationTest):
Caused an ERROR
[junit] null w
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
YI (William) ZHU wrote:
>
> stax-api jar file is in \{CXF-home}\lib
>
> unpackage it, you will find the javax.xml.namespace.QName class.
>
> delete it, and re-package the file.
stax-api jar file is in \{CXF-home}\lib
unpackage it, you will find the javax.xml.namespace.QName class.
delete it, and re-package the file.
try it.
chengas123 wrote:
>
> Hi,
> I was getting a "java.lang.NoSuchMethodError:
> javax.jws.WebService.portName()Ljava/lang/String;" error on WebLog
actually, it's "stax-api-1.0.1.jar".
(on CXF 2.0.2 and CXF 2.0.3)
chengas123 <[EMAIL PROTECTED]> wrote:
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
YI (William) ZHU wrote:
>
> stax-api jar file is in \{CXF-home}
Haha. I would have realized that was the same .jar
The only one included in 2.0.4 is stax-utils-20060502.jar
YI (William) ZHU wrote:
>
> actually, it's "stax-api-1.0.1.jar".
> (on CXF 2.0.2 and CXF 2.0.3)
>
>
>
> chengas123 <[EMAIL PROTECTED]> wrote:
>
> I downloaded apache-cxf-2
On Thursday 31 January 2008, Mayank Thakore wrote:
> Hi Dan,
>
> This worked very well! How can I do this on the client side?
It's very similar, but kind of in reverse. You also need to deal with
the case of the protocol headers map not being create yet:
BindingProvider bp = (BindingProvider)
This is actually per spec according to the WS-I Basic Profile. Section
---snip---
5.6.7 Wire Signatures for Operations
An endpoint that supports multiple operations must unambiguously identify
the operation being invoked based on the input message that it receives.
This is only possible if al
chengas123 wrote:
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
2.0.4 ships geronimo-stax-api_1.0_spec-1.0.jar instead, but this doesn't
include the QName class so probably doesn't help you.
Ian
--
Ian Roberts
on CXF2.0.4, it's "geronimo-stax-api_1.0_spec-1.0.jar".
chengas123 <[EMAIL PROTECTED]> wrote:
Haha. I would have realized that was the same .jar
The only one included in 2.0.4 is stax-utils-20060502.jar
YI (William) ZHU wrote:
>
> actually, it's "stax-api-1.0.1.jar".
> (on CXF 2.0.2
Thank you for your help. I finally got WebLogic to start. I'm not sure what
exactly I did to fix it, but part of it was definitely clearing the weblogic
cache.
Thanks again,
Ben
ianroberts wrote:
>
> chengas123 wrote:
>> I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any
FYI: for 2.0.4, we specifically switched to the geronimo version as it
does NOT have the QName class in it like the stax-api version that we
used in 2.0.3 does. Thus, the problem should be reduced.
Dan
On Thursday 31 January 2008, William Zhu wrote:
> on CXF2.0.4, it's "geronimo-stax-api
I think the only option is the "-nexclude namespace" option to have it
not generate code for stuff in a specific namespace.
Dan
On Thursday 31 January 2008, Cybexion wrote:
> Hi,
>
> I would like to reuse my xsd generated classes in different projects.
> Therefore I would like to have a sta
Honestly, looking at the jaxb spec, I don't see anything that would allow
that.Thats something you may want to ask on the jaxb lists:
https://jaxb.dev.java.net/servlets/ProjectMailingListList
There might be some hidden flag or something that could be used to set
it. I don't really know.
Hi,
I am developing using the Java first approach (using jaxb data binding),
and the wsdl is auto generated by the cxf servlet at
http://localhost/SomeService?wsdl
Short of annotating each class with @XmlType(namespace="http://x.y.z";),
is there a setting which inform the servlet to use the
On Thu, 2008-01-31 at 17:01 -0500, Daniel Kulp wrote:
> Honestly, looking at the jaxb spec, I don't see anything that would allow
> that.Thats something you may want to ask on the jaxb lists:
>
> https://jaxb.dev.java.net/servlets/ProjectMailingListList
>
> There might be some hidden flag o
Well, I have to agree. The docs seem to be the last thing that a developer
thinks about - because it's so obvious right? CXF, like a lot of software,
badly needs some end to end examples at the very least.
Currently, it's very lacking, as was XFire!
Mayank Thakore-2 wrote:
>
> well, i have sp
OK. Let's flip this around a bit... Describe the type of example that
would (or would have) helped you do what you wanted to do. We can work
to get one in place.
CXF has a bunch of samples already that cover a large variety of
different configuations and samples. Knowing where they are d
Hmm... That's really not good.
Is there any chance you can get a wire trace of the test with both 2.0.3
and 2.0.4? Is it CXF on both sides of the wire? There were some
updates to the fault handling/mapping to make it honor the
elementFormDefault flags of the schemas. Thus, the fault
With 2.0.4, we added a publishedEndpointUrl attribute to jaxws:endpoint
to allow you to specify the exact address that is published in the wsdl.
That may help.
Dan
On Thursday 31 January 2008, Richard Newton wrote:
> We are currently creating a Web Service using CXF configured with
> Spring a
Rob,
Writing a new databinding is slightly tricky to get completely working
correctly. I don't think we have any good docs for it yet. The new
xmlbeans databinding (on trunk only) is probably the easiest to follow
as an example as it doesn't do anything that complex yet.
The steps to crea
Thanks for that Daniel.
Do you know if there's a consistent sequence that cxf forces the
binders and invokers to follow i.e. Reader -> Invoker -> Writer or if
there are scenarios that should cause the sequnce to change?
Cheers, Rob
On Feb 1, 2008 1:27 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
41 matches
Mail list logo
