Re: Maven java2wsdl plugin error with jaxws

2007-07-13 Thread Cameron Jones

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 from the other sources. i'm considering writing a plugin
that will do this or log this kind of info somewhere as i think it'd
be a really useful in general for maven projects.

Thanks,
Cam

On 7/13/07, James Mao [EMAIL PROTECTED] wrote:

Looks like maven does not load the jaxws/simpl/soap jars from the
classpath,  you can turn on the flag to print the classpath maven used
to load the jars.

Another easiest way to load the jars, is build your own code-gen plugin
by yourself, just add  the dependencies(jaxws/simple/soap) in the
code-gen plugin pom

We will add those dependencies in cxf later, but at moment there is a
cycle dependencies.

If you're using the binary version of cxf, and don't know how to build
the code-gen plugin, give me a shout, i will build one for you.

James.

 I tried explicitly adding those dependencies to the plugin, however
 still getting the error:

 12-Jul-2007 10:00:57
 org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor process
 INFO: Classpath during Java2Wsdl: C:\Documents and Settings\joncam\My
 Documents\Workspace\slice\sandbox\sandbox-web\target\classes
 JavaToWSDL Error : Can not find or initialize the ServiceBuilder for
 style: Jaxws Reason:
 org.apache.cxf.jaxws.JaxwsServiceBuilder

 I think the problem is that it isn't building the classpath - it's
 even being logged as info what the classpath was before the task is
 executed and what it is for the task. The only classes included in the
 task itself are my own project classes - no project dependencies or
 plugin dependencies seem to be loaded.

 I'm expecting that something has gone awry since no-one else seems to
 have the problem, but i just don't know enough about the software to
 know what it could be. I tried upgrading to the 2.1 version of the
 cxf-codegen-plugin but that hasn't fixed the problem.

 Here's the current state of the pom:

plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version2.1-incubator-SNAPSHOT/version
dependencies
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-frontend-jaxws/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-frontend-simple/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-bindings-soap/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
/dependencies
executions
execution
idgenerate-wsdl/id
phaseprocess-classes/phase
configuration

 classNamesandbox.web.service.SandboxService/className
/configuration
goals
goaljava2wsdl/goal
/goals
/execution
/executions
/plugin


 Thanks,
 Cam

 On 7/12/07, James Mao [EMAIL PROTECTED] wrote:
 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:
 
 plugin
 groupIdorg.apache.cxf/groupId
 artifactIdcxf-codegen-plugin/artifactId
 version2.0-incubator-SNAPSHOT/version
 dependencies
 dependency
 groupIdorg.apache.cxf/groupId
 artifactIdcxf-rt-frontend-jaxws/artifactId
 version2.0-incubator-RC-SNAPSHOT/version
 /dependency
 /dependencies
 executions
 execution
 idgenerate-wsdl/id
 phaseprocess-classes/phase
 configuration
 
  classNamesandbox.web.service.SandboxService/className
 /configuration
 goals
 goaljava2wsdl/goal
 /goals
 /execution
 /executions
 /plugin
 
  I've been following the 

Re: Maven java2wsdl plugin error with jaxws

2007-07-12 Thread Cameron Jones

I tried explicitly adding those dependencies to the plugin, however
still getting the error:

12-Jul-2007 10:00:57
org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor process
INFO: Classpath during Java2Wsdl: C:\Documents and Settings\joncam\My
Documents\Workspace\slice\sandbox\sandbox-web\target\classes
JavaToWSDL Error : Can not find or initialize the ServiceBuilder for
style: Jaxws Reason:
org.apache.cxf.jaxws.JaxwsServiceBuilder

I think the problem is that it isn't building the classpath - it's
even being logged as info what the classpath was before the task is
executed and what it is for the task. The only classes included in the
task itself are my own project classes - no project dependencies or
plugin dependencies seem to be loaded.

I'm expecting that something has gone awry since no-one else seems to
have the problem, but i just don't know enough about the software to
know what it could be. I tried upgrading to the 2.1 version of the
cxf-codegen-plugin but that hasn't fixed the problem.

Here's the current state of the pom:

   plugin
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-codegen-plugin/artifactId
   version2.1-incubator-SNAPSHOT/version
   dependencies
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-jaxws/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-simple/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-bindings-soap/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   /dependencies
   executions
   execution
   idgenerate-wsdl/id
   phaseprocess-classes/phase
   configuration

classNamesandbox.web.service.SandboxService/className
   /configuration
   goals
   goaljava2wsdl/goal
   /goals
   /execution
   /executions
   /plugin


Thanks,
Cam

On 7/12/07, James Mao [EMAIL PROTECTED] wrote:

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:

plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version2.0-incubator-SNAPSHOT/version
dependencies
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-frontend-jaxws/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
/dependencies
executions
execution
idgenerate-wsdl/id
phaseprocess-classes/phase
configuration

 classNamesandbox.web.service.SandboxService/className
/configuration
goals
goaljava2wsdl/goal
/goals
/execution
/executions
/plugin

 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: Maven java2wsdl plugin error with jaxws

2007-07-12 Thread James Mao
Looks like maven does not load the jaxws/simpl/soap jars from the 
classpath,  you can turn on the flag to print the classpath maven used 
to load the jars.


Another easiest way to load the jars, is build your own code-gen plugin 
by yourself, just add  the dependencies(jaxws/simple/soap) in the 
code-gen plugin pom


We will add those dependencies in cxf later, but at moment there is a 
cycle dependencies.


If you're using the binary version of cxf, and don't know how to build 
the code-gen plugin, give me a shout, i will build one for you.


James.


I tried explicitly adding those dependencies to the plugin, however
still getting the error:

12-Jul-2007 10:00:57
org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor process
INFO: Classpath during Java2Wsdl: C:\Documents and Settings\joncam\My
Documents\Workspace\slice\sandbox\sandbox-web\target\classes
JavaToWSDL Error : Can not find or initialize the ServiceBuilder for
style: Jaxws Reason:
org.apache.cxf.jaxws.JaxwsServiceBuilder

I think the problem is that it isn't building the classpath - it's
even being logged as info what the classpath was before the task is
executed and what it is for the task. The only classes included in the
task itself are my own project classes - no project dependencies or
plugin dependencies seem to be loaded.

I'm expecting that something has gone awry since no-one else seems to
have the problem, but i just don't know enough about the software to
know what it could be. I tried upgrading to the 2.1 version of the
cxf-codegen-plugin but that hasn't fixed the problem.

Here's the current state of the pom:

   plugin
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-codegen-plugin/artifactId
   version2.1-incubator-SNAPSHOT/version
   dependencies
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-jaxws/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-simple/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-bindings-soap/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   /dependencies
   executions
   execution
   idgenerate-wsdl/id
   phaseprocess-classes/phase
   configuration

classNamesandbox.web.service.SandboxService/className
   /configuration
   goals
   goaljava2wsdl/goal
   /goals
   /execution
   /executions
   /plugin


Thanks,
Cam

On 7/12/07, James Mao [EMAIL PROTECTED] wrote:

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:

plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version2.0-incubator-SNAPSHOT/version
dependencies
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-frontend-jaxws/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
/dependencies
executions
execution
idgenerate-wsdl/id
phaseprocess-classes/phase
configuration

 classNamesandbox.web.service.SandboxService/className
/configuration
goals
goaljava2wsdl/goal
/goals
/execution
/executions
/plugin

 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 

Maven java2wsdl plugin error with jaxws

2007-07-11 Thread Cameron Jones

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:

   plugin
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-codegen-plugin/artifactId
   version2.0-incubator-SNAPSHOT/version
   dependencies
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-jaxws/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   /dependencies
   executions
   execution
   idgenerate-wsdl/id
   phaseprocess-classes/phase
   configuration

classNamesandbox.web.service.SandboxService/className
   /configuration
   goals
   goaljava2wsdl/goal
   /goals
   /execution
   /executions
   /plugin

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: Maven java2wsdl plugin error with jaxws

2007-07-11 Thread Cameron Jones

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:

plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version2.0-incubator-SNAPSHOT/version
dependencies
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-frontend-jaxws/artifactId
version2.0-incubator-RC-SNAPSHOT/version
/dependency
/dependencies
executions
execution
idgenerate-wsdl/id
phaseprocess-classes/phase
configuration

classNamesandbox.web.service.SandboxService/className
/configuration
goals
goaljava2wsdl/goal
/goals
/execution
/executions
/plugin

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: Maven java2wsdl plugin error with jaxws

2007-07-11 Thread Dan Diephouse

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:

 plugin
 groupIdorg.apache.cxf/groupId
 artifactIdcxf-codegen-plugin/artifactId
 version2.0-incubator-SNAPSHOT/version
 dependencies
 dependency
 groupIdorg.apache.cxf/groupId
 artifactIdcxf-rt-frontend-jaxws/artifactId
 version2.0-incubator-RC-SNAPSHOT/version
 /dependency
 /dependencies
 executions
 execution
 idgenerate-wsdl/id
 phaseprocess-classes/phase
 configuration

 classNamesandbox.web.service.SandboxService/className
 /configuration
 goals
 goaljava2wsdl/goal
 /goals
 /execution
 /executions
 /plugin

 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: Maven java2wsdl plugin error with jaxws

2007-07-11 Thread James Mao

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:

   plugin
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-codegen-plugin/artifactId
   version2.0-incubator-SNAPSHOT/version
   dependencies
   dependency
   groupIdorg.apache.cxf/groupId
   artifactIdcxf-rt-frontend-jaxws/artifactId
   version2.0-incubator-RC-SNAPSHOT/version
   /dependency
   /dependencies
   executions
   execution
   idgenerate-wsdl/id
   phaseprocess-classes/phase
   configuration

classNamesandbox.web.service.SandboxService/className
   /configuration
   goals
   goaljava2wsdl/goal
   /goals
   /execution
   /executions
   /plugin

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?