Re: axis2-wsdl2code-maven-plugin use

2009-07-13 Thread Håkon Sagehaug
Hi

Not sure this is exact what you are asking about but here is how I use the
plugin,  I have a separate class stored in src/main/java that extends the
skeleton created by wsdl2code tool and implements the service. Then change
the ServiceClass parameter in service xml file to refer to the new class
that implements the service.

 parameter name=ServiceClassnew.package.ServiceImpl/parameter

Then it's also easy to use the maven aar plugin for packaging the hole
thing.

cheers, Håkon

2009/7/11 Larry Meadors larry.mead...@gmail.com

 That wouldn't solve the issue - the problem is that I have to edit one
 of the files that it creates, but it creates it in a temporary
 location (everything under target is wiped when you run mvn clean),
 and if I have a second copy, then the compile blows chunks. :-(

 I will stick with my ant trick - it works adequately, and if the
 interface changes because of a change to the WSDL file, the compile
 will fail, and I'll have a copy of the generated file that I can merge
 with my implemented file.

 For any others with the same problem, here's the code from my pom.xml:

 build
...
plugins
...
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idmove-skeleton/id
phaseprocess-sources/phase
goalsgoalrun/goal/goals
configuration
tasks
echoMove the
 generated skeleton/echo
move
 file=${basedir}/target/generated-sources/.../BlahSkeleton.java

  
 tofile=${basedir}/target/generated-sources/.../BlahSkeleton.java.generated/
/tasks
/configuration
/execution
/executions
/plugin
/plugins
 /build

 Running ant tasks from maven feels a bit like cheating, but it does the
 trick.

 Larry




-- 
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)


axis2-wsdl2code-maven-plugin use

2009-07-10 Thread Larry Meadors
How does this plug-in fit in a normal development work flow?

I'm using it to create a service from a wsdl file that is provided by
a vendor, and I think I have it creating the sources correctly, but
the default behavior is to generate the classes into the target
directory (specifically target/generated-sources/axis2/wsdl2code/src).

One of the generated classes is the skeleton for the service, so if I
change it and run maven clean package to build a new war file...it
gets deleted. :-)

If I copy that class to my src/main/java directory, then I get a
[INFO] Compilation failure message because I have a duplicate class.

I think for now, I'll just use the ant tasks to delete the generated
version. That seems a bit wonky...but it'll do it.

Can someone who is using this help me figure out a way to fit it into
my work flow?

Larry


RE: axis2-wsdl2code-maven-plugin use

2009-07-10 Thread Martin Gainty

assume you're referring to
http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-wsdl2code-plugin.html

where the default of Target directory, where sources are being
target/generated-sources/axis2/wsdl2code generated.

what if you redirect the parameter outputDirectory to point to classes folder?
-DoutputDirectory=/classes
?
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 Date: Fri, 10 Jul 2009 17:11:11 -0600
 Subject: axis2-wsdl2code-maven-plugin use
 From: larry.mead...@gmail.com
 To: axis-user@ws.apache.org
 
 How does this plug-in fit in a normal development work flow?
 
 I'm using it to create a service from a wsdl file that is provided by
 a vendor, and I think I have it creating the sources correctly, but
 the default behavior is to generate the classes into the target
 directory (specifically target/generated-sources/axis2/wsdl2code/src).
 
 One of the generated classes is the skeleton for the service, so if I
 change it and run maven clean package to build a new war file...it
 gets deleted. :-)
 
 If I copy that class to my src/main/java directory, then I get a
 [INFO] Compilation failure message because I have a duplicate class.
 
 I think for now, I'll just use the ant tasks to delete the generated
 version. That seems a bit wonky...but it'll do it.
 
 Can someone who is using this help me figure out a way to fit it into
 my work flow?
 
 Larry

_
Lauren found her dream laptop. Find the PC that’s right for you.
http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290

Re: axis2-wsdl2code-maven-plugin use

2009-07-10 Thread Larry Meadors
That wouldn't solve the issue - the problem is that I have to edit one
of the files that it creates, but it creates it in a temporary
location (everything under target is wiped when you run mvn clean),
and if I have a second copy, then the compile blows chunks. :-(

I will stick with my ant trick - it works adequately, and if the
interface changes because of a change to the WSDL file, the compile
will fail, and I'll have a copy of the generated file that I can merge
with my implemented file.

For any others with the same problem, here's the code from my pom.xml:

build
...
plugins
...
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idmove-skeleton/id
phaseprocess-sources/phase
goalsgoalrun/goal/goals
configuration
tasks
echoMove the 
generated skeleton/echo
move 
file=${basedir}/target/generated-sources/.../BlahSkeleton.java
  
tofile=${basedir}/target/generated-sources/.../BlahSkeleton.java.generated/
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build

Running ant tasks from maven feels a bit like cheating, but it does the trick.

Larry