My crash happens long before it gets anywhere near actual CXF code.
-Original Message-
From: Johnson Ma [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 12:26 AM
To: cxf-user@incubator.apache.org
Subject: Re: Eclipse STP installation process
Hi
The stp europa release
Johnson,
I hate to be a grump, and I'd prefer to help you refine this thing.
Here's my vision of the local architecture:
1) A large body of POJO code, including some classes that will
eventually travel across web service interfaces. My approach has been to
use Aegis on these classes to supply
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...
Hiya,
Now I've really fixed this in SVN and integrated in a test case. You can try
building the CXF sources yourself, or we'll get a snapshot published
sometime before tomorrow I believe. Thanks,
- Dan
On 7/22/07, Dan Diephouse [EMAIL PROTECTED] wrote:
Hi Julio,
In case you thought we've
Hi Jesse,
I don't think you'll get under two megabytes as CXF depends on JAXB. And
JAXB itself is two megabytes.
The minimal set of dependencies is around 8 jars for the dynamic client I
think. Its probably around 6 megs. There is a WHICH_JARS file in the
distribution which highlights what is
Thanks Dan, I'll test it and let u know.
On Jul 23, 2007, at 7:31 AM, Dan Diephouse wrote:
Hiya,
Now I've really fixed this in SVN and integrated in a test case.
You can try
building the CXF sources yourself, or we'll get a snapshot published
sometime before tomorrow I believe. Thanks,
-
I'm attempting to integrate CXF with an existing Spring app and I'm bean
getting instantiation errors on startup... The culprit is
org.apache.cxf.catalot.OASISCatalogManager which references
org.apache.xml.resolver.CatalogManager (which is in the jaxb-xjc-2.0.jar).
Getting a NoClassDefFound on
Yes, you can do that with Aegis or Jaxb binding. (Xfire defaults to
Aegis).
-Original Message-
From: Dave Kallstrom [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 1:58 PM
To: cxf-user@incubator.apache.org
Subject: wsdl generation ala Xfire
We are thinking about migrating from
Here is my beans.xml when I deploy my project to weblogic (9.2 - 10) I get
the exception below:
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:http=http://cxf.apache.org/transports/http/configuration;
Dan:
I just tried the snapshot (2.0.1-incubator-SNAPSHOT) and it worked
without having to do ParameterStyle.BARE. Looks like it's fixed now.
:)
Anyone know when 2.0.1 will be promoted to release?
Thanks.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
Just figured out what was going wrong. This page
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html is
incorrect.Theschema reference
http://cxf.apache.org/schema/jaxws.xsd should be
http://cxf.apache.org/schemas/jaxws.xsd. It's missing the s in schemas
FYI
On 7/23/07, Clough, Samuel
I get the exact same error using the HelloWorld example from the user
documentation. I am deploying to WL 10, and cxf, 2.1-incubator-SNAPSHOT
sameh wrote:
When I deploy my project to weblogic (9.2 or 10) or tomcat-5.5.23 I get
the exception below
beans.xml:
beans
Fixed. Thanks.
Dan
On Monday 23 July 2007 16:50, Dave Kallstrom wrote:
Just figured out what was going wrong. This page
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html is
incorrect.Theschema reference
http://cxf.apache.org/schema/jaxws.xsd should be
You need to add the xml-resolver-1.2.jar into your class path.
Willem.
Brad Harper wrote:
I'm attempting to integrate CXF with an existing Spring app and I'm bean
getting instantiation errors on startup... The culprit is
org.apache.cxf.catalot.OASISCatalogManager which references
Given the customer http rest sample, I defined a spring config with
the following endpoint:
jaxws:endpoint
id=customerServiceXML
implementor=com.esri.aws.CustomerService
address=/xml
bindingUri=http://apache.org/cxf/binding/http;
jaxws:serviceFactory
Hi Benson,
We don't support your use case in current STP, but it is on the way...
The current Pojo/java first support in stp is using cxf w2j and j2w tools,
which are based on jaxb binding.
I think CXF guys are going to provide a new java2service tool to directly
support Pojo.
That tool will
16 matches
Mail list logo