You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Ajith Ranabahu <aj...@gmail.com> on 2006/04/18 17:42:40 UTC
[Axis2] Dependancy problem with XMLBeans module
oops - forgot the prefix!
---------- Forwarded message ----------
From: Ajith Ranabahu <aj...@gmail.com>
Date: Apr 18, 2006 6:47 PM
Subject: Dependancy problem with XMLBeans module
To: Axis developer list <ax...@ws.apache.org>
Hi all,
After the XMLBeans module has been moved out, I'm facing a problem
with running WSDL2Java in the IDE. What happens is that the XMLBeans
module depends on the codegen module for compilation (since
org.apache.axis2.xmlbeans.CodeGenerationUtility included in the
xmlbeans module) but if I'm running WSDL2Java with -d xmlbeans option
then I need the xmlbeans module in the classpath. This causes a cyclic
dependancy !!
ideas ?
--
Ajith Ranabahu
--
Ajith Ranabahu
Re: [Axis2] Dependancy problem with XMLBeans module
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
I don't know anything about IDEA (just say "no" to concealed source code
:-) ), but it sounds like you want to either merge these two Axis2
modules into a single IDEA module (if IDEA's flexible enough to allow
that approach) or switch to running your codegen from the xmlbeans
module (which has a dependancy on the codegen module, so should be able
to access the classes in that module, right?). Seems like everyone is
always raving about how great IDEA is, so at least one of these
alternatives should work. ;-)
- Dennis
Ajith Ranabahu wrote:
>Hi,
>Sorry if I did not explain the problem properly. This is regarding
>running the codegen main class from the IDE (IntellijIDEA to be
>exact). I've set up the project as a multi module project (which I
>think is the right way to do so) and module dependancies can be put
>only in one direction. Since xmlbeans module has a dependancy on the
>codegen module at compilation, I cannot put a dependancy in the
>codegen module on the xmlbeans module for running the codegen. In
>other words I cannot run the codegen with -d xmlbeans option inside
>the IDE
>
>On 4/19/06, Dennis Sosnoski <dm...@sosnoski.com> wrote:
>
>
>>Ajith Ranabahu wrote:
>>
>>
>>
>>>After the XMLBeans module has been moved out, I'm facing a problem
>>>with running WSDL2Java in the IDE. What happens is that the XMLBeans
>>>module depends on the codegen module for compilation (since
>>>org.apache.axis2.xmlbeans.CodeGenerationUtility included in the
>>>xmlbeans module) but if I'm running WSDL2Java with -d xmlbeans option
>>>then I need the xmlbeans module in the classpath. This causes a cyclic
>>>dependancy !!
>>>
>>>
>>>
>>>
>>Why do you need to run WSDL2Java with -d xmlbeans option in order to
>>build the codegen module? AFAIK you should be able to build the codegen
>>module without running the xmlbeans code, then can build the xmlbeans
>>module after that. That's the way the maven build is set up, anyway.
>>
>> - Dennis
>>
>>
>>
>>
>
>
>--
>Ajith Ranabahu
>
>
>
Re: [Axis2] Dependancy problem with XMLBeans module
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Sorry if I did not explain the problem properly. This is regarding
running the codegen main class from the IDE (IntellijIDEA to be
exact). I've set up the project as a multi module project (which I
think is the right way to do so) and module dependancies can be put
only in one direction. Since xmlbeans module has a dependancy on the
codegen module at compilation, I cannot put a dependancy in the
codegen module on the xmlbeans module for running the codegen. In
other words I cannot run the codegen with -d xmlbeans option inside
the IDE
On 4/19/06, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Ajith Ranabahu wrote:
>
> >After the XMLBeans module has been moved out, I'm facing a problem
> >with running WSDL2Java in the IDE. What happens is that the XMLBeans
> >module depends on the codegen module for compilation (since
> >org.apache.axis2.xmlbeans.CodeGenerationUtility included in the
> >xmlbeans module) but if I'm running WSDL2Java with -d xmlbeans option
> >then I need the xmlbeans module in the classpath. This causes a cyclic
> >dependancy !!
> >
> >
> Why do you need to run WSDL2Java with -d xmlbeans option in order to
> build the codegen module? AFAIK you should be able to build the codegen
> module without running the xmlbeans code, then can build the xmlbeans
> module after that. That's the way the maven build is set up, anyway.
>
> - Dennis
>
>
--
Ajith Ranabahu
Re: [Axis2] Dependancy problem with XMLBeans module
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Ajith Ranabahu wrote:
>After the XMLBeans module has been moved out, I'm facing a problem
>with running WSDL2Java in the IDE. What happens is that the XMLBeans
>module depends on the codegen module for compilation (since
>org.apache.axis2.xmlbeans.CodeGenerationUtility included in the
>xmlbeans module) but if I'm running WSDL2Java with -d xmlbeans option
>then I need the xmlbeans module in the classpath. This causes a cyclic
>dependancy !!
>
>
Why do you need to run WSDL2Java with -d xmlbeans option in order to
build the codegen module? AFAIK you should be able to build the codegen
module without running the xmlbeans code, then can build the xmlbeans
module after that. That's the way the maven build is set up, anyway.
- Dennis