Hi,
I just dug the code, here is the code in the JaxWsServiceConfiguration
to tell which method is the WebMethod.
@Override
public Boolean isOperation(Method method) {
Method origMethod = method;
method = getDeclaredMethod(method);
if
How do I configure in my applicationContext.xml to use Aegis?
Is there anywhere an example?
Regards
Marc
Original-Nachricht
Datum: Thu, 12 Jul 2007 13:35:58 -0600
Von: Dan Diephouse [EMAIL PROTECTED]
An: cxf-user@incubator.apache.org
Betreff: Re:
JAXB can't handle
Hm, I have the Jetty Module (cxf-rt-transports-http-jetty) in my classpath and
it doesn't work.
How can I set up the CXF Servlet in a JUnit Test? I want to set up a web
service in a before test method, test my service and shut the web service
down.
Marc
Original-Nachricht
Hi Marc,
For setup the CXF servlet in a junit test, you can get more details from
trunk/systests/src/test/java/org/apache/cxf/systest/servlet/SpringServletTest.java
and it's superclass
trunk/systests/src/test/java/org/apache/cxf/systest/servlet/AbstractServletTest.java
Best Regards
Freeman
Hi Freeman,
thank you for your response. I want to do something like this with xfire:
@BeforeTest
public void beforeTest(){
serverFactory = new
org.springframework.context.support.ClassPathXmlApplicationContext(
classpath: + SERVER_CONTEXT);
Hello,
I need to develop a CORBA-SOAP bridge that will integrate into JBoss
and dynamically translate CORBA calls to SOAP/HTTP calls and vice
versa. I am investigating if I can implement this with Apache CXF and
Yoko. My basic idea is simple:
JACORB/VISIBROKER - YOKO BINDING - CXF - SOAP/HTTP
Hi Dan Willem,
Thanks for your support!
The problem I have is in this peace of code (AbstractHTTPTransportFactory):
/**
* This static call creates a connection factory based on
* the existence of the SSL (TLS) client side configuration.
*/
static HttpURLConnectionFactory
Hi Marc,
I believe you can do it similar in CXF.
For client side, you can do it like
ClassPathXmlApplicationContext context
= new ClassPathXmlApplicationContext(new String[]
{demo/spring/client/client-beans.xml});
HelloWorld client =
Hi James,
That's all good, shouldn't have a problem doing a build. To fix
problems with cyclic dependencies i think you can use exclusions in
the pom dependencies to stop maven from drilling into them. This is
something i'd really like to see throughout cxf to reduce the inherent
dependencies
Hi Marc,
Your cxf-version is 2.0-incubator-SNAPSHOT, it's a bit out of date,
please use 2.1-incubator-SNAPSHOT,
Cheers
Freeman
Marc Baumgartner wrote:
Hi Freeman,
I am working with maven and I can't find a repository with 2.1 libs. My pom
contains these libs:
dependency
Hi Marc,
If you don't want to use webapp/web.xml, you can start a standlone cxf
server with spring context instead of deploying cxf service into servlet
container.
Cheers
Freeman
Marc Baumgartner wrote:
Hi Freeman,
I understand your solution, but is it possible to do it without using the
We came up with our own attempt at wsdl2js that generates clients that
can be run in browsers, and were hoping to retire it.
-Original Message-
From: Jeff Zhang [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 12, 2007 10:13 PM
To: cxf-user@incubator.apache.org
Subject: Re: javascript
Hi,
Could you try the trunk version of CXF,
I test the below configuration in the trunk,
configuredConduit.getTlsClientParameters() is not null and it just is a size of
zero list.
http:conduit
name={http://www.google.com/api/adsense/v2}AccountServiceService.http-conduit;
Just answer the annotations question,
CXF has two front-end, one is simple-front-end which do not consume the
WebService related annotation , the other is Jaxws-front-end which looks
up the annotation.
You can specify to use different front-end in you pom.xml :)
Cheers,
Willem
Marc
Hi Marc,
You can do it like
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
Hi Freeman,
I understand your solution, but is it possible to do it without using the
webapp folder / web.xml?
I would like to define the hole behaviour of the server in the test itself
without a reference other files.
Regards,
Marc
Original-Nachricht
Datum: Fri, 13 Jul
Hi all,
I was reading the feature list and I can't find MessageBinding.
Does cxf support MessageBinding?
http://xfire.codehaus.org/Message+Binding
Thanks.
Regards,
Zdenek
Hi,
I have exposed a web service using cxf using the systex below, and it works
fine
jaxws:endpoint id=testService implementor=com.test.testServiceImpl
address= /MyTestService /jaxws:endpoint
What I then did was to actully make the service do something (access a
database through
Bizarre... If you had a moment, I improved that line of code post 2.0 and
included some better error reporting. Any chance you'd be willing to try out
a snapshot quick and let us know if it works correctly?
http://incubator.apache.org/cxf/download.html
Otherwise I'll take a stab at figuring out
Hi,
I am using Spring (2.0) and I tried XFire and cxf.
With xFire I could get wsdl using an url like:
http://localhost:8080/ecm_syn/services/EchoService?wsdl
I could not find in documentation how to do the same behaviour with cxf.
another question is it a good approach to generate wsdl like
Hi,
It work using like:
http://localhost:8080/ecm_syn/services/EchoService?wsdl
But I still have the question :
Is it a good approach to generate wsdl using an url or using tool java2wsdl is
better ?
Thanks for your advice
Willy
- Message d'origine
De : [EMAIL PROTECTED]
Willem,
In 2.0, there is no JettyHttpTransportFactory.
There is a JettyHTTPTransportFactory.
But it has no getEngine().
?
-Original Message-
From: Willem Jiang [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 11, 2007 10:35 PM
To: cxf-user@incubator.apache.org
Subject: Re: Getting
I am an XFire user planning to evaluate CXF for my project. What is the
maven dependency for CXF to be used? While using XFire, I had the following
dependencies.
dependency
groupIdorg.codehaus.xfire/groupId
artifactIdxfire-jaxb2/artifactId
version1.2.5/version
I believe this is what you want:
bean id=foo class=com.test.testServiceImpl
property name=testDAO ref bean=TestDAO /
/bean
jaxws:endpoint id=testService implementor=#foo
address= /MyTestService
Hope that helps :-)
- Dan
On 7/13/07, Marc Preddie [EMAIL PROTECTED] wrote:
Hi,
I have exposed
How do I configure the RESTful HTTP-binding with Spring, as opposed to
the SOAP binding given in the documentation?
Thanks,
Brad
I went ahead and created a JIRA issue for this:
https://issues.apache.org/jira/browse/CXF-789
- Dan
On 7/13/07, Liu, Jervis [EMAIL PROTECTED] wrote:
Hi, I actually believe this is a bug in CXF. What happened in CXF is that
we first reflect impl class, all methods defined in impl class become
This should definitely make its way in the docs, but here is an example from
the mailing list earlier:
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
Hmmm that does seem to be something that isn't ported yet. I'll try to hack
something up though - it should be simple enough that you could even drop it
into your project with 2.0. Need to catch a plane in a bit, but maybe I'll
have something to report back with after that :-)
- Dan
On 7/13/07,
Yeah, our JS stuff only runs in Rhino.
I started in on a pure browser solution once, but it fell by the wayside. I
would love to see someone actually do such a thing. The CXF code be used as
a basis for a generator I would think. We'd definitely welcome contributions
in this area ;-)
Cheers,
-
If you take away the serviceFactory.setServiceclass() line I think it'll fix
your problem. Effectively you're telling CXF not to look at the @WebService
annotation on the NameIndexServiceImpl, which I don't think is what you want
to do :-). CXF will automatically introspect the service bean and
Thanks for the response. After implementing the code below and working
out the associated dependencies, I get the following error, which I find
one reference to on Google, but no answers -- Help! The stack trace is
below:
ERROR [main] (ContextLoader.java:203) - Context initialization failed
Out of curiosity, if I wanted the primary source of annotations to be
the interface, then the cure would be to put endpointInterface on the
interface?
-Original Message-
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: Friday, July 13, 2007 5:46 PM
To: cxf-user@incubator.apache.org
I'm appealing to anyone out there who can please help me with this
problem. All I'm trying to do is standard configuration of a single
service, with a single method, using Http binding, using Spring. If I
cannot get this problem resolved soon, as much as I do not want to, I'm
going to have to
Willem,
The recipe in 2.0 looks like:
Bus bus = BusFactory.getDefaultBus();
DestinationFactoryManager dfm =
bus.getExtension(DestinationFactoryManager.class);
JettyHTTPTransportFactory df = (JettyHTTPTransportFactory)
Hi Benson,
It's my fault that I missed something about getting the destination from the
transport factory.
It is JettyHTTPTransportFactory and not JettyHttpTransportFactory
The code should be
Bus bus = BusFactory.getDefaultBus();
DestinationFactoryManager dfm =
I'm pretty sure that per the JAX-WS spec, the serviceName goes on the impl
class regardless. So I think you still need @WebService on the impl and on
the interface. Does that answer your question?
- Dan
On 7/13/07, Benson Margulies [EMAIL PROTECTED] wrote:
Out of curiosity, if I wanted the
36 matches
Mail list logo