Re: When will CXF become a top level project?
Daniel Kulp gave the best possible answer for this recently: http://tinyurl.com/2su4tt Glen Am Donnerstag, den 12.07.2007, 09:39 +0700 schrieb Joshua Jackson: > Dear all, > > When will CXF become a top level project? Since for some people such > as our clients, incubator means that the product is not ready for > production yet. > > Thanks in advance >
Re: Generated client to connect to a https ws
Please take the hello_world_https in the samples directory as a example.
Here is the sample configuration files for you case:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:sec="http://cxf.apache.org/configuration/security";
xmlns:http="http://cxf.apache.org/transports/http/configuration";
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
name="{http://www.google.com/api/adsense/v2}AccountService.http-conduit";>
Cheers,
Willem.
Pirola Davide wrote:
Hi,
i'm new on cxf.
I want to generate a client in order to connect to AdSense api of
google:
http://code.google.com/apis/adsense/developer/adsense_api_services.html
I'm using wsdl2java, and I run it to point to a wsdl like this one:
https://www.google.com/api/adsense/v2/AccountService?wsdl
it generate all needed classes. So it's seems pretty cool :D
But... when I try to connect to the google server I receive this error:
11-lug-2007 14.40.45 org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
eSenderInterceptor.java:48)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC
hain.java:206)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:204)
at
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134)
at $Proxy28.createAdSenseAccount(Unknown Source)
at
com.google.api.adsense.v2.AccountServiceClient2.main(AccountServiceClien
t2.java:54)
Caused by: java.io.IOException: Illegal Protocol https for HTTP
URLConnection Factory.
at
org.apache.cxf.transport.http.HttpURLConnectionFactoryImpl.createConnect
ion(HttpURLConnectionFactoryImpl.java:44)
at
org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:468)
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
eSenderInterceptor.java:46)
... 7 more
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Could
not send Message.
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:168)
at $Proxy28.createAdSenseAccount(Unknown Source)
at
com.google.api.adsense.v2.AccountServiceClient2.main(AccountServiceClien
t2.java:54)
Caused by: org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
eSenderInterceptor.java:48)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC
hain.java:206)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:204)
at
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134)
... 2 more
Caused by: java.io.IOException: Illegal Protocol https for HTTP
URLConnection Factory.
at
org.apache.cxf.transport.http.HttpURLConnectionFactoryImpl.createConnect
ion(HttpURLConnectionFactoryImpl.java:44)
at
org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:468)
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
eSenderInterceptor.java:46)
... 7 more
Seems that the generated client is not able to connect via https.
Someone have any idea about this problem?
What I miss??
Thanks
Davide
When will CXF become a top level project?
Dear all, When will CXF become a top level project? Since for some people such as our clients, incubator means that the product is not ready for production yet. Thanks in advance -- It's not just about coding, it's a matter of fulfilling you core being YM!: thejavafreak Blog: http://joshuajava.wordpress.com/
Re: Getting the HTTP server off the bus
Hi Benson,
All the Jetty related stuff of CXF are in the
cxf-rt-transports-http-jetty module.
You can get the serverEngine which wraps the Jetty instance from the
JettyHttpTransportFactory.
You can use the below codes to get the serverEngine.
Bus bus = BusFactory.getDefaultBus();
DestinationFactoryManager dfm =
bus.getExtension(DestinationFactoryManager.class);
JettyHttpTransportFactory df = (JettyHttpTransportFactory)
dfm.getDestinationFactory("http://cxf.apache.org/transports/http/configuration";);
ServerEngine engine= df.getEngine();
The you just need to extends JettyHTTPHandler to deal with the static
content directory, and add it into the engine by call addServant(URL
url, JettyHTTPHandler handler).
You can find the detail information about the ServerEngine and
JettyHTTPHandler from this directory
https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty
Enjoy hacking the code !
Willem.
Benson Margulies wrote:
Could someone reveal how to ask the default bus for the running Jetty
instance? I want to add a static content directory for it to handle.
Re: Maven java2wsdl plugin error with jaxws
You also need the simple frontend and soap bindings James. hi, i've been having some trouble getting the java2wsdl plugin to generate the wsdl from a java annotated service class, the error i'm getting is: Error : Can not find the ServiceBulider for style: Jaxws Here's the config in my pom: org.apache.cxf cxf-codegen-plugin 2.0-incubator-SNAPSHOT org.apache.cxf cxf-rt-frontend-jaxws 2.0-incubator-RC-SNAPSHOT generate-wsdl process-classes sandbox.web.service.SandboxService java2wsdl I've been following the instructions on the wiki and found a post on this mailing list which recommended to add the dependency to the plugin configuration - this fixed their problem howvere i'm still seeing the same error after applying this. What's interesting is that in the console output which i've attatched there is an info message saying the state of the classpath before the tool is launched - this contains all of the jar files defined in the project dependencies, however after this there is another info message with the classpath during Java2wsdl which only contains the target classes directory of the project and doesn't even include the dependency explicitly added to the plugin configuration. Am i missing something glaringly obvious?
Getting the HTTP server off the bus
Could someone reveal how to ask the default bus for the running Jetty instance? I want to add a static content directory for it to handle.
Re: XSD path incorrect
Please check it[1] out http://cwiki.apache.org/CXF20DOC/schemas-and-namespaces.html Krishnan, Ramanathan wrote: Hi, Both of the following links don't exist. Does anyone know where its moved to? http://cxf.apache.org/schema/jaxws.xsd http://cxf.apache.org/schemas/jaxws.xsd Regards, Krishnan
XSD path incorrect
> Hi, > Both of the following links don't exist. Does anyone know where > its moved to? > > http://cxf.apache.org/schema/jaxws.xsd > > http://cxf.apache.org/schemas/jaxws.xsd > > Regards, > Krishnan
Re: validation error; missing schema
Len Josephs wrote: Hello! I'm trying to use Spring with a JAX-WS style service endpoint with the 2.0 release version of CXF (binary). I'm a newbie so I'm trying to work through this tutorial from the user guide on the wiki: http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html Of course I'm seeing the same parse exceptions Christian (and others) have reported - the public URLs for the schema location are not available. This causes runtime issues when Spring starts resolving dependencies. In particular http://cxf.apache.org/schema/jaxws.xsd doesn't seem to be available. Hi Len, You should use http://cxf.apache.org/schemas/jaxws.xsd instead. And you are right, the inavailability of the schemas at http://cxf.apache.org has to do with the incubation status, but - at least as far as Spring's validating parser is concerned - that does not matter as the schemas are on the classpath. See http://cwiki.apache.org/CXF20DOC/schemas-and-namespaces.html Cheers, Andrea. The http://cxf.apache.org/schema schemas currently doesn't resolve; reading JIRA (cxf-673) and the mailing lists suggest that this problem has to do with this being the desired URL for the schemas but that cxf.apache.org is not yet available due to the incubator status of the project Christian seems to have gotten past this by adding a dependency in his Maven build files (I think)... My question: what is the easiest and/or best way to work around this issue? Do I need to build from source? Do I need a newer snapshot? Do I need to modify all my *.xsd files? Thanks for helping, Len IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: validation error; missing schema
Hello! I'm trying to use Spring with a JAX-WS style service endpoint with the 2.0 release version of CXF (binary). I'm a newbie so I'm trying to work through this tutorial from the user guide on the wiki: http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html Of course I'm seeing the same parse exceptions Christian (and others) have reported - the public URLs for the schema location are not available. This causes runtime issues when Spring starts resolving dependencies. In particular http://cxf.apache.org/schema/jaxws.xsd doesn't seem to be available. The http://cxf.apache.org/schema schemas currently doesn't resolve; reading JIRA (cxf-673) and the mailing lists suggest that this problem has to do with this being the desired URL for the schemas but that cxf.apache.org is not yet available due to the incubator status of the project Christian seems to have gotten past this by adding a dependency in his Maven build files (I think)... My question: what is the easiest and/or best way to work around this issue? Do I need to build from source? Do I need a newer snapshot? Do I need to modify all my *.xsd files? Thanks for helping, Len
Re: Maven java2wsdl plugin error with jaxws
Cool, thanks.
C:\Documents and Settings\joncam\My
Documents\Workspace\slice\sandbox\sandbox-web>mvn process-classes
[INFO] Scanning for projects...
[INFO]
[INFO] Building Sandbox-Web
[INFO]task-segment: [process-classes]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [cxf-codegen:java2wsdl {execution: generate-wsdl}]
11-Jul-2007 14:55:03
org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor process
INFO: Classpath before Java2Wsdl: C:\Documents and Settings\joncam\My
Documents\Workspace\slice\sandbox\sandbox-web\target\classes;C:\Docume
nts and
Settings\joncam\.m2\repository\javax\xml\ws\jaxws-api\2.0\jaxws-api-2.0.jar;C:\Documents
and Settings\joncam\.m2\repository\aopallia
nce\aopalliance\1.0\aopalliance-1.0.jar;C:\Documents and
Settings\joncam\.m2\repository\org\codehaus\woodstox\wstx-asl\3.2.1\wstx-asl-3.2.1.
jar;C:\Documents and
Settings\joncam\.m2\repository\log4j\log4j\1.2.12\log4j-1.2.12.jar;C:\Documents
and Settings\joncam\.m2\repository\org\
apache\cxf\cxf-common-utilities\2.0-incubator-RC-SNAPSHOT\cxf-common-utilities-2.0-incubator-RC-SNAPSHOT.jar;C:\Documents
and Settings\jonca
m\.m2\repository\org\apache\cxf\cxf-rt-bindings-xml\2.0-incubator-RC-SNAPSHOT\cxf-rt-bindings-xml-2.0-incubator-RC-SNAPSHOT.jar;C:\Documents
and
Settings\joncam\.m2\repository\org\apache\cxf\cxf-api\2.0-incubator-RC-SNAPSHOT\cxf-api-2.0-incubator-RC-SNAPSHOT.jar;C:\Documents
and
Settings\joncam\.m2\repository\org\apache\geronimo\specs\geronimo-annotation_1.0_spec\1.0\geronimo-annotation_1.0_spec-1.0.jar;C:\Documents
and
Settings\joncam\.m2\repository\org\apache\cxf\cxf-rt-bindings-soap\2.0-incubator-RC-SNAPSHOT\cxf-rt-bindings-soap-2.0-incubator-RC-SNAPS
HOT.jar;C:\Documents and
Settings\joncam\.m2\repository\org\mortbay\jetty\jetty\6.1.2rc0\jetty-6.1.2rc0.jar;C:\Documents
and Settings\joncam
\.m2\repository\stax\stax-api\1.0.1\stax-api-1.0.1.jar;C:\Documents
and Settings\joncam\.m2\repository\com\sun\xml\bind\jaxb-xjc\2.0\jaxb-xj
c-2.0.jar;C:\Documents and
Settings\joncam\.m2\repository\org\apache\geronimo\specs\geronimo-javamail_1.4_spec\1.0-M1\geronimo-javamail_1.4_
spec-1.0-M1.jar;C:\Documents and
Settings\joncam\.m2\repository\org\apache\cxf\cxf-rt-core\2.0-incubator-RC-SNAPSHOT\cxf-rt-core-2.0-incubat
or-RC-SNAPSHOT.jar;C:\Documents and
Settings\joncam\.m2\repository\org\mortbay\jetty\jetty-sslengine\6.1.2rc0\jetty-sslengine-6.1.2rc0.jar;C
:\Documents and
Settings\joncam\.m2\repository\javax\xml\bind\jaxb-api\2.0\jaxb-api-2.0.jar;C:\Documents
and Settings\joncam\.m2\repository\
org\apache\cxf\cxf-rt-frontend-simple\2.0-incubator-RC-SNAPSHOT\cxf-rt-frontend-simple-2.0-incubator-RC-SNAPSHOT.jar;C:\Documents
and Settin
gs\joncam\.m2\repository\org\apache\ws\commons\schema\XmlSchema\1.2\XmlSchema-1.2.jar;C:\Documents
and Settings\joncam\.m2\repository\sandbo
x\sandbox-core\0.0.1\sandbox-core-0.0.1.jar;C:\Documents and
Settings\joncam\.m2\repository\xml-resolver\xml-resolver\1.2\xml-resolver-1.2.j
ar;C:\Documents and
Settings\joncam\.m2\repository\org\springframework\spring-beans\2.0.4\spring-beans-2.0.4.jar;C:\Documents
and Settings\j
oncam\.m2\repository\org\mortbay\jetty\jetty-util\6.1.2rc0\jetty-util-6.1.2rc0.jar;C:\Documents
and Settings\joncam\.m2\repository\org\apach
e\cxf\cxf-rt-transports-http\2.0-incubator-RC-SNAPSHOT\cxf-rt-transports-http-2.0-incubator-RC-SNAPSHOT.jar;C:\Documents
and Settings\joncam
\.m2\repository\org\apache\geronimo\specs\geronimo-servlet_2.5_spec\1.1-M1\geronimo-servlet_2.5_spec-1.1-M1.jar;C:\Documents
and Settings\jo
ncam\.m2\repository\org\apache\cxf\cxf-rt-databinding-jaxb\2.0-incubator-RC-SNAPSHOT\cxf-rt-databinding-jaxb-2.0-incubator-RC-SNAPSHOT.jar;C
:\Documents and
Settings\joncam\.m2\repository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar;C:\Documents
and Settings\joncam\
.m2\repository\com\sun\xml\bind\jaxb-impl\2.0.5\jaxb-impl-2.0.5.jar;C:\Documents
and Settings\joncam\.m2\repository\javax\servlet\servlet-ap
i\2.3\servlet-api-2.3.jar;C:\Documents and
Settings\joncam\.m2\repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;C:\Documents
and Sett
ings\joncam\.m2\repository\org\apache\geronimo\specs\geronimo-ws-metadata_2.0_spec\1.1-M1\geronimo-ws-metadata_2.0_spec-1.1-M1.jar;C:\Docume
nts and
Settings\joncam\.m2\repository\org\mortbay\jetty\servlet-api-2.5\6.1.2rc0\servlet-api-2.5-6.1.2rc0.jar;C:\Documents
and Settings\jon
cam\.m2\repository\org\apache\geronimo\specs\geronimo-activation_1.1_spec\1.0-M1\geronimo-activation_1.1_spec-1.0-M1.jar;C:\Documents
and Se
ttings\joncam\.m2\repository\org\apache\cxf\cxf-rt-frontend-jaxws\2.0-incubator-RC-SNAPSHOT\cxf-rt-frontend-jaxws-2.0-incubator-RC-SNAPSHOT.
jar;C:\Documents and
Settings\joncam\.m2\repository\org\springfram
Re: Maven java2wsdl plugin error with jaxws
Hi Cam, I think your attachment got stripped. Can you paste it in a reply? Thanks, - Dan On 7/11/07, Cameron Jones <[EMAIL PROTECTED]> wrote: console output attatched... Thanks, Cam On 7/11/07, Cameron Jones <[EMAIL PROTECTED]> wrote: > hi, > > i've been having some trouble getting the java2wsdl plugin to generate > the wsdl from a java annotated service class, the error i'm getting > is: > > Error : Can not find the ServiceBulider for style: Jaxws > > Here's the config in my pom: > > > org.apache.cxf > cxf-codegen-plugin > 2.0-incubator-SNAPSHOT > > > org.apache.cxf > cxf-rt-frontend-jaxws > 2.0-incubator-RC-SNAPSHOT > > > > > generate-wsdl > process-classes > > > sandbox.web.service.SandboxService > > > java2wsdl > > > > > > I've been following the instructions on the wiki and found a post on > this mailing list which recommended to add the dependency to the > plugin configuration - this fixed their problem howvere i'm still > seeing the same error after applying this. > > What's interesting is that in the console output which i've attatched > there is an info message saying the state of the classpath before the > tool is launched - this contains all of the jar files defined in the > project dependencies, however after this there is another info message > with the classpath during Java2wsdl which only contains the target > classes directory of the project and doesn't even include the > dependency explicitly added to the plugin configuration. > > Am i missing something glaringly obvious? > -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: wsdl2java jaxb: vendor-independent?
The wsdl2java classes should work on any JAX-WS implementation. Re: JAXB, there is only one implementation of JAXB, so I wouldn't worry too much there :-) - Dan On 7/11/07, Guy Pardon <[EMAIL PROTECTED]> wrote: Hi, To what extent are the generated wsdl2java classes (with jaxb) provider-independent? Thanks, Guy -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
wsdl2java jaxb: vendor-independent?
Hi, To what extent are the generated wsdl2java classes (with jaxb) provider-independent? Thanks, Guy
Re: maven build problems
You need to run an install at least once first... mvn -Pfastinstall mvn -Psetup.eclipse should do it. Dan On Wednesday 11 July 2007 10:14, Nikolajs Krasnikovs wrote: > Hello, > I am trying to download and build CXF using the instructions provided > on site. > The problem is, I am getting error when launching > > mvn -Psetup.eclipse > > The build reports an error as it "Failed to resolve artifact." > The artifact missing is > > org.apache.cxf:cxf-buildtools:jar:2.1-incubator-SNAPSHOT > > I am using maven 2.0.7 > > Any help would be appreciated. > Regards > Nick -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
maven build problems
Hello, I am trying to download and build CXF using the instructions provided on site. The problem is, I am getting error when launching mvn -Psetup.eclipse The build reports an error as it "Failed to resolve artifact." The artifact missing is org.apache.cxf:cxf-buildtools:jar:2.1-incubator-SNAPSHOT I am using maven 2.0.7 Any help would be appreciated. Regards Nick
Re: Maven java2wsdl plugin error with jaxws
console output attatched... Thanks, Cam On 7/11/07, Cameron Jones <[EMAIL PROTECTED]> wrote: hi, i've been having some trouble getting the java2wsdl plugin to generate the wsdl from a java annotated service class, the error i'm getting is: Error : Can not find the ServiceBulider for style: Jaxws Here's the config in my pom: org.apache.cxf cxf-codegen-plugin 2.0-incubator-SNAPSHOT org.apache.cxf cxf-rt-frontend-jaxws 2.0-incubator-RC-SNAPSHOT generate-wsdl process-classes sandbox.web.service.SandboxService java2wsdl I've been following the instructions on the wiki and found a post on this mailing list which recommended to add the dependency to the plugin configuration - this fixed their problem howvere i'm still seeing the same error after applying this. What's interesting is that in the console output which i've attatched there is an info message saying the state of the classpath before the tool is launched - this contains all of the jar files defined in the project dependencies, however after this there is another info message with the classpath during Java2wsdl which only contains the target classes directory of the project and doesn't even include the dependency explicitly added to the plugin configuration. Am i missing something glaringly obvious?
Re: unable to return null
Kevin, That schema would allow the returned list to contain null's, not that the list could be null. Unfortunately, I'm not really thinking of any way that would work short of creating a "wrapper" type to hold the list. . Probably not what you want though. Dan On Tuesday 10 July 2007 17:26, kevin Wong wrote: > Hi, > I am developing a WSDL first web service. There is a method, getNames > which return a List. I would like to return null, but failed > to do so. What I got on the client side was an empty list. Is nillable > = "true" in XMLSchema work for a list ?? Please take a look at > nillable="true" type="s:string" maxOccurs="unbounded" minOccurs="0">. > Thanks. > > > > http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime=" > http://schemas.xmlsoap.org/wsdl/mime/"; > xmlns:tns="http://avid.com/xena"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:http=" > http://schemas.xmlsoap.org/wsdl/http/"; > targetNamespace="http://my.com/FIG"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> > > > > http://my.com/FIG";> > > > > > > > > maxOccurs="1" minOccurs="0"> > > > > > > > > > > > > > > nillable="true" type="s:string" maxOccurs="unbounded" minOccurs="0"> > > > > > > > > > > > > > > > > > > > > > > > > > >wsdl:part> > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; /> > > > > http://my.com/FIG/getNames"; > style="document" /> > > > > > > > > > > > > > > > > > > > > > > > > http://localhost:8080/fig/FIG"; /> > > > > > > -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Maven java2wsdl plugin error with jaxws
hi, i've been having some trouble getting the java2wsdl plugin to generate the wsdl from a java annotated service class, the error i'm getting is: Error : Can not find the ServiceBulider for style: Jaxws Here's the config in my pom: org.apache.cxf cxf-codegen-plugin 2.0-incubator-SNAPSHOT org.apache.cxf cxf-rt-frontend-jaxws 2.0-incubator-RC-SNAPSHOT generate-wsdl process-classes sandbox.web.service.SandboxService java2wsdl I've been following the instructions on the wiki and found a post on this mailing list which recommended to add the dependency to the plugin configuration - this fixed their problem howvere i'm still seeing the same error after applying this. What's interesting is that in the console output which i've attatched there is an info message saying the state of the classpath before the tool is launched - this contains all of the jar files defined in the project dependencies, however after this there is another info message with the classpath during Java2wsdl which only contains the target classes directory of the project and doesn't even include the dependency explicitly added to the plugin configuration. Am i missing something glaringly obvious?
Re: CXF and JDK 1.6 compatibility
Hi Daniel On 7/10/2007 4:46 PM,User Daniel Kulp wrote: Krystian, Those emails about Java6 issues were back when we were targetting JAX-WS 2.1 and JAXB 2.1. Since then, we backed down to JAX-WS 2.0 and JAXB 2.0 so most of the problems aren't problems right now. That said, now that we have shipped a JAX-WS 2.0 compliant version, we plan to restart the 2.1 work very shortly and the problems will pop up again. Thanks for the explanation, I was a little bit confused why is it working. -- Best Regards, Krystian Lider
Re: Endpoints: JAX-WS vs. WCF
Is there a Contract on Semantics, on Cost, on Quality?
In a world of mashups and MOSS, I think it is likely that decisions
such as "make vs. buy" and "local vs. remote" will be inserted between
the Endpoint and the competing Services.
It was unfair of me to compare JAX-WS with WCF. JAX-WS has no
pretension of being a component architecture.
-- Dan Connelly
Ted Neward wrote:
That's not *exactly* correct, Dan; a WCF endpoint is created with a
Contract, which can be specified using a variety of things, including a C#
(or VB or C++/CLI or ...) interface with the appropriate custom attributes
describing the contract, or it can also be done directly on a class using
same said attributes. Most of the time when we demo WCF ("we" being "myself
and the folks I teach with at Pluralsight"), we show the attributes on
interfaces because that is the model that was most widely discussed and
promoted for .NET Remoting and ASMX, not because it's the model that makes
the most sense.
I'm not suggesting that Microsoft *didn’t* get it right here... I'm just
wondering if it's really all that important to be able to slide a different
implementation behind an interface, when the actual point of coupling is not
the language interface, but the XML messages being sent back and forth.
Anyway, just my $.02 worth. I, for one, am not all that upset at the idea of
a single concrete class being tied to an endpoint, because I'm not convinced
that the value of the interface-implementation idiom is that critical in a
distributed system where the contract isn't given by the interface itself.
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
-Original Message-
From: Dan Connelly [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2007 11:40 AM
To: cxf-user@incubator.apache.org
Subject: Endpoints: JAX-WS vs. WCF
A JAX-WS Endpoint must be created using a service implementation.
A (Microsoft) WCF Endpoint, on the other hand, is created with an SEI
(C# interface), not an implementation.This allows multiple impls of
the same service interface to be reached through the WCF Endpoint. The
Dispatcher, which is configured separately, has rules for invoking the
desired implementation.
It seems to me that Microsoft got it right.Does anyone want to
comment on that?
Why is there no DispatchingInvoker class in CXF as a convenience when
the user needs a Dispatcher?Is there a sample showing the coding for
a dispatching Invoker?
-- Dan Connelly
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.2/891 - Release Date: 7/8/2007
6:32 PM
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.2/893 - Release Date: 7/9/2007
5:22 PM
Re: wsdl2java: velocity engin write errors (NPE)
Done: https://issues.apache.org/jira/browse/CXF-777 2007/7/11, Freeman Fang <[EMAIL PROTECTED]>: Hi Christian, Maybe you need create a jira issue and append your attachment on jira website. You attachment is filtered again in this email. :-) Best Regards Freeman Christian Vest Hansen wrote: > It *is* in the same directory and I *did* attach the schema... I dunno > why it didn't get through to the list. Anyway, here it is again. > The WebStat schema references another schema which I'm also attaching > in the hopes that it wont get plundered by foul thieves along its > voyage to your inbox. > > > > 2007/7/11, James Mao <[EMAIL PROTECTED]>: >> Hi, >> >> Wsdl2java do support schema import and wsdl import, do you have the >> >> WebStat1.0.xsd in the same directory as the wsdl file. >> >> Please also attach the schema, so we can reproduce >> >> Thanks >> James >> >> >> Christian Vest Hansen wrote: >> > Hi, >> > >> > Busy day, I guess... When I run the wsdl2java tool on the attached >> > WSDL and schemas, I get an exception about "velocity engin write >> > errors" whos cause appear to be an NPE. >> > >> > I'm wondering that the schemas might be too complex, or the tool can't >> > handle the importing. >> > >> > Can you guys shed some light on what's going on, and tell me if >> > there's a way to get past this? I tried the tool on a much simple wsdl >> > and it worked out alright. >> > >> > Here's the output from wsdl2java: >> > >> > Loading FrontEnd jaxws ... >> > Loading DataBinding jaxb ... >> > wsdl2java -verbose -client -server -impl -d >> > /Users/vest/workspace/Statistics2/src/main/java >> > /Users/vest/workspace/Statistics2/src/main/resources/WebStat1.0.wsdl >> > wsdl2java - 2.0-incubator-SNAPSHOT >> > >> > >> > WSDLToJava Error : velocity engin write errors >> > >> > org.apache.cxf.tools.common.ToolException: velocity engin write errors >> > at >> > >> org.apache.cxf.tools.common.VelocityGenerator.doWrite(VelocityGenerator.java:103) >> >> > >> > at >> > >> org.apache.cxf.tools.wsdlto.core.AbstractGenerator.doWrite(AbstractGenerator.java:49) >> >> > >> > at >> > >> org.apache.cxf.tools.wsdlto.frontend.jaxws.generators.ClientGenerator.generate(ClientGenerator.java:118) >> >> > >> > at >> > >> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:185) >> >> > >> > at >> > >> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:215) >> >> > >> > at >> > >> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:84) >> >> > >> > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102) >> > at >> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171) >> > Caused by: org.apache.velocity.exception.MethodInvocationException: >> > Invocation of method 'getDefaultTypeValue' in class >> > org.apache.cxf.tools.common.model.JavaParameter threw exception class >> > java.lang.NullPointerException : null >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) >> >> > at >> > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) >> >> > at >> > >> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:89) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) >> >> > at >> > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) >> > at >> > >> org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) >> >> > >> > at >> > >> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) >> >> > >> > at org.apache.velocity.Template.merge(Template.java:256) >> > at >> > >> org.apache.cxf.tools.common.VelocityGenerator.doWrite(VelocityGenerator.java:99) >> >> > >> > ... 7 more >> > >> > >> > >> >> > >> > >> > http://schemas.xmlsoap.org/wsdl/"; >> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; >> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; >> xmlns:xs="http://www.w3.org/2001/XMLSchema"; >> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; >> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; >> xmlns:unw="http://ws.unwire.dk/webstat/v1";
Re: wsdl2java: velocity engin write errors (NPE)
Hi Christian, Maybe you need create a jira issue and append your attachment on jira website. You attachment is filtered again in this email. :-) Best Regards Freeman Christian Vest Hansen wrote: It *is* in the same directory and I *did* attach the schema... I dunno why it didn't get through to the list. Anyway, here it is again. The WebStat schema references another schema which I'm also attaching in the hopes that it wont get plundered by foul thieves along its voyage to your inbox. 2007/7/11, James Mao <[EMAIL PROTECTED]>: Hi, Wsdl2java do support schema import and wsdl import, do you have the WebStat1.0.xsd in the same directory as the wsdl file. Please also attach the schema, so we can reproduce Thanks James Christian Vest Hansen wrote: > Hi, > > Busy day, I guess... When I run the wsdl2java tool on the attached > WSDL and schemas, I get an exception about "velocity engin write > errors" whos cause appear to be an NPE. > > I'm wondering that the schemas might be too complex, or the tool can't > handle the importing. > > Can you guys shed some light on what's going on, and tell me if > there's a way to get past this? I tried the tool on a much simple wsdl > and it worked out alright. > > Here's the output from wsdl2java: > > Loading FrontEnd jaxws ... > Loading DataBinding jaxb ... > wsdl2java -verbose -client -server -impl -d > /Users/vest/workspace/Statistics2/src/main/java > /Users/vest/workspace/Statistics2/src/main/resources/WebStat1.0.wsdl > wsdl2java - 2.0-incubator-SNAPSHOT > > > WSDLToJava Error : velocity engin write errors > > org.apache.cxf.tools.common.ToolException: velocity engin write errors > at > org.apache.cxf.tools.common.VelocityGenerator.doWrite(VelocityGenerator.java:103) > > at > org.apache.cxf.tools.wsdlto.core.AbstractGenerator.doWrite(AbstractGenerator.java:49) > > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.generators.ClientGenerator.generate(ClientGenerator.java:118) > > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:185) > > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:215) > > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:84) > > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102) > at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171) > Caused by: org.apache.velocity.exception.MethodInvocationException: > Invocation of method 'getDefaultTypeValue' in class > org.apache.cxf.tools.common.model.JavaParameter threw exception class > java.lang.NullPointerException : null > at > org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193) > > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) > > at > org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220) > > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) > > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) > > at > org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:89) > > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) > > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) > > at org.apache.velocity.Template.merge(Template.java:256) > at > org.apache.cxf.tools.common.VelocityGenerator.doWrite(VelocityGenerator.java:99) > > ... 7 more > > > > > > http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:unw="http://ws.unwire.dk/webstat/v1"; xmlns:ns="http://unwire.dk/statistics"; targetNamespace="http://ws.unwire.dk/webstat/v1";> > http://ws.unwire.dk/webstat/v1"; location="WebStat1.0.xsd"/> > > targetNamespace="http://ws.unwire.dk/webstat/v1"; elementFormDefault="qualified"/> > > > > > > > type="ReportConfigurationList"/> > > > > > > type="ReportConfiguration"/> >
