Hi Dan,
I did some clean up of the simple front-end spring parser,
Can you review my last commit (svn commit: r557161)?
Thanks,
Willem.
Dan Diephouse wrote:
With the simple frontend its called a serviceBean:
Cheers,
- Dan
On 7/17/07, Jacob Marcus <[EMAIL PROTECTED]> wrote:
Hi Willem,
Hi Benson,
Would you please append your java class?
From the exception, it seems your class method are bare mode so that
java2wsdl load jaxb to process your method parameter type class, but
unfortunately, this type class has two properties with same name, which
is illegal for jaxb.
As you said
java2wsdl/wsdl2java ant tasks was in the trunk, i checked in days ago,
but you have to build by your own, it's in /trunk/tools/anttask
Let me know if you have any problems with it.
James
I know that ant tasks are pending. Until then, I tried to roll my own.
And I crashed with a complaint that
Here is another way to add the LocalTransport by adding these in your
spring.xml instead of including META-INF/cxf/cxf-extension-local.xml
lazy-init="false">
http://cxf.apache.org/transports/local
http://schemas.xmlsoap.org/soap/http
http:
The cxf.xml is contained in the cxf-rt-core-*.jar, if you use the
bundler jar, it should be in the cxf-2.*-incubator-*.jar.
Benson Margulies wrote:
I know that ant tasks are pending. Until then, I tried to roll my own.
And I crashed with a complaint that cxf.xml was not found in classpath.
What
Hi Chris, to use local transport, you need to manually register
LocalTransportFactory with all the namespaces that might be used, for example,
"http://schemas.xmlsoap.org/soap/http";. An example of how this is done can be
found from
\trunk\rt\frontend\jaxws/src/test/java/org/apache/cxf/jaxws/Ab
You may need to add the
-META-INF/cxf/cxf-extension-local.xml
And I just searched the codes with
"http://schemas.xmlsoap.org/soap/http";, there are some hard code of it
in the SoapBindingConfiguration.
You have to register do some register of local transport factory with
"http://schemas.xmlso
Hi Samuel,
javax.xml.ws.soap.SOAPBinding is class from jax-ws api, so you need make your
service jaxws compatible
add jaxws BindingType annotation into your TestServiceImpl
@BindingType (value = SoapBinding.SOAP11HTTP_MTOM_BINDING)
And use JaxWsServerFactoryBean instead of ServerFactoryBean to c
Additionally, in CXF you can access the Exchange object (which is the XFire
MessageContext equivalent) by adding it to your web service's parameter:
public String echo(String s, Exchange e) { ... }
Cheers,
- Dan
On 7/17/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
Hi Jacob,
I'm not sur
Is there something special I have to do to run java2wsdl for an aegis
environment? As it is, I get a very mysterious rejection letter until I
ask for -verbose, and then I get the following...
org.apache.cxf.bus.spring.BusApplicationContext getConfigResources
[java] INFO: Could not find the co
I know that ant tasks are pending. Until then, I tried to roll my own.
And I crashed with a complaint that cxf.xml was not found in classpath.
What jar file is supposed to contain it for this purpose?
Java2wsdl (the shell script) does not react well to being run from a
cygwin shell. It ends up with the wrong path separators.
If this isn't in the queue, I'll post a JIRA with a patch.
Hi Marty, as you said, you've examined the message flowing between client and
client and it is correct, in this case, must be sth wrong with your client. You
may want to send us your client code, so that we can take a quick look to see
what happened there.
Thanks,
Jervis
-Original Message-
Hi Christopher -
If you are using maven you need to add this dependency:
org.apache.cxf
cxf-rt-transports-http-jetty
${cxf.version}
If your not using maven just add that jar to your application classpath.
On Jul 17, 2007, at 12:04 PM, Christopher Moesel wrote:
Hello
Am Dienstag, den 17.07.2007, 12:07 -0400 schrieb James Royalty:
> Hi,
>
> I'm starting a project using CXF and having a couple of newbie issues.
> Hoping someone can shed some light on these.
>
> First, I'm doing Java-first development, using WS and JAXB annotations.
> I'm publishing into a s
Hi Dan,
I've created the JIRA:
http://issues.apache.org/jira/browse/CXF-803
Thanks,
Zarar
Dan Diephouse wrote:
>
> Hi Zarar,
> It'd be great if you could file a feature request in JIRA for this though:
>
> http://issues.apache.org/jira/browse/CXF
>
> Thanks,
> - Dan
>
> On 7/17/07, Andre
At some risk of redundancy:
Step 1: set up Aegis+JAX-WS environment with some exceptions on the
service interface (and of course implementation).
Step 2: observe that WSDL seems plausible.
Step 3: run unit test. The throw is
org.apache.cxf.binding.soap.SoapFault, not any of mine.
Step 4: In a s
Dan,
Reading the code of 2.0, I see no evidence of any client-side code
capable of taking a soap fault and turning it into a custom exception
class. The two interceptors I see (the 1.1 and 1.2 versions) both end up
throwing the CXF-specific SoapFault class.
What am I missing?
--benson
> -O
With the simple frontend its called a serviceBean:
Cheers,
- Dan
On 7/17/07, Jacob Marcus <[EMAIL PROTECTED]> wrote:
Hi Willem,
I believe I am using version CXF incubator 2.0. The simple.xsd does not
support implementor as an attribute. It does support implementor as an
element. But it ne
Hi Tristan,
Thanks for posting that sample. We sorely need more docs/examples in this
area. I'll try to beef it up, but if you'd like to help out it'd be most
welcome. You can edit the documentation by clicking the edit link at the
top. We can also include samples if you'd like to contribute any.
Hi Zarar,
It'd be great if you could file a feature request in JIRA for this though:
http://issues.apache.org/jira/browse/CXF
Thanks,
- Dan
On 7/17/07, Andrea Smyth <[EMAIL PROTECTED]> wrote:
Hi Zarar,
As part of its JAXWS implementation CXF supports the
@javax.jws.HandlerChain annotation fo
Thanks I fixed this.
Which discussion are you referring to? If you are using the JAX-WS frontend,
you do need to use @WebFault. If you're using the simple frontend, things
*should* work without the @WebFault annotation.
Regards,
- Dan
On 7/17/07, Benson Margulies <[EMAIL PROTECTED]> wrote:
ht
Hi Benson,
More tests are always welcome! Just send along a patch. Cheers,
- Dan
On 7/17/07, Benson Margulies <[EMAIL PROTECTED]> wrote:
I note that the source tree contains some careful set up of exceptions
to allow for some testing of exceptions, but no exceptions are tested.
Does this refle
I am using CXF as both the client and server, and I'm just trying to get
the following simple service working:
@WebService
public interface HelloWorld {
String sayHi(String text);
}
The implementation just returns "Hello " + text. I examined the XML
flowing between the client & server an
I thoroughly appreciate this concern. I'm working on fixing it for the next
release, but internally we followed the wsdl2 http model, which kind of
constrains us in this respect. Sorry I have nothing better to offer than
that right now!
- Dan
On 7/16/07, Jason Mihalick <[EMAIL PROTECTED]> wrote:
Dan,
You are 100% correct. This solved the problem! Thanks!
Brad
Dan Diephouse wrote:
Hi Brad,
The JaxWsServiceFactoryBean is not resusable across various services. Try
embedding it inside your service definition:
...
Let me know if that helps!
- Dan
On 7/16/07, Brad O'Hearne <[EMAI
Hi Deno,
That is correct - you can just use the single spring jar.
- Dan
On 7/16/07, Deno Vichas <[EMAIL PROTECTED]> wrote:
(somebody correctly me if I'm wrong here) you can just all the main
spring jar and not all the smaller individuals ones. Sure, your project
will be slightly bigger but l
Ok, I'm trying to add this to a service hosted by the ServerFactoryBean
(the way specified in the Xfire migration guide) .
If I do the following to get to the binding to turn on MTOM:
ServerFactoryBean sf = new ServerFactoryBean();
sf.getServiceFactory().setDataBinding(new AegisDatabindi
Hello All,
I'm trying to write some JUnit tests that can test my SOAP web services
using the local transport
(http://cwiki.apache.org/CXF20DOC/local-transport.html).
Normally I run my services using the CXF Servlet, so doing it
servlet-less is somewhat new to me. Here is what I'm doing:
Using a
Hi Brad,
The JaxWsServiceFactoryBean is not resusable across various services. Try
embedding it inside your service definition:
...
Let me know if that helps!
- Dan
On 7/16/07, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
Hello,
I am having problems running more than one RESTful service,
Everything looks dandy, so I'm a bit confused as to what could be happening
here. Regarding your classpath - if you copy the contents of the .classpath
file inside your eclipse project and copy it into the email, that should
helps us figure out a little bit more... Then hopefully my next message
I am not importing the cxf bean definitions in my spring configuration.
Here is my cxf.xml file.
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:simple="http://cxf.apache.org/simple";
xsi:schemaLocation="
http://www.sprin
OK-- I've edited the wiki page to indicate that any users wishing to try
retrotranslator should read this thread first (with a link to it on
nabble).
-Chris
-Original Message-
From: Roelofsen, Roman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 12:37 PM
To: cxf-user@incubator.ap
On Tuesday 17 July 2007 06:55, Benson Margulies wrote:
> I'm about to borrow AbstractCXFTest and a subclass or two to set up
> test of my own service. It occurs to me that you all could package a
> jar file with the contents of org.apache.cxf.test and the generally
> useful pieces of AbstractAegisT
Can you show me what your web.xml and whole cxf.xml look like? How are you
importing the CXF bean definitions?
Thanks,
- Dan
On 7/16/07, Jacob Marcus <[EMAIL PROTECTED]> wrote:
Thanks Dan. That worked.
from the cxf.xml I would like to refer to a bean defined else where like,
http://localhost
I tried.
Retrotranslater maps thinks like
- Annotation API
- StringBuilder -> StringBuffer
But NOT
- java.util.Properties.loadFromXML
- and hundreds of other methods
- and hundreds of new classes
I got it working by using Apache Harmony to override/add the missing classes
etc. In addition, t
On Tuesday 17 July 2007 08:49, Roelofsen, Roman wrote:
> With retrotranslator you only solve language problems like
>
> - generics
> - annotations
> - etc
>
> But CXF also uses new classes introduced in Java5, existing classes
> got new methods, etc. So the bigger problem is running CXF with a
> Ja
I have looked at that doc. I was trying to see if there was a simple
setting like what Xfire had that would activate it on byte[] property.
We're doing Java first dev since all the services here are in house and
nothing uses Annotations right now for the services, so I was trying to
do it without
My fix is committed.
You would need to rebuild the common/common stuff. The aegis binding
was OK, it's just the XMLDepthStreamReader thing from common-utilities
that it used was a problem.
Dan
On Tuesday 17 July 2007 11:52, Clough, Samuel (USPC.PRG.Atlanta) wrote:
> Wow, thanks for that
Hi,
I'm starting a project using CXF and having a couple of newbie issues.
Hoping someone can shed some light on these.
First, I'm doing Java-first development, using WS and JAXB annotations.
I'm publishing into a servlet container (Tomcat). My service publishes
fine, but I'm interested i
Hi Samuel,
Have you looked at the MTOM documentation in the user guide?
http://cwiki.apache.org/CXF20DOC/mtom.html
If so, then what information is missing (or incorrect) that you need?
-Chris
-Original Message-
From: Clough, Samuel (USPC.PRG.Atlanta)
[mailto:[EMAIL PROTECTED]
Sent: Tue
Wow, thanks for that. Should I go ahead and build my own patched Aegis,
or should I wait for you to finish your testing to make sure this is all
we need? What project owns the Aegis code now?
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 11
Samuel,
I managed to track this down. It's a bug in the DepthXMLStreamReader
that isn't getting the "END_ELEMENT" events lined up correctly in the
Aegis binding.Thus, while reading the first object, it's sucking in
all the rest of the data so it doesn't deserialize the second parameter.
Hi Jacob,
I'm not sure how to do this without annotations. With annotations, you
would do this the JAX-WS approved way, by adding this to your service
implementation class:
@Resource private WebServiceContext context;
Then you could use the WebServiceContext object to get the message
detai
In XFire, there was a very convenient way to get a handle to the
MessageContext in the web service implementations. This could be achieved by
adding a MessageContext paramater to the method signature.
Is there a similar strategy possible in CXF? Or is there a recomended
approach? I am a potential
Hi Willem,
I believe I am using version CXF incubator 2.0. The simple.xsd does not
support implementor as an attribute. It does support implementor as an
element. But it needs child elements.
Should I be using a different version (snapshot) of CXF?
Thanks,
Jacob
On 7/17/07, Jiang, Ning (Wille
I think the spring syntext should be
Because I checked the trunk code, it only deals with the attribute implementor
now.
Willem.
-Original Message-
From: Jacob Marcus [mailto:[EMAIL PROTECTED]
Sent: Tue 7/17/2007 22:55
To: cxf-user@incubator.apache.org
Subject: Re: How can cxf.
Hi Zarar,
As part of its JAXWS implementation CXF supports the
@javax.jws.HandlerChain annotation for JAX-WS handlers.
There are no custom annotations in CXF that allow to specify
inbound/outbound fault/message interceptors (i.e. CXF handlers) ..
Regards,
Andrea.
Zarar Siddiqi wrote:
Is th
I am using the Simple front end approach without annotations.
I think the problem is in the SpringBus. The CXFServlet does not seem to
have access to the ApplicationContext I have loaded using the
ContextLoaderLister in the web.xml
Is there some additional configuration required?
Thanks,
Ja
Is there support for configuring interceptors using annotations? I'm looking
for something like the org.codehaus.xfire.annotations.InHandlers and
org.codehaus.xfire.annotations.OutHandlers class where were present in
XFire.
I'm thinking of writing similar annotations and want to make sure that th
We're trying to convert some services off of XFire and onto CXF. On
XFire, the following would automatically enable MTOM for any types in a
service that returned a byte array:
Service service = serviceFactory.create(FeedbackFilesService.class);
service.setInvoker(new BeanInvoker(new FeedbackFile
I think you could try to use the endpoint's attribute implementor.
It should be workable with the # convention.
Here is an example for it
Willem
-Original Message-
From: Jacob Marcus [mailto:[EMAIL PROTECTED]
Sent: Tue 7/17/2007 21:59
To: cxf-user@incubator.apache.org
Subject: How can
IMHO, yes.
> -Original Message-
> From: Christopher Moesel [mailto:[EMAIL PROTECTED]
> Sent: 17 July 2007 14:11
> To: cxf-user@incubator.apache.org
> Subject: RE: Java 1.4
>
>
> Thanks for the extra info, Roman. I was going based on a
> snippet in the
> XFire Migration Guide on the WI
Hi all,
I am an xfire user who is used to the xfire services.xml. I am now porting
the services.xml to cxf.xml and have it working for a simple 'Hello World'
case.
I have a requirement to refer to beans defined else where in the cxf.xml.
XFire used to let me do this using the # convention.
Exam
I note that the source tree contains some careful set up of exceptions
to allow for some testing of exceptions, but no exceptions are tested.
Does this reflect some state of the implementation, or just that no one
has had time to fill in more test cases? I'd volunteer to make tests
that try the exc
http://cwiki.apache.org/CXF20DOC/developing-a-service.html
This page states that @WebFault goes on methods. However, it looks to me
as if @WebFault only goes on exception classes. The page could also use
an example.
XFire had a whole discussion about faults, which doesn't seem to have
perco
Thanks! that worked. When you are updating the wiki, you may want to check
the sample xml file also.
On 7/16/07, Willem Jiang <[EMAIL PROTECTED]> wrote:
Here is a litter trick for the endpoint address setting with using
servlet transport. I will update wiki for it.
Because of CXFServlet can't
I added some comments and cleaned out some grit.
> -Original Message-
> From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 17, 2007 9:38 AM
> To: cxf-user@incubator.apache.org
> Subject: RE: Getting the HTTP server off the bus
>
> Done.
>
> Here is the URL
>
http:
Done.
Here is the URL
http://cwiki.apache.org/confluence/display/CXF20DOC/Standalone+HTTP+Transport
-Original Message-
From: Clough, Samuel (USPC.PRG.Atlanta) [mailto:[EMAIL PROTECTED]
Sent: Tue 7/17/2007 20:39
To: cxf-user@incubator.apache.org
Subject: RE: Getting the HTTP server off th
Hi Lukas,
You just need set the endpoint address with different port,
Here are the example, if you publish service with jaxws api:
Object implementor = new GreeterImpl();
String address1 = "http://localhost:9000/SoapContext/GreeterPort";;
Endpoint.publish(address, implemen
Thanks for the extra info, Roman. I was going based on a snippet in the
XFire Migration Guide on the WIKI:
"The only other reason not to migrate to CXF that we see is a
requirement for Java 1.4. Although, we would encourage users to take a
look at using CXF on Java 1.4 via Retrotranslator."
Shou
With retrotranslator you only solve language problems like
- generics
- annotations
- etc
But CXF also uses new classes introduced in Java5, existing classes got new
methods, etc. So the bigger problem is running CXF with a Java4 library. You
could use a project like Apache Harmony to fill thi
Every time I send this with a code zip attached it is bounced as spam,
so I'll try to send you the code zip offline.
This is a java first case. What we are doing is hooking up applications
that are completely internal, so the wsdl is not so much of a concern
per se for this application because th
Lukas,
You may be able to use CXF with the help of Retrotranslator. This is an
open source project that translates 1.5 byte code to 1.4-compatible byte
code. More info here:
http://retrotranslator.sourceforge.net/
-Chris
-Original Message-
From: Willem Jiang [mailto:[EMAIL PROTECTED]
I think it would be helpful on a wiki...
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 8:55 PM
To: cxf-user@incubator.apache.org
Subject: RE: Getting the HTTP server off the bus
Well, you can ignore the first paragraph. The rest of my an
I find that my exception classes are collapsing into SoapFault. What am
I missing?
java.lang.Exception: Unexpected exception,
expected but
was
at
org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRun
ner.java:91)
at
org.junit.internal.runners.BeforeAndAfterRunner
If you're creating multiple services off the embedded http server, just
pass the port in the url. If it's different it will automatically
listen off of that port for that endpoint.
-Original Message-
From: Lukas Zapletal [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 6:45 AM
To:
I'm about to borrow AbstractCXFTest and a subclass or two to set up test
of my own service. It occurs to me that you all could package a jar file
with the contents of org.apache.cxf.test and the generally useful pieces
of AbstractAegisTest. Spring does something like this with the 'mock'
jar, no?
Hello,
can I change the port of the standalone http server? I would like to
run two servers on one machine. Thanks
--
Lukas Zapletal
http://lukas.zapletalovi.com
By the way will the invoker work when I will call the WS over Apache
Yoko CORBA Binding? I mean will the request be already translated from
CORBA types to WS/Java types?
2007/7/17, Lukas Zapletal <[EMAIL PROTECTED]>:
Thanks. And how do I create a DummyService? I mean a service that has
no method
70 matches
Mail list logo