You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Lasantha Ranaweera <la...@opensource.lk> on 2007/01/26 16:21:14 UTC
RE: Axis2 Integration - Replace RPCMessageReciever with
JAXWSMessageReciever
Hi Lin,
No more class loading issues right now. It looks now there is a
Unmarshalling problem of SOAP request. That is the progress ;).
There might be some missing properties in the Axis2 integration side of
code and right now I am investigating it.
Also please don't take me as a blocker here and go ahead what ever you
think to contribute to the work as we all are working on the OS model. :)
Thanks,
Lasantha
> Hi Lasantha,
>
> Were you able to make any progress towards the replacing
> RPCMessageReciever
> with JAXWSMessageReciever? I went through my eclipse debugger a few times
> and looks like a classloader issue... Let me know if you want me to look
> into this.
>
> I tried to look into No. 2 below. Looks like the following code would
> create
> default configuration context based on axis2-default.xml on the classpath.
> However, the servicepath is always set to "services" no matter what
> url-pattern I specify in web.xml.
>
> configurationContext =
> ConfigurationContextFactory.createDefaultConfigurationContext();
> AxisService service =
> AxisService.createService(endpointClassName,
> configurationContext.getAxisConfiguration(), RPCMessageReceiver.class);
>
> I am hoping you or dims can comment a bit on this. I'll dig more into
> it...
>
>
> Lin
>
> -----Original Message-----
> From: Lasantha Ranaweera [mailto:lasantha@opensource.lk]
> Sent: Wednesday, January 24, 2007 6:17 AM
> To: dev@geronimo.apache.org
> Subject: Re: Axis2 Integration - Replace RPCMessageReciever with
> JAXWSMessageReciever
>
> Hi Lin,
>
> Thanks for reviewing the patch. Please read my in line comments.
>
> Thanks,
> Lasantha
>
> Lin Sun wrote:
>> Hi Lasantha,
>>
>> Thanks for submitting the patch! Your patch (java portion) looks look
>> to
>> me. I don't quite understand the pom.xml portion of the patch as to why
> the
>> changes are needed. Was this related to some class loading issues you
>> mentioned to me in another note?
> Yes I had so many class linkage problems with our previous model when I
> was doing some changes in the source code and was trying to follow the
> same structure of CXF.
>> Also, my guess is that you don't have
>> G2746-new patch yet which I removed the hardcoded version to use
>> dependencymanagement. I'd appreciate if you could apply that onto your
>> machine to make the applying patch process easier.
>>
> Sure, I will do it. It would be fine if somebody in the list with
> committer rights will apply in to the trunk if it is correct.
>> I noticed the following aren't working yet and I'll work on them while
>> you
>> work on Axis2ServiceRefBuilder.
>>
>> 1) haven't able to get first test of jaxws-test running (post a soap
> request
>> and get a soap response). Did that work for you? ?wsdl works fine.
>>
> Yes you are correct here and I have missed the soap response test and it
> is not working correctly either :-\ . I will correct it and create a new
> patch soon.
>> 2) we had two servlet-mappings & used an asterisk in the jax-ws test app
> for
>> axis2. This seems invalid per the spec.
>>
>> I have been reading JSR 109 rev 1.2 lately and I saw the following in
>> page
>> 61 (sec 7.1.2) where it says:
>> --//--
>> Servlet Mapping. A developer may optionally specify a servlet-mapping,
>> in
>> the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
> Endpoint.
>> No more than one servlet-mapping may be specified for a servlet that is
>> linked to by a port-component.
>> The url-pattern of the servlet-mapping must be an exact match pattern
> (i.e.
>> it must not contain an asterisk ("*")).
>> --//--
>>
>>
>> I am also interested in handling cases where wsdl files aren't there and
>> users are using web services annotation. Currently the code just throws
>> a
>> warning or exception.
>>
> Please go ahead since I am not going to touch that part pretty soon. My
> plan is to finish the JAXWS stuff with XML file and moving in to the
> RefBuilder ASAP.
>> Please keep me posted on what you are working on. Thanks.
>>
>> Lin
>>
>>
>> ________________________________________
>> From: Lasantha Ranaweera [mailto:lasantha@opensource.lk]
>> Sent: Tuesday, January 23, 2007 6:13 AM
>> To: dev@geronimo.apache.org
>> Subject: Axis2 Integration - Replace RPCMessageReciever with
>> JAXWSMessageReciever
>>
>> Hi,
>>
>> Initial patch for the replacing RPCMessageReciever with
> JAXWSMessageReciever
>> is submitted under GERONIMO-2776. Had to change some of the coding to
>> handle ?wsdl request correctly in the newer version.
>>
>> Thanks,
>> Lasantha Ranaweera
>>
>>
>>
>
>
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 1/26/07, Alan D. Cabrera <li...@toolazydogs.com> wrote:
>
> On Jan 26, 2007, at 12:39 PM, Jacek Laskowski wrote:
...
> > What Maven's version are you using? I hope it is not 2.0.4 as it would
> > be the answer to your question ;-)
>
>
> The latest and greatest maven is v2.0.4. What other version should
> we be using?
2.0.4 indeed, but if the author of the question didn't use it, it
would be the answer to his/her troubles.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Jan 26, 2007, at 12:39 PM, Jacek Laskowski wrote:
> On 1/26/07, Fei Fei <mi...@hotmail.com> wrote:
>
>> so.please tell me what happened?why?
>
> I'm shooting in the dark, but it might eventually help.
>
> What Maven's version are you using? I hope it is not 2.0.4 as it would
> be the answer to your question ;-)
The latest and greatest maven is v2.0.4. What other version should
we be using?
Regards,
Alan
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 1/26/07, Fei Fei <mi...@hotmail.com> wrote:
> so.please tell me what happened?why?
I'm shooting in the dark, but it might eventually help.
What Maven's version are you using? I hope it is not 2.0.4 as it would
be the answer to your question ;-)
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: url-pattern issue during Axis2 integration
Posted by Davanum Srinivas <da...@gmail.com>.
Lin,
Isn't setServicePath("") enough to do the trick?
thanks,
dims
On 1/30/07, Lin Sun <li...@gmail.com> wrote:
> Hi there,
>
> I have been working on one particular issue related to Axis2 integration
> into Geronimo. Basically the problem is that in the jaxws test, we had to
> use /services/* as the url-pattern for the servlet:
>
> <servlet-mapping>
> <servlet-name>cxfPojoServlet</servlet-name>
> <url-pattern>/services/*</url-pattern>
> </servlet-mapping>
>
> This is invalid per JSR 109 spec. There are two problems here:
>
> First, a user will have to use /services as part of the url-pattern. After
> digging into this prob, I found out that the axis2 configurationcontext
> default the servicePath to 'services'. One fix that I can think of
> (without a lot of work) is to use the configurationContext.setServicePath
> method to override the default 'services' value. This looks okay to me as
> we are building one configurationcontext and one axisservice per
> endpointClass.
>
> To do this, I will have to either set url-pattern for the user when none is
> specified for the servlet/Implclass, or grab the url-pattern from web.xml.
> So I have been studying on how to get the url-pattern for a particular
> servlet from Geronimo. One approach I can think of is:
> 1) inside Axis2Builder, the module object is passed in when configurePOJO is
> called.
> 2) then I can get the getOriginalSpecDD from webmodule, then use
> webModuleBuilder.convertToServletSchema to get the webAppType object.
> 3) I can then get the url-pattern from webApp.getServletMappingArray() with
> some processing.
>
> This seems rather complicated to me so please let me know if there is a
> better way to do it.
>
> Second, the url-pattern of the servlet-mapping must be an exact match
> pattern (* is not permitted). I tried to remove the * but I would get 404
> when I issue ?wsdl from the browser. I think this is something we may have
> to write code to work around the spec requirement, as a user needs to be
> able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
> test?wsdl...). For example, a user can only specify 1 (or 0)
> servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
> integration code can add other url-patterns to the web deployment plan
> (web.xml). I am wondering if there is anyway to overwrite the in- memory
> version of servlet-mapping or url-pattern for Geronimo to use (of course,
> don't overwrite the original web.xml)?
>
> Reference doc:
> JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
> --//--
> Servlet Mapping. A developer may optionally specify a servlet-mapping,
> In the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
> Endpoint.
> No more than one servlet-mapping may be specified for a servlet that is
> linked to by a port-component.
> The url-pattern of the servlet-mapping must be an exact match pattern
> (i.e. it must not contain an asterisk ("*")).
> --//--
>
> Thanks for any input in advance!
>
> Lin
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: url-pattern issue during Axis2 integration
Posted by Jarek Gawor <jg...@gmail.com>.
Lin Sun,
When WebServicesBuilder.findWebServices() is called, the 3rd argument
(Map servletLocations) contains the mapping between the servlet-name
and its context location. For example, there would be a mapping of
'cxfPojoServlet' to '/<war name>/services' or something similar.
Jarek
On 1/30/07, Lin Sun <li...@gmail.com> wrote:
> Hi there,
>
> I have been working on one particular issue related to Axis2 integration
> into Geronimo. Basically the problem is that in the jaxws test, we had to
> use /services/* as the url-pattern for the servlet:
>
> <servlet-mapping>
> <servlet-name>cxfPojoServlet</servlet-name>
> <url-pattern>/services/*</url-pattern>
> </servlet-mapping>
>
> This is invalid per JSR 109 spec. There are two problems here:
>
> First, a user will have to use /services as part of the url-pattern. After
> digging into this prob, I found out that the axis2 configurationcontext
> default the servicePath to 'services'. One fix that I can think of
> (without a lot of work) is to use the configurationContext.setServicePath
> method to override the default 'services' value. This looks okay to me as
> we are building one configurationcontext and one axisservice per
> endpointClass.
>
> To do this, I will have to either set url-pattern for the user when none is
> specified for the servlet/Implclass, or grab the url-pattern from web.xml.
> So I have been studying on how to get the url-pattern for a particular
> servlet from Geronimo. One approach I can think of is:
> 1) inside Axis2Builder, the module object is passed in when configurePOJO is
> called.
> 2) then I can get the getOriginalSpecDD from webmodule, then use
> webModuleBuilder.convertToServletSchema to get the webAppType object.
> 3) I can then get the url-pattern from webApp.getServletMappingArray() with
> some processing.
>
> This seems rather complicated to me so please let me know if there is a
> better way to do it.
>
> Second, the url-pattern of the servlet-mapping must be an exact match
> pattern (* is not permitted). I tried to remove the * but I would get 404
> when I issue ?wsdl from the browser. I think this is something we may have
> to write code to work around the spec requirement, as a user needs to be
> able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
> test?wsdl...). For example, a user can only specify 1 (or 0)
> servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
> integration code can add other url-patterns to the web deployment plan
> (web.xml). I am wondering if there is anyway to overwrite the in- memory
> version of servlet-mapping or url-pattern for Geronimo to use (of course,
> don't overwrite the original web.xml)?
>
> Reference doc:
> JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
> --//--
> Servlet Mapping. A developer may optionally specify a servlet-mapping,
> In the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
> Endpoint.
> No more than one servlet-mapping may be specified for a servlet that is
> linked to by a port-component.
> The url-pattern of the servlet-mapping must be an exact match pattern
> (i.e. it must not contain an asterisk ("*")).
> --//--
>
> Thanks for any input in advance!
>
> Lin
>
>
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Prasad Kashyap <go...@gmail.com>.
I have been experiencing problems with plexus artifacts downloaded
from the codehaus repo. More specifically, the problems are regarding
the plexus-compiler artifact and it's parent. The poms there have been
corrupted.
Cheers
Prasad
On 1/26/07, Kevan Miller <ke...@gmail.com> wrote:
>
> On Jan 26, 2007, at 3:17 PM, Fei Fei wrote:
>
> >
> > so.please tell me what happened?why? isn't some plugins is not in
> > maven's repository(%HOME%/.m2/repository)?
> > thanks.
> > -A Fei-
>
> A Fei,
> I recommend you cleanup your local repo a bit. One of the repo
> servers has been serving up some bad content recently...
>
> Start by removing \.m2\repository\org\apache\geronimo\genesis (and
> all sub dirs). If that doesn't work (or you want to skip to the heavy
> handed approach), just wipe out your whole repo -- .m2\repository
>
> Let us know if this helps...
>
> --kevan
>
Re: Build geronimo failed..(Resolved )
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 1/27/07, Fei Fei <mi...@hotmail.com> wrote:
> E:\workspace\openejb\openejb3>mvn -e eclipse:eclipse
> .............
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
Congratulation! I hope your working with Geronimo won't be that hard
any longer! :P
> 1.
> maven 2.0.4 cannot work at JDK1.6 platform,only 1.5,so you should edit file
> mvn.bat(in %MVN_HOME%/bin/) and add command(dose not contains the double
> quotation marks ) "set JAVA_HOME=E:\JDK150"(of course this path is jdk1.5
> home dir in you system) at previous line of this command line: if not
> "%JAVA_HOME%" == "" goto OkJHome.
> this prob resolved can resolve many another prob.
...or better yet, set JAVA_HOME in your environment whenever you want
to work with m2. I'm doing it all the time in Cygwin where I set a
couple of aliases that change JAVA_HOME to what the project is
supposed to work with.
> 2.
> I found dir name is "maven-clipse-plugin" in dir
> .m2\repository\org\apache\maven\plugins\
That's strange. I have never come across it before. Worth to keep it
in archive in case it will happen again. Thanks for reporting!
> Maven runtime cannot load class org\apache\tools\ant\launch\AntMain,I copy
> the ant.jar,ant-launcher.jar from E:\IDE\Ant170\lib to
> E:\IDE\Maven204\lib,the result is it work now.
I'd not had to do it as you did. Are you sure your m2 is not broken?
I'd suggest that you delete m2 and install it again. You'd be better
off checking your environment variables, too. Even if it works for you
now, chances are other errors may surface in the not-so-distant future
due to the steps you did, but you shouldn't have done.
> If you know my meaning from above,Congratulate you.
You see - he's talking about me! Wish me lack with other readings I've
got on my plate ;-)
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Build geronimo failed..(Resolved )
Posted by Fei Fei <mi...@hotmail.com>.
Now.I can see following message:
E:\workspace\openejb\openejb3>mvn -e eclipse:eclipse
.............
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10 minutes 31 seconds
[INFO] Finished at: Sat Jan 27 16:49:54 CST 2007
[INFO] Final Memory: 19M/35M
[INFO]
------------------------------------------------------------------------
That is means build successful of project openejb.sure you know too.
Now.I will list my operation step following,maybe can help novice(like me):
1.
maven 2.0.4 cannot work at JDK1.6 platform,only 1.5,so you should edit file
mvn.bat(in %MVN_HOME%/bin/) and add command(dose not contains the double
quotation marks ) "set JAVA_HOME=E:\JDK150"(of course this path is jdk1.5
home dir in you system) at previous line of this command line: if not
"%JAVA_HOME%" == "" goto OkJHome.
this prob resolved can resolve many another prob.
2.
I found dir name is "maven-clipse-plugin" in dir
.m2\repository\org\apache\maven\plugins\,NOTE that is not
"maven-eclipse-plugin",and the maven runtime used is
maven-clipse-plugin,(why?I don't know,maybe you can tell me,thanks.),so I
guess the contents should is contents in
.m2\repository\org\apache\maven\plugins\maven-eclipse-plugin,because I do
search with google use keyword "maven-clipse-plugin" cannot found any
result. I copy the contents of dir
.m2\repository\org\apache\maven\plugins\maven-eclipse-plugin to
.m2\repository\org\apache\maven\plugins\maven-clipse-plugin,It working very
good.
another :
Maven runtime cannot load class org\apache\tools\ant\launch\AntMain,I copy
the ant.jar,ant-launcher.jar from E:\IDE\Ant170\lib to
E:\IDE\Maven204\lib,the result is it work now.
I hope write more.But my english ability is very bad.
If you know my meaning from above,Congratulate you.
-A Fei-
_________________________________________________________________
FREE online classifieds from Windows Live Expo buy and sell with people
you know
http://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://expo.live.com?s_cid=Hotmail_tagline_12/06
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Fei Fei <mi...@hotmail.com>.
>A Fei,
>I recommend you cleanup your local repo a bit. One of the repo servers has
>been serving up some bad content recently...
>
>Start by removing \.m2\repository\org\apache\geronimo\genesis (and all sub
>dirs). If that doesn't work (or you want to skip to the heavy handed
>approach), just wipe out your whole repo -- .m2\repository
>
>Let us know if this helps...
>
>--kevan
Thank you kevan and thanks for all give assistance to me.
Now.as though new probleam was happened.
I removed .m2\repository\org\apache\geronimo\genesis ,and I run command
again:
E:\workspace\openejb\openejb3>java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode)
E:\workspace\openejb\openejb3>mvn -v
Maven version: 2.0.4
E:\workspace\openejb\openejb3>mvn -e clean install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] OpenEJB
[INFO] OpenEJB :: iTests
[INFO] OpenEJB :: iTests Beans
[INFO] OpenEJB :: iTests Client
[INFO] OpenEJB :: iTests App
[INFO] OpenEJB :: Container
[INFO] OpenEJB :: Container :: Loader
[INFO] OpenEJB :: Container :: Java Agent
[INFO] OpenEJB :: Container :: Java EE
[INFO] OpenEJB :: Container :: Core
[INFO] OpenEJB :: Server
[INFO] OpenEJB :: Server :: Client
[INFO] OpenEJB :: Server :: Core
[INFO] OpenEJB :: Server :: EJBd
[INFO] OpenEJB :: Server :: Admin
[INFO] OpenEJB :: Server :: Http
[INFO] OpenEJB :: Server :: Telnet
[INFO] OpenEJB :: Server :: XFire
[INFO] OpenEJB :: Server :: Axis
[INFO] OpenEJB :: Server :: ActiveMQ
[INFO] OpenEJB :: Server :: CORBA
[INFO] OpenEJB :: Server :: Derby Network Service
[INFO] OpenEJB :: Server :: Hsql
[INFO] OpenEJB :: Examples :: HelloWorld Stateful POJO
[INFO] OpenEJB :: Examples :: Calculator Stateless Pojo
[INFO] OpenEJB :: Examples :: Counter Stateful Pojo
[INFO] OpenEJB :: Examples :: EJB Injection
[INFO] OpenEJB :: Examples :: Resource Injection
[INFO] OpenEJB :: Examples :: Telephone Stateful Pojo
[INFO] OpenEJB :: Examples
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/t
ools-maven-plugin/1.1/tools-maven-plugin-1.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/p
lugins/1.1/plugins-1.1.pom
5K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1
.1/genesis-1.1.pom
6K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/t
ools-maven-plugin/1.1/tools-maven-plugin-1.1.jar
22K downloaded
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building OpenEJB
[INFO] task-segment: [clean, install]
[INFO]
-------------------------------------------------------------------------
---
[INFO] [clean:clean]
[INFO] Deleting directory E:\workspace\openejb\openejb3\target
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\classes
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\test-classes
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/p
lugin-support/1.1/plugin-support-1.1.pom
1011b downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/p
lugin-support/1.1/plugin-support-1.1.jar
47K downloaded
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] org.apache.commons.logging.LogConfigurationException:
org.apache.commons.
logging.LogConfigurationException: Invalid class loader hierarchy. You have
mor
e than one version of 'org.apache.commons.logging.Log' visible, which is not
all
owed. (Caused by org.apache.commons.logging.LogConfigurationException:
Invalid c
lass loader hierarchy. You have more than one version of
'org.apache.commons.lo
gging.Log' visible, which is not allowed.) (Caused by
org.apache.commons.logging
.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException
: Invalid class loader hierarchy. You have more than one version of
'org.apache
.commons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commo
ns.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed.))
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging
.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException
: Invalid class loader hierarchy. You have more than one version of
'org.apache
.commons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commo
ns.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed.) (Caused by org.apache.commons.logging.LogConfigurationException:
org.a
pache.commons.logging.LogConfigurationException: Invalid class loader
hierarchy.
You have more than one version of 'org.apache.commons.logging.Log'
visible, wh
ich is not allowed. (Caused by
org.apache.commons.logging.LogConfigurationExcept
ion: Invalid class loader hierarchy. You have more than one version of
'org.apa
che.commons.logging.Log' visible, which is not allowed.))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at org.apache.geronimo.genesis.logging.Logging.init(Logging.java:44)
at
org.apache.geronimo.genesis.MojoSupport.<init>(MojoSupport.java:81)
at
org.apache.geronimo.genesis.plugins.tools.RequireJavaVersionMojo.<ini
t>(RequireJavaVersionMojo.java:36)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newIn
stance(JavaComponentFactory.java:44)
at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(De
faultPlexusContainer.java:1464)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.create
ComponentInstance(AbstractComponentManager.java:93)
at
org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo
mponent(PerLookupComponentManager.java:48)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul
tPluginManager.java:524)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:390)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.comm
ons.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed. (Caused by org.apache.commons.logging.LogConfigurationException:
Inval
id class loader hierarchy. You have more than one version of
'org.apache.common
s.logging.Log' visible, which is not allowed.)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:397)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
... 37 more
Caused by: org.apache.commons.logging.LogConfigurationException: Invalid
class l
oader hierarchy. You have more than one version of
'org.apache.commons.logging.
Log' visible, which is not allowed.
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:385)
... 38 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Sat Jan 27 14:37:32 CST 2007
[INFO] Final Memory: 7M/17M
[INFO]
------------------------------------------------------------------------
I guess this prob about of common logging.and I have more
commons-logging-*.jar in runtime environment:
E:\IDE\Maven204\lib\commons-logging-1.1.jar
.m2\repository\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar
.m2\repository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar
If I remove file E:\IDE\Maven204\lib\commons-logging-1.1.jar,run the command
will throw an error of java.lang.NoClassDefFoundError:
org/apache/commons/logging/Log.so I move file
.m2\repository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar
to dir E:\IDE\Maven204\lib\,and I delete .m2\repository\commons-logging,run
command again:
E:\workspace\openejb\openejb3>mvn -e clean install
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building OpenEJB
[INFO] task-segment: [clean, install]
[INFO]
-------------------------------------------------------------------------
---
[INFO] [clean:clean]
[INFO] Deleting directory E:\workspace\openejb\openejb3\target
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\classes
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\test-classes
Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4
/commons-logging-1.0.4.pom
5K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.3
/commons-logging-1.0.3.pom
866b downloaded
Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4
/commons-logging-1.0.4.jar
37K downloaded
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] org.apache.commons.logging.LogConfigurationException:
org.apache.commons.
logging.LogConfigurationException: Invalid class loader hierarchy. You have
mor
e than one version of 'org.apache.commons.logging.Log' visible, which is not
all
owed. (Caused by org.apache.commons.logging.LogConfigurationException:
Invalid c
lass loader hierarchy. You have more than one version of
'org.apache.commons.lo
gging.Log' visible, which is not allowed.) (Caused by
org.apache.commons.logging
.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException
: Invalid class loader hierarchy. You have more than one version of
'org.apache
.commons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commo
ns.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed.))
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging
.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException
: Invalid class loader hierarchy. You have more than one version of
'org.apache
.commons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commo
ns.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed.) (Caused by org.apache.commons.logging.LogConfigurationException:
org.a
pache.commons.logging.LogConfigurationException: Invalid class loader
hierarchy.
You have more than one version of 'org.apache.commons.logging.Log'
visible, wh
ich is not allowed. (Caused by
org.apache.commons.logging.LogConfigurationExcept
ion: Invalid class loader hierarchy. You have more than one version of
'org.apa
che.commons.logging.Log' visible, which is not allowed.))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at org.apache.geronimo.genesis.logging.Logging.init(Logging.java:44)
at
org.apache.geronimo.genesis.MojoSupport.<init>(MojoSupport.java:81)
at
org.apache.geronimo.genesis.plugins.tools.RequireJavaVersionMojo.<ini
t>(RequireJavaVersionMojo.java:36)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newIn
stance(JavaComponentFactory.java:44)
at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(De
faultPlexusContainer.java:1464)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.create
ComponentInstance(AbstractComponentManager.java:93)
at
org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo
mponent(PerLookupComponentManager.java:48)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul
tPluginManager.java:524)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:390)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.comm
ons.logging.LogConfigurationException: Invalid class loader hierarchy. You
have
more than one version of 'org.apache.commons.logging.Log' visible, which is
not
allowed. (Caused by org.apache.commons.logging.LogConfigurationException:
Inval
id class loader hierarchy. You have more than one version of
'org.apache.common
s.logging.Log' visible, which is not allowed.)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:397)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
... 37 more
Caused by: org.apache.commons.logging.LogConfigurationException: Invalid
class l
oader hierarchy. You have more than one version of
'org.apache.commons.logging.
Log' visible, which is not allowed.
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:385)
... 38 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Sat Jan 27 14:57:43 CST 2007
[INFO] Final Memory: 7M/16M
[INFO]
------------------------------------------------------------------------
I do search with google,use keyword "Invalid class loader hierarchy. You
have more than one version",the results list many question like this,but
cannot found any answer can resolve my prob.
Thaks again.
-A Fei-
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 26, 2007, at 3:17 PM, Fei Fei wrote:
>
> so.please tell me what happened?why? isn't some plugins is not in
> maven's repository(%HOME%/.m2/repository)?
> thanks.
> -A Fei-
A Fei,
I recommend you cleanup your local repo a bit. One of the repo
servers has been serving up some bad content recently...
Start by removing \.m2\repository\org\apache\geronimo\genesis (and
all sub dirs). If that doesn't work (or you want to skip to the heavy
handed approach), just wipe out your whole repo -- .m2\repository
Let us know if this helps...
--kevan
Build geronimo failed..Is this maven's probleam or openejb( or geronimo?)?
Posted by Fei Fei <mi...@hotmail.com>.
hello everyone.
I did something according to web page
"http://cwiki.apache.org/GMOxDEV/building-apache-geronimo-with-maven-2.html",and
the source code of openejb is checkout successfully from apache
SVN:http://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3.
the build log list following:
E:\workspace\openejb\openejb3>mvn -e clean install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] OpenEJB
[INFO] OpenEJB :: iTests
[INFO] OpenEJB :: iTests Beans
[INFO] OpenEJB :: iTests Client
[INFO] OpenEJB :: iTests App
[INFO] OpenEJB :: Container
[INFO] OpenEJB :: Container :: Loader
[INFO] OpenEJB :: Container :: Java Agent
[INFO] OpenEJB :: Container :: Java EE
[INFO] OpenEJB :: Container :: Core
[INFO] OpenEJB :: Server
[INFO] OpenEJB :: Server :: Client
[INFO] OpenEJB :: Server :: Core
[INFO] OpenEJB :: Server :: EJBd
[INFO] OpenEJB :: Server :: Admin
[INFO] OpenEJB :: Server :: Http
[INFO] OpenEJB :: Server :: Telnet
[INFO] OpenEJB :: Server :: XFire
[INFO] OpenEJB :: Server :: Axis
[INFO] OpenEJB :: Server :: ActiveMQ
[INFO] OpenEJB :: Server :: CORBA
[INFO] OpenEJB :: Server :: Derby Network Service
[INFO] OpenEJB :: Server :: Hsql
[INFO] OpenEJB :: Examples :: HelloWorld Stateful POJO
[INFO] OpenEJB :: Examples :: Calculator Stateless Pojo
[INFO] OpenEJB :: Examples :: Counter Stateful Pojo
[INFO] OpenEJB :: Examples :: EJB Injection
[INFO] OpenEJB :: Examples :: Resource Injection
[INFO] OpenEJB :: Examples :: Telephone Stateful Pojo
[INFO] OpenEJB :: Examples
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building OpenEJB
[INFO] task-segment: [clean, install]
[INFO]
-------------------------------------------------------------------------
---
[INFO] [clean:clean]
[INFO] Deleting directory E:\workspace\openejb\openejb3\target
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\classes
[INFO] Deleting directory E:\workspace\openejb\openejb3\target\test-classes
[INFO] [tools:require-java-version {execution: default}]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to lookup required components
Embedded error: Component descriptor cannot be found in the component
repository
: org.apache.geronimo.genesis.dependency.DependencyHelper.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to lookup
require
d components
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to lookup
requ
ired components
at
org.apache.geronimo.genesis.MojoSupport.init(MojoSupport.java:104)
at
org.apache.geronimo.genesis.MojoSupport.execute(MojoSupport.java:119)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 16 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExc
eption: Component descriptor cannot be found in the component repository:
org.ap
ache.geronimo.genesis.dependency.DependencyHelper.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.apache.geronimo.genesis.MojoSupport.init(MojoSupport.java:101)
... 19 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Sat Jan 27 04:03:30 CST 2007
[INFO] Final Memory: 7M/14M
[INFO]
------------------------------------------------------------------------
E:\workspace\Geronimo>mvn -e eclipse:eclipse
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geronimo
[INFO] Geronimo Test Support
[INFO] Geronimo Test Support :: Common
[INFO] Geronimo Test Support :: Selenium
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: EJB
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: WAR
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: RAR
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: EAR
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: EJB
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: WAR
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: RAR
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: EAR
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: EJB
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: WAR
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: RAR
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: EAR
[INFO] Geronimo :: Modules
[INFO] Geronimo :: Activation
[INFO] Geronimo :: ActiveMQ Embedded RAR
[INFO] Geronimo :: Util
[INFO] Geronimo :: Kernel
[INFO] Geronimo :: Common
[INFO] Geronimo :: System
[INFO] Geronimo :: Management API
[INFO] Geronimo :: J2EE
[INFO] Geronimo :: ActiveMQ GBean Management Interfaces
[INFO] Geronimo :: Core
[INFO] Geronimo :: Transaction
[INFO] Geronimo :: Interceptor
[INFO] Geronimo :: Security
[INFO] Geronimo :: Naming
[INFO] Geronimo :: Deployment
[INFO] Geronimo :: Connector
[INFO] Geronimo :: ActiveMQ GBeans
[INFO] Geronimo :: Web Services
[INFO] Geronimo :: Axis
[INFO] Geronimo :: Deploy :: Common Config
[INFO] Geronimo :: Service :: Builder
[INFO] Geronimo :: J2EE Schema
[INFO] Geronimo :: J2EE :: Builder
[INFO] Geronimo :: Naming :: Builder
[INFO] Geronimo :: Webservices :: Builder
[INFO] Geronimo :: Axis :: Builder
[INFO] Geronimo :: Client
[INFO] Geronimo :: Security :: Builder
[INFO] Geronimo :: Test :: DDBeans
[INFO] Geronimo :: Connector :: Builder
[INFO] Geronimo :: Client Builder
[INFO] Geronimo :: Clustering
[INFO] Geronimo :: Clustering WADI
[INFO] Geronimo :: Configuration Converter
[INFO] Geronimo :: Deploy :: JSR-88
[INFO] Geronimo :: Deploy :: CLI Tool
[INFO] Geronimo :: Derby
[INFO] Geronimo :: Directory
[INFO] Geronimo :: Deploy :: Hot Deployer
[INFO] Geronimo :: JMX Remoting
[INFO] Geronimo :: Mail
[INFO] Geronimo :: OpenEJB
[INFO] Geronimo :: OpenEJB :: Builder
[INFO] Geronimo :: Timer
[INFO] Geronimo :: Tomcat
[INFO] Geronimo :: Web 2.5 :: Builder
[INFO] Geronimo :: Tomcat :: Builder
[INFO] Geronimo :: Upgrade
[INFO] Geronimo :: Transformer
[INFO] Geronimo :: Persistence 3.0
[INFO] Geronimo :: Persistence JPA1.0 :: Builder
[INFO] Geronimo :: CXF
[INFO] Geronimo :: CXF :: Builder
[INFO] Geronimo :: AXIS2
[INFO] Geronimo :: Axis2 :: Builder
[INFO] Geronimo :: Jetty 6
[INFO] Geronimo :: Jetty 6 :: Builder
[INFO] Geronimo :: Jetty 6 Clustering over WADI
[INFO] Geronimo :: Jetty 6 :: Clustering Builder for WADI
[INFO] Geronimo :: Transaction JTA 11
[INFO] Geronimo Maven2 Plugins
[INFO] Geronimo Maven2 Plugins :: CAR
[INFO] Geronimo Maven2 Plugins :: Geronimo
[INFO] Geronimo Maven2 Plugins :: Selenium
[INFO] Geronimo Maven2 Plugins :: Testsuite Plugin
[INFO] Geronimo Maven2 Plugins :: Testsuite Archetype
[INFO] Geronimo Applications
[INFO] Geronimo Applications :: Welcome
[INFO] Geronimo Applications :: Dojo
[INFO] Geronimo Applications, Examples
[INFO] Geronimo Applications, Examples :: JSP (JSR 152)
[INFO] Geronimo Applications, Examples :: Servlet (JSR 154)
[INFO] Geronimo Applications :: Console
[INFO] Geronimo Applications, Console :: Core
[INFO] Geronimo Applications, Console :: Standard Portlets
[INFO] Geronimo Applications, Console :: Portal Framework
[INFO] Geronimo Applications, Console :: EAR
[INFO] Geronimo Applications :: Remote Deploy
[INFO] Geronimo Applications :: UDDI Server Database
[INFO] Geronimo Applications :: UDDI Server
[INFO] Geronimo Applications :: LDAP Demo
[INFO] Geronimo Applications :: The Magic G Ball
[INFO] Geronimo Applications, The Magic G Ball :: EJB
[INFO] Geronimo Applications, The Magic G Ball :: Client
[INFO] Geronimo Applications, The Magic G Ball :: WAR
[INFO] Geronimo Applications, The Magic G Ball :: EAR
[INFO] Geronimo Applications :: Demo
[INFO] Geronimo Applications :: CA Helper Application
[INFO] Geronimo Configs
[INFO] Geronimo Configs :: GBean Deployer
[INFO] Geronimo Configs :: JavaEE Specs
[INFO] Geronimo Configs :: J2EE System
[INFO] Geronimo Configs :: RMI Naming
[INFO] Geronimo Configs :: J2EE Security
[INFO] Geronimo Configs :: J2EE Server
[INFO] Geronimo Configs :: J2EE Deployer
[INFO] Geronimo Configs :: Transaction Manager JTA11
[INFO] Geronimo Configs :: Connector Deployer
[INFO] Geronimo Configs :: System Database
[INFO] Geronimo Configs :: ActiveMQ Broker
[INFO] Geronimo Configs :: ActiveMQ
[INFO] Geronimo Configs :: Axis
[INFO] Geronimo Configs :: Axis Deployer
[INFO] Geronimo Configs :: Client System
[INFO] Geronimo Configs :: J2EE Client
[INFO] Geronimo Configs :: J2EE Client transaction
[INFO] Geronimo Configs :: Application Client Deployments
[INFO] Geronimo Configs :: J2EE Client Security
[INFO] Geronimo Configs :: Clustering
[INFO] Geronimo Configs :: Directory
[INFO] Geronimo Configs :: Hot Deployer
[INFO] Geronimo Configs :: JavaMail
[INFO] Geronimo Configs :: WebServices Common
[INFO] Geronimo Configs :: Jetty 6
[INFO] Geronimo Configs :: Jetty Deployer
[INFO] Geronimo Configs :: JSP Examples Jetty
[INFO] Geronimo Configs :: Tomcat
[INFO] Geronimo Configs :: Tomcat Deployer
[INFO] Geronimo Configs :: JSP Examples Tomcat
[INFO] Geronimo Configs :: LDAP Demo for Jetty
[INFO] Geronimo Configs :: LDAP Demo for Tomcat
[INFO] Geronimo Configs :: LDAP Security Realm
[INFO] Geronimo Configs :: Online Deployer
[INFO] Geronimo Configs :: OpenEJB
[INFO] Geronimo Configs :: OpenEJB Deployer
[INFO] Geronimo Configs :: Remote Deploy Jetty
[INFO] Geronimo Configs :: Remote Deploy Tomcat
[INFO] Geronimo Configs :: Servlet Examples for Jetty
[INFO] Geronimo Configs :: Servlet Examples for Tomcat
[INFO] Geronimo Configs :: Shared Library
[INFO] Geronimo Configs :: Shutdown
[INFO] Geronimo Configs :: UDDI Tomcat
[INFO] Geronimo Configs :: Unavailable Client Deployer
[INFO] Geronimo Configs :: Unavailable EJB Deployer
[INFO] Geronimo Configs :: Unavailable Web Services Deployer
[INFO] Geronimo Configs :: Plan Upgrade
[INFO] Geronimo Configs :: CLI Upgrade
[INFO] Geronimo Configs :: Clustering over WADI
[INFO] Geronimo Configs :: Dojo app Tomcat
[INFO] Geronimo Configs :: WebConsole Tomcat
[INFO] Geronimo Configs :: Welcome app Jetty
[INFO] Geronimo Configs :: Welcome app Tomcat
[INFO] Geronimo Configs :: CA Helper app - Jetty
[INFO] Geronimo Configs :: CA Helper app - Tomcat
[INFO] Geronimo Configs :: Transformer Agent
[INFO] Geronimo Configs :: Persistence Deployer
[INFO] Geronimo Configs :: OpenJPA with dependencies
[INFO] Geronimo Configs :: CXF
[INFO] Geronimo Configs :: CXF Deployer
[INFO] Geronimo Configs :: Axis2
[INFO] Geronimo Configs :: Axis2 Deployer
[INFO] Geronimo Configs :: Dojo app jetty6
[INFO] Geronimo Configs :: Jetty 6 :: Clustering Builder for WADI
[INFO] Geronimo Configs :: Jetty 6 Clustering over WADI
[INFO] Geronimo Configs :: UDDI Jetty6
[INFO] Geronimo Configs :: WebConsole Jetty6
[INFO] Geronimo Assemblies
[INFO] Geronimo Assemblies :: Boilerplate Minimal
[INFO] Geronimo Assemblies :: Boilerplate JEE5
[INFO] Geronimo Assemblies :: JEE5 + Jetty6
[INFO] Geronimo Assemblies :: JEE5 + Tomcat
[INFO] Geronimo Assemblies :: Minimal Framework
[INFO] Geronimo Assemblies :: Minimal + Jetty6
[INFO] Geronimo Assemblies :: Minimal + Tomcat
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] snapshot org.apache.geronimo.plugins:car-maven-plugin:2.0-SNAPSHOT:
check
ing for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.plugins:car-maven-plugin:2.0-SNAPSHOT:
check
ing for updates from codehaus-snapshots
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ger
onimo/plugins/car-maven-plugin/2.0-SNAPSHOT/car-maven-plugin-2.0-20070124.044558
-5.jar
42K downloaded
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building Geronimo
[INFO] task-segment: [eclipse:eclipse]
[INFO]
-------------------------------------------------------------------------
---
[INFO] Preparing eclipse:eclipse
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to lookup required components
Embedded error: Component descriptor cannot be found in the component
repository
: org.apache.geronimo.genesis.dependency.DependencyHelper.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to lookup
require
d components
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
cle(DefaultLifecycleExecutor.java:891)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
aultLifecycleExecutor.java:734)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:505)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to lookup
requ
ired components
at
org.apache.geronimo.genesis.MojoSupport.init(MojoSupport.java:104)
at
org.apache.geronimo.genesis.MojoSupport.execute(MojoSupport.java:119)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 20 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExc
eption: Component descriptor cannot be found in the component repository:
org.ap
ache.geronimo.genesis.dependency.DependencyHelper.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.apache.geronimo.genesis.MojoSupport.init(MojoSupport.java:101)
... 23 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 21 seconds
[INFO] Finished at: Sat Jan 27 04:16:38 CST 2007
[INFO] Final Memory: 54M/103M
[INFO]
------------------------------------------------------------------------
E:\workspace\openejb\openejb3>
and I did
so.please tell me what happened?why? isn't some plugins is not in maven's
repository(%HOME%/.m2/repository)?
thanks.
-A Fei-
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
url-pattern issue during Axis2 integration
Posted by Lin Sun <li...@gmail.com>.
Hi there,
I have been working on one particular issue related to Axis2 integration
into Geronimo. Basically the problem is that in the jaxws test, we had to
use /services/* as the url-pattern for the servlet:
<servlet-mapping>
<servlet-name>cxfPojoServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>
This is invalid per JSR 109 spec. There are two problems here:
First, a user will have to use /services as part of the url-pattern. After
digging into this prob, I found out that the axis2 configurationcontext
default the servicePath to 'services'. One fix that I can think of
(without a lot of work) is to use the configurationContext.setServicePath
method to override the default 'services' value. This looks okay to me as
we are building one configurationcontext and one axisservice per
endpointClass.
To do this, I will have to either set url-pattern for the user when none is
specified for the servlet/Implclass, or grab the url-pattern from web.xml.
So I have been studying on how to get the url-pattern for a particular
servlet from Geronimo. One approach I can think of is:
1) inside Axis2Builder, the module object is passed in when configurePOJO is
called.
2) then I can get the getOriginalSpecDD from webmodule, then use
webModuleBuilder.convertToServletSchema to get the webAppType object.
3) I can then get the url-pattern from webApp.getServletMappingArray() with
some processing.
This seems rather complicated to me so please let me know if there is a
better way to do it.
Second, the url-pattern of the servlet-mapping must be an exact match
pattern (* is not permitted). I tried to remove the * but I would get 404
when I issue ?wsdl from the browser. I think this is something we may have
to write code to work around the spec requirement, as a user needs to be
able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
test?wsdl...). For example, a user can only specify 1 (or 0)
servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
integration code can add other url-patterns to the web deployment plan
(web.xml). I am wondering if there is anyway to overwrite the in- memory
version of servlet-mapping or url-pattern for Geronimo to use (of course,
don't overwrite the original web.xml)?
Reference doc:
JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
--//--
Servlet Mapping. A developer may optionally specify a servlet-mapping,
In the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
Endpoint.
No more than one servlet-mapping may be specified for a servlet that is
linked to by a port-component.
The url-pattern of the servlet-mapping must be an exact match pattern
(i.e. it must not contain an asterisk ("*")).
--//--
Thanks for any input in advance!
Lin