Hi guys,
I´m trying configure an endpoint to use JMS queues with CXF. The use case is
a client that sends a message to an activemq queue. I have a few questions
about this:
1. Should I using CXF over JMS?
I´m not sure if i should using CXF over HTTP, and for example Camel for
routing the
Hi Juanjo,
Use the name attribute instead:
jms:destination name={
http://services.com/}DummyJMSServiceImplPort.jms-destination;
/jms:destination
Cheers,
Andrea.
but then i get this error:
org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '{
Hi,
You can use CXF over JMS, we support JMS transport in CXF.
There are some JMS spring configuration updates in CXF 2.0, you need to
change
jms:destination id={
http://services.com/}DummyJMSServiceImplPort.jms-destination;
to
jms:destination name={
Basically You need to run mvn install first to down load and build the
project first and then run mvn eclipse:eclispse to setup the eclipse
workspace.
mvn -Pfastinstall
Means you run 'mvn install' and skip the check style , pmd checking and
testing.
Then you run
mvn -Psetup.eclipse
It will
Good pointer...had to introduce to the classpath the compiled file
package-info.java with the following content
@javax.xml.bind.annotation.XmlSchema(
namespace = http://customer.acme.com;,
elementFormDefault = javax.xml.bind.annotation.XmlNsForm.QUALIFIED
) package com.acme.customer;
Hi Fred,
I was involved in Header support stuff so I am looking into CXF--790.
One alternative I am trying to see if it can be fixed in general with
some kind of marking for application specific headers and CXF headers
and filtering them while copying into JAX-WS responseContext or
Hello
I developed a simple CXF Web Service which is deployed as a WAR-File on a
JBoss Java EE Application Server (Spring Configuration).
The Service works fine. But if i try to call another WebService from this
WebService, i get the following error (see stack trace bellow):
No conduit
Hi Matthias,
Ensure that cxf-rt-transports-http-2.1-incubator-SNAPSHOT.jar and
cxf-rt-transports-http-jetty-2.1-incubator-SNAPSHOT.jar is on your
servlet container classpath.
Best Regards
Freeman
[EMAIL PROTECTED] wrote:
Hello
I developed a simple CXF Web Service which is deployed as a
Hi,
Thanks for your response. I'm using the Release 2.0 of Apache CXF. I can't
find the mentioned jar files.
I don't think that a jar file is missing because i can call the other
WebService with a standalone client which has the same jar files in the
classpath as the web application.
Thank you guys, it looks that this configuration works:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
Thanks, Ulhas.
I'll work to implement some system tests, then, in CXF, which will
exercise the WSS4J interceptor in such a way that it reproduces the
bug. I'll add the tests as a patch to the ticket, so that when we
fix the issue, the tests will pass.
-Fred
On Jul 24, 2007, at 6:51 AM,
Hi there,
Has anyone seen the following error with wsdl2service? Am trying to
generate a JMS service but it's not working... I get the same kind of
error (Tools Error: Can not found wsdl plugin...) when I try and run
the wsdl2xml tool...
Hi Christian,
I think this could be down to the fact that you haven't declared a
target namespace or a default namespace, avoiding this will probably
cause problems with the HelloWorldPort input message. Try sticking
something like this into the definitions element:
wsdl:definitions
That made no difference. :(
2007/7/24, Murphy, Martin [EMAIL PROTECTED]:
Hi Christian,
I think this could be down to the fact that you haven't declared a
target namespace or a default namespace, avoiding this will probably
cause problems with the HelloWorldPort input message. Try sticking
I have enabled aegis bindings using the following xml configuration snippet.
jaxws:endpoint id=CollectiveServices implementor=#serviceBean
bindingUri=http://apache.org/cxf/binding/http;
address=/cxf/CollectiveServices
jaxws:serviceFactory
bean class=
I just tried this with trunk and it seems OK.
Passed Validation : Valid WSDL
I'll start getting a new snapshot deployed. (takes an hour or so)
Dan
On Tuesday 24 July 2007 11:14, Christian Vest Hansen wrote:
Hi,
Using the (currently) latest snapshot, namely
Joshua,
What are you trying to achieve?
The instructions at:
http://incubator.apache.org/cxf/setting-up-eclipse.html
are for CXF developers that want to get the CXF trunk up in eclipse for
developing CXF itself. It has nothing to do with the Eclipse STP
plugins and getting STP to work.
Marty,
We're still fixing bugs.. :-)
Seriously, we're hoping to do the 2.0.1 release builds either this coming
Friday or Monday.
Dan
On Monday 23 July 2007 16:16, Marty Saxton wrote:
Dan:
I just tried the snapshot (2.0.1-incubator-SNAPSHOT) and it worked
without having to do
Hi,
Can you attach the whole stacktrace?
My first impression is that you don't have the cxf-jms jar in your
classpath, can you confirm that
Also, let me know which version of cxf you are using
Regards,
James
Hi there,
Has anyone seen the following error with wsdl2service? Am trying to
Hi David
It looks like some xml parser work issue, can you list your
environments, such as JDK version, the hello_world's class path etc.
I guess there may have some inflictions of JAXB between the CXF used
and the NSE used.
Hope this can help you out :)
Willem.
David Du wrote:
Hi,
20 matches
Mail list logo
