You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Jim Foster <jf...@tmtsaz.com> on 2008/02/12 18:42:30 UTC

Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Hello,

I am attempting to use the "Plan Creator" feature of 2.1 using
liferay-portal-4.4.1.war as the target, but I am receiving a
security-related error (full text bottom of this post). 

Even though I have been using Geronimo for some time, the changes in 2.1
(which are all excellent) still leave me unsure of where the problem lies:
Geronimo base, the deployment plan, or Liferay's distribution.

For the record, I am using the code from svn, Revision 620253.

Any advise would be most appreciated.

Thank you for your time!

Jim


>From Plan Creator, following clicking on the "Deploy" button on the last
wizard screen.
=======================================================
org.apache.geronimo.common.DeploymentException:

  web.xml for web app liferay/liferay-portal-4.4.1/4.4.1/war 

includes security elements but Geronimo deployment plan is not provided or
does not  
contain <security-realm-name> element necessary to configure security
accordingly.

at
org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext(AbstractWebModuleBuilder.java:349)
at
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext(TomcatModuleBuilder.java:326)
at
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext(SwitchingModuleBuilder.java:159)
at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:595)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at
org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
at
org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
at java.lang.Thread.run(Thread.java:595)
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15437773.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
Missed attaching geronimo.web.xml last time. Here it goes.

-- 
Thanks,
Shiva

On Thu, Feb 14, 2008 at 5:09 PM, Shiva Kumar H R <sh...@gmail.com> wrote:

> There are two problems, both in Plan Creator feature:
> 1) Error message/Java Exceptions are suppressed by Plan Creator code and
> not shown to the user at all :-(
>
> With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
> remote connected via Eclipse (with a break point put at the beginning of
> org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
> function inside "plancreator-portlets" module), I found that we are getting
> following exception:
>
> org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
> Could not load servlet class: com.liferay.portal.servlet.MainServlet
>
> Instead of showing this error on Console, plan creator is currently
> suppressing it in an empty catch() block. *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
> *is opened for this.
>
> 2) Secondly, I see that the class it is complaining "
> com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
> compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
> Creator has a current limitation :-( in resolving such classes. *
> GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
> opened for this.
>
> Due to these bugs/limitations, I am sorry to say that you will again have
> to create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> from it and attached it in this mail. Please see if it works. (I guess it
> requires some pre-requisite db-pools to be deployed before the WAR can be
> deployed). Hope it helps.
>
> --
> Thanks,
> Shiva
>
> On Wed, Feb 13, 2008 at 6:17 PM, Shiva Kumar H R <sh...@gmail.com>
> wrote:
>
> > Hi Jim,
> > Looks like there is some problem. I am looking at it.
> >
> > --
> > Thanks,
> > Shiva
> >
> > On Feb 12, 2008 11:12 PM, Jim Foster <jf...@tmtsaz.com> wrote:
> >
> > >
> > > Hello,
> > >
> > > I am attempting to use the "Plan Creator" feature of 2.1 using
> > > liferay-portal-4.4.1.war as the target, but I am receiving a
> > > security-related error (full text bottom of this post).
> > >
> > > Even though I have been using Geronimo for some time, the changes in
> > > 2.1
> > > (which are all excellent) still leave me unsure of where the problem
> > > lies:
> > > Geronimo base, the deployment plan, or Liferay's distribution.
> > >
> > > For the record, I am using the code from svn, Revision 620253.
> > >
> > > Any advise would be most appreciated.
> > >
> > > Thank you for your time!
> > >
> > > Jim
> > >
> > >
> > > From Plan Creator, following clicking on the "Deploy" button on the
> > > last
> > > wizard screen.
> > > =======================================================
> > > org.apache.geronimo.common.DeploymentException:
> > >
> > >  web.xml for web app liferay/liferay-portal-4.4.1/4.4.1/war
> > >
> > > includes security elements but Geronimo deployment plan is not
> > > provided or
> > > does not
> > > contain <security-realm-name> element necessary to configure security
> > > accordingly.
> > >
> > > at
> > >
> > > org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext
> > > (AbstractWebModuleBuilder.java:349)
> > > at
> > > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext(
> > > TomcatModuleBuilder.java:326)
> > > at
> > > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext
> > > (SwitchingModuleBuilder.java:159)
> > > at
> > >
> > > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration
> > > (EARConfigBuilder.java:595)
> > > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
> > > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(
> > > NativeMethodAccessorImpl.java:39)
> > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > at
> > > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(
> > > ReflectionMethodInvoker.java:34)
> > > at
> > > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(
> > > GBeanOperation.java:124)
> > > at
> > > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(
> > > GBeanInstance.java:867)
> > > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(
> > > BasicKernel.java:239)
> > > at
> > >
> > > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy
> > > (AbstractDeployCommand.java:116)
> > > at
> > > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(
> > > DistributeCommand.java:61)
> > > at java.lang.Thread.run(Thread.java:595)
> > > --
> > > View this message in context:
> > > http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15437773.html
> > > Sent from the Apache Geronimo - Users mailing list archive at
> > > Nabble.com.
> > >
> > >
> >
> >
>
>

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@pmb.mine.nu>.
I just noticed David is giving you some help on this, don't know why the 
thread was split up into a second one it made me miss the info you got 
from him. I hope my post wont confuse you it was made under the 
assumption of tweaking the cars you got from liferays homepage from 
Geronomo v2.0.2 to Geronomo v2.1.

David I am afraid the liferay project is using ant for build system.

peter petersson

Peter Petersson wrote:
> Hi Jim
>
> I assume you are trying to install liferay in geronimo and not just 
> generate a new plan, with you do not need to, as Shiva have provided 
> you with one (the geronimo-web.xml).
>
> Aside from the security dependency issue you have that I hope 
> **someone else** that are more familiar with the security (dependency) 
> changes done between G v2.0.2 and v2.1 will help you with, there are a 
> couple of more things to do:
>
> As the liferay-portal-geronimo-tomcat car is dependent (if you haven't 
> changed the geronimo-web.xml regarding the db pool) on the 
> liferay-portal-geronimo-derby-pool car, so to successfully install the 
> liferay-portal-geronimo-tomcat car you have to install the derby pool 
> **before** the liferay-portal-geronimo-tomcat car.
>  
> After a smal tweak of the META-INF/geronimo-plugin.xml included in the 
> derby-pool car file you should be able to install the db pool by issuing
> deploy --user <user> --password <passoword> install-plugin <derby pool car file>
>   
> The geronimo-plugin.xml tweak consist of changing the version tag in 
> the geronimo-plugin.xml to <version>2.1-SNAPSHOT</version> (omit 
> -snapshot for released geronimo). The same command (as above) can then 
> be used on the liferay-portal-geronimo-tomcat car (when the security 
> dependency issue is fixed)
>
> Maybe this link will be of some help to you even though it is a bit 
> outdated http://wiki.liferay.com/index.php/Liferay_with_Geronimo
>
>  regards
>   peter petersson
>  
>
> Jim Foster wrote:
>> Shiva Kumar H R wrote:
>>   
>>> There are two problems, both in Plan Creator feature:
>>> 1) Error message/Java Exceptions are suppressed by Plan Creator code and
>>> not
>>> shown to the user at all :-(
>>>
>>> With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
>>> remote
>>> connected via Eclipse (with a break point put at the beginning of
>>> org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
>>> function inside "plancreator-portlets" module), I found that we are
>>> getting
>>> following exception:
>>>
>>> org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
>>> Could not load servlet class: com.liferay.portal.servlet.MainServlet
>>>
>>> Instead of showing this error on Console, plan creator is currently
>>> suppressing it in an empty catch() block.
>>> *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
>>> *is opened for this.
>>>
>>> 2) Secondly, I see that the class it is complaining "
>>> com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
>>> compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
>>> Creator has a current limitation :-( in resolving such classes. *
>>> GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
>>> opened for this.
>>>
>>> Due to these bugs/limitations, I am sorry to say that you will again have
>>> to
>>> create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
>>> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
>>> from it and attached it in this mail. Please see if it works. (I guess it
>>> requires some pre-requisite db-pools to be deployed before the WAR can be
>>> deployed). Hope it helps.
>>>
>>> ...
>>>
>>>
>>>     
>>
>>
>>
>> Hi Shiva,
>>
>> Is there any new word on the origins of the security configuration errors we
>> were seeing?
>>
>> I have spent a good deal of time this week reading everything I could get my
>> hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
>> developerworks.
>> (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true). 
>>
>> However, the most recent I could find that seemed relevant to this issue was
>> on the wiki:
>>
>> http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
>>
>> However, this is an installation document, and provides little in the way of
>> debugging guidelines, and I  am only now just far enough along in wrapping
>> my head around all the technologies that make up Geronimo to get myself in
>> trouble.
>>
>> Suggestions?
>>
>>
>> Once past this, I would like your advise on how to bring up to date the
>> Liferay-provided .car file for the derby pool. I looked at its contents, and
>> I see that they are clearly wrong (my guess is that they were written for
>> v1.1), but I am not quite sure how to go about fixing it so as to be in
>> alignment with v2.1
>>
>> ...one step at a time though...first the security issue.
>>
>>
>> Thank you for your time, patience, and advise.
>>
>> Jim
>>
>>
>>
>>
>>   
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

Peter Petersson wrote:
> 
> Hi Jim
> 
> I assume you are trying to install liferay in geronimo and not just 
> generate a new plan, with you do not need to, as Shiva have provided you 
> with one (the geronimo-web.xml).
> 
> ...
> 
>  regards
>   peter petersson
>  
> 


Hi Peter,

I have an on-going discussion in process with David covering several
subtopics on this issue of running the Liferay portal in Geronimo.

We are going to put a lid on these security issues, then move forward from
there...including addressing the Connector issue. Perhaps it would be best
if we all knew what we were all saying to each other? Please see the thread 

  "Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.4.1"

started by djencks.

I will return to this thread and pick up with your suggestions if you think
this is distinct from that conversation, and can be done in parallel with
it.


Thanks you for your advise!

Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15634438.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@pmb.mine.nu>.
Shiva Kumar H R wrote:
>
>
> On Fri, Feb 22, 2008 at 4:59 PM, Shiva Kumar H R <shivahr@gmail.com 
> <ma...@gmail.com>> wrote:
>
>
>
>     On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson
>     <peter@pmb.mine.nu <ma...@pmb.mine.nu>> wrote:
>
>         Hi Jim
>
>         I assume you are trying to install liferay in geronimo and not
>         just generate a new plan, with you do not need to, as Shiva
>         have provided you with one (the geronimo-web.xml).
>
>         Aside from the security dependency issue you have that I hope
>         **someone else** that are more familiar with the security
>         (dependency) changes done between G v2.0.2 and v2.1 will help
>         you with, there are a couple of more things to do:
>
>         As the liferay-portal-geronimo-tomcat car is dependent (if you
>         haven't changed the geronimo-web.xml regarding the db pool) on
>         the liferay-portal-geronimo-derby-pool car, so to successfully
>         install the liferay-portal-geronimo-tomcat car you have to
>         install the derby pool **before** the
>         liferay-portal-geronimo-tomcat car.
>          
>         After a smal tweak of the META-INF/geronimo-plugin.xml
>         included in the derby-pool car file you should be able to
>         install the db pool by issuing
>
>         deploy --user <user> --password <passoword> install-plugin <derby pool car file>
>               
>
>         The geronimo-plugin.xml tweak consist of changing the version
>         tag in the geronimo-plugin.xml to
>         <version>2.1-SNAPSHOT</version> (omit -snapshot for released
>         geronimo). The same command (as above) can then be used on the
>         liferay-portal-geronimo-tomcat car (when the security
>         dependency issue is fixed)
>
>
>     Looks like there is more to it than just that. I have been trying
>     it since yesterday and it is failing with below error:
>
>     Installation FAILED: A plugin configuration must include one
>     plugin artifact, not 0
>
>
> Alright this is now solved :) . Update the geronimo-plugin.xml inside 
> liferay-portal-geronimo-derby-pool-4.4.1.car with the one attached here.
>
> (The schema for geronimo-plugin.xml has changed and I have updated it 
> accordingly by looking at other examples.)
ahh, yes now I remember it was more to it than just the version it was a 
couple of weeks ago I messed around with the pool and it slipped my 
mind, good to here you solved it.
regards
   peter petersson
>  
> Now let me deploy liferay-portal-4.4.1.war using the plan provided by 
> DJencks.
>
> -- 
> Thanks,
> Shiva
>
>
>     Any idea where is the source for
>     liferay-portal-geronimo-derby-pool-4.4.1.car ?
>
>
>         Maybe this link will be of some help to you even though it is
>         a bit outdated
>         http://wiki.liferay.com/index.php/Liferay_with_Geronimo
>
>          regards
>           peter petersson
>
>          
>
>         Jim Foster wrote:
>>         Shiva Kumar H R wrote:
>>           
>>>         There are two problems, both in Plan Creator feature:
>>>         1) Error message/Java Exceptions are suppressed by Plan Creator code and
>>>         not
>>>         shown to the user at all :-(
>>>
>>>         With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
>>>         remote
>>>         connected via Eclipse (with a break point put at the beginning of
>>>         org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
>>>         function inside "plancreator-portlets" module), I found that we are
>>>         getting
>>>         following exception:
>>>
>>>         org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
>>>         Could not load servlet class: com.liferay.portal.servlet.MainServlet
>>>
>>>         Instead of showing this error on Console, plan creator is currently
>>>         suppressing it in an empty catch() block.
>>>         *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
>>>         *is opened for this.
>>>
>>>         2) Secondly, I see that the class it is complaining "
>>>         com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
>>>         compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
>>>         Creator has a current limitation :-( in resolving such classes. *
>>>         GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
>>>         opened for this.
>>>
>>>         Due to these bugs/limitations, I am sorry to say that you will again have
>>>         to
>>>         create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
>>>         liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
>>>         from it and attached it in this mail. Please see if it works. (I guess it
>>>         requires some pre-requisite db-pools to be deployed before the WAR can be
>>>         deployed). Hope it helps.
>>>
>>>         ...
>>>
>>>
>>>             
>>         Hi Shiva,
>>
>>         Is there any new word on the origins of the security configuration errors we
>>         were seeing?
>>
>>         I have spent a good deal of time this week reading everything I could get my
>>         hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
>>         developerworks.
>>         (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true <http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true>). 
>>
>>         However, the most recent I could find that seemed relevant to this issue was
>>         on the wiki:
>>
>>         http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
>>
>>         However, this is an installation document, and provides little in the way of
>>         debugging guidelines, and I  am only now just far enough along in wrapping
>>         my head around all the technologies that make up Geronimo to get myself in
>>         trouble.
>>
>>         Suggestions?
>>
>>
>>         Once past this, I would like your advise on how to bring up to date the
>>         Liferay-provided .car file for the derby pool. I looked at its contents, and
>>         I see that they are clearly wrong (my guess is that they were written for
>>         v1.1), but I am not quite sure how to go about fixing it so as to be in
>>         alignment with v2.1
>>
>>         ...one step at a time though...first the security issue.
>>
>>
>>         Thank you for your time, patience, and advise.
>>
>>         Jim
>>
>>
>>
>>
>>           
>
>
>
>
>     -- 
>     Thanks,
>     Shiva 
>
>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
On Fri, Feb 22, 2008 at 5:44 PM, Shiva Kumar H R <sh...@gmail.com> wrote:

>
>
> On Fri, Feb 22, 2008 at 4:59 PM, Shiva Kumar H R <sh...@gmail.com>
> wrote:
>
> >
> >
> > On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu>
> > wrote:
> >
> > >  Hi Jim
> > >
> > > I assume you are trying to install liferay in geronimo and not just
> > > generate a new plan, with you do not need to, as Shiva have provided you
> > > with one (the geronimo-web.xml).
> > >
> > > Aside from the security dependency issue you have that I hope
> > > **someone else** that are more familiar with the security (dependency)
> > > changes done between G v2.0.2 and v2.1 will help you with, there are a
> > > couple of more things to do:
> > >
> > > As the liferay-portal-geronimo-tomcat car is dependent (if you haven't
> > > changed the geronimo-web.xml regarding the db pool) on the
> > > liferay-portal-geronimo-derby-pool car, so to successfully install the
> > > liferay-portal-geronimo-tomcat car you have to install the derby pool
> > > **before** the liferay-portal-geronimo-tomcat car.
> > >
> > > After a smal tweak of the META-INF/geronimo-plugin.xml included in the
> > > derby-pool car file you should be able to install the db pool by issuing
> > >
> > > deploy --user <user> --password <passoword> install-plugin <derby pool car file>
> > >
> > > The geronimo-plugin.xml tweak consist of changing the version tag in
> > > the geronimo-plugin.xml to <version>2.1-SNAPSHOT</version> (omit
> > > -snapshot for released geronimo). The same command (as above) can then be
> > > used on the liferay-portal-geronimo-tomcat car (when the security dependency
> > > issue is fixed)
> > >
> >
> > Looks like there is more to it than just that. I have been trying it
> > since yesterday and it is failing with below error:
> >
> > Installation FAILED: A plugin configuration must include one plugin
> > artifact, not 0
> >
>
> Alright this is now solved :) . Update the geronimo-plugin.xml inside
> liferay-portal-geronimo-derby-pool-4.4.1.car with the one attached here.
>
> (The schema for geronimo-plugin.xml has changed and I have updated it
> accordingly by looking at other examples.)
>
> Now let me deploy liferay-portal-4.4.1.war using the plan provided by
> DJencks.
>

I have further tweaked the plan provided by DJencks and attached here.
(Plan changes: updated groupId for j2ee-security and added dependency on
javax.portlet/portlet-api//jar - the latter one is required as deploy was
complaining about not finding javax.portlet.RenderResponse).

Deploy was also complaining about
com.liferay.portal.kernel.servlet.PortalDelegatorServlet class not being
there, so put portal-kernel.jar & portal-service.jar into your into
<GERONIMO_HOME>/var/shared/lib directory and restart G to pick up those
JARs.

Deploy of liferay-portal-4.4.1.war is successful! However it fails to start
with following exceptions:

18:58:26,170 WARN  [ConfigurationUtil] Could not load gbean
liferay/liferay-port
al-tomcat/4.4.1/car?J2EEApplication=null,j2eeType=WebModule,name=liferay/liferay
-portal-tomcat/4.4.1/car
org.apache.geronimo.gbean.InvalidConfigurationException: Getter return type
in w
rong classloader: type: interface javax.management.j2ee.statistics.Statswanted
in classloader: [org.apache.geronimo.kernel.classloader.JarFileClassLoaderid=li
feray/liferay-portal-tomcat/4.4.1/car] actual: [
org.apache.geronimo.kernel.class
loader.JarFileClassLoader id=org.apache.geronimo.framework
/jee-specs/2.1/car]
        at org.apache.geronimo.gbean.runtime.GBeanAttribute
.<init>(GBeanAttribut
e.java:241)

-- 
Thanks,
Shiva


> --
> Thanks,
> Shiva
>
>
> > Any idea where is the source for
> > liferay-portal-geronimo-derby-pool-4.4.1.car ?
> >
> >
> > > Maybe this link will be of some help to you even though it is a bit
> > > outdated http://wiki.liferay.com/index.php/Liferay_with_Geronimo
> > >
> > >  regards
> > >   peter petersson
> > >
> > >
> > >
> > > Jim Foster wrote:
> > >
> > > Shiva Kumar H R wrote:
> > >
> > >
> > >  There are two problems, both in Plan Creator feature:
> > > 1) Error message/Java Exceptions are suppressed by Plan Creator code and
> > > not
> > > shown to the user at all :-(
> > >
> > > With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
> > > remote
> > > connected via Eclipse (with a break point put at the beginning oforg.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
> > > function inside "plancreator-portlets" module), I found that we are
> > > getting
> > > following exception:
> > > org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
> > > Could not load servlet class: com.liferay.portal.servlet.MainServlet
> > >
> > > Instead of showing this error on Console, plan creator is currently
> > > suppressing it in an empty catch() block.
> > > *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850> <https://issues.apache.org/jira/browse/GERONIMO-3850>
> > > *is opened for this.
> > >
> > > 2) Secondly, I see that the class it is complaining "com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
> > > compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
> > > Creator has a current limitation :-( in resolving such classes. *
> > > GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
> > > opened for this.
> > >
> > > Due to these bugs/limitations, I am sorry to say that you will again have
> > > to
> > > create geronimo-web.xml by hand. I found one "geronimo-web.xml" insideliferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> > > from it and attached it in this mail. Please see if it works. (I guess it
> > > requires some pre-requisite db-pools to be deployed before the WAR can be
> > > deployed). Hope it helps.
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >  Hi Shiva,
> > >
> > > Is there any new word on the origins of the security configuration errors we
> > > were seeing?
> > >
> > > I have spent a good deal of time this week reading everything I could get my
> > > hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
> > > developerworks.
> > > (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true).
> > >
> > > However, the most recent I could find that seemed relevant to this issue was
> > > on the wiki:
> > > http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
> > >
> > > However, this is an installation document, and provides little in the way of
> > > debugging guidelines, and I  am only now just far enough along in wrapping
> > > my head around all the technologies that make up Geronimo to get myself in
> > > trouble.
> > >
> > > Suggestions?
> > >
> > >
> > > Once past this, I would like your advise on how to bring up to date the
> > > Liferay-provided .car file for the derby pool. I looked at its contents, and
> > > I see that they are clearly wrong (my guess is that they were written forv1.1), but I am not quite sure how to go about fixing it so as to be in
> > > alignment with v2.1
> > >
> > > ...one step at a time though...first the security issue.
> > >
> > >
> > > Thank you for your time, patience, and advise.
> > >
> > > Jim
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Thanks,
> > Shiva
>
>
>
>

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
On Fri, Feb 22, 2008 at 4:59 PM, Shiva Kumar H R <sh...@gmail.com> wrote:

>
>
> On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu>
> wrote:
>
> >  Hi Jim
> >
> > I assume you are trying to install liferay in geronimo and not just
> > generate a new plan, with you do not need to, as Shiva have provided you
> > with one (the geronimo-web.xml).
> >
> > Aside from the security dependency issue you have that I hope **someone
> > else** that are more familiar with the security (dependency) changes done
> > between G v2.0.2 and v2.1 will help you with, there are a couple of more
> > things to do:
> >
> > As the liferay-portal-geronimo-tomcat car is dependent (if you haven't
> > changed the geronimo-web.xml regarding the db pool) on the
> > liferay-portal-geronimo-derby-pool car, so to successfully install the
> > liferay-portal-geronimo-tomcat car you have to install the derby pool
> > **before** the liferay-portal-geronimo-tomcat car.
> >
> > After a smal tweak of the META-INF/geronimo-plugin.xml included in the
> > derby-pool car file you should be able to install the db pool by issuing
> >
> > deploy --user <user> --password <passoword> install-plugin <derby pool car file>
> >
> > The geronimo-plugin.xml tweak consist of changing the version tag in the
> > geronimo-plugin.xml to <version>2.1-SNAPSHOT</version> (omit -snapshot
> > for released geronimo). The same command (as above) can then be used on the
> > liferay-portal-geronimo-tomcat car (when the security dependency issue is
> > fixed)
> >
>
> Looks like there is more to it than just that. I have been trying it since
> yesterday and it is failing with below error:
>
> Installation FAILED: A plugin configuration must include one plugin
> artifact, not 0
>

Alright this is now solved :) . Update the geronimo-plugin.xml inside
liferay-portal-geronimo-derby-pool-4.4.1.car with the one attached here.

(The schema for geronimo-plugin.xml has changed and I have updated it
accordingly by looking at other examples.)

Now let me deploy liferay-portal-4.4.1.war using the plan provided by
DJencks.

-- 
Thanks,
Shiva


> Any idea where is the source for
> liferay-portal-geronimo-derby-pool-4.4.1.car ?
>
>
> > Maybe this link will be of some help to you even though it is a bit
> > outdated http://wiki.liferay.com/index.php/Liferay_with_Geronimo
> >
> >  regards
> >   peter petersson
> >
> >
> >
> > Jim Foster wrote:
> >
> > Shiva Kumar H R wrote:
> >
> >
> >  There are two problems, both in Plan Creator feature:
> > 1) Error message/Java Exceptions are suppressed by Plan Creator code and
> > not
> > shown to the user at all :-(
> >
> > With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
> > remote
> > connected via Eclipse (with a break point put at the beginning oforg.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
> > function inside "plancreator-portlets" module), I found that we are
> > getting
> > following exception:
> > org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
> > Could not load servlet class: com.liferay.portal.servlet.MainServlet
> >
> > Instead of showing this error on Console, plan creator is currently
> > suppressing it in an empty catch() block.
> > *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850> <https://issues.apache.org/jira/browse/GERONIMO-3850>
> > *is opened for this.
> >
> > 2) Secondly, I see that the class it is complaining "com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
> > compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
> > Creator has a current limitation :-( in resolving such classes. *
> > GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
> > opened for this.
> >
> > Due to these bugs/limitations, I am sorry to say that you will again have
> > to
> > create geronimo-web.xml by hand. I found one "geronimo-web.xml" insideliferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> > from it and attached it in this mail. Please see if it works. (I guess it
> > requires some pre-requisite db-pools to be deployed before the WAR can be
> > deployed). Hope it helps.
> >
> > ...
> >
> >
> >
> >
> >  Hi Shiva,
> >
> > Is there any new word on the origins of the security configuration errors we
> > were seeing?
> >
> > I have spent a good deal of time this week reading everything I could get my
> > hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
> > developerworks.
> > (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true).
> >
> > However, the most recent I could find that seemed relevant to this issue was
> > on the wiki:
> > http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
> >
> > However, this is an installation document, and provides little in the way of
> > debugging guidelines, and I  am only now just far enough along in wrapping
> > my head around all the technologies that make up Geronimo to get myself in
> > trouble.
> >
> > Suggestions?
> >
> >
> > Once past this, I would like your advise on how to bring up to date the
> > Liferay-provided .car file for the derby pool. I looked at its contents, and
> > I see that they are clearly wrong (my guess is that they were written forv1.1), but I am not quite sure how to go about fixing it so as to be in
> > alignment with v2.1
> >
> > ...one step at a time though...first the security issue.
> >
> >
> > Thank you for your time, patience, and advise.
> >
> > Jim
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Thanks,
> Shiva

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Mar 4, 2008, at 12:21 PM, Peter Petersson wrote:

> Hi Jim
>
> If you do a google search on "liferay permgen" you will get a lot  
> of results about it so this seems to be a general "issue".
>
> I have been testing out several older versions of Liferay with  
> Geronimo 1.1.1 and 2.0.2 and my experience with it is that Liferay  
> is a real best, although a nice one ;) that likes a lot of memory  
> so try bump up memory by setting it to something like -Xms128m - 
> Xmx1024m -XX:MaxPermSize=128m in you java opts and hopefully it  
> will stabilize.

Yes!! I don't know if we fixed something or what happened but  
increasing perm size and memory moved us onto  a different,  
classloading, error that was easy to fix.

I've updated the instructions a bit. Since then I've gotten a bit  
farther.  Apparently liferay wants to be run with contextPath "/".   
After unpacking the server if you adjust var/config/config- 
substitutions.properties so LiferayContextPath=/
then the server will start and you can see the start page at /
However there's still something wrong, I get
17:04:07,548 ERROR [jsp] java.lang.StringIndexOutOfBoundsException:  
String index out of range: -12
         at java.lang.String.substring(String.java:1768)
         at  
com.liferay.portlet.PortletContextImpl.getRequestDispatcher 
(PortletContextImpl.java:99)
         at  
com.liferay.portal.struts.PortletRequestProcessor.doInclude 
(PortletRequestProcessor.java:452)
         at  
com.liferay.portal.struts.PortletRequestProcessor.doForward 
(PortletRequestProcessor.java:435)
         at  
org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition 
(TilesRequestProcessor.java:239)
         at  
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig 
(TilesRequestProcessor.java:302)
         at  
com.liferay.portal.struts.PortletRequestProcessor.processForwardConfig 
(PortletRequestProcessor.java:276)
         at org.apache.struts.action.RequestProcessor.process 
(RequestProcessor.java:241)
         at com.liferay.portal.struts.PortletRequestProcessor.process 
(PortletRequestProcessor.java:123)
         at com.liferay.portlet.StrutsPortlet.include 
(StrutsPortlet.java:224)
         at com.liferay.portlet.StrutsPortlet.doView 
(StrutsPortlet.java:195)
         at  
com.liferay.portal.kernel.portlet.LiferayPortlet.doDispatch 
(LiferayPortlet.java:51)
         at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
         at com.liferay.portlet.CachePortlet._invoke 
(CachePortlet.java:440)
         at com.liferay.portlet.CachePortlet.render(CachePortlet.java: 
251)
         at  
org.apache.jsp.html.portal.render_005fportlet_jsp._jspService 
(render_005fportlet_jsp.java:1345)
         at org.apache.jasper.runtime.HttpJspBase.service 
(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
         at org.apache.jasper.servlet.JspServletWrapper.service 
(JspServletWrapper.java:388)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile 
(JspServlet.java:320)

whenever I view a page and the create account functionality isn't  
available.

Any ideas what might be wrong?  Maybe the liferay people would like  
to help???

thanks
david jencks

>
>
> Good luck with this, I am following it with great interest,  
> unfortunately I have a buzzy time with work at the moment else I  
> would have joined in this endeavour.
>
> regards
>    peter petersson
>
> Jim Foster wrote:
>>
>> djencks wrote:
>>
>>> On Mar 3, 2008, at 8:33 AM, Jim Foster wrote:
>>>
>>>
>>>> djencks wrote:
>>>>
>>>>> On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:
>>>>>
>>>>>
>>>>>> djencks wrote:
>>>>>>
>>>>>>> Your plan works for me.  I jar'ed up my sample and attached it
>>>>>>> to the
>>>>>>> wiki page.  Could you see if you can detect the relevant
>>>>>>> difference?
>>>>>>>
>>>>>>> thanks
>>>>>>> david jencks
>>>>>>>
>>>>>>>  <snip>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> I think I see the point of confusion.
>>>>>>
>>>>>> In your doc, you have this:
>>>>>>
>>>>>> [3] Repackage the liferay war
>>>>>>
>>>>>> mvn archetype:create \
>>>>>>   -DarchetypeGroupId=org.apache.maven.archetypes \
>>>>>>   -DarchetypeArtifactId=maven-archetype-webapp \
>>>>>>   -DarchetypeVersion=1.0 \
>>>>>>   -DgroupId=com.liferay \
>>>>>>   -DartifactId=liferay-portal-lesslibs \
>>>>>>   -Dversion=4.4.1-NOLIB-SNAPSHOT
>>>>>> cd liferay-portal
>>>>>> rm -rf src
>>>>>>
>>>>>>
>>>>>> Shouldn't that artifactId be "liferay-portal"?
>>>>>>
>>>>>>
>>>>> I don't think so.  Previously we've installed the liferay  
>>>>> portal war
>>>>> from liferay in the local maven repo as com.liferay/liferay- 
>>>>> portal/
>>>>> 4.4.1/war so we don't want another project claiming to generate  
>>>>> the
>>>>> same artifactId.  In fact I tried this at first but just having a
>>>>> different version between input and output doesn't work -- maven
>>>>> objects.
>>>>>
>>>>>
>>>> Hi David,
>>>>
>>>> I just don't see how in your documentation you can have this:
>>>>
>>>>   mvn archetype:create \
>>>>     ...
>>>>     -DartifactId=liferay-portal-lesslibs \
>>>>     ...
>>>>
>>>> followed by this:
>>>>
>>>>   cd liferay-portal
>>>>
>>>>
>>>> There isn't a directory liferay-portal, but there is
>>>> liferay-portal-lesslibs, so one or the other must be out of sync.
>>>>
>>>>
>>>>
>>>> Also, in your liferay-sample.jar, you have the directory structure
>>>>
>>>> liferay-parent/
>>>>                      pom.xml
>>>>
>>>>                      geronimo-jetty-liferay/
>>>>                                                       pom.xml
>>>>
>>>>                      liferay-derby/
>>>>                                         pom.xml
>>>>                                         src/
>>>>                                              main/
>>>>                                                      plan/
>>>>                                                              
>>>> plan.xml
>>>>
>>>>                                                      resources/
>>>>
>>>>                      liferay-jetty/
>>>>                                         pom.xml
>>>>                                         src/
>>>>                                              main/
>>>>                                                      plan/
>>>>                                                              
>>>> plan.xml
>>>>
>>>>                                                      resources/
>>>>
>>>>                      liferay-portal/
>>>>                                          pom.xml
>>>>
>>>>
>>>>
>>>> Where did the directory liferay-portal-lesslibs go?
>>>>
>>>> And where did directory liferay-portal come from?
>>>>
>>> This is what happens without proper review :-).  I started with
>>> calling my repackaged liferay liferay-portal but the duplicate
>>> artifactId didn't work.  I then missed updating the name change in a
>>> lot of places.
>>>
>>> Hopefully it's fixed now....  waiting for your review...
>>>
>>> thanks
>>> david jencks
>>>
>>>
>>>
>>
>> Hi David,
>>
>> I am glad that this is turning out to be a productive discussion.
>>
>> I have some more review notes for you.
>>
>> For reference:
>>
>>   Constructing a special-purpose server using maven
>>
>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
>> +special-purpose+server+using+maven
>>
>>     [1] Preparation – find the artifacts
>>     [2] Set up a parent maven project
>>     [3] Repackage the liferay war
>>     [4] Build a database plugin
>>     [5] Build the liferay war plugin
>>     [6] Build an assembly
>>     [7] Run the project
>>
>>
>> Note:
>> In the following, I use the term "baseline" to mean your liferay- 
>> sample.jar
>> attached to your wiki doc, which builds as it should in maven (hence
>> "baseline"), and  "doc" to mean your wiki documentation.
>>
>>
>> [3] baseline has this:
>>
>>       <version>4.4.1</version>
>>
>>     whereas the doc has this:
>>
>>       <version>${liferayVersion}</version>
>>
>>     which produces an artifact not found error (i.e., there is no
>> liferayVersion defined at this point of the process).
>>
>>
>> [5] baseline has this:
>>
>>       <dependency>
>>         <groupId>com.liferay</groupId>
>>         <artifactId>liferay-portal-lesslibs</artifactId>
>>         <version>${liferayVersion}-SNAPSHOT</version>
>>         <type>war</type>
>>         <scope>provided</scope>
>>       </dependency>
>>
>>     whereas the doc has this:
>>
>>       <dependency>
>>         <groupId>com.liferay</groupId>
>>         <artifactId>liferay-portal-lesslibs</artifactId>
>>         <version>${liferayVersion}</version>
>>         <type>war</type>
>>         <scope>provided</scope>
>>       </dependency>
>>
>>     which produces
>>
>>       [INFO]
>> --------------------------------------------------------------------- 
>> ---
>>       [ERROR] BUILD ERROR
>>       [INFO]
>> --------------------------------------------------------------------- 
>> ---
>>       [INFO] Failed to resolve artifact.
>>
>>       GroupId: com.liferay
>>       ArtifactId: liferay-portal-lesslibs
>>       Version: 4.4.1
>>
>>
>> [6] baseline has this:
>>
>>       <properties>
>>         <geronimoVersion>2.1</geronimoVersion>
>>       </properties>
>>
>>     whereas the mvn command generates this:
>>
>>       <properties>
>>         <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>       </properties>
>>
>>     which produces
>>
>>       [INFO]
>> --------------------------------------------------------------------- 
>> ---
>>       [ERROR] BUILD ERROR
>>       [INFO]
>> --------------------------------------------------------------------- 
>> ---
>>       [INFO] Failed to resolve artifact.
>>
>>       GroupId: org.apache.geronimo.assemblies
>>       ArtifactId: assemblies
>>       Version: 2.2-SNAPSHOT
>>
>>       Reason: Unable to download the artifact from any repository
>>
>>
>>
>> [7] I see the same PermGen error.
>>
>> I wonder if we built this using MySQL rather than the system  
>> database (as
>> the Liferay folks intended) we would be in better shape?
>>
>> After all, that database (the MySQL version at least) is just shy  
>> of 60MB,
>> so it stands to reason that we are taxing resources here.
>>
>> I would like to explore this. Could you please guide me?
>>
>> I think I have the basics down of what would be needed, but I  
>> don't think I
>> quite have it all down yet, and I would like to know for sure by  
>> hearing it
>> from you.
>>
>> I would like to see us put this puppy to bed, you folks bless it  
>> for the
>> general public, and move on (Liferay portal is but the first of  
>> several apps
>> I am building on top of Geronimo - details of this project to be  
>> shared as
>> we go).
>>
>>
>>
>> Thanks!
>>
>> Jim
>>
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> I ran into this too.  liferay is using activemq configured with xbean- 
> spring and our copy of activemq does not include xbean or spring in  
> its classloader.  So, you have to make sure liferay uses activemq  
> from its classloader instead of geronimo's classloader.
> 
> In my sample I did this by including this in the liferay-jetty plan:
> 
>      <environment>
>          <inverse-classloading/>
>      </environment>
> 
> which makes that module try to load stuff (such as activemq) from the  
> module before trying parent classloaders such as activemq-broker
> 
> and
> 
> <!-- replaces activemq jar in lib dir -->
>          <dependency>
>              <groupId>org.apache.activemq</groupId>
>              <artifactId>activemq-core</artifactId>
>              <type>jar</type>
>              <version>4.1.1</version>
>          </dependency>
> 
> 
> in liferay-jetty/pom.xml
> 
> and
> 
>                                  <!-- use geronimo dependencies  
> rather than inclusion for published artifacts -->
>                                  <exclude>WEB-INF/lib/activemq.jar</ 
> exclude>
> 
> in liferay-portal-lesslibs to remove the activemq jar from the  
> liferay war itself.
> 
> It looks to me as if all these steps are in the wiki page, but that  
> doesn't mean the process is easy to follow, and maybe I missed  
> something else that is required.... suggestions welcome.
> 
> thanks
> david jencks
> 
> 



Hi David,

As you said, I see that you have made some modifications to your wiki
instructions since I last revisited this, so I walked through all of this
again - from the top.

Following these steps in the wiki:

    [1] Preparation – find the artifacts
    [2] Set up a parent maven project
    [3] Repackage the liferay war
    [4] Build a database plugin
    [5] Build the liferay war plugin
    [6] Build an assembly
    [7] Run the project

All works well until [5].

If one does "mvn clean install" from the liferay-jetty directory after doing
all the modifications for step [5] as outlined in the wiki, one sees the
output listed at the bottom of this post as

    [1] COMMAND LINE:  liferay-parent/liferay-jetty>mvn clean install
  
In particular one see this:

    Missing:
    ----------
    1) com.liferay:portal-service:jar:${liferayVersion}
    2) com.liferay:portal-kernel:jar:${liferayVersion}

    
Not a problem, I thought, I will replace ${liferayVersion} with what
actually exists in my repository, meaning 4.4.1.

The result is what I have listed at the bottom of this post as

    [2] COMMAND LINE:  liferay-parent/liferay-jetty>mvn -e clean install
  
In particular one see this:

    [INFO]
------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO]
------------------------------------------------------------------------
    [INFO] null


I have to admit that I am totally without a clue on this one, though the
trace does point to the exception:

  org.apache.maven.lifecycle.LifecycleExecutionException


What do you think?


Jim



ATTACHMENTS BELOW:

  [1] COMMAND LINE:  liferay-parent/liferay-jetty>mvn clean install
  [2] COMMAND LINE:  liferay-parent/liferay-jetty>mvn -e clean install
    
    
==================================================================
[1] COMMAND LINE:  liferay-parent/liferay-jetty>mvn clean install

    where liferay-jetty/pom.xml contains:
    
    <dependencies>
        ...
        <dependency>
            <groupId>com.liferay</groupId>
            <artifactId>portal-kernel</artifactId>
            <version>${liferayVersion}</version>
        </dependency>
        <dependency>
            <groupId>com.liferay</groupId>
            <artifactId>portal-service</artifactId>
            <version>${liferayVersion}</version>
        </dependency>
        ...
    </dependencies>
==================================================================
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed -
org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
[INFO]    task-segment: [clean, install]
[INFO]
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.geronimo.framework:geronimo-plugin:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-plugin:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-plugin:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:framework:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:framework:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:framework:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-system:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-system:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-system:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-cli:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-cli:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-cli:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-kernel:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-kernel:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-kernel:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-common:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-common:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-common:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-crypto:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-crypto:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-crypto:2.2-SNAPSHOT:
checking for updates from apache.snapshots
Downloading:
http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-tool:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-tool:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-tool:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-service-builder:2.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-service-builder:2.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-service-builder:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deployment:2.2-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deployment:2.2-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deployment:2.2-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-config:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-config:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-config:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] [car:validate-configuration]
log4j:WARN No appenders could be found for logger
(org.codehaus.mojo.pluginsupport.logging.Logging).
log4j:WARN Please initialize the log4j system properly.
[INFO] [car:prepare-plan]
[INFO] Generated:
D:\Geronimo\liferay\liferay-parent\liferay-jetty\target\resources\META-INF\plan.xml
Downloading:
http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-kernel/${liferayVersion}/portal-kernel-${liferayVersion}.pom
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-service/${liferayVersion}/portal-service-${liferayVersion}.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/catalina/6.0.14-G614585/catalina-6.0.14-G614585.pom
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-service/${liferayVersion}/portal-service-${liferayVersion}.jar
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-kernel/${liferayVersion}/portal-kernel-${liferayVersion}.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) com.liferay:portal-service:jar:${liferayVersion}

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=com.liferay
-DartifactId=portal-service \
          -Dversion=${liferayVersion} -Dpackaging=jar -Dfile=/path/to/file
  
  Alternatively, if you host your own repository you can deploy the file
there:
      mvn deploy:deploy-file -DgroupId=com.liferay
-DartifactId=portal-service \
          -Dversion=${liferayVersion} -Dpackaging=jar -Dfile=/path/to/file \
          -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
        2) com.liferay:portal-service:jar:${liferayVersion}

2) com.liferay:portal-kernel:jar:${liferayVersion}

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=com.liferay
-DartifactId=portal-kernel \
          -Dversion=${liferayVersion} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=com.liferay -DartifactId=portal-kernel \
          -Dversion=${liferayVersion} -Dpackaging=jar -Dfile=/path/to/file \
           -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
        2) com.liferay:portal-kernel:jar:${liferayVersion}

----------
2 required artifacts are missing.

for artifact:
  org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 28 seconds
[INFO] Finished at: Fri Mar 14 04:03:00 MST 2008
[INFO] Final Memory: 40M/127M
[INFO]
------------------------------------------------------------------------



==================================================================
[2] COMMAND LINE:  liferay-parent/liferay-jetty>mvn -e clean install

    where liferay-jetty/pom.xml contains:
    
    <dependencies>
        ...
        <dependency>
            <groupId>com.liferay</groupId>
            <artifactId>portal-kernel</artifactId>
            <version>4.4.1</version>
        </dependency>
        <dependency>
            <groupId>com.liferay</groupId>
            <artifactId>portal-service</artifactId>
            <version>4.4.1</version>
        </dependency>
        ...
    </dependencies>
==================================================================

+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed -
org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
[INFO]    task-segment: [clean, install]
[INFO]
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory
D:\Geronimo\liferay\liferay-parent\liferay-jetty\target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [car:validate-configuration]
log4j:WARN No appenders could be found for logger
(org.codehaus.mojo.pluginsupport.logging.Logging).
log4j:WARN Please initialize the log4j system properly.
[INFO] [car:prepare-plan]
[INFO] Generated:
D:\Geronimo\liferay\liferay-parent\liferay-jetty\target\resources\META-INF\plan.xml
Downloading:
http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-kernel/4.4.1/portal-kernel-4.4.1.pom
Downloading:
http://repo1.maven.org/maven2/com/liferay/portal-service/4.4.1/portal-service-4.4.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/catalina/6.0.14-G614585/catalina-6.0.14-G614585.pom
[INFO] [car:package]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null

[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        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
        at
org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:137)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
        ... 16 more
Caused by: java.lang.NullPointerException
        at
org.codehaus.mojo.pluginsupport.MojoSupport.fillMissingArtifactVersion(MojoSupport.java:342)
        at
org.codehaus.mojo.pluginsupport.MojoSupport.createArtifact(MojoSupport.java:216)
        at
org.codehaus.mojo.pluginsupport.MojoSupport.getArtifact(MojoSupport.java:258)
        at
org.apache.geronimo.mavenplugins.car.PackageMojo.doExecute(PackageMojo.java:222)
        at
org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:122)
        ... 18 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14 seconds
[INFO] Finished at: Fri Mar 14 04:47:10 MST 2008
[INFO] Final Memory: 42M/127M
[INFO]
------------------------------------------------------------------------



-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p16048064.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
I ran into this too.  liferay is using activemq configured with xbean- 
spring and our copy of activemq does not include xbean or spring in  
its classloader.  So, you have to make sure liferay uses activemq  
from its classloader instead of geronimo's classloader.

In my sample I did this by including this in the liferay-jetty plan:

     <environment>
         <inverse-classloading/>
     </environment>

which makes that module try to load stuff (such as activemq) from the  
module before trying parent classloaders such as activemq-broker

and

<!-- replaces activemq jar in lib dir -->
         <dependency>
             <groupId>org.apache.activemq</groupId>
             <artifactId>activemq-core</artifactId>
             <type>jar</type>
             <version>4.1.1</version>
         </dependency>


in liferay-jetty/pom.xml

and

                                 <!-- use geronimo dependencies  
rather than inclusion for published artifacts -->
                                 <exclude>WEB-INF/lib/activemq.jar</ 
exclude>

in liferay-portal-lesslibs to remove the activemq jar from the  
liferay war itself.

It looks to me as if all these steps are in the wiki page, but that  
doesn't mean the process is easy to follow, and maybe I missed  
something else that is required.... suggestions welcome.

thanks
david jencks

On Mar 13, 2008, at 9:12 AM, Jim Foster wrote:

>
>
> Kevan Miller wrote:
>>
>>
>> On Mar 7, 2008, at 12:12 PM, Jim Foster wrote:
>>
>>>>
>>>> Hi Jim,
>>>> There are a lot of knobs and switches.
>>
>> ...
>>
>> [snip]
>>
>>
>
>
> Hi Kevan,
>
> I took yours, David's and Peter's suggestions and have been working  
> on this
> a fair bit this week, but I seem to be at a point where I am  
> chasing my
> tail, so I need to ask to bend the dev team's ear a bit more.
>
> The common denominator that I run into appears to be either
> lifecycle-related, or associated with creation of gbeans,  
> themselves. I
> don't have enough insight yet into Geronimo's core architecture to  
> say for
> sure.
>
> For example, the first error in the log file looks like this:
>
> java.lang.ExceptionInInitializerError
> 	at
> com.liferay.portal.velocity.LiferayResourceCache.get 
> (LiferayResourceCache.java:43)
>
>
> I have included the latest (and lengthy) log file at the end of  
> this post.
>
> Any advice would be most appreciated!
>
>
> Jim
>
>
> START ATTACHMENT - geronimo-jetty-liferay-1.0-SNAPSHOT/var/log/ 
> geronimo.txt
> ---------------------------------------------------------------------- 
> --------------------
> 07:09:14,468 INFO  [Log4jService]
> ----------------------------------------------
> 07:09:14,468 INFO  [Log4jService] Started Logging Service
> 07:09:14,468 INFO  [Log4jService] Runtime Information:
> 07:09:14,468 INFO  [Log4jService]   Install Directory =
> D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT
> 07:09:14,468 INFO  [Log4jService]   JVM in use = Sun Microsystems  
> Inc. Java
> 1.5.0_15
> 07:09:14,468 INFO  [Log4jService] Java Information:
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.runtime.name]  =
> Java(TM) 2 Runtime Environment, Standard Edition
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.runtime.version]
> = 1.5.0_15-b04
> 07:09:14,468 INFO  [Log4jService]   System property  
> [os.name]             =
> Windows XP
> 07:09:14,468 INFO  [Log4jService]   System property  
> [os.version]          =
> 5.1
> 07:09:14,468 INFO  [Log4jService]   System property  
> [sun.os.patch.level]  =
> Service Pack 2
> 07:09:14,468 INFO  [Log4jService]   System property  
> [os.arch]             =
> x86
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.class.version]  =
> 49.0
> 07:09:14,468 INFO  [Log4jService]   System property  
> [locale]              =
> en_US
> 07:09:14,468 INFO  [Log4jService]   System property  
> [unicode.encoding]    =
> UnicodeLittle
> 07:09:14,468 INFO  [Log4jService]   System property  
> [file.encoding]       =
> Cp1252
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.vm.name]        =
> Java HotSpot(TM) Client VM
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.vm.vendor]      =
> Sun Microsystems Inc.
> 07:09:14,468 INFO  [Log4jService]   System property  
> [java.vm.version]     =
> 1.5.0_15-b04
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.vm.info]        =
> mixed mode
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.home]           =
> D:\Languages\Java\JDK5\jre
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.classpath]      =
> null
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.library.path]   =
> D:\Languages\Java\JDK5\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C: 
> \WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Apache 
> \Maven2\maven-2.0.7\bin;D:\Apache\Ant\ant-1.7.0\bin;D:\Languages 
> \Java\bin;I:\Database
> Tools\MySQL\MySQL Server\bin
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.endorsed.dirs]  =
> D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\lib\endorsed;D: 
> \Languages\Java\JDK5\jre\lib\endorsed
> 07:09:14,484 INFO  [Log4jService]   System property  
> [java.ext.dirs]       =
> D:\Languages\Java\JDK5\jre\lib\ext
> 07:09:14,484 INFO  [Log4jService]   System property  
> [sun.boot.class.path] =
> D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\lib\endorsed\yoko- 
> rmi-spec-1.0-r615303.jar;D:\Geronimo\geronimo-jetty-liferay-1.0- 
> SNAPSHOT\lib\endorsed\yoko-spec-corba-1.0-r615303.jar;D:\Languages 
> \Java\JDK5\jre\lib\rt.jar;D:\Languages\Java\JDK5\jre\lib\i18n.jar;D: 
> \Languages\Java\JDK5\jre\lib\sunrsasign.jar;D:\Languages\Java\JDK5 
> \jre\lib\jsse.jar;D:\Languages\Java\JDK5\jre\lib\jce.jar;D: 
> \Languages\Java\JDK5\jre\lib\charsets.jar;D:\Languages\Java\JDK5\jre 
> \classes
> 07:09:14,484 INFO  [Log4jService]
> ----------------------------------------------
> 07:09:24,734 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.framework/rmi-naming/2.1/car? 
> ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/ 
> car,j2eeType=Context,name=JavaCompContext
> at name java:comp
> 07:09:24,734 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.framework/rmi-naming/2.1/car? 
> ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/ 
> car,j2eeType=Context,name=JavaContext
> at name java:
> 07:09:24,734 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.framework/rmi-naming/2.1/car? 
> ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/ 
> car,j2eeType=Context,name=GeronimoContext
> at name ger:
> 07:09:25,015 INFO  [MailGBean] JavaMail session bound to ger:/ 
> MailSession
> 07:09:26,406 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/javamail/2.1/car? 
> ServiceModule=org.apache.geronimo.configs/javamail/2.1/ 
> car,j2eeType=JavaMailResource,name=mail/MailSession
> at name
> org.apache.geronimo.configs/javamail/JavaMailResource/mail/MailSession
> 07:09:26,406 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/transaction/2.1/car? 
> ServiceModule=org.apache.geronimo.configs/transaction/2.1/ 
> car,j2eeType=Context,name=ResourceBindings
> at name jca:
> 07:09:28,781 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/system-database/2.1/car? 
> J2EEApplication=null,JCAConnectionFactory=SystemDatasource,JCAResource 
> =org.apache.geronimo.configs/system-database/2.1/ 
> car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/ 
> car,ResourceAdapterModule=org.apache.geronimo.configs/system- 
> database/2.1/ 
> car,j2eeType=JCAManagedConnectionFactory,name=SystemDatasource
> at name
> org.apache.geronimo.configs/system-database/ 
> JCAManagedConnectionFactory/SystemDatasource
> 07:09:29,703 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/system-database/2.1/car? 
> J2EEApplication=null,JCAConnectionFactory=NoTxDatasource,JCAResource=o 
> rg.apache.geronimo.configs/system-database/2.1/ 
> car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/ 
> car,ResourceAdapterModule=org.apache.geronimo.configs/system- 
> database/2.1/ 
> car,j2eeType=JCAManagedConnectionFactory,name=NoTxDatasource
> at name
> org.apache.geronimo.configs/system-database/ 
> JCAManagedConnectionFactory/NoTxDatasource
> 07:09:30,171 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car? 
> J2EEApplication=null,JCAConnectionFactory=jdbc/ 
> LiferayPool,JCAResource=org.apache.geronimo.plugins/liferay-derby/ 
> 1.0-SNAPSHOT/car,ResourceAdapter=org.apache.geronimo.plugins/ 
> liferay-derby/1.0-SNAPSHOT/ 
> car,ResourceAdapterModule=org.apache.geronimo.plugins/liferay-derby/ 
> 1.0-SNAPSHOT/car,j2eeType=JCAManagedConnectionFactory,name=jdbc/ 
> LiferayPool
> at name
> org.apache.geronimo.plugins/liferay-derby/ 
> JCAManagedConnectionFactory/jdbc/LiferayPool
> 07:09:33,562 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/activemq-ra/2.1/car? 
> J2EEApplication=null,JCAConnectionFactory=DefaultActiveMQConnectionFac 
> tory,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/ 
> car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/ 
> car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/ 
> 2.1/ 
> car,j2eeType=JCAManagedConnectionFactory,name=DefaultActiveMQConnectio 
> nFactory
> at name
> org.apache.geronimo.configs/activemq-ra/JCAManagedConnectionFactory/ 
> DefaultActiveMQConnectionFactory
> 07:09:33,578 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/activemq-ra/2.1/car? 
> J2EEApplication=null,JCAResource=org.apache.geronimo.configs/ 
> activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/ 
> activemq-ra/2.1/ 
> car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/ 
> 2.1/car,j2eeType=JCAAdminObject,name=MDBTransferBeanOutQueue
> at name
> org.apache.geronimo.configs/activemq-ra/JCAAdminObject/ 
> MDBTransferBeanOutQueue
> 07:09:33,578 INFO  [KernelContextGBean] bound gbean
> org.apache.geronimo.configs/activemq-ra/2.1/car? 
> J2EEApplication=null,JCAResource=org.apache.geronimo.configs/ 
> activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/ 
> activemq-ra/2.1/ 
> car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/ 
> 2.1/car,j2eeType=JCAAdminObject,name=SendReceiveQueue
> at name
> org.apache.geronimo.configs/activemq-ra/JCAAdminObject/ 
> SendReceiveQueue
> 07:09:33,937 INFO  [log] Logging to
> org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via
> org.mortbay.log.Slf4jLog
> 07:09:33,937 INFO  [log] jetty-6.1.7
> 07:09:34,000 INFO  [log] Opened
> D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\var\log 
> \jetty_2008_03_13.log
> 07:09:34,312 INFO  [log] Started SelectChannelConnector@0.0.0.0:8080
> 07:09:34,328 INFO  [log] AJP13 is not a secure protocol. Please  
> protect port
> 8009
> 07:09:34,328 INFO  [log] Started Ajp13SocketConnector@0.0.0.0:8009
> 07:09:34,812 INFO  [log] Started
> GeronimoSelectChannelSSLListener@0.0.0.0:8443
> 07:09:42,000 ERROR [log] failed Secure MainServlet Filter
> java.lang.ExceptionInInitializerError
> 	at
> com.liferay.portal.velocity.LiferayResourceCache.get 
> (LiferayResourceCache.java:43)
> 	at
> org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource 
> (ResourceManagerImpl.java:288)
> 	at
> org.apache.velocity.runtime.RuntimeInstance.getTemplate 
> (RuntimeInstance.java:1102)
> 	at
> org.apache.velocity.runtime.RuntimeInstance.getTemplate 
> (RuntimeInstance.java:1077)
> 	at
> org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro 
> (VelocimacroFactory.java:196)
> 	at
> org.apache.velocity.runtime.RuntimeInstance.init 
> (RuntimeInstance.java:251)
> 	at
> org.apache.velocity.runtime.RuntimeSingleton.init 
> (RuntimeSingleton.java:113)
> 	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
> 	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
> 	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
> 	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
> 	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
> 	at org.mortbay.jetty.servlet.FilterHolder.doStart 
> (FilterHolder.java:97)
> 	at
> org.apache.geronimo.jetty6.JettyFilterHolder 
> $InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
> 	at
> org.apache.geronimo.jetty6.JettyFilterHolder 
> $InternalFilterHolder.access$100(JettyFilterHolder.java:70)
> 	at
> org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder 
> $2.lifecycleMethod(JettyFilterHolder.java:107)
> 	at
> org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleC 
> ommand(AbstractImmutableHandler.java:62)
> 	at
> org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleC 
> ommand(ThreadClassloaderHandler.java:57)
> 	at
> org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleC 
> ommand(AbstractImmutableHandler.java:60)
> 	at
> org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCom 
> mand(InstanceContextHandler.java:81)
> 	at
> org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleC 
> ommand(AbstractImmutableHandler.java:60)
> 	at
> org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCom 
> mand(UserTransactionHandler.java:63)
> 	at
> org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleC 
> ommand(AbstractImmutableHandler.java:60)
> 	at
> org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCo 
> mmand(ComponentContextHandler.java:57)
> 	at
> org.apache.geronimo.jetty6.JettyFilterHolder 
> $InternalFilterHolder.doStart(JettyFilterHolder.java:110)
> 	at org.mortbay.component.AbstractLifeCycle.start 
> (AbstractLifeCycle.java:40)
> 	at
> org.apache.geronimo.jetty6.JettyFilterHolder.doStart 
> (JettyFilterHolder.java:55)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance 
> (GBeanInstance.java:998)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( 
> GBeanInstanceState.java:268)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
> (GBeanInstanceState.java:102)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstance.start 
> (GBeanInstance.java:541)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart 
> (GBeanDependency.java:111)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget 
> (GBeanDependency.java:146)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running 
> (GBeanDependency.java:120)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEven 
> t(BasicLifecycleMonitor.java:176)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300 
> (BasicLifecycleMonitor.java:44)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor 
> $RawLifecycleBroadcaster.fireRunningEvent 
> (BasicLifecycleMonitor.java:254)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( 
> GBeanInstanceState.java:294)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
> (GBeanInstanceState.java:102)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstance.start 
> (GBeanInstance.java:541)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart 
> (GBeanDependency.java:111)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget 
> (GBeanDependency.java:146)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running 
> (GBeanDependency.java:120)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEven 
> t(BasicLifecycleMonitor.java:176)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300 
> (BasicLifecycleMonitor.java:44)
> 	at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor 
> $RawLifecycleBroadcaster.fireRunningEvent 
> (BasicLifecycleMonitor.java:254)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( 
> GBeanInstanceState.java:294)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
> (GBeanInstanceState.java:102)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive 
> (GBeanInstanceState.java:124)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive 
> (GBeanInstance.java:555)
> 	at
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean 
> (BasicKernel.java:379)
> 	at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration 
> GBeans(ConfigurationUtil.java:456)
> 	at
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start 
> (KernelConfigurationManager.java:187)
> 	at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf 
> iguration(SimpleConfigurationManager.java:534)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at
> sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
> 	at
> sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke 
> (ReflectionMethodInvoker.java:34)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke 
> (GBeanOperation.java:124)
> 	at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke 
> (GBeanInstance.java:832)
> 	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke 
> (RawInvoker.java:57)
> 	at
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke 
> (RawOperationInvoker.java:35)
> 	at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept 
> (ProxyMethodInterceptor.java:96)
> 	at
> org.apache.geronimo.kernel.config.EditableConfigurationManager$ 
> $EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
> 	at
> org.apache.geronimo.system.main.EmbeddedDaemon.doStartup 
> (EmbeddedDaemon.java:156)
> 	at
> org.apache.geronimo.system.main.EmbeddedDaemon.execute 
> (EmbeddedDaemon.java:78)
> 	at
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main 
> (MainConfigurationBootstrapper.java:45)
> 	at org.apache.geronimo.cli.AbstractCLI.executeMain 
> (AbstractCLI.java:67)
> 	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
> Caused by:  
> org.springframework.beans.factory.CannotLoadBeanClassException:
> Error loading class [org.apache.activemq.xbean.BrokerFactoryBean]  
> for bean
> with name 'org.apache.activemq.Broker' defined in class path resource
> [META-INF/activemq-spring-jms.xml]: problem with class file or  
> dependent
> class; nested exception is java.lang.NoClassDefFoundError:
> org/springframework/beans/factory/FactoryBean
> 	at
> org.springframework.beans.factory.support.AbstractBeanFactory.resolveB 
> eanClass(AbstractBeanFactory.java:1163)
> 	at
> <snip>

Geronimo failure at startup - unable to bind rmi://0.0.0.0:1099/JMXConnector, UnknownHostException etc.

Posted by Pete Robinson <pe...@gmx.de>.
Hello All,

I'm a Geronimo / Linux Newbie.

I was having a number of problems with geronimo 2+ running on a Linux
installation on a laptop I've justed installed with SUSE 10.2.

I couldn't get the server to start. I kept getting various problems
around binding, although I have the same setup on another machine and it
works fine.

Example:

java.io.IOException: Cannot bind to URL [rmi://0.0.0.0:1099/JMXConnector]:

or...

05:03:56,173 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state:
abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car?ServiceModule=org.apache.geronimo.configs/j2ee-security/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer"
java.net.UnknownHostException: Vigor12: Vigor12
	at java.net.InetAddress.getLocalHost(InetAddress.java:1346)
	at
org.activeio.net.SocketStreamChannelFactory.bindStreamChannel(SocketStreamChannelFactory.java:93)

Basically, I couldn't get Geronimo to start. A number of people have
experienced the same as far as I can gather from forums I found.

I diagnosed the cause of my problem and would like to share the
workaround I implemented.

Diagnosis

Scenario: I am sitting in a wireless environment.

When I attach the laptop to my router, the server starts fine. When I
remove the cable and restart the network geronimo won't start. So,
geronimo was actually having problems locating the JMXConnector.

Solution/Work around

In the {geronimo-home-directory}/config/config-substitutions.properties,
I replaced the line:

PlanServerHostname=0.0.0.0

with

PlanServerHostname=127.0.0.1

Apparently in my wireless only environment, geronimo was unable to
locate JMXConnector. Even though I could ping 0.0.0.0.

Well, I hope that helps some poor guy who searches for daysin vain  for
a solution like I did. If not, I only wasted 15 minutes.

Cheers,
Pete


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

Kevan Miller wrote:
> 
> 
> On Mar 7, 2008, at 12:12 PM, Jim Foster wrote:
> 
>>>
>>> Hi Jim,
>>> There are a lot of knobs and switches. 
> 
> ...
> 
> [snip]
> 
> 


Hi Kevan,

I took yours, David's and Peter's suggestions and have been working on this
a fair bit this week, but I seem to be at a point where I am chasing my
tail, so I need to ask to bend the dev team's ear a bit more.

The common denominator that I run into appears to be either
lifecycle-related, or associated with creation of gbeans, themselves. I
don't have enough insight yet into Geronimo's core architecture to say for
sure.

For example, the first error in the log file looks like this:

java.lang.ExceptionInInitializerError
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)


I have included the latest (and lengthy) log file at the end of this post.

Any advice would be most appreciated!


Jim


START ATTACHMENT - geronimo-jetty-liferay-1.0-SNAPSHOT/var/log/geronimo.txt
------------------------------------------------------------------------------------------
07:09:14,468 INFO  [Log4jService]
----------------------------------------------
07:09:14,468 INFO  [Log4jService] Started Logging Service
07:09:14,468 INFO  [Log4jService] Runtime Information:
07:09:14,468 INFO  [Log4jService]   Install Directory =
D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT
07:09:14,468 INFO  [Log4jService]   JVM in use = Sun Microsystems Inc. Java
1.5.0_15
07:09:14,468 INFO  [Log4jService] Java Information:
07:09:14,468 INFO  [Log4jService]   System property [java.runtime.name]  =
Java(TM) 2 Runtime Environment, Standard Edition
07:09:14,468 INFO  [Log4jService]   System property [java.runtime.version] 
= 1.5.0_15-b04
07:09:14,468 INFO  [Log4jService]   System property [os.name]             =
Windows XP
07:09:14,468 INFO  [Log4jService]   System property [os.version]          =
5.1
07:09:14,468 INFO  [Log4jService]   System property [sun.os.patch.level]  =
Service Pack 2
07:09:14,468 INFO  [Log4jService]   System property [os.arch]             =
x86
07:09:14,468 INFO  [Log4jService]   System property [java.class.version]  =
49.0
07:09:14,468 INFO  [Log4jService]   System property [locale]              =
en_US
07:09:14,468 INFO  [Log4jService]   System property [unicode.encoding]    =
UnicodeLittle
07:09:14,468 INFO  [Log4jService]   System property [file.encoding]       =
Cp1252
07:09:14,468 INFO  [Log4jService]   System property [java.vm.name]        =
Java HotSpot(TM) Client VM
07:09:14,468 INFO  [Log4jService]   System property [java.vm.vendor]      =
Sun Microsystems Inc.
07:09:14,468 INFO  [Log4jService]   System property [java.vm.version]     =
1.5.0_15-b04
07:09:14,484 INFO  [Log4jService]   System property [java.vm.info]        =
mixed mode
07:09:14,484 INFO  [Log4jService]   System property [java.home]           =
D:\Languages\Java\JDK5\jre
07:09:14,484 INFO  [Log4jService]   System property [java.classpath]      =
null
07:09:14,484 INFO  [Log4jService]   System property [java.library.path]   =
D:\Languages\Java\JDK5\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Apache\Maven2\maven-2.0.7\bin;D:\Apache\Ant\ant-1.7.0\bin;D:\Languages\Java\bin;I:\Database
Tools\MySQL\MySQL Server\bin
07:09:14,484 INFO  [Log4jService]   System property [java.endorsed.dirs]  =
D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\lib\endorsed;D:\Languages\Java\JDK5\jre\lib\endorsed
07:09:14,484 INFO  [Log4jService]   System property [java.ext.dirs]       =
D:\Languages\Java\JDK5\jre\lib\ext
07:09:14,484 INFO  [Log4jService]   System property [sun.boot.class.path] =
D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\lib\endorsed\yoko-rmi-spec-1.0-r615303.jar;D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\lib\endorsed\yoko-spec-corba-1.0-r615303.jar;D:\Languages\Java\JDK5\jre\lib\rt.jar;D:\Languages\Java\JDK5\jre\lib\i18n.jar;D:\Languages\Java\JDK5\jre\lib\sunrsasign.jar;D:\Languages\Java\JDK5\jre\lib\jsse.jar;D:\Languages\Java\JDK5\jre\lib\jce.jar;D:\Languages\Java\JDK5\jre\lib\charsets.jar;D:\Languages\Java\JDK5\jre\classes
07:09:14,484 INFO  [Log4jService]
----------------------------------------------
07:09:24,734 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=JavaCompContext
at name java:comp
07:09:24,734 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=JavaContext
at name java:
07:09:24,734 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=GeronimoContext
at name ger:
07:09:25,015 INFO  [MailGBean] JavaMail session bound to ger:/MailSession
07:09:26,406 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/javamail/2.1/car?ServiceModule=org.apache.geronimo.configs/javamail/2.1/car,j2eeType=JavaMailResource,name=mail/MailSession
at name
org.apache.geronimo.configs/javamail/JavaMailResource/mail/MailSession
07:09:26,406 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/transaction/2.1/car?ServiceModule=org.apache.geronimo.configs/transaction/2.1/car,j2eeType=Context,name=ResourceBindings
at name jca:
07:09:28,781 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/system-database/2.1/car?J2EEApplication=null,JCAConnectionFactory=SystemDatasource,JCAResource=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/system-database/2.1/car,j2eeType=JCAManagedConnectionFactory,name=SystemDatasource
at name
org.apache.geronimo.configs/system-database/JCAManagedConnectionFactory/SystemDatasource
07:09:29,703 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/system-database/2.1/car?J2EEApplication=null,JCAConnectionFactory=NoTxDatasource,JCAResource=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/system-database/2.1/car,j2eeType=JCAManagedConnectionFactory,name=NoTxDatasource
at name
org.apache.geronimo.configs/system-database/JCAManagedConnectionFactory/NoTxDatasource
07:09:30,171 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car?J2EEApplication=null,JCAConnectionFactory=jdbc/LiferayPool,JCAResource=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,ResourceAdapter=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,ResourceAdapterModule=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,j2eeType=JCAManagedConnectionFactory,name=jdbc/LiferayPool
at name
org.apache.geronimo.plugins/liferay-derby/JCAManagedConnectionFactory/jdbc/LiferayPool
07:09:33,562 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAManagedConnectionFactory,name=DefaultActiveMQConnectionFactory
at name
org.apache.geronimo.configs/activemq-ra/JCAManagedConnectionFactory/DefaultActiveMQConnectionFactory
07:09:33,578 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAAdminObject,name=MDBTransferBeanOutQueue
at name
org.apache.geronimo.configs/activemq-ra/JCAAdminObject/MDBTransferBeanOutQueue
07:09:33,578 INFO  [KernelContextGBean] bound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAAdminObject,name=SendReceiveQueue
at name
org.apache.geronimo.configs/activemq-ra/JCAAdminObject/SendReceiveQueue
07:09:33,937 INFO  [log] Logging to
org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via
org.mortbay.log.Slf4jLog
07:09:33,937 INFO  [log] jetty-6.1.7
07:09:34,000 INFO  [log] Opened
D:\Geronimo\geronimo-jetty-liferay-1.0-SNAPSHOT\var\log\jetty_2008_03_13.log
07:09:34,312 INFO  [log] Started SelectChannelConnector@0.0.0.0:8080
07:09:34,328 INFO  [log] AJP13 is not a secure protocol. Please protect port
8009
07:09:34,328 INFO  [log] Started Ajp13SocketConnector@0.0.0.0:8009
07:09:34,812 INFO  [log] Started
GeronimoSelectChannelSSLListener@0.0.0.0:8443
07:09:42,000 ERROR [log] failed Secure MainServlet Filter
java.lang.ExceptionInInitializerError
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
	at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
	at
org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
	at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
	at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.apache.geronimo.jetty6.JettyFilterHolder.doStart(JettyFilterHolder.java:55)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Error loading class [org.apache.activemq.xbean.BrokerFactoryBean] for bean
with name 'org.apache.activemq.Broker' defined in class path resource
[META-INF/activemq-spring-jms.xml]: problem with class file or dependent
class; nested exception is java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
	at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
	at
com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
	at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
	at
com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
	at
com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
	... 70 more
Caused by: java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:308)
	at java.security.AccessController.doPrivileged(Native Method)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:260)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:470)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:456)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
	at
org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
	... 86 more
07:09:42,015 ERROR [log] Nested in java.lang.ExceptionInInitializerError:
org.springframework.beans.factory.CannotLoadBeanClassException: Error
loading class [org.apache.activemq.xbean.BrokerFactoryBean] for bean with
name 'org.apache.activemq.Broker' defined in class path resource
[META-INF/activemq-spring-jms.xml]: problem with class file or dependent
class; nested exception is java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
	at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
	at
com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
	at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
	at
com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
	at
com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
	at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
	at
org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
	at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
	at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.apache.geronimo.jetty6.JettyFilterHolder.doStart(JettyFilterHolder.java:55)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:308)
	at java.security.AccessController.doPrivileged(Native Method)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:260)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:470)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:456)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
	at
org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
	... 86 more
07:09:42,015 ERROR [log] Nested in
org.springframework.beans.factory.CannotLoadBeanClassException: Error
loading class [org.apache.activemq.xbean.BrokerFactoryBean] for bean with
name 'org.apache.activemq.Broker' defined in class path resource
[META-INF/activemq-spring-jms.xml]: problem with class file or dependent
class; nested exception is java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean:
java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:308)
	at java.security.AccessController.doPrivileged(Native Method)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:260)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:470)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:456)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
	at
org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
	at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
	at
com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
	at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
	at
com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
	at
com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
	at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
	at
org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
	at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
	at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.apache.geronimo.jetty6.JettyFilterHolder.doStart(JettyFilterHolder.java:55)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:42,375 ERROR [GBeanInstanceState] Error while starting; GBean is now
in the FAILED state:
abstractName="org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car?J2EEApplication=null,WebModule=org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilter,name=Secure%20MainServlet%20Filter"
java.lang.ExceptionInInitializerError
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
	at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
	at
org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
	at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
	at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.apache.geronimo.jetty6.JettyFilterHolder.doStart(JettyFilterHolder.java:55)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Error loading class [org.apache.activemq.xbean.BrokerFactoryBean] for bean
with name 'org.apache.activemq.Broker' defined in class path resource
[META-INF/activemq-spring-jms.xml]: problem with class file or dependent
class; nested exception is java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
	at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
	at
com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
	at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
	at
com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
	at
com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
	... 70 more
Caused by: java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:308)
	at java.security.AccessController.doPrivileged(Native Method)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:260)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:470)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:456)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
	at
org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
	... 86 more
07:09:42,656 WARN  [BasicLifecycleMonitor] Exception occured while notifying
listener
java.lang.ExceptionInInitializerError
	at
com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
	at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
	at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
	at
org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
	at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
	at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
	at org.apache.velocity.app.Velocity.init(Velocity.java:83)
	at com.liferay.portal.events.InitAction.run(InitAction.java:210)
	at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
	at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.apache.geronimo.jetty6.JettyFilterHolder.doStart(JettyFilterHolder.java:55)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Error loading class [org.apache.activemq.xbean.BrokerFactoryBean] for bean
with name 'org.apache.activemq.Broker' defined in class path resource
[META-INF/activemq-spring-jms.xml]: problem with class file or dependent
class; nested exception is java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
	at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
	at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
	at
com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
	at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
	at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
	at
com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
	at
com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
	at
com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
	... 70 more
Caused by: java.lang.NoClassDefFoundError:
org/springframework/beans/factory/FactoryBean
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:308)
	at java.security.AccessController.doPrivileged(Native Method)
	at
org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:260)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:470)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClassInternal(MultiParentClassLoader.java:456)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:498)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407)
	at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
	at
org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
	... 86 more
07:09:42,984 ERROR [log] failed Secure MainServlet Filter
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setFilterMappings(ServletHandler.java:1016)
	at
org.mortbay.jetty.servlet.ServletHandler.addFilterMapping(ServletHandler.java:875)
	at
org.apache.geronimo.jetty6.JettyFilterMapping.<init>(JettyFilterMapping.java:119)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:43,453 ERROR [GBeanInstanceState] Error while starting; GBean is now
in the FAILED state:
abstractName="org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car?J2EEApplication=null,WebFilter=Session%20Id%20Filter,WebModule=org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car,j2eeType=URLWebFilterMapping,name=%22[/%5C*]%22"
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setFilterMappings(ServletHandler.java:1016)
	at
org.mortbay.jetty.servlet.ServletHandler.addFilterMapping(ServletHandler.java:875)
	at
org.apache.geronimo.jetty6.JettyFilterMapping.<init>(JettyFilterMapping.java:119)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:43,593 WARN  [BasicLifecycleMonitor] Exception occured while notifying
listener
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setFilterMappings(ServletHandler.java:1016)
	at
org.mortbay.jetty.servlet.ServletHandler.addFilterMapping(ServletHandler.java:875)
	at
org.apache.geronimo.jetty6.JettyFilterMapping.<init>(JettyFilterMapping.java:119)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:43,843 ERROR [log] failed Secure MainServlet Filter
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at
org.apache.geronimo.jetty6.JettyDefaultServletHolder.<init>(JettyDefaultServletHolder.java:40)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:43,968 ERROR [GBeanInstanceState] Error while starting; GBean is now
in the FAILED state:
abstractName="org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car?J2EEApplication=null,WebModule=org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car,j2eeType=Servlet,name=default"
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at
org.apache.geronimo.jetty6.JettyDefaultServletHolder.<init>(JettyDefaultServletHolder.java:40)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:44,265 WARN  [BasicLifecycleMonitor] Exception occured while notifying
listener
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at
org.apache.geronimo.jetty6.JettyDefaultServletHolder.<init>(JettyDefaultServletHolder.java:40)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:44,484 ERROR [log] failed Secure MainServlet Filter
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:44,609 ERROR [GBeanInstanceState] Error while starting; GBean is now
in the FAILED state:
abstractName="org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car?J2EEApplication=null,WebModule=org.apache.geronimo.plugins/liferay-jetty/1.0-SNAPSHOT/car,j2eeType=Servlet,name=MainServlet"
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:44,750 WARN  [BasicLifecycleMonitor] Exception occured while notifying
listener
java.lang.NoClassDefFoundError
	at com.liferay.filters.secure.SecureFilter.init(SecureFilter.java:73)
	at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.internalDoStart(JettyFilterHolder.java:114)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.access$100(JettyFilterHolder.java:70)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder$2.lifecycleMethod(JettyFilterHolder.java:107)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:62)
	at
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63)
	at
org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:60)
	at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57)
	at
org.apache.geronimo.jetty6.JettyFilterHolder$InternalFilterHolder.doStart(JettyFilterHolder.java:110)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
	at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:589)
	at
org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980)
	at
org.mortbay.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1037)
	at
org.mortbay.jetty.servlet.ServletHandler.addServletMapping(ServletHandler.java:736)
	at
org.apache.geronimo.jetty6.JettyWebAppContext.registerServletHolder(JettyWebAppContext.java:497)
	at
org.apache.geronimo.jetty6.JettyServletHolder.<init>(JettyServletHolder.java:80)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
	at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
	at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
	at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555)
	at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
	at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
	at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:832)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$70b71ad8.startConfiguration(<generated>)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
	at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
	at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
07:09:45,093 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=JavaCompContext
at name java:comp
07:09:45,093 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/transaction/2.1/car?ServiceModule=org.apache.geronimo.configs/transaction/2.1/car,j2eeType=Context,name=ResourceBindings
at name jca:
07:09:45,093 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=GeronimoContext
at name ger:
07:09:45,093 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.framework/rmi-naming/2.1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.1/car,j2eeType=Context,name=JavaContext
at name java:
07:09:53,359 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/javamail/2.1/car?ServiceModule=org.apache.geronimo.configs/javamail/2.1/car,j2eeType=JavaMailResource,name=mail/MailSession
at name
org.apache.geronimo.configs/javamail/JavaMailResource/mail/MailSession
07:09:53,375 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/system-database/2.1/car?J2EEApplication=null,JCAConnectionFactory=SystemDatasource,JCAResource=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/system-database/2.1/car,j2eeType=JCAManagedConnectionFactory,name=SystemDatasource
at name
org.apache.geronimo.configs/system-database/JCAManagedConnectionFactory/SystemDatasource
07:09:53,375 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car?J2EEApplication=null,JCAConnectionFactory=jdbc/LiferayPool,JCAResource=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,ResourceAdapter=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,ResourceAdapterModule=org.apache.geronimo.plugins/liferay-derby/1.0-SNAPSHOT/car,j2eeType=JCAManagedConnectionFactory,name=jdbc/LiferayPool
at name
org.apache.geronimo.plugins/liferay-derby/JCAManagedConnectionFactory/jdbc/LiferayPool
07:09:53,375 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAManagedConnectionFactory,name=DefaultActiveMQConnectionFactory
at name
org.apache.geronimo.configs/activemq-ra/JCAManagedConnectionFactory/DefaultActiveMQConnectionFactory
07:09:53,375 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/system-database/2.1/car?J2EEApplication=null,JCAConnectionFactory=NoTxDatasource,JCAResource=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapter=org.apache.geronimo.configs/system-database/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/system-database/2.1/car,j2eeType=JCAManagedConnectionFactory,name=NoTxDatasource
at name
org.apache.geronimo.configs/system-database/JCAManagedConnectionFactory/NoTxDatasource
07:09:53,406 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAAdminObject,name=SendReceiveQueue
at name
org.apache.geronimo.configs/activemq-ra/JCAAdminObject/SendReceiveQueue
07:09:53,406 INFO  [KernelContextGBean] unbound gbean
org.apache.geronimo.configs/activemq-ra/2.1/car?J2EEApplication=null,JCAResource=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapter=org.apache.geronimo.configs/activemq-ra/2.1/car,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/2.1/car,j2eeType=JCAAdminObject,name=MDBTransferBeanOutQueue
at name
org.apache.geronimo.configs/activemq-ra/JCAAdminObject/MDBTransferBeanOutQueue
------------------------------------------------------------------------------------------
END ATTACHMENT
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p16030465.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Kevan Miller <ke...@gmail.com>.
On Mar 7, 2008, at 12:12 PM, Jim Foster wrote:

>>
>> Hi Jim,
>> There are a lot of knobs and switches. However, you can cause as much
>> harm as good trying to fine tune their settings. My advice to you is
>> to keep things as simple as possible until you know you have a  
>> problem.
>>
>
>
> Hi Kevan,
>
> Simple is good.
>
> I will certainly take your advice. I just know from experience that  
> it best
> to put a lasso around potential system-related problems like this  
> early in
> the game...if not they may assume an exponential flight path.

Understood. IMO, this is a like optimizing code execution. Spend some  
time with algorithmic analysis, but don't spend too much time trying  
to optimize arbitrary code paths. Wait until you have actual  
performance data that indicates where you will get the most bang for  
your buck. Measure, then optimize.

You may find the following blog useful -- http://kirk.blog-city.com/advice_on_jvm_heap_tuning_dont_touch_that_dial.htm

>
>
>
>
> Kevan Miller wrote:
>>
>> The JVM can print GC statistics to STDOUT. Often I find this
>> sufficient for getting a broad overview of what's going on. You can
>> also configure the JVM to create a heapdump on OOME conditions. If  
>> you
>> have a memory leak, you can then analyze the heapdump using a variety
>> of tools (I like YourKit). There are a number of tools which can also
>> perform further analysis on runtime data (memory allocations, method
>> execution, etc).
>>
>> Something like the following should work  (set max heap and max perm
>> to suit your environment):
>>
>> -Xmx512m -XX:MaxPermSize=128m -verbose:gc -XX:+PrintGCDetails -XX:
>> +HeapDumpOnOutOfMemoryError
>>
>> --kevan
>>
>>
>
>
> This is good to know.
>
> It's probably too early for me to be thinking of dropping $500 for a
> profiler like YourKit, but just leveraging the command line options  
> as you
> suggest should help in keeping things from getting out of control.
>
> I appreciate your sharing this.  Thanks!

Heh.

/me confesses that I use YourKit under an Open Source license (e.g.  
free). I also mainly use it for memory leak diagnosis...

There are free tools that will analyze the GC statistics. However, I  
generally just eyeball things until I'm really getting serious about  
tuning... HPjtune is pretty good -- http://www.hp.com/products1/unix/java/java2/hpjtune/

--kevan

--kevan

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

Kevan Miller wrote:
> 
> 
> On Mar 6, 2008, at 10:37 AM, Jim Foster wrote:
> 
>>
>> Hi Peter,
>>
>> Thank you for this info!
>>
>> I took your suggestion and brought myself up to speed on PermGen,  
>> and a good
>> bit of all things related to Java.lang.OutOfMemoryError.
>>
>> All I can say is that there's certainly a lot more to fine-tuning the
>> classloading going on behind the scenes than one would first imagine.
>>
>> This brings up another question: How do you folks manage this?
>>
>> What tools would you recommend that I add to my toolbox so that I  
>> can really
>> understand what's really going on beneath the covers?
>>
>> As I mentioned in my earlier post, this project I am involved with  
>> will be
>> weaving together several applications to be deployed on top of  
>> Geronimo, so
>> sooner or later, fine-tuning performance issues will become a reality.
>>
>> I'd like to get a handle on such things as early in the development  
>> cycle as
>> possible.
> 
> 
> Hi Jim,
> There are a lot of knobs and switches. However, you can cause as much  
> harm as good trying to fine tune their settings. My advice to you is  
> to keep things as simple as possible until you know you have a problem.
> 


Hi Kevan,

Simple is good. 

I will certainly take your advice. I just know from experience that it best
to put a lasso around potential system-related problems like this early in
the game...if not they may assume an exponential flight path. 



Kevan Miller wrote:
> 
> The JVM can print GC statistics to STDOUT. Often I find this  
> sufficient for getting a broad overview of what's going on. You can  
> also configure the JVM to create a heapdump on OOME conditions. If you  
> have a memory leak, you can then analyze the heapdump using a variety  
> of tools (I like YourKit). There are a number of tools which can also  
> perform further analysis on runtime data (memory allocations, method  
> execution, etc).
> 
> Something like the following should work  (set max heap and max perm  
> to suit your environment):
> 
> -Xmx512m -XX:MaxPermSize=128m -verbose:gc -XX:+PrintGCDetails -XX: 
> +HeapDumpOnOutOfMemoryError
> 
> --kevan
> 
> 


This is good to know. 

It's probably too early for me to be thinking of dropping $500 for a
profiler like YourKit, but just leveraging the command line options as you
suggest should help in keeping things from getting out of control.

I appreciate your sharing this.  Thanks!

Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15901210.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Kevan Miller <ke...@gmail.com>.
On Mar 6, 2008, at 10:37 AM, Jim Foster wrote:

>
> Hi Peter,
>
> Thank you for this info!
>
> I took your suggestion and brought myself up to speed on PermGen,  
> and a good
> bit of all things related to Java.lang.OutOfMemoryError.
>
> All I can say is that there's certainly a lot more to fine-tuning the
> classloading going on behind the scenes than one would first imagine.
>
> This brings up another question: How do you folks manage this?
>
> What tools would you recommend that I add to my toolbox so that I  
> can really
> understand what's really going on beneath the covers?
>
> As I mentioned in my earlier post, this project I am involved with  
> will be
> weaving together several applications to be deployed on top of  
> Geronimo, so
> sooner or later, fine-tuning performance issues will become a reality.
>
> I'd like to get a handle on such things as early in the development  
> cycle as
> possible.

Hi Jim,
There are a lot of knobs and switches. However, you can cause as much  
harm as good trying to fine tune their settings. My advice to you is  
to keep things as simple as possible until you know you have a problem.

The JVM can print GC statistics to STDOUT. Often I find this  
sufficient for getting a broad overview of what's going on. You can  
also configure the JVM to create a heapdump on OOME conditions. If you  
have a memory leak, you can then analyze the heapdump using a variety  
of tools (I like YourKit). There are a number of tools which can also  
perform further analysis on runtime data (memory allocations, method  
execution, etc).

Something like the following should work  (set max heap and max perm  
to suit your environment):

-Xmx512m -XX:MaxPermSize=128m -verbose:gc -XX:+PrintGCDetails -XX: 
+HeapDumpOnOutOfMemoryError

--kevan

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

Peter Petersson-2 wrote:
> 
> Hi Jim
> 
> If you do a google search on "liferay permgen" you will get a lot of
> results about it so this seems to be a general "issue".
> 
> I have been testing out several older versions of Liferay with Geronimo
> 1.1.1 and 2.0.2 and my experience with it is that Liferay is a real best,
> although a nice one ;) that likes a lot of memory so try bump up memory by
> setting it to something like -Xms128m -Xmx1024m -XX:MaxPermSize=128m in
> you java opts and hopefully it will stabilize.
> 
> Good luck with this, I am following it with great interest, unfortunately
> I have a buzzy time with work at the moment else I would have joined in
> this endeavour.
> 
> regards
>    peter petersson
> 


Hi Peter,

Thank you for this info!

I took your suggestion and brought myself up to speed on PermGen, and a good
bit of all things related to Java.lang.OutOfMemoryError.

All I can say is that there's certainly a lot more to fine-tuning the
classloading going on behind the scenes than one would first imagine.

This brings up another question: How do you folks manage this? 

What tools would you recommend that I add to my toolbox so that I can really
understand what's really going on beneath the covers?

As I mentioned in my earlier post, this project I am involved with will be
weaving together several applications to be deployed on top of Geronimo, so
sooner or later, fine-tuning performance issues will become a reality.

I'd like to get a handle on such things as early in the development cycle as
possible.

Again, thanks for the tip!

Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15874624.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@gmail.com>.
Hi Jim

If you do a google search on "liferay permgen" you will get a lot of 
results about it so this seems to be a general "issue".

I have been testing out several older versions of Liferay with Geronimo 
1.1.1 and 2.0.2 and my experience with it is that Liferay is a real 
best, although a nice one ;) that likes a lot of memory so try bump up 
memory by setting it to something like -Xms128m -Xmx1024m 
-XX:MaxPermSize=128m in you java opts and hopefully it will stabilize.

Good luck with this, I am following it with great interest, 
unfortunately I have a buzzy time with work at the moment else I would 
have joined in this endeavour.

regards
   peter petersson

Jim Foster wrote:
> djencks wrote:
>   
>> On Mar 3, 2008, at 8:33 AM, Jim Foster wrote:
>>
>>     
>>> djencks wrote:
>>>       
>>>> On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:
>>>>
>>>>         
>>>>> djencks wrote:
>>>>>           
>>>>>> Your plan works for me.  I jar'ed up my sample and attached it  
>>>>>> to the
>>>>>> wiki page.  Could you see if you can detect the relevant  
>>>>>> difference?
>>>>>>
>>>>>> thanks
>>>>>> david jencks
>>>>>>
>>>>>>  <snip>
>>>>>>
>>>>>>
>>>>>>             
>>>>> Hi David,
>>>>>
>>>>> I think I see the point of confusion.
>>>>>
>>>>> In your doc, you have this:
>>>>>
>>>>> [3] Repackage the liferay war
>>>>>
>>>>> mvn archetype:create \
>>>>>   -DarchetypeGroupId=org.apache.maven.archetypes \
>>>>>   -DarchetypeArtifactId=maven-archetype-webapp \
>>>>>   -DarchetypeVersion=1.0 \
>>>>>   -DgroupId=com.liferay \
>>>>>   -DartifactId=liferay-portal-lesslibs \
>>>>>   -Dversion=4.4.1-NOLIB-SNAPSHOT
>>>>> cd liferay-portal
>>>>> rm -rf src
>>>>>
>>>>>
>>>>> Shouldn't that artifactId be "liferay-portal"?
>>>>>
>>>>>           
>>>> I don't think so.  Previously we've installed the liferay portal war
>>>> from liferay in the local maven repo as com.liferay/liferay-portal/
>>>> 4.4.1/war so we don't want another project claiming to generate the
>>>> same artifactId.  In fact I tried this at first but just having a
>>>> different version between input and output doesn't work -- maven
>>>> objects.
>>>>
>>>>         
>>> Hi David,
>>>
>>> I just don't see how in your documentation you can have this:
>>>
>>>   mvn archetype:create \
>>>     ...
>>>     -DartifactId=liferay-portal-lesslibs \
>>>     ...
>>>
>>> followed by this:
>>>
>>>   cd liferay-portal
>>>
>>>
>>> There isn't a directory liferay-portal, but there is
>>> liferay-portal-lesslibs, so one or the other must be out of sync.
>>>
>>>
>>>
>>> Also, in your liferay-sample.jar, you have the directory structure
>>>
>>> liferay-parent/
>>>                      pom.xml
>>>
>>>                      geronimo-jetty-liferay/
>>>                                                       pom.xml
>>>
>>>                      liferay-derby/
>>>                                         pom.xml
>>>                                         src/
>>>                                              main/
>>>                                                      plan/
>>>                                                             plan.xml
>>>
>>>                                                      resources/
>>>
>>>                      liferay-jetty/
>>>                                         pom.xml
>>>                                         src/
>>>                                              main/
>>>                                                      plan/
>>>                                                             plan.xml
>>>
>>>                                                      resources/
>>>
>>>                      liferay-portal/
>>>                                          pom.xml
>>>
>>>
>>>
>>> Where did the directory liferay-portal-lesslibs go?
>>>
>>> And where did directory liferay-portal come from?
>>>       
>> This is what happens without proper review :-).  I started with  
>> calling my repackaged liferay liferay-portal but the duplicate  
>> artifactId didn't work.  I then missed updating the name change in a  
>> lot of places.
>>
>> Hopefully it's fixed now....  waiting for your review...
>>
>> thanks
>> david jencks
>>
>>
>>     
>
>
> Hi David,
>
> I am glad that this is turning out to be a productive discussion.
>
> I have some more review notes for you.
>
> For reference:
>
>   Constructing a special-purpose server using maven
>  
> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
>   
>     [1] Preparation – find the artifacts
>     [2] Set up a parent maven project
>     [3] Repackage the liferay war
>     [4] Build a database plugin
>     [5] Build the liferay war plugin
>     [6] Build an assembly
>     [7] Run the project
>   
>   
> Note:
> In the following, I use the term "baseline" to mean your liferay-sample.jar
> attached to your wiki doc, which builds as it should in maven (hence
> "baseline"), and  "doc" to mean your wiki documentation.
>   
>
> [3] baseline has this:
>
>       <version>4.4.1</version>
>
>     whereas the doc has this:
>
>       <version>${liferayVersion}</version>
>
>     which produces an artifact not found error (i.e., there is no
> liferayVersion defined at this point of the process).
>
>
> [5] baseline has this:
>
>       <dependency>
>         <groupId>com.liferay</groupId>
>         <artifactId>liferay-portal-lesslibs</artifactId>
>         <version>${liferayVersion}-SNAPSHOT</version>
>         <type>war</type>
>         <scope>provided</scope>
>       </dependency>
>
>     whereas the doc has this:
>
>       <dependency>
>         <groupId>com.liferay</groupId>
>         <artifactId>liferay-portal-lesslibs</artifactId>
>         <version>${liferayVersion}</version>
>         <type>war</type>
>         <scope>provided</scope>
>       </dependency>
>     
>     which produces
>     
>       [INFO]
> ------------------------------------------------------------------------
>       [ERROR] BUILD ERROR
>       [INFO]
> ------------------------------------------------------------------------
>       [INFO] Failed to resolve artifact.
>
>       GroupId: com.liferay
>       ArtifactId: liferay-portal-lesslibs
>       Version: 4.4.1
>     
>
> [6] baseline has this:
>
>       <properties>
>         <geronimoVersion>2.1</geronimoVersion>
>       </properties>
>
>     whereas the mvn command generates this:
>
>       <properties>
>         <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>       </properties>
>       
>     which produces
>
>       [INFO]
> ------------------------------------------------------------------------
>       [ERROR] BUILD ERROR
>       [INFO]
> ------------------------------------------------------------------------
>       [INFO] Failed to resolve artifact.
>
>       GroupId: org.apache.geronimo.assemblies
>       ArtifactId: assemblies
>       Version: 2.2-SNAPSHOT
>
>       Reason: Unable to download the artifact from any repository
>       
>       
>       
> [7] I see the same PermGen error.
>
> I wonder if we built this using MySQL rather than the system database (as
> the Liferay folks intended) we would be in better shape?
>     
> After all, that database (the MySQL version at least) is just shy of 60MB,
> so it stands to reason that we are taxing resources here.
>     
> I would like to explore this. Could you please guide me? 
>     
> I think I have the basics down of what would be needed, but I don't think I
> quite have it all down yet, and I would like to know for sure by hearing it
> from you.
>     
> I would like to see us put this puppy to bed, you folks bless it for the
> general public, and move on (Liferay portal is but the first of several apps
> I am building on top of Geronimo - details of this project to be shared as
> we go).
>     
>     
>
> Thanks!
>     
> Jim
>
>   


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@gmail.com>.
David Jencks wrote:
>
> On Jun 8, 2008, at 3:03 PM, Peter Petersson wrote:
>
>> David Jencks wrote:
>>>
>>> On Jun 8, 2008, at 1:44 PM, Peter Petersson wrote:
>>>
>>>> Hi David
>>>>
>>>> I have been taking a look at your excellent "Constructing a 
>>>> special-purpose server using maven" (link below) in the hope to 
>>>> actually get Liferay 5.0.1 (rc1) running on Geronimo 2.1.1 in a 
>>>> special purpose build. Working on this i noticed what I believe is 
>>>> a typo in the documentation of the liferay-jetty pom
>>>>
>>>>              <configuration>
>>>>                      :
>>>>                  <module>
>>>>                      <groupId>com.liferay</groupId>
>>>>                      <artifactId>liferay-portal</artifactId>
>>>>                      <version>${liferayVersion}</version>
>>>>                      <type>war</type>
>>>>                  </module>
>>>>                     :
>>>>
>>>> If I understand things right the artifactId should be 
>>>> "liferay-portal-lesslibs" else the liferay portal plugin would be 
>>>> the unmodified liferay war.
>>>
>>> I agree, fixed, thanks!
>>>>
>>>>
>>>> Despite this finding I am unfortunately stuck at the same 404 error 
>>>> at http://localhost:8080/c as pointed out in the documentation. 
>>>> Although I added the debugviews console portlet plugin and trying 
>>>> to squeeze some logging out of liferay to find out what is going on 
>>>> I have so far not been able to get past this problem.
>>>>
>>>> Have anyone got some luck with this ?
>>>> Any suggestion on what to do to get more information out of 
>>>> liferay/geronimo to be able to pinpoint and fix this error is 
>>>> greatly appreciated!
>>>
>>> I talked with Brian Chan a little bit at JavaOne and it sounded like 
>>> liferay had some way to get running on current geronimo, and he 
>>> sounded interested in pursuing plugins.  However, I haven't been 
>>> able to contact him since.
>> Ah good I will take a look at it. Would it be any point in take the 
>> maven assembling source I have come up with for G 2.1.1 and Liferay 
>> 5.0.1 and set it up like the roller plugin? If appropriate I can put 
>> it (zip of the source tree) in a jira hopefully it is just some minor 
>> fixes that is needed for it to run and maybe I (or someone else) will 
>> be able to come up with a running bundle.
>
> I think the ideal situation would be if liferay took over this code as 
> their geronimo integration.  So, maybe opening an issue there with the 
> code would provoke some movement :-).  However if that doesn't work I 
> think that a geronimo-hosted plugin would be a good idea.
Yes that would probably be a good idea, although I will wait until I 
actually have a working (jetty,tomcat) plugin which have proven to be a 
bit more troublesome than I anticipated ;/ I have got my hands on the 
geronimo 2.1.1 liferay 5.0.1 rc1 bundle and maybe it will give me some 
hints on whats needed for the plugin to get past that annoying "out of 
the blue" /c 404 problem ;-). If it is possible to use the vanilla 
liferay-portal.war (or even better the lesslibs variant) and dependency 
jars (like portal-kernel, portal-service, portlet) to build a 
geronimo-liferay plugin it would IMHO be a good "showcase" of the 
modularity of Geronimo and its plugin concept. Its just a mater of time 
until someone pulls this together.  
regards
  peter petersson
>
> thanks
> david jencks
>>
>>
>> regards
>>  peter petersson
>>>
>>> thanks!
>>> david jencks
>>>>
>>>>
>>>> regards
>>>> peter petersson
>>>>
>>>>
>>>> David Jencks wrote:
>>>>>
>>>>> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
>>>>>> <snip>
>>>>>> Hi David,
>>>>>>
>>>>>> I am glad that this is turning out to be a productive discussion.
>>>>>>
>>>>>> I have some more review notes for you.
>>>>>>
>>>>>> For reference:
>>>>>>
>>>>>> Constructing a special-purpose server using maven
>>>>>>
>>>>>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven 
>>>>>>
>>>>>>
>>>>>>   [1] Preparation – find the artifacts
>>>>>>   [2] Set up a parent maven project
>>>>>>   [3] Repackage the liferay war
>>>>>>   [4] Build a database plugin
>>>>>>   [5] Build the liferay war plugin
>>>>>>   [6] Build an assembly
>>>>>>   [7] Run the project
>>>>>>
>>>>>>
>>>>>> Note:
>>>>>> In the following, I use the term "baseline" to mean your 
>>>>>> liferay-sample.jar
>>>>>> attached to your wiki doc, which builds as it should in maven (hence
>>>>>> "baseline"), and  "doc" to mean your wiki documentation.
>>>>>>
>>>>>>
>>>>>> [3] baseline has this:
>>>>>>
>>>>>>     <version>4.4.1</version>
>>>>>>
>>>>>>   whereas the doc has this:
>>>>>>
>>>>>>     <version>${liferayVersion}</version>
>>>>>>
>>>>>>   which produces an artifact not found error (i.e., there is no
>>>>>> liferayVersion defined at this point of the process).
>>>>>>
>>>>>
>>>>> fixed
>>>>>>
>>>>>> [5] baseline has this:
>>>>>>
>>>>>>     <dependency>
>>>>>>       <groupId>com.liferay</groupId>
>>>>>>       <artifactId>liferay-portal-lesslibs</artifactId>
>>>>>>       <version>${liferayVersion}-SNAPSHOT</version>
>>>>>>       <type>war</type>
>>>>>>       <scope>provided</scope>
>>>>>>     </dependency>
>>>>>>
>>>>>>   whereas the doc has this:
>>>>>>
>>>>>>     <dependency>
>>>>>>       <groupId>com.liferay</groupId>
>>>>>>       <artifactId>liferay-portal-lesslibs</artifactId>
>>>>>>       <version>${liferayVersion}</version>
>>>>>>       <type>war</type>
>>>>>>       <scope>provided</scope>
>>>>>>     </dependency>
>>>>>>
>>>>>>   which produces
>>>>>>
>>>>>>     [INFO]
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>>     [ERROR] BUILD ERROR
>>>>>>     [INFO]
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>>     [INFO] Failed to resolve artifact.
>>>>>>
>>>>>>     GroupId: com.liferay
>>>>>>     ArtifactId: liferay-portal-lesslibs
>>>>>>     Version: 4.4.1
>>>>>>
>>>>>>
>>>>> fixed
>>>>>> [6] baseline has this:
>>>>>>
>>>>>>     <properties>
>>>>>>       <geronimoVersion>2.1</geronimoVersion>
>>>>>>     </properties>
>>>>>>
>>>>>>   whereas the mvn command generates this:
>>>>>>
>>>>>>     <properties>
>>>>>>       <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>>>>>     </properties>
>>>>>>
>>>>>>   which produces
>>>>>>
>>>>>>     [INFO]
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>>     [ERROR] BUILD ERROR
>>>>>>     [INFO]
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>>     [INFO] Failed to resolve artifact.
>>>>>>
>>>>>>     GroupId: org.apache.geronimo.assemblies
>>>>>>     ArtifactId: assemblies
>>>>>>     Version: 2.2-SNAPSHOT
>>>>>>
>>>>>>     Reason: Unable to download the artifact from any repository
>>>>>>
>>>>>>
>>>>>
>>>>> added a note near the top about this.
>>>>>>
>>>>>> [7] I see the same PermGen error.
>>>>>>
>>>>>> I wonder if we built this using MySQL rather than the system 
>>>>>> database (as
>>>>>> the Liferay folks intended) we would be in better shape?
>>>>>>
>>>>>> After all, that database (the MySQL version at least) is just shy 
>>>>>> of 60MB,
>>>>>> so it stands to reason that we are taxing resources here.
>>>>>>
>>>>>> I would like to explore this. Could you please guide me?
>>>>>
>>>>> It's worth a try, although it's also a bit worrysome.  permGen OOM 
>>>>> errors normally mean you are creating too many classes.  The 
>>>>> amount of data being fed into a database shouldn't affect the 
>>>>> number of classes needed so if it is somehow affecting this I 
>>>>> wonder if something else is wrong.
>>>>>
>>>>> I'll see if I can write up an example later today, but meanwhile 
>>>>> you might look at the mysql plugin for roller under 
>>>>> plugins/roller/trunk.  The basic idea is to build another database 
>>>>> plugin, like the derby one but using the mysql wrapper and include 
>>>>> something like this so the mysql plugin gets used instead of the 
>>>>> derby one when it's installed.
>>>>>
>>>>>                           <artifact-alias 
>>>>> key="org.apache.geronimo.plugins/roller-derby-database/${version}/car">org.apache.geronimo.plugins/roller-mysql-database/${version}/car</artifact-alias> 
>>>>>
>>>>>
>>>>>
>>>>> Apache can't distribute something that automatically downloads  
>>>>> the mysql driver jar which is why the roller plugin has mysql as a 
>>>>> prerequisite.  If you are in an environment where this is not a 
>>>>> concern you can leave out the prerequisite and geronimo will 
>>>>> install the mysql jar for you when you install the mysql plugin.
>>>>>
>>>>>
>>>>>>
>>>>>> I think I have the basics down of what would be needed, but I 
>>>>>> don't think I
>>>>>> quite have it all down yet, and I would like to know for sure by 
>>>>>> hearing it
>>>>>> from you.
>>>>>
>>>>> I think you are getting there, keep asking questions!
>>>>>>
>>>>>> I would like to see us put this puppy to bed, you folks bless it 
>>>>>> for the
>>>>>> general public, and move on (Liferay portal is but the first of 
>>>>>> several apps
>>>>>> I am building on top of Geronimo - details of this project to be 
>>>>>> shared as
>>>>>> we go).
>>>>>>
>>>>>
>>>>> looking forward to it!
>>>>> thanks
>>>>> david jencks
>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>> -- 
>>>>>> View this message in context: 
>>>>>> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html 
>>>>>>
>>>>>> Sent from the Apache Geronimo - Users mailing list archive at 
>>>>>> Nabble.com.
>>>>>>
>>>>>
>>>>
>>>
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Jun 8, 2008, at 3:03 PM, Peter Petersson wrote:

> David Jencks wrote:
>>
>> On Jun 8, 2008, at 1:44 PM, Peter Petersson wrote:
>>
>>> Hi David
>>>
>>> I have been taking a look at your excellent "Constructing a  
>>> special-purpose server using maven" (link below) in the hope to  
>>> actually get Liferay 5.0.1 (rc1) running on Geronimo 2.1.1 in a  
>>> special purpose build. Working on this i noticed what I believe is  
>>> a typo in the documentation of the liferay-jetty pom
>>>
>>>              <configuration>
>>>                      :
>>>                  <module>
>>>                      <groupId>com.liferay</groupId>
>>>                      <artifactId>liferay-portal</artifactId>
>>>                      <version>${liferayVersion}</version>
>>>                      <type>war</type>
>>>                  </module>
>>>                     :
>>>
>>> If I understand things right the artifactId should be "liferay- 
>>> portal-lesslibs" else the liferay portal plugin would be the  
>>> unmodified liferay war.
>>
>> I agree, fixed, thanks!
>>>
>>>
>>> Despite this finding I am unfortunately stuck at the same 404  
>>> error at http://localhost:8080/c as pointed out in the  
>>> documentation. Although I added the debugviews console portlet  
>>> plugin and trying to squeeze some logging out of liferay to find  
>>> out what is going on I have so far not been able to get past this  
>>> problem.
>>>
>>> Have anyone got some luck with this ?
>>> Any suggestion on what to do to get more information out of  
>>> liferay/geronimo to be able to pinpoint and fix this error is  
>>> greatly appreciated!
>>
>> I talked with Brian Chan a little bit at JavaOne and it sounded  
>> like liferay had some way to get running on current geronimo, and  
>> he sounded interested in pursuing plugins.  However, I haven't been  
>> able to contact him since.
> Ah good I will take a look at it. Would it be any point in take the  
> maven assembling source I have come up with for G 2.1.1 and Liferay  
> 5.0.1 and set it up like the roller plugin? If appropriate I can put  
> it (zip of the source tree) in a jira hopefully it is just some  
> minor fixes that is needed for it to run and maybe I (or someone  
> else) will be able to come up with a running bundle.

I think the ideal situation would be if liferay took over this code as  
their geronimo integration.  So, maybe opening an issue there with the  
code would provoke some movement :-).  However if that doesn't work I  
think that a geronimo-hosted plugin would be a good idea.

thanks
david jencks
>
>
> regards
>  peter petersson
>>
>> thanks!
>> david jencks
>>>
>>>
>>> regards
>>> peter petersson
>>>
>>>
>>> David Jencks wrote:
>>>>
>>>> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
>>>>> <snip>
>>>>> Hi David,
>>>>>
>>>>> I am glad that this is turning out to be a productive discussion.
>>>>>
>>>>> I have some more review notes for you.
>>>>>
>>>>> For reference:
>>>>>
>>>>> Constructing a special-purpose server using maven
>>>>>
>>>>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
>>>>>
>>>>>   [1] Preparation – find the artifacts
>>>>>   [2] Set up a parent maven project
>>>>>   [3] Repackage the liferay war
>>>>>   [4] Build a database plugin
>>>>>   [5] Build the liferay war plugin
>>>>>   [6] Build an assembly
>>>>>   [7] Run the project
>>>>>
>>>>>
>>>>> Note:
>>>>> In the following, I use the term "baseline" to mean your liferay- 
>>>>> sample.jar
>>>>> attached to your wiki doc, which builds as it should in maven  
>>>>> (hence
>>>>> "baseline"), and  "doc" to mean your wiki documentation.
>>>>>
>>>>>
>>>>> [3] baseline has this:
>>>>>
>>>>>     <version>4.4.1</version>
>>>>>
>>>>>   whereas the doc has this:
>>>>>
>>>>>     <version>${liferayVersion}</version>
>>>>>
>>>>>   which produces an artifact not found error (i.e., there is no
>>>>> liferayVersion defined at this point of the process).
>>>>>
>>>>
>>>> fixed
>>>>>
>>>>> [5] baseline has this:
>>>>>
>>>>>     <dependency>
>>>>>       <groupId>com.liferay</groupId>
>>>>>       <artifactId>liferay-portal-lesslibs</artifactId>
>>>>>       <version>${liferayVersion}-SNAPSHOT</version>
>>>>>       <type>war</type>
>>>>>       <scope>provided</scope>
>>>>>     </dependency>
>>>>>
>>>>>   whereas the doc has this:
>>>>>
>>>>>     <dependency>
>>>>>       <groupId>com.liferay</groupId>
>>>>>       <artifactId>liferay-portal-lesslibs</artifactId>
>>>>>       <version>${liferayVersion}</version>
>>>>>       <type>war</type>
>>>>>       <scope>provided</scope>
>>>>>     </dependency>
>>>>>
>>>>>   which produces
>>>>>
>>>>>     [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>     [ERROR] BUILD ERROR
>>>>>     [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>     [INFO] Failed to resolve artifact.
>>>>>
>>>>>     GroupId: com.liferay
>>>>>     ArtifactId: liferay-portal-lesslibs
>>>>>     Version: 4.4.1
>>>>>
>>>>>
>>>> fixed
>>>>> [6] baseline has this:
>>>>>
>>>>>     <properties>
>>>>>       <geronimoVersion>2.1</geronimoVersion>
>>>>>     </properties>
>>>>>
>>>>>   whereas the mvn command generates this:
>>>>>
>>>>>     <properties>
>>>>>       <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>>>>     </properties>
>>>>>
>>>>>   which produces
>>>>>
>>>>>     [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>     [ERROR] BUILD ERROR
>>>>>     [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>     [INFO] Failed to resolve artifact.
>>>>>
>>>>>     GroupId: org.apache.geronimo.assemblies
>>>>>     ArtifactId: assemblies
>>>>>     Version: 2.2-SNAPSHOT
>>>>>
>>>>>     Reason: Unable to download the artifact from any repository
>>>>>
>>>>>
>>>>
>>>> added a note near the top about this.
>>>>>
>>>>> [7] I see the same PermGen error.
>>>>>
>>>>> I wonder if we built this using MySQL rather than the system  
>>>>> database (as
>>>>> the Liferay folks intended) we would be in better shape?
>>>>>
>>>>> After all, that database (the MySQL version at least) is just  
>>>>> shy of 60MB,
>>>>> so it stands to reason that we are taxing resources here.
>>>>>
>>>>> I would like to explore this. Could you please guide me?
>>>>
>>>> It's worth a try, although it's also a bit worrysome.  permGen  
>>>> OOM errors normally mean you are creating too many classes.  The  
>>>> amount of data being fed into a database shouldn't affect the  
>>>> number of classes needed so if it is somehow affecting this I  
>>>> wonder if something else is wrong.
>>>>
>>>> I'll see if I can write up an example later today, but meanwhile  
>>>> you might look at the mysql plugin for roller under plugins/ 
>>>> roller/trunk.  The basic idea is to build another database  
>>>> plugin, like the derby one but using the mysql wrapper and  
>>>> include something like this so the mysql plugin gets used instead  
>>>> of the derby one when it's installed.
>>>>
>>>>                           <artifact-alias  
>>>> key="org.apache.geronimo.plugins/roller-derby-database/${version}/ 
>>>> car">org.apache.geronimo.plugins/roller-mysql-database/${version}/ 
>>>> car</artifact-alias>
>>>>
>>>>
>>>> Apache can't distribute something that automatically downloads   
>>>> the mysql driver jar which is why the roller plugin has mysql as  
>>>> a prerequisite.  If you are in an environment where this is not a  
>>>> concern you can leave out the prerequisite and geronimo will  
>>>> install the mysql jar for you when you install the mysql plugin.
>>>>
>>>>
>>>>>
>>>>> I think I have the basics down of what would be needed, but I  
>>>>> don't think I
>>>>> quite have it all down yet, and I would like to know for sure by  
>>>>> hearing it
>>>>> from you.
>>>>
>>>> I think you are getting there, keep asking questions!
>>>>>
>>>>> I would like to see us put this puppy to bed, you folks bless it  
>>>>> for the
>>>>> general public, and move on (Liferay portal is but the first of  
>>>>> several apps
>>>>> I am building on top of Geronimo - details of this project to be  
>>>>> shared as
>>>>> we go).
>>>>>
>>>>
>>>> looking forward to it!
>>>> thanks
>>>> david jencks
>>>>
>>>>>
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Jim
>>>>>
>>>>> -- 
>>>>> View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html
>>>>> Sent from the Apache Geronimo - Users mailing list archive at  
>>>>> Nabble.com.
>>>>>
>>>>
>>>
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@gmail.com>.
David Jencks wrote:
>
> On Jun 8, 2008, at 1:44 PM, Peter Petersson wrote:
>
>> Hi David
>>
>> I have been taking a look at your excellent "Constructing a 
>> special-purpose server using maven" (link below) in the hope to 
>> actually get Liferay 5.0.1 (rc1) running on Geronimo 2.1.1 in a 
>> special purpose build. Working on this i noticed what I believe is a 
>> typo in the documentation of the liferay-jetty pom
>>
>>               <configuration>
>>                       :
>>                   <module>
>>                       <groupId>com.liferay</groupId>
>>                       <artifactId>liferay-portal</artifactId>
>>                       <version>${liferayVersion}</version>
>>                       <type>war</type>
>>                   </module>
>>                      :
>>
>> If I understand things right the artifactId should be 
>> "liferay-portal-lesslibs" else the liferay portal plugin would be the 
>> unmodified liferay war.
>
> I agree, fixed, thanks!
>>
>>
>> Despite this finding I am unfortunately stuck at the same 404 error 
>> at http://localhost:8080/c as pointed out in the documentation. 
>> Although I added the debugviews console portlet plugin and trying to 
>> squeeze some logging out of liferay to find out what is going on I 
>> have so far not been able to get past this problem.
>>
>> Have anyone got some luck with this ?
>> Any suggestion on what to do to get more information out of 
>> liferay/geronimo to be able to pinpoint and fix this error is greatly 
>> appreciated!
>
> I talked with Brian Chan a little bit at JavaOne and it sounded like 
> liferay had some way to get running on current geronimo, and he 
> sounded interested in pursuing plugins.  However, I haven't been able 
> to contact him since.
Ah good I will take a look at it. Would it be any point in take the 
maven assembling source I have come up with for G 2.1.1 and Liferay 
5.0.1 and set it up like the roller plugin? If appropriate I can put it 
(zip of the source tree) in a jira hopefully it is just some minor fixes 
that is needed for it to run and maybe I (or someone else) will be able 
to come up with a running bundle.

regards
   peter petersson
>
> thanks!
> david jencks
>>
>>
>> regards
>> peter petersson
>>
>>
>> David Jencks wrote:
>>>
>>> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
>>>> <snip>
>>>> Hi David,
>>>>
>>>> I am glad that this is turning out to be a productive discussion.
>>>>
>>>> I have some more review notes for you.
>>>>
>>>> For reference:
>>>>
>>>>  Constructing a special-purpose server using maven
>>>>
>>>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven 
>>>>
>>>>
>>>>    [1] Preparation – find the artifacts
>>>>    [2] Set up a parent maven project
>>>>    [3] Repackage the liferay war
>>>>    [4] Build a database plugin
>>>>    [5] Build the liferay war plugin
>>>>    [6] Build an assembly
>>>>    [7] Run the project
>>>>
>>>>
>>>> Note:
>>>> In the following, I use the term "baseline" to mean your 
>>>> liferay-sample.jar
>>>> attached to your wiki doc, which builds as it should in maven (hence
>>>> "baseline"), and  "doc" to mean your wiki documentation.
>>>>
>>>>
>>>> [3] baseline has this:
>>>>
>>>>      <version>4.4.1</version>
>>>>
>>>>    whereas the doc has this:
>>>>
>>>>      <version>${liferayVersion}</version>
>>>>
>>>>    which produces an artifact not found error (i.e., there is no
>>>> liferayVersion defined at this point of the process).
>>>>
>>>
>>> fixed
>>>>
>>>> [5] baseline has this:
>>>>
>>>>      <dependency>
>>>>        <groupId>com.liferay</groupId>
>>>>        <artifactId>liferay-portal-lesslibs</artifactId>
>>>>        <version>${liferayVersion}-SNAPSHOT</version>
>>>>        <type>war</type>
>>>>        <scope>provided</scope>
>>>>      </dependency>
>>>>
>>>>    whereas the doc has this:
>>>>
>>>>      <dependency>
>>>>        <groupId>com.liferay</groupId>
>>>>        <artifactId>liferay-portal-lesslibs</artifactId>
>>>>        <version>${liferayVersion}</version>
>>>>        <type>war</type>
>>>>        <scope>provided</scope>
>>>>      </dependency>
>>>>
>>>>    which produces
>>>>
>>>>      [INFO]
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>      [ERROR] BUILD ERROR
>>>>      [INFO]
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>      [INFO] Failed to resolve artifact.
>>>>
>>>>      GroupId: com.liferay
>>>>      ArtifactId: liferay-portal-lesslibs
>>>>      Version: 4.4.1
>>>>
>>>>
>>> fixed
>>>> [6] baseline has this:
>>>>
>>>>      <properties>
>>>>        <geronimoVersion>2.1</geronimoVersion>
>>>>      </properties>
>>>>
>>>>    whereas the mvn command generates this:
>>>>
>>>>      <properties>
>>>>        <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>>>      </properties>
>>>>
>>>>    which produces
>>>>
>>>>      [INFO]
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>      [ERROR] BUILD ERROR
>>>>      [INFO]
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>      [INFO] Failed to resolve artifact.
>>>>
>>>>      GroupId: org.apache.geronimo.assemblies
>>>>      ArtifactId: assemblies
>>>>      Version: 2.2-SNAPSHOT
>>>>
>>>>      Reason: Unable to download the artifact from any repository
>>>>
>>>>
>>>
>>> added a note near the top about this.
>>>>
>>>> [7] I see the same PermGen error.
>>>>
>>>> I wonder if we built this using MySQL rather than the system 
>>>> database (as
>>>> the Liferay folks intended) we would be in better shape?
>>>>
>>>> After all, that database (the MySQL version at least) is just shy 
>>>> of 60MB,
>>>> so it stands to reason that we are taxing resources here.
>>>>
>>>> I would like to explore this. Could you please guide me?
>>>
>>> It's worth a try, although it's also a bit worrysome.  permGen OOM 
>>> errors normally mean you are creating too many classes.  The amount 
>>> of data being fed into a database shouldn't affect the number of 
>>> classes needed so if it is somehow affecting this I wonder if 
>>> something else is wrong.
>>>
>>> I'll see if I can write up an example later today, but meanwhile you 
>>> might look at the mysql plugin for roller under 
>>> plugins/roller/trunk.  The basic idea is to build another database 
>>> plugin, like the derby one but using the mysql wrapper and include 
>>> something like this so the mysql plugin gets used instead of the 
>>> derby one when it's installed.
>>>
>>>                            <artifact-alias 
>>> key="org.apache.geronimo.plugins/roller-derby-database/${version}/car">org.apache.geronimo.plugins/roller-mysql-database/${version}/car</artifact-alias> 
>>>
>>>
>>>
>>> Apache can't distribute something that automatically downloads  the 
>>> mysql driver jar which is why the roller plugin has mysql as a 
>>> prerequisite.  If you are in an environment where this is not a 
>>> concern you can leave out the prerequisite and geronimo will install 
>>> the mysql jar for you when you install the mysql plugin.
>>>
>>>
>>>>
>>>> I think I have the basics down of what would be needed, but I don't 
>>>> think I
>>>> quite have it all down yet, and I would like to know for sure by 
>>>> hearing it
>>>> from you.
>>>
>>> I think you are getting there, keep asking questions!
>>>>
>>>> I would like to see us put this puppy to bed, you folks bless it 
>>>> for the
>>>> general public, and move on (Liferay portal is but the first of 
>>>> several apps
>>>> I am building on top of Geronimo - details of this project to be 
>>>> shared as
>>>> we go).
>>>>
>>>
>>> looking forward to it!
>>> thanks
>>> david jencks
>>>
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> Jim
>>>>
>>>> -- 
>>>> View this message in context: 
>>>> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html 
>>>>
>>>> Sent from the Apache Geronimo - Users mailing list archive at 
>>>> Nabble.com.
>>>>
>>>
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Jun 8, 2008, at 1:44 PM, Peter Petersson wrote:

> Hi David
>
> I have been taking a look at your excellent "Constructing a special- 
> purpose server using maven" (link below) in the hope to actually get  
> Liferay 5.0.1 (rc1) running on Geronimo 2.1.1 in a special purpose  
> build. Working on this i noticed what I believe is a typo in the  
> documentation of the liferay-jetty pom
>
>               <configuration>
>                       :
>                   <module>
>                       <groupId>com.liferay</groupId>
>                       <artifactId>liferay-portal</artifactId>
>                       <version>${liferayVersion}</version>
>                       <type>war</type>
>                   </module>
>                      :
>
> If I understand things right the artifactId should be "liferay- 
> portal-lesslibs" else the liferay portal plugin would be the  
> unmodified liferay war.

I agree, fixed, thanks!
>
>
> Despite this finding I am unfortunately stuck at the same 404 error  
> at http://localhost:8080/c as pointed out in the documentation.  
> Although I added the debugviews console portlet plugin and trying to  
> squeeze some logging out of liferay to find out what is going on I  
> have so far not been able to get past this problem.
>
> Have anyone got some luck with this ?
> Any suggestion on what to do to get more information out of liferay/ 
> geronimo to be able to pinpoint and fix this error is greatly  
> appreciated!

I talked with Brian Chan a little bit at JavaOne and it sounded like  
liferay had some way to get running on current geronimo, and he  
sounded interested in pursuing plugins.  However, I haven't been able  
to contact him since.

thanks!
david jencks
>
>
> regards
> peter petersson
>
>
> David Jencks wrote:
>>
>> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
>>> <snip>
>>> Hi David,
>>>
>>> I am glad that this is turning out to be a productive discussion.
>>>
>>> I have some more review notes for you.
>>>
>>> For reference:
>>>
>>>  Constructing a special-purpose server using maven
>>>
>>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
>>>
>>>    [1] Preparation – find the artifacts
>>>    [2] Set up a parent maven project
>>>    [3] Repackage the liferay war
>>>    [4] Build a database plugin
>>>    [5] Build the liferay war plugin
>>>    [6] Build an assembly
>>>    [7] Run the project
>>>
>>>
>>> Note:
>>> In the following, I use the term "baseline" to mean your liferay- 
>>> sample.jar
>>> attached to your wiki doc, which builds as it should in maven (hence
>>> "baseline"), and  "doc" to mean your wiki documentation.
>>>
>>>
>>> [3] baseline has this:
>>>
>>>      <version>4.4.1</version>
>>>
>>>    whereas the doc has this:
>>>
>>>      <version>${liferayVersion}</version>
>>>
>>>    which produces an artifact not found error (i.e., there is no
>>> liferayVersion defined at this point of the process).
>>>
>>
>> fixed
>>>
>>> [5] baseline has this:
>>>
>>>      <dependency>
>>>        <groupId>com.liferay</groupId>
>>>        <artifactId>liferay-portal-lesslibs</artifactId>
>>>        <version>${liferayVersion}-SNAPSHOT</version>
>>>        <type>war</type>
>>>        <scope>provided</scope>
>>>      </dependency>
>>>
>>>    whereas the doc has this:
>>>
>>>      <dependency>
>>>        <groupId>com.liferay</groupId>
>>>        <artifactId>liferay-portal-lesslibs</artifactId>
>>>        <version>${liferayVersion}</version>
>>>        <type>war</type>
>>>        <scope>provided</scope>
>>>      </dependency>
>>>
>>>    which produces
>>>
>>>      [INFO]
>>> ------------------------------------------------------------------------
>>>      [ERROR] BUILD ERROR
>>>      [INFO]
>>> ------------------------------------------------------------------------
>>>      [INFO] Failed to resolve artifact.
>>>
>>>      GroupId: com.liferay
>>>      ArtifactId: liferay-portal-lesslibs
>>>      Version: 4.4.1
>>>
>>>
>> fixed
>>> [6] baseline has this:
>>>
>>>      <properties>
>>>        <geronimoVersion>2.1</geronimoVersion>
>>>      </properties>
>>>
>>>    whereas the mvn command generates this:
>>>
>>>      <properties>
>>>        <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>>      </properties>
>>>
>>>    which produces
>>>
>>>      [INFO]
>>> ------------------------------------------------------------------------
>>>      [ERROR] BUILD ERROR
>>>      [INFO]
>>> ------------------------------------------------------------------------
>>>      [INFO] Failed to resolve artifact.
>>>
>>>      GroupId: org.apache.geronimo.assemblies
>>>      ArtifactId: assemblies
>>>      Version: 2.2-SNAPSHOT
>>>
>>>      Reason: Unable to download the artifact from any repository
>>>
>>>
>>
>> added a note near the top about this.
>>>
>>> [7] I see the same PermGen error.
>>>
>>> I wonder if we built this using MySQL rather than the system  
>>> database (as
>>> the Liferay folks intended) we would be in better shape?
>>>
>>> After all, that database (the MySQL version at least) is just shy  
>>> of 60MB,
>>> so it stands to reason that we are taxing resources here.
>>>
>>> I would like to explore this. Could you please guide me?
>>
>> It's worth a try, although it's also a bit worrysome.  permGen OOM  
>> errors normally mean you are creating too many classes.  The amount  
>> of data being fed into a database shouldn't affect the number of  
>> classes needed so if it is somehow affecting this I wonder if  
>> something else is wrong.
>>
>> I'll see if I can write up an example later today, but meanwhile  
>> you might look at the mysql plugin for roller under plugins/roller/ 
>> trunk.  The basic idea is to build another database plugin, like  
>> the derby one but using the mysql wrapper and include something  
>> like this so the mysql plugin gets used instead of the derby one  
>> when it's installed.
>>
>>                            <artifact-alias  
>> key="org.apache.geronimo.plugins/roller-derby-database/${version}/ 
>> car">org.apache.geronimo.plugins/roller-mysql-database/${version}/ 
>> car</artifact-alias>
>>
>>
>> Apache can't distribute something that automatically downloads  the  
>> mysql driver jar which is why the roller plugin has mysql as a  
>> prerequisite.  If you are in an environment where this is not a  
>> concern you can leave out the prerequisite and geronimo will  
>> install the mysql jar for you when you install the mysql plugin.
>>
>>
>>>
>>> I think I have the basics down of what would be needed, but I  
>>> don't think I
>>> quite have it all down yet, and I would like to know for sure by  
>>> hearing it
>>> from you.
>>
>> I think you are getting there, keep asking questions!
>>>
>>> I would like to see us put this puppy to bed, you folks bless it  
>>> for the
>>> general public, and move on (Liferay portal is but the first of  
>>> several apps
>>> I am building on top of Geronimo - details of this project to be  
>>> shared as
>>> we go).
>>>
>>
>> looking forward to it!
>> thanks
>> david jencks
>>
>>>
>>>
>>> Thanks!
>>>
>>> Jim
>>>
>>> -- 
>>> View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html
>>> Sent from the Apache Geronimo - Users mailing list archive at  
>>> Nabble.com.
>>>
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@gmail.com>.
Hi David

I have been taking a look at your excellent "Constructing a 
special-purpose server using maven" (link below) in the hope to actually 
get Liferay 5.0.1 (rc1) running on Geronimo 2.1.1 in a special purpose 
build. Working on this i noticed what I believe is a typo in the 
documentation of the liferay-jetty pom

                <configuration>
                        :
                    <module>
                        <groupId>com.liferay</groupId>
                        <artifactId>liferay-portal</artifactId>
                        <version>${liferayVersion}</version>
                        <type>war</type>
                    </module>
                       :

If I understand things right the artifactId should be 
"liferay-portal-lesslibs" else the liferay portal plugin would be the 
unmodified liferay war.

Despite this finding I am unfortunately stuck at the same 404 error at 
http://localhost:8080/c as pointed out in the documentation. Although I 
added the debugviews console portlet plugin and trying to squeeze some 
logging out of liferay to find out what is going on I have so far not 
been able to get past this problem.

Have anyone got some luck with this ? 

Any suggestion on what to do to get more information out of 
liferay/geronimo to be able to pinpoint and fix this error is greatly 
appreciated!

regards
  peter petersson


David Jencks wrote:
>
> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
>> <snip>
>> Hi David,
>>
>> I am glad that this is turning out to be a productive discussion.
>>
>> I have some more review notes for you.
>>
>> For reference:
>>
>>   Constructing a special-purpose server using maven
>>
>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
>>
>>     [1] Preparation – find the artifacts
>>     [2] Set up a parent maven project
>>     [3] Repackage the liferay war
>>     [4] Build a database plugin
>>     [5] Build the liferay war plugin
>>     [6] Build an assembly
>>     [7] Run the project
>>
>>
>> Note:
>> In the following, I use the term "baseline" to mean your 
>> liferay-sample.jar
>> attached to your wiki doc, which builds as it should in maven (hence
>> "baseline"), and  "doc" to mean your wiki documentation.
>>
>>
>> [3] baseline has this:
>>
>>       <version>4.4.1</version>
>>
>>     whereas the doc has this:
>>
>>       <version>${liferayVersion}</version>
>>
>>     which produces an artifact not found error (i.e., there is no
>> liferayVersion defined at this point of the process).
>>
>
> fixed
>>
>> [5] baseline has this:
>>
>>       <dependency>
>>         <groupId>com.liferay</groupId>
>>         <artifactId>liferay-portal-lesslibs</artifactId>
>>         <version>${liferayVersion}-SNAPSHOT</version>
>>         <type>war</type>
>>         <scope>provided</scope>
>>       </dependency>
>>
>>     whereas the doc has this:
>>
>>       <dependency>
>>         <groupId>com.liferay</groupId>
>>         <artifactId>liferay-portal-lesslibs</artifactId>
>>         <version>${liferayVersion}</version>
>>         <type>war</type>
>>         <scope>provided</scope>
>>       </dependency>
>>
>>     which produces
>>
>>       [INFO]
>> ------------------------------------------------------------------------
>>       [ERROR] BUILD ERROR
>>       [INFO]
>> ------------------------------------------------------------------------
>>       [INFO] Failed to resolve artifact.
>>
>>       GroupId: com.liferay
>>       ArtifactId: liferay-portal-lesslibs
>>       Version: 4.4.1
>>
>>
> fixed
>> [6] baseline has this:
>>
>>       <properties>
>>         <geronimoVersion>2.1</geronimoVersion>
>>       </properties>
>>
>>     whereas the mvn command generates this:
>>
>>       <properties>
>>         <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>>       </properties>
>>
>>     which produces
>>
>>       [INFO]
>> ------------------------------------------------------------------------
>>       [ERROR] BUILD ERROR
>>       [INFO]
>> ------------------------------------------------------------------------
>>       [INFO] Failed to resolve artifact.
>>
>>       GroupId: org.apache.geronimo.assemblies
>>       ArtifactId: assemblies
>>       Version: 2.2-SNAPSHOT
>>
>>       Reason: Unable to download the artifact from any repository
>>
>>
>
> added a note near the top about this.
>>
>> [7] I see the same PermGen error.
>>
>> I wonder if we built this using MySQL rather than the system database (as
>> the Liferay folks intended) we would be in better shape?
>>
>> After all, that database (the MySQL version at least) is just shy of 
>> 60MB,
>> so it stands to reason that we are taxing resources here.
>>
>> I would like to explore this. Could you please guide me? 
>
> It's worth a try, although it's also a bit worrysome.  permGen OOM 
> errors normally mean you are creating too many classes.  The amount of 
> data being fed into a database shouldn't affect the number of classes 
> needed so if it is somehow affecting this I wonder if something else 
> is wrong.
>
> I'll see if I can write up an example later today, but meanwhile you 
> might look at the mysql plugin for roller under plugins/roller/trunk. 
>  The basic idea is to build another database plugin, like the derby 
> one but using the mysql wrapper and include something like this so the 
> mysql plugin gets used instead of the derby one when it's installed.
>
>                             <artifact-alias 
> key="org.apache.geronimo.plugins/roller-derby-database/${version}/car">org.apache.geronimo.plugins/roller-mysql-database/${version}/car</artifact-alias>
>
>
> Apache can't distribute something that automatically downloads  the 
> mysql driver jar which is why the roller plugin has mysql as a 
> prerequisite.  If you are in an environment where this is not a 
> concern you can leave out the prerequisite and geronimo will install 
> the mysql jar for you when you install the mysql plugin.
>
>
>>
>> I think I have the basics down of what would be needed, but I don't 
>> think I
>> quite have it all down yet, and I would like to know for sure by 
>> hearing it
>> from you.
>
> I think you are getting there, keep asking questions!
>>
>> I would like to see us put this puppy to bed, you folks bless it for the
>> general public, and move on (Liferay portal is but the first of 
>> several apps
>> I am building on top of Geronimo - details of this project to be 
>> shared as
>> we go).
>>
>
> looking forward to it!
> thanks
> david jencks
>
>>
>>
>> Thanks!
>>
>> Jim
>>
>> -- 
>> View this message in context: 
>> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html
>> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.


djencks wrote:
> 
> Works OK for me.... is there some chance your copy of one of the  
> genesis poms got corrupted?  You might try rm -rf ~/.m2/repository/ 
> org/apache/geronimo/genesis
> 
> thanks
> david jencks
> 
> On Mar 7, 2008, at 2:41 PM, Jim Foster wrote:
> 
>>
>>
>> djencks wrote:
>>>
>>> Sorry for the delay, trying to get a release out is amazingly time-
>>> consuming.
>>>
>>
>> No problem, I figured as much.
>>
>>
>>
>> djencks wrote:
>>>
>>> On Mar 6, 2008, at 7:42 AM, Jim Foster wrote
>>>
>>>> djencks wrote:
>>>>>
>>>>> I'll see if I can write up an example later today, but meanwhile
>>>>> you might
>>>>> look at the mysql plugin for roller under plugins/roller/trunk.
>>>>>
>>>>
>>>>
>>>> I did take a look at roller, which is where I got the "basics" of
>>>> what I
>>>> know.
>>>>
>>>> However, building it presented problems, so I could only go so far.
>>>>
>>>> Here are my review notes for roller:
>>>>
>>>>
>>>> [1] Doing an mvn from the roller plugin root directory to do a top
>>>> level
>>>> build of the plugin yields the following:
>>>>
>>>>
>>>> -------------------------------------------------------------------- 
>>>> --
>>>> ---------------------------------
>>>>       [INFO] Scanning for projects...
>>>>       Downloading:
>>>> http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/
>>>> project-config/1.4/project-config-1.4.pom
>>>>       [INFO]
>>>> -------------------------------------------------------------------- 
>>>> --
>>>> --
>>>>       [ERROR] FATAL ERROR
>>>>       [INFO]
>>>> -------------------------------------------------------------------- 
>>>> --
>>>> --
>>>>       [INFO] Failed to resolve artifact.
>>>>
>>>>       GroupId: org.apache.geronimo.genesis.config
>>>>       ArtifactId: project-config
>>>>       Version: 1.4
>>>>
>>>
>>> Yup, this is part of trying to get ready for the roller plugin
>>> release.  If you change it to 1.3 it should work.
>>> <snip>
>>>
>>>
>>>> [2] Missing artifacts
>>>>
>>>>       [INFO]
>>>> -------------------------------------------------------------------- 
>>>> --
>>>> --
>>>>       [ERROR] BUILD ERROR
>>>>       [INFO]
>>>> -------------------------------------------------------------------- 
>>>> --
>>>> --
>>>>       [INFO] Failed to resolve artifact.
>>>>
>>>>
>>>
>>> I've fixed these two to artifacts I'm pretty sure are available :-)
>>>
>>>>
>>>>
>>>> Did I miss something obvious, or does this also need some  
>>>> tweaking, as
>>>> indicated above?
>>>
>>> Should be better now :-)  Please let me know if there are more  
>>> problems.
>>>
>>> david jencks
>>>
>>>>
>>>> Jim
>>>> -- 
>>>> View this message in context: http://www.nabble.com/Geronimo-v2.1-
>>>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1- 
>>>> tp15437773s134p15875526.html
>>>> Sent from the Apache Geronimo - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>
>>>
>>
>>
>>
>> I think we need to revisit this.
>>
>> Having this in roller/pom.xml:
>>
>>     <parent>
>>         <groupId>org.apache.geronimo.genesis.config</groupId>
>>         <artifactId>project-config</artifactId>
>>         <version>1.3</version>
>>     </parent>
>>
>>
>> yields the following:
>>
>>
>> [INFO] Scanning for projects...
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [ERROR] FATAL ERROR
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
>>
>> Reason: Cannot find parent:
>> org.apache.geronimo.genesis.config:project-config for project:
>> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for project
>> org.apache.geronimo.plugins:roller-par
>> ent:pom:1.0-SNAPSHOT
>>
>>
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] Trace
>> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
>> org.apache.geronimo.genesis.config:project-config for project:
>> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for proj
>> ect org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
>>         at org.apache.maven.DefaultMaven.getProjects 
>> (DefaultMaven.java:378)
>>         at org.apache.maven.DefaultMaven.doExecute 
>> (DefaultMaven.java:290)
>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
>> 125)
>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke 
>> (NativeMethodAccessorImpl.java:39)
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke 
>> (DelegatingMethodAccessorImpl.java:25)
>>         at java.lang.reflect.Method.invoke(Method.java:585)
>>         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.project.ProjectBuildingException:  
>> Cannot find
>> parent: org.apache.geronimo.genesis.config:project-config for project:
>> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPS
>> HOT for project org.apache.geronimo.plugins:roller-parent:pom:1.0- 
>> SNAPSHOT
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage 
>> (DefaultMavenProjectBuilder.java:1261)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal 
>> (DefaultMavenProjectBuilder.java:747)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil 
>> eInternal(DefaultMavenProjectBuilder.java:479)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.build 
>> (DefaultMavenProjectBuilder.java:200)
>>         at org.apache.maven.DefaultMaven.getProject 
>> (DefaultMaven.java:553)
>>         at
>> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
>>         at org.apache.maven.DefaultMaven.getProjects 
>> (DefaultMaven.java:364)
>>         ... 11 more
>> Caused by: org.apache.maven.project.InvalidProjectModelException:  
>> Parse
>> error reading POM. Reason: only whitespace content allowed before  
>> start tag
>> and not \uef (position: START_DOCUMENT seen \uef...
>> @1:1)  for project org.apache.geronimo.genesis.config:project- 
>> config at
>> R:\.m2\org\apache\geronimo\genesis\config\project-config\1.3 
>> \project-config-1.3.pom
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
>> (DefaultMavenProjectBuilder.java:1422)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
>> (DefaultMavenProjectBuilder.java:1379)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos 
>> itory(DefaultMavenProjectBuilder.java:530)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage 
>> (DefaultMavenProjectBuilder.java:1257)
>>         ... 17 more
>> Caused by:  
>> org.codehaus.plexus.util.xml.pull.XmlPullParserException: only
>> whitespace content allowed before start tag and not \uef (position:
>> START_DOCUMENT seen \uef... @1:1)
>>         at
>> org.codehaus.plexus.util.xml.pull.MXParser.parseProlog 
>> (MXParser.java:1516)
>>         at
>> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java: 
>> 1392)
>>         at
>> org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
>>         at
>> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read 
>> (MavenXpp3Reader.java:4419)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
>> (DefaultMavenProjectBuilder.java:1418)
>>         ... 20 more
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] Total time: < 1 second
>> [INFO] Finished at: Fri Mar 07 15:22:52 MST 2008
>> [INFO] Final Memory: 1M/2M
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>
>>
>>
>> For the record, I am using the latest and greatest from both Roller  
>> and
>> Geronimo, namely:
>>
>> https://svn.apache.org/repos/asf/roller/tags/roller_4.0/
>> Revision 634853
>>
>> https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/
>> Revision 634853
>>
>> and am following your instructions at
>> https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/README
>>
>>
>> Jim
>> -- 
>> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15908001.html
>> Sent from the Apache Geronimo - Users mailing list archive at  
>> Nabble.com.
>>
> 
> 
> 


Hi David,

Good catch!

I deleted that entire genesis directory and rebuilt fresh, and it worked!

I have a self-imposed "hands-off" policy with my local repository, so I have
no clue as to why it got corrupted.


Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15908361.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
Works OK for me.... is there some chance your copy of one of the  
genesis poms got corrupted?  You might try rm -rf ~/.m2/repository/ 
org/apache/geronimo/genesis

thanks
david jencks

On Mar 7, 2008, at 2:41 PM, Jim Foster wrote:

>
>
> djencks wrote:
>>
>> Sorry for the delay, trying to get a release out is amazingly time-
>> consuming.
>>
>
> No problem, I figured as much.
>
>
>
> djencks wrote:
>>
>> On Mar 6, 2008, at 7:42 AM, Jim Foster wrote
>>
>>> djencks wrote:
>>>>
>>>> I'll see if I can write up an example later today, but meanwhile
>>>> you might
>>>> look at the mysql plugin for roller under plugins/roller/trunk.
>>>>
>>>
>>>
>>> I did take a look at roller, which is where I got the "basics" of
>>> what I
>>> know.
>>>
>>> However, building it presented problems, so I could only go so far.
>>>
>>> Here are my review notes for roller:
>>>
>>>
>>> [1] Doing an mvn from the roller plugin root directory to do a top
>>> level
>>> build of the plugin yields the following:
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> --
>>> ---------------------------------
>>>       [INFO] Scanning for projects...
>>>       Downloading:
>>> http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/
>>> project-config/1.4/project-config-1.4.pom
>>>       [INFO]
>>> -------------------------------------------------------------------- 
>>> --
>>> --
>>>       [ERROR] FATAL ERROR
>>>       [INFO]
>>> -------------------------------------------------------------------- 
>>> --
>>> --
>>>       [INFO] Failed to resolve artifact.
>>>
>>>       GroupId: org.apache.geronimo.genesis.config
>>>       ArtifactId: project-config
>>>       Version: 1.4
>>>
>>
>> Yup, this is part of trying to get ready for the roller plugin
>> release.  If you change it to 1.3 it should work.
>> <snip>
>>
>>
>>> [2] Missing artifacts
>>>
>>>       [INFO]
>>> -------------------------------------------------------------------- 
>>> --
>>> --
>>>       [ERROR] BUILD ERROR
>>>       [INFO]
>>> -------------------------------------------------------------------- 
>>> --
>>> --
>>>       [INFO] Failed to resolve artifact.
>>>
>>>
>>
>> I've fixed these two to artifacts I'm pretty sure are available :-)
>>
>>>
>>>
>>> Did I miss something obvious, or does this also need some  
>>> tweaking, as
>>> indicated above?
>>
>> Should be better now :-)  Please let me know if there are more  
>> problems.
>>
>> david jencks
>>
>>>
>>> Jim
>>> -- 
>>> View this message in context: http://www.nabble.com/Geronimo-v2.1-
>>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1- 
>>> tp15437773s134p15875526.html
>>> Sent from the Apache Geronimo - Users mailing list archive at
>>> Nabble.com.
>>>
>>
>>
>
>
>
> I think we need to revisit this.
>
> Having this in roller/pom.xml:
>
>     <parent>
>         <groupId>org.apache.geronimo.genesis.config</groupId>
>         <artifactId>project-config</artifactId>
>         <version>1.3</version>
>     </parent>
>
>
> yields the following:
>
>
> [INFO] Scanning for projects...
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [ERROR] FATAL ERROR
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
>
> Reason: Cannot find parent:
> org.apache.geronimo.genesis.config:project-config for project:
> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for project
> org.apache.geronimo.plugins:roller-par
> ent:pom:1.0-SNAPSHOT
>
>
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.apache.geronimo.genesis.config:project-config for project:
> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for proj
> ect org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
>         at org.apache.maven.DefaultMaven.getProjects 
> (DefaultMaven.java:378)
>         at org.apache.maven.DefaultMaven.doExecute 
> (DefaultMaven.java:290)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
> 125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         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.project.ProjectBuildingException:  
> Cannot find
> parent: org.apache.geronimo.genesis.config:project-config for project:
> org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPS
> HOT for project org.apache.geronimo.plugins:roller-parent:pom:1.0- 
> SNAPSHOT
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage 
> (DefaultMavenProjectBuilder.java:1261)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal 
> (DefaultMavenProjectBuilder.java:747)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil 
> eInternal(DefaultMavenProjectBuilder.java:479)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.build 
> (DefaultMavenProjectBuilder.java:200)
>         at org.apache.maven.DefaultMaven.getProject 
> (DefaultMaven.java:553)
>         at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
>         at org.apache.maven.DefaultMaven.getProjects 
> (DefaultMaven.java:364)
>         ... 11 more
> Caused by: org.apache.maven.project.InvalidProjectModelException:  
> Parse
> error reading POM. Reason: only whitespace content allowed before  
> start tag
> and not \uef (position: START_DOCUMENT seen \uef...
> @1:1)  for project org.apache.geronimo.genesis.config:project- 
> config at
> R:\.m2\org\apache\geronimo\genesis\config\project-config\1.3 
> \project-config-1.3.pom
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
> (DefaultMavenProjectBuilder.java:1422)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
> (DefaultMavenProjectBuilder.java:1379)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos 
> itory(DefaultMavenProjectBuilder.java:530)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage 
> (DefaultMavenProjectBuilder.java:1257)
>         ... 17 more
> Caused by:  
> org.codehaus.plexus.util.xml.pull.XmlPullParserException: only
> whitespace content allowed before start tag and not \uef (position:
> START_DOCUMENT seen \uef... @1:1)
>         at
> org.codehaus.plexus.util.xml.pull.MXParser.parseProlog 
> (MXParser.java:1516)
>         at
> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java: 
> 1392)
>         at
> org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
>         at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read 
> (MavenXpp3Reader.java:4419)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel 
> (DefaultMavenProjectBuilder.java:1418)
>         ... 20 more
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Total time: < 1 second
> [INFO] Finished at: Fri Mar 07 15:22:52 MST 2008
> [INFO] Final Memory: 1M/2M
> [INFO]
> ---------------------------------------------------------------------- 
> --
>
>
>
> For the record, I am using the latest and greatest from both Roller  
> and
> Geronimo, namely:
>
> https://svn.apache.org/repos/asf/roller/tags/roller_4.0/
> Revision 634853
>
> https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/
> Revision 634853
>
> and am following your instructions at
> https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/README
>
>
> Jim
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15908001.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> Sorry for the delay, trying to get a release out is amazingly time- 
> consuming.
> 

No problem, I figured as much.



djencks wrote:
> 
> On Mar 6, 2008, at 7:42 AM, Jim Foster wrote
> 
>> djencks wrote:
>>>
>>> I'll see if I can write up an example later today, but meanwhile  
>>> you might
>>> look at the mysql plugin for roller under plugins/roller/trunk.
>>>
>>
>>
>> I did take a look at roller, which is where I got the "basics" of  
>> what I
>> know.
>>
>> However, building it presented problems, so I could only go so far.
>>
>> Here are my review notes for roller:
>>
>>
>> [1] Doing an mvn from the roller plugin root directory to do a top  
>> level
>> build of the plugin yields the following:
>>
>>
>> ---------------------------------------------------------------------- 
>> ---------------------------------
>>       [INFO] Scanning for projects...
>>       Downloading:
>> http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/ 
>> project-config/1.4/project-config-1.4.pom
>>       [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>       [ERROR] FATAL ERROR
>>       [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>       [INFO] Failed to resolve artifact.
>>
>>       GroupId: org.apache.geronimo.genesis.config
>>       ArtifactId: project-config
>>       Version: 1.4
>>
> 
> Yup, this is part of trying to get ready for the roller plugin  
> release.  If you change it to 1.3 it should work.
> <snip>
> 
> 
>> [2] Missing artifacts
>>
>>       [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>       [ERROR] BUILD ERROR
>>       [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>       [INFO] Failed to resolve artifact.
>>
>>
> 
> I've fixed these two to artifacts I'm pretty sure are available :-)
> 
>>
>>
>> Did I miss something obvious, or does this also need some tweaking, as
>> indicated above?
> 
> Should be better now :-)  Please let me know if there are more problems.
> 
> david jencks
> 
>>
>> Jim
>> -- 
>> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15875526.html
>> Sent from the Apache Geronimo - Users mailing list archive at  
>> Nabble.com.
>>
> 
> 



I think we need to revisit this.

Having this in roller/pom.xml:

    <parent>
        <groupId>org.apache.geronimo.genesis.config</groupId>
        <artifactId>project-config</artifactId>
        <version>1.3</version>
    </parent>


yields the following:


[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT

Reason: Cannot find parent:
org.apache.geronimo.genesis.config:project-config for project:
org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for project
org.apache.geronimo.plugins:roller-par
ent:pom:1.0-SNAPSHOT


[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.apache.geronimo.genesis.config:project-config for project:
org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT for proj
ect org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        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.project.ProjectBuildingException: Cannot find
parent: org.apache.geronimo.genesis.config:project-config for project:
org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPS
HOT for project org.apache.geronimo.plugins:roller-parent:pom:1.0-SNAPSHOT
        at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1261)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:747)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553)
        at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
        ... 11 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Parse
error reading POM. Reason: only whitespace content allowed before start tag
and not \uef (position: START_DOCUMENT seen \uef...
@1:1)  for project org.apache.geronimo.genesis.config:project-config at
R:\.m2\org\apache\geronimo\genesis\config\project-config\1.3\project-config-1.3.pom
        at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1422)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1379)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:530)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1257)
        ... 17 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: only
whitespace content allowed before start tag and not \uef (position:
START_DOCUMENT seen \uef... @1:1)
        at
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1516)
        at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392)
        at
org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
        at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4419)
        at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1418)
        ... 20 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Fri Mar 07 15:22:52 MST 2008
[INFO] Final Memory: 1M/2M
[INFO]
------------------------------------------------------------------------



For the record, I am using the latest and greatest from both Roller and
Geronimo, namely:

https://svn.apache.org/repos/asf/roller/tags/roller_4.0/
Revision 634853

https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/
Revision 634853

and am following your instructions at
https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk/README


Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15908001.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
Sorry for the delay, trying to get a release out is amazingly time- 
consuming.


On Mar 6, 2008, at 7:42 AM, Jim Foster wrote

<snip>

> djencks wrote:
>>
>> I'll see if I can write up an example later today, but meanwhile  
>> you might
>> look at the mysql plugin for roller under plugins/roller/trunk.
>>
>
>
> I did take a look at roller, which is where I got the "basics" of  
> what I
> know.
>
> However, building it presented problems, so I could only go so far.
>
> Here are my review notes for roller:
>
>
> [1] Doing an mvn from the roller plugin root directory to do a top  
> level
> build of the plugin yields the following:
>
>
> ---------------------------------------------------------------------- 
> ---------------------------------
>       [INFO] Scanning for projects...
>       Downloading:
> http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/ 
> project-config/1.4/project-config-1.4.pom
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [ERROR] FATAL ERROR
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [INFO] Failed to resolve artifact.
>
>       GroupId: org.apache.geronimo.genesis.config
>       ArtifactId: project-config
>       Version: 1.4
>

Yup, this is part of trying to get ready for the roller plugin  
release.  If you change it to 1.3 it should work.
<snip>
>
> [2] Missing artifacts
>
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [ERROR] BUILD ERROR
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [INFO] Failed to resolve artifact.
>
>

I've fixed these two to artifacts I'm pretty sure are available :-)

>
>
> Did I miss something obvious, or does this also need some tweaking, as
> indicated above?

Should be better now :-)  Please let me know if there are more problems.

david jencks

>
> Jim
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15875526.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> 
> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
> 
> <snip>
> 
>> [7] I see the same PermGen error.
>>
>> I wonder if we built this using MySQL rather than the system database (as
>> the Liferay folks intended) we would be in better shape?
>>
>> After all, that database (the MySQL version at least) is just shy of
>> 60MB,
>> so it stands to reason that we are taxing resources here.
>>
>> I would like to explore this. Could you please guide me? 
> 
> It's worth a try, although it's also a bit worrysome.  permGen OOM errors
> normally mean you are creating too many classes.  The amount of data being
> fed into a database shouldn't affect the number of classes needed so if it
> is somehow affecting this I wonder if something else is wrong.
> 


Hi David,

Based on what Perter said, and the research I did as a result of his
suggestion, I see what you mean.



djencks wrote:
> 
> I'll see if I can write up an example later today, but meanwhile you might
> look at the mysql plugin for roller under plugins/roller/trunk.
> 


I did take a look at roller, which is where I got the "basics" of what I
know.

However, building it presented problems, so I could only go so far. 

Here are my review notes for roller:


[1] Doing an mvn from the roller plugin root directory to do a top level
build of the plugin yields the following:

     
-------------------------------------------------------------------------------------------------------
      [INFO] Scanning for projects...
      Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/project-config/1.4/project-config-1.4.pom
      [INFO]
------------------------------------------------------------------------
      [ERROR] FATAL ERROR
      [INFO]
------------------------------------------------------------------------
      [INFO] Failed to resolve artifact.

      GroupId: org.apache.geronimo.genesis.config
      ArtifactId: project-config
      Version: 1.4

      Reason: Unable to download the artifact from any repository

        org.apache.geronimo.genesis.config:project-config:pom:1.4

      from the specified remote repositories:
        central (http://repo1.maven.org/maven2)
        
        ...
        
     
-------------------------------------------------------------------------------------------------------


    There is no version 1.4. 

    Changing the parent version to 1.3 works until [2].
    
    
    
[2] Missing artifacts

      [INFO]
------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO]
------------------------------------------------------------------------
      [INFO] Failed to resolve artifact.

      Missing:
      ----------
      1) apache-xalan:serializer:jar:j_2.7.0

        Try downloading the file manually from the project website.

        Then, install it using the command:
            mvn install:install-file -DgroupId=apache-xalan
-DartifactId=serializer \
                -Dversion=j_2.7.0 -Dpackaging=jar -Dfile=/path/to/file
      Alternatively, if you host your own repository you can deploy the file
there:
                mvn deploy:deploy-file -DgroupId=apache-xalan
-DartifactId=serializer \
                -Dversion=j_2.7.0 -Dpackaging=jar -Dfile=/path/to/file \
                -Durl=[url] -DrepositoryId=[id]

        Path to dependency:
              1) org.apache.geronimo.plugins:roller-jetty:car:1.0-SNAPSHOT
              2) apache-xalan:serializer:jar:j_2.7.0

      2) oswego-concurrent:concurrent:jar:1.3.4

        Try downloading the file manually from the project website.

        Then, install it using the command:
            mvn install:install-file -DgroupId=oswego-concurrent
-DartifactId=concurrent \
                -Dversion=1.3.4 -Dpackaging=jar -Dfile=/path/to/file
      Alternatively, if you host your own repository you can deploy the file
there:
                mvn deploy:deploy-file -DgroupId=oswego-concurrent
-DartifactId=concurrent \
                -Dversion=1.3.4 -Dpackaging=jar -Dfile=/path/to/file \
                -Durl=[url] -DrepositoryId=[id]

        Path to dependency:
              1) org.apache.geronimo.plugins:roller-jetty:car:1.0-SNAPSHOT
              2) oswego-concurrent:concurrent:jar:1.3.4

      ----------
      2 required artifacts are missing.

      for artifact:
        org.apache.geronimo.plugins:roller-jetty:car:1.0-SNAPSHOT

      from the specified remote repositories:
        central (http://repo1.maven.org/maven2),
        apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository),
        apache-snapshots
(http://people.apache.org/repo/m2-snapshot-repository),
        codehaus-snapshots (http://snapshots.repository.codehaus.org),
        apache-incubator
(http://people.apache.org/repo/m2-incubating-repository/)
        
        

Did I miss something obvious, or does this also need some tweaking, as
indicated above?
        
Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15875526.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
> <snip>
> Hi David,
>
> I am glad that this is turning out to be a productive discussion.
>
> I have some more review notes for you.
>
> For reference:
>
>   Constructing a special-purpose server using maven
>
> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
> +special-purpose+server+using+maven
>
>     [1] Preparation – find the artifacts
>     [2] Set up a parent maven project
>     [3] Repackage the liferay war
>     [4] Build a database plugin
>     [5] Build the liferay war plugin
>     [6] Build an assembly
>     [7] Run the project
>
>
> Note:
> In the following, I use the term "baseline" to mean your liferay- 
> sample.jar
> attached to your wiki doc, which builds as it should in maven (hence
> "baseline"), and  "doc" to mean your wiki documentation.
>
>
> [3] baseline has this:
>
>       <version>4.4.1</version>
>
>     whereas the doc has this:
>
>       <version>${liferayVersion}</version>
>
>     which produces an artifact not found error (i.e., there is no
> liferayVersion defined at this point of the process).
>

fixed
>
> [5] baseline has this:
>
>       <dependency>
>         <groupId>com.liferay</groupId>
>         <artifactId>liferay-portal-lesslibs</artifactId>
>         <version>${liferayVersion}-SNAPSHOT</version>
>         <type>war</type>
>         <scope>provided</scope>
>       </dependency>
>
>     whereas the doc has this:
>
>       <dependency>
>         <groupId>com.liferay</groupId>
>         <artifactId>liferay-portal-lesslibs</artifactId>
>         <version>${liferayVersion}</version>
>         <type>war</type>
>         <scope>provided</scope>
>       </dependency>
>
>     which produces
>
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [ERROR] BUILD ERROR
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [INFO] Failed to resolve artifact.
>
>       GroupId: com.liferay
>       ArtifactId: liferay-portal-lesslibs
>       Version: 4.4.1
>
>
fixed
> [6] baseline has this:
>
>       <properties>
>         <geronimoVersion>2.1</geronimoVersion>
>       </properties>
>
>     whereas the mvn command generates this:
>
>       <properties>
>         <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
>       </properties>
>
>     which produces
>
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [ERROR] BUILD ERROR
>       [INFO]
> ---------------------------------------------------------------------- 
> --
>       [INFO] Failed to resolve artifact.
>
>       GroupId: org.apache.geronimo.assemblies
>       ArtifactId: assemblies
>       Version: 2.2-SNAPSHOT
>
>       Reason: Unable to download the artifact from any repository
>
>

added a note near the top about this.
>
> [7] I see the same PermGen error.
>
> I wonder if we built this using MySQL rather than the system  
> database (as
> the Liferay folks intended) we would be in better shape?
>
> After all, that database (the MySQL version at least) is just shy  
> of 60MB,
> so it stands to reason that we are taxing resources here.
>
> I would like to explore this. Could you please guide me?

It's worth a try, although it's also a bit worrysome.  permGen OOM  
errors normally mean you are creating too many classes.  The amount  
of data being fed into a database shouldn't affect the number of  
classes needed so if it is somehow affecting this I wonder if  
something else is wrong.

I'll see if I can write up an example later today, but meanwhile you  
might look at the mysql plugin for roller under plugins/roller/ 
trunk.  The basic idea is to build another database plugin, like the  
derby one but using the mysql wrapper and include something like this  
so the mysql plugin gets used instead of the derby one when it's  
installed.

                             <artifact-alias  
key="org.apache.geronimo.plugins/roller-derby-database/${version}/ 
car">org.apache.geronimo.plugins/roller-mysql-database/${version}/ 
car</artifact-alias>


Apache can't distribute something that automatically downloads  the  
mysql driver jar which is why the roller plugin has mysql as a  
prerequisite.  If you are in an environment where this is not a  
concern you can leave out the prerequisite and geronimo will install  
the mysql jar for you when you install the mysql plugin.


>
> I think I have the basics down of what would be needed, but I don't  
> think I
> quite have it all down yet, and I would like to know for sure by  
> hearing it
> from you.

I think you are getting there, keep asking questions!
>
> I would like to see us put this puppy to bed, you folks bless it  
> for the
> general public, and move on (Liferay portal is but the first of  
> several apps
> I am building on top of Geronimo - details of this project to be  
> shared as
> we go).
>

looking forward to it!
thanks
david jencks

>
>
> Thanks!
>
> Jim
>
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> 
> On Mar 3, 2008, at 8:33 AM, Jim Foster wrote:
> 
>>
>>
>> djencks wrote:
>>>
>>>
>>> On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:
>>>
>>>>
>>>> djencks wrote:
>>>>>
>>>>> Your plan works for me.  I jar'ed up my sample and attached it  
>>>>> to the
>>>>> wiki page.  Could you see if you can detect the relevant  
>>>>> difference?
>>>>>
>>>>> thanks
>>>>> david jencks
>>>>>
>>>>>  <snip>
>>>>>
>>>>>
>>>>
>>>> Hi David,
>>>>
>>>> I think I see the point of confusion.
>>>>
>>>> In your doc, you have this:
>>>>
>>>> [3] Repackage the liferay war
>>>>
>>>> mvn archetype:create \
>>>>   -DarchetypeGroupId=org.apache.maven.archetypes \
>>>>   -DarchetypeArtifactId=maven-archetype-webapp \
>>>>   -DarchetypeVersion=1.0 \
>>>>   -DgroupId=com.liferay \
>>>>   -DartifactId=liferay-portal-lesslibs \
>>>>   -Dversion=4.4.1-NOLIB-SNAPSHOT
>>>> cd liferay-portal
>>>> rm -rf src
>>>>
>>>>
>>>> Shouldn't that artifactId be "liferay-portal"?
>>>>
>>>
>>> I don't think so.  Previously we've installed the liferay portal war
>>> from liferay in the local maven repo as com.liferay/liferay-portal/
>>> 4.4.1/war so we don't want another project claiming to generate the
>>> same artifactId.  In fact I tried this at first but just having a
>>> different version between input and output doesn't work -- maven
>>> objects.
>>>
>>
>>
>> Hi David,
>>
>> I just don't see how in your documentation you can have this:
>>
>>   mvn archetype:create \
>>     ...
>>     -DartifactId=liferay-portal-lesslibs \
>>     ...
>>
>> followed by this:
>>
>>   cd liferay-portal
>>
>>
>> There isn't a directory liferay-portal, but there is
>> liferay-portal-lesslibs, so one or the other must be out of sync.
>>
>>
>>
>> Also, in your liferay-sample.jar, you have the directory structure
>>
>> liferay-parent/
>>                      pom.xml
>>
>>                      geronimo-jetty-liferay/
>>                                                       pom.xml
>>
>>                      liferay-derby/
>>                                         pom.xml
>>                                         src/
>>                                              main/
>>                                                      plan/
>>                                                             plan.xml
>>
>>                                                      resources/
>>
>>                      liferay-jetty/
>>                                         pom.xml
>>                                         src/
>>                                              main/
>>                                                      plan/
>>                                                             plan.xml
>>
>>                                                      resources/
>>
>>                      liferay-portal/
>>                                          pom.xml
>>
>>
>>
>> Where did the directory liferay-portal-lesslibs go?
>>
>> And where did directory liferay-portal come from?
> 
> This is what happens without proper review :-).  I started with  
> calling my repackaged liferay liferay-portal but the duplicate  
> artifactId didn't work.  I then missed updating the name change in a  
> lot of places.
> 
> Hopefully it's fixed now....  waiting for your review...
> 
> thanks
> david jencks
> 
> 


Hi David,

I am glad that this is turning out to be a productive discussion.

I have some more review notes for you.

For reference:

  Constructing a special-purpose server using maven
 
http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
  
    [1] Preparation – find the artifacts
    [2] Set up a parent maven project
    [3] Repackage the liferay war
    [4] Build a database plugin
    [5] Build the liferay war plugin
    [6] Build an assembly
    [7] Run the project
  
  
Note:
In the following, I use the term "baseline" to mean your liferay-sample.jar
attached to your wiki doc, which builds as it should in maven (hence
"baseline"), and  "doc" to mean your wiki documentation.
  

[3] baseline has this:

      <version>4.4.1</version>

    whereas the doc has this:

      <version>${liferayVersion}</version>

    which produces an artifact not found error (i.e., there is no
liferayVersion defined at this point of the process).


[5] baseline has this:

      <dependency>
        <groupId>com.liferay</groupId>
        <artifactId>liferay-portal-lesslibs</artifactId>
        <version>${liferayVersion}-SNAPSHOT</version>
        <type>war</type>
        <scope>provided</scope>
      </dependency>

    whereas the doc has this:

      <dependency>
        <groupId>com.liferay</groupId>
        <artifactId>liferay-portal-lesslibs</artifactId>
        <version>${liferayVersion}</version>
        <type>war</type>
        <scope>provided</scope>
      </dependency>
    
    which produces
    
      [INFO]
------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO]
------------------------------------------------------------------------
      [INFO] Failed to resolve artifact.

      GroupId: com.liferay
      ArtifactId: liferay-portal-lesslibs
      Version: 4.4.1
    

[6] baseline has this:

      <properties>
        <geronimoVersion>2.1</geronimoVersion>
      </properties>

    whereas the mvn command generates this:

      <properties>
        <geronimoVersion>2.2-SNAPSHOT</geronimoVersion>
      </properties>
      
    which produces

      [INFO]
------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO]
------------------------------------------------------------------------
      [INFO] Failed to resolve artifact.

      GroupId: org.apache.geronimo.assemblies
      ArtifactId: assemblies
      Version: 2.2-SNAPSHOT

      Reason: Unable to download the artifact from any repository
      
      
      
[7] I see the same PermGen error.

I wonder if we built this using MySQL rather than the system database (as
the Liferay folks intended) we would be in better shape?
    
After all, that database (the MySQL version at least) is just shy of 60MB,
so it stands to reason that we are taxing resources here.
    
I would like to explore this. Could you please guide me? 
    
I think I have the basics down of what would be needed, but I don't think I
quite have it all down yet, and I would like to know for sure by hearing it
from you.
    
I would like to see us put this puppy to bed, you folks bless it for the
general public, and move on (Liferay portal is but the first of several apps
I am building on top of Geronimo - details of this project to be shared as
we go).
    
    

Thanks!
    
Jim

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15833008.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Mar 3, 2008, at 8:33 AM, Jim Foster wrote:

>
>
> djencks wrote:
>>
>>
>> On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:
>>
>>>
>>> djencks wrote:
>>>>
>>>> Your plan works for me.  I jar'ed up my sample and attached it  
>>>> to the
>>>> wiki page.  Could you see if you can detect the relevant  
>>>> difference?
>>>>
>>>> thanks
>>>> david jencks
>>>>
>>>>  <snip>
>>>>
>>>>
>>>
>>> Hi David,
>>>
>>> I think I see the point of confusion.
>>>
>>> In your doc, you have this:
>>>
>>> [3] Repackage the liferay war
>>>
>>> mvn archetype:create \
>>>   -DarchetypeGroupId=org.apache.maven.archetypes \
>>>   -DarchetypeArtifactId=maven-archetype-webapp \
>>>   -DarchetypeVersion=1.0 \
>>>   -DgroupId=com.liferay \
>>>   -DartifactId=liferay-portal-lesslibs \
>>>   -Dversion=4.4.1-NOLIB-SNAPSHOT
>>> cd liferay-portal
>>> rm -rf src
>>>
>>>
>>> Shouldn't that artifactId be "liferay-portal"?
>>>
>>
>> I don't think so.  Previously we've installed the liferay portal war
>> from liferay in the local maven repo as com.liferay/liferay-portal/
>> 4.4.1/war so we don't want another project claiming to generate the
>> same artifactId.  In fact I tried this at first but just having a
>> different version between input and output doesn't work -- maven
>> objects.
>>
>
>
> Hi David,
>
> I just don't see how in your documentation you can have this:
>
>   mvn archetype:create \
>     ...
>     -DartifactId=liferay-portal-lesslibs \
>     ...
>
> followed by this:
>
>   cd liferay-portal
>
>
> There isn't a directory liferay-portal, but there is
> liferay-portal-lesslibs, so one or the other must be out of sync.
>
>
>
> Also, in your liferay-sample.jar, you have the directory structure
>
> liferay-parent/
>                      pom.xml
>
>                      geronimo-jetty-liferay/
>                                                       pom.xml
>
>                      liferay-derby/
>                                         pom.xml
>                                         src/
>                                              main/
>                                                      plan/
>                                                             plan.xml
>
>                                                      resources/
>
>                      liferay-jetty/
>                                         pom.xml
>                                         src/
>                                              main/
>                                                      plan/
>                                                             plan.xml
>
>                                                      resources/
>
>                      liferay-portal/
>                                          pom.xml
>
>
>
> Where did the directory liferay-portal-lesslibs go?
>
> And where did directory liferay-portal come from?

This is what happens without proper review :-).  I started with  
calling my repackaged liferay liferay-portal but the duplicate  
artifactId didn't work.  I then missed updating the name change in a  
lot of places.

Hopefully it's fixed now....  waiting for your review...

thanks
david jencks

>
>
> Jim
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15807715.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> 
> On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:
> 
>>
>> djencks wrote:
>>>
>>> Your plan works for me.  I jar'ed up my sample and attached it to the
>>> wiki page.  Could you see if you can detect the relevant difference?
>>>
>>> thanks
>>> david jencks
>>>
>>>  <snip>
>>>
>>>
>>
>> Hi David,
>>
>> I think I see the point of confusion.
>>
>> In your doc, you have this:
>>
>> [3] Repackage the liferay war
>>
>> mvn archetype:create \
>>   -DarchetypeGroupId=org.apache.maven.archetypes \
>>   -DarchetypeArtifactId=maven-archetype-webapp \
>>   -DarchetypeVersion=1.0 \
>>   -DgroupId=com.liferay \
>>   -DartifactId=liferay-portal-lesslibs \
>>   -Dversion=4.4.1-NOLIB-SNAPSHOT
>> cd liferay-portal
>> rm -rf src
>>
>>
>> Shouldn't that artifactId be "liferay-portal"?
>>
> 
> I don't think so.  Previously we've installed the liferay portal war  
> from liferay in the local maven repo as com.liferay/liferay-portal/ 
> 4.4.1/war so we don't want another project claiming to generate the  
> same artifactId.  In fact I tried this at first but just having a  
> different version between input and output doesn't work -- maven  
> objects.
> 


Hi David,

I just don't see how in your documentation you can have this:

  mvn archetype:create \
    ...
    -DartifactId=liferay-portal-lesslibs \
    ...

followed by this:

  cd liferay-portal


There isn't a directory liferay-portal, but there is
liferay-portal-lesslibs, so one or the other must be out of sync.



Also, in your liferay-sample.jar, you have the directory structure

liferay-parent/
                     pom.xml
               
                     geronimo-jetty-liferay/
                                                      pom.xml
               
                     liferay-derby/
                                        pom.xml
                                        src/
                                             main/
                                                     plan/
                                                            plan.xml

                                                     resources/

                     liferay-jetty/
                                        pom.xml
                                        src/
                                             main/
                                                     plan/
                                                            plan.xml

                                                     resources/

                     liferay-portal/
                                         pom.xml



Where did the directory liferay-portal-lesslibs go?

And where did directory liferay-portal come from?


Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15807715.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Mar 1, 2008, at 10:02 AM, Jim Foster wrote:

>
>
>
> djencks wrote:
>>
>> Your plan works for me.  I jar'ed up my sample and attached it to the
>> wiki page.  Could you see if you can detect the relevant difference?
>>
>> thanks
>> david jencks
>>
>>  <snip>
>>
>>
>
> Hi David,
>
> I think I see the point of confusion.
>
> In your doc, you have this:
>
> [3] Repackage the liferay war
>
> mvn archetype:create \
>   -DarchetypeGroupId=org.apache.maven.archetypes \
>   -DarchetypeArtifactId=maven-archetype-webapp \
>   -DarchetypeVersion=1.0 \
>   -DgroupId=com.liferay \
>   -DartifactId=liferay-portal-lesslibs \
>   -Dversion=4.4.1-NOLIB-SNAPSHOT
> cd liferay-portal
> rm -rf src
>
>
> Shouldn't that artifactId be "liferay-portal"?
>

I don't think so.  Previously we've installed the liferay portal war  
from liferay in the local maven repo as com.liferay/liferay-portal/ 
4.4.1/war so we don't want another project claiming to generate the  
same artifactId.  In fact I tried this at first but just having a  
different version between input and output doesn't work -- maven  
objects.


Would it be clearer if the heading said,
[3] Create a project to repackage the liferay war
(and similarly for the other projects/steps)?

thanks
david jencks

>
> Jim
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15779083.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.


djencks wrote:
> 
> Your plan works for me.  I jar'ed up my sample and attached it to the  
> wiki page.  Could you see if you can detect the relevant difference?
> 
> thanks
> david jencks
> 
>  <snip>
> 
> 

Hi David,

I think I see the point of confusion.

In your doc, you have this:

[3] Repackage the liferay war

mvn archetype:create \
  -DarchetypeGroupId=org.apache.maven.archetypes \
  -DarchetypeArtifactId=maven-archetype-webapp \
  -DarchetypeVersion=1.0 \
  -DgroupId=com.liferay \
  -DartifactId=liferay-portal-lesslibs \
  -Dversion=4.4.1-NOLIB-SNAPSHOT
cd liferay-portal
rm -rf src


Shouldn't that artifactId be "liferay-portal"?


Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15779083.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
Your plan works for me.  I jar'ed up my sample and attached it to the  
wiki page.  Could you see if you can detect the relevant difference?

thanks
david jencks

On Feb 29, 2008, at 1:52 PM, Jim Foster wrote:

>
> Hi David,
>
> You bet...though it's just a copy-n-paste of what you have in your
> documentation.
>
> Contents of liferay-parent/liferay-derby/src/main/plan/plan.xml:
> ---------------------------------------------------------------------- 
> --------------------------------------------
> <?xml version="1.0" encoding="UTF-8"?>
>
> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/ 
> connector-1.2">
>     <resourceadapter>
>         <outbound-resourceadapter>
>             <connection-definition>
>
> <connectionfactory-interface>javax.sql.DataSource</ 
> connectionfactory-interface>
>                 <connectiondefinition-instance>
>                     <name>jdbc/LiferayPool</name>
>                     <config-property-setting
> name="Password">liferay</config-property-setting>
>                     <config-property-setting
> name="UserName">liferay</config-property-setting>
>                     <config-property-setting
> name="DatabaseName">liferay</config-property-setting>
>                     <connectionmanager>
>                         <local-transaction/>
>                         <single-pool>
>                             <max-size>10</max-size>
>                             <min-size>0</min-size>
>                             <match-one/>
>                         </single-pool>
>                     </connectionmanager>
>                 </connectiondefinition-instance>
> <!-- Leave until we figure out if non-jta datasource is needed -->
> <!--
>                 <connectiondefinition-instance>
>                     <name>jdbc/NoTxrollerdb</name>
>                     <config-property-setting
> name="Password">roller</config-property-setting>
>                     <config-property-setting
> name="UserName">roller</config-property-setting>
>                     <config-property-setting
> name="DatabaseName">roller</config-property-setting>
>                     <connectionmanager>
>                         <no-transaction/>
>                         <single-pool>
>                             <max-size>10</max-size>
>                             <min-size>0</min-size>
>                             <match-one/>
>                         </single-pool>
>                     </connectionmanager>
>                 </connectiondefinition-instance>
> -->
>             </connection-definition>
>         </outbound-resourceadapter>
>     </resourceadapter>
>
> </connector>
> ---------------------------------------------------------------------- 
> --------------------------------------------
>
> Jim
>
>
> djencks wrote:
>>
>> Can you post liferay-parent/liferay-derby/src/main/plan/plan.xml?  I
>> think that is what xmlbeans is complaining about.
>>
>> thanks
>> david jencks
>>
>> On Feb 29, 2008, at 1:15 PM, Jim Foster wrote:
>>
>>>
>>> <snip>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.
Hi David,

You bet...though it's just a copy-n-paste of what you have in your
documentation.

Contents of liferay-parent/liferay-derby/src/main/plan/plan.xml:
------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>

<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2">
    <resourceadapter>
        <outbound-resourceadapter>
            <connection-definition>
               
<connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
                <connectiondefinition-instance>
                    <name>jdbc/LiferayPool</name>
                    <config-property-setting
name="Password">liferay</config-property-setting>
                    <config-property-setting
name="UserName">liferay</config-property-setting>
                    <config-property-setting
name="DatabaseName">liferay</config-property-setting>
                    <connectionmanager>
                        <local-transaction/>
                        <single-pool>
                            <max-size>10</max-size>
                            <min-size>0</min-size>
                            <match-one/>
                        </single-pool>
                    </connectionmanager>
                </connectiondefinition-instance>
<!-- Leave until we figure out if non-jta datasource is needed -->
<!--
                <connectiondefinition-instance>
                    <name>jdbc/NoTxrollerdb</name>
                    <config-property-setting
name="Password">roller</config-property-setting>
                    <config-property-setting
name="UserName">roller</config-property-setting>
                    <config-property-setting
name="DatabaseName">roller</config-property-setting>
                    <connectionmanager>
                        <no-transaction/>
                        <single-pool>
                            <max-size>10</max-size>
                            <min-size>0</min-size>
                            <match-one/>
                        </single-pool>
                    </connectionmanager>
                </connectiondefinition-instance>
-->
            </connection-definition>
        </outbound-resourceadapter>
    </resourceadapter>

</connector>
------------------------------------------------------------------------------------------------------------------

Jim


djencks wrote:
> 
> Can you post liferay-parent/liferay-derby/src/main/plan/plan.xml?  I  
> think that is what xmlbeans is complaining about.
> 
> thanks
> david jencks
> 
> On Feb 29, 2008, at 1:15 PM, Jim Foster wrote:
> 
>>
>>
>> djencks wrote:
>>>
>>>
>>> So I found the schema and I think you need
>>>
>>>      <pluginRepositories>
>>>
>>>          <pluginRepository>
>>>              <id>apache-snapshots</id>
>>>              <name>Apache Snapshots Repository</name>
>>>              <url>http://people.apache.org/repo/m2-snapshot-
>>> repository</url>
>>>              <layout>default</layout>
>>>              <snapshots>
>>>                  <enabled>true</enabled>
>>>                  <updatePolicy>daily</updatePolicy>
>>>                  <checksumPolicy>ignore</checksumPolicy>
>>>              </snapshots>
>>>              <releases>
>>>                  <enabled>false</enabled>
>>>              </releases>
>>>          </pluginRepository>
>>>
>>>      </pluginRepositories >
>>>
>>>
>>> thanks
>>>
>>> david jencks
>>>
>>>
>>
>>
>> Hi David,
>>
>> The following reports my test results so far.
>>
>> In a word, we seem to be good until actually running the project.  
>> Output to
>> console for this step with -e switch is included, below.
>>
>> For the benefit of other readers of this discussion, the primary  
>> reference
>> doc is:
>>
>>   Constructing a special-purpose server using maven
>>
>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
>> +special-purpose+server+using+maven
>>
>>
>> What I outline below follows the steps of the primary doc, step-for- 
>> step.
>>
>>   Steps:
>>   ------
>>   [1] Preparation – find the artifacts
>>   [2] Set up a parent maven project
>>   [3] Repackage the liferay war
>>   [4] Build a database plugin
>>   [5] Build the liferay war plugin
>>   [6] Build an assembly
>>   [7] Run the project
>>
>>
>>   Details:
>>   --------
>>   [1] Preparation – find the artifacts
>>   [2] Set up a parent maven project
>>   [3] Repackage the liferay war
>>
>>     Following your instructions in the primary doc were successful, no
>> problems or modifications needed for the steps above.
>>
>>
>>   [4] Build a database plugin
>>
>>     As you suggested in your post yesterday, I modified my  
>> settings.xml to
>> the following so as to access the archetype:
>>
>>       ...
>>       <activeProfiles>
>>         <activeProfile>profile-1</activeProfile>
>>       </activeProfiles>
>>       <profiles>
>>         <profile>
>>           <id>profile-1</id>
>>           <pluginRepositories>
>>             <pluginRepository>
>>               <id>apache-snapshots</id>
>>               <name>Apache Snapshots Repository</name>
>>
>> <url>http://people.apache.org/repo/m2-snapshot-repository</url>
>>               <layout>default</layout>
>>               <snapshots>
>>                 <enabled>true</enabled>
>>                 <updatePolicy>daily</updatePolicy>
>>                 <checksumPolicy>ignore</checksumPolicy>
>>               </snapshots>
>>               <releases>
>>                 <enabled>false</enabled>
>>               </releases>
>>             </pluginRepository>
>>           </pluginRepositories>
>>         </profile>
>>       </profiles>
>>       ...
>>
>>     This proved to be successful.
>>
>>     Once past the schema issue (as you suspected) the rest of your
>> instructions in the primary doc were also successful, meaning
>>
>>       liferay-derby/pom.xml
>>
>>         and
>>
>>       liferay-derby/src/main/plan/plan.xml
>>
>>     were modified just as you have outlined in the primary doc.
>>
>>
>>   [5] Build the liferay war plugin
>>
>>     These:
>>
>>       liferay-jetty/pom.xml
>>
>>         and
>>
>>       liferay-jetty/src/main/plan/plan.xml
>>
>>     were modified just as you have outlined in the primary doc.
>>
>>
>>   [6] Build an assembly
>>
>>     Following your instructions in the primary doc were successful.
>>
>>
>>   [7] Run the project
>>
>> Full output to the console:
>> ---------------------------------------------------------------------- 
>> ---------------------------------------------------------------------- 
>> -----
>> D:\Geronimo\plugins\liferay\liferay-parent>mvn -e clean install
>> + Error stacktraces are turned on.
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO]   liferay-parent
>> [INFO]   Unnamed -
>> org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
>> [INFO]   Unnamed -
>> org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
>> [INFO]   Unnamed -
>> org.apache.geronimo.plugins:geronimo-jetty-liferay:application- 
>> assembly:1.0-SNAPSHOT
>> [INFO]
>> ---------------------------------------------------------------------- 
>> ------
>> [INFO] Building liferay-parent
>> [INFO]    task-segment: [clean, install]
>> [INFO]
>> ---------------------------------------------------------------------- 
>> ------
>> [INFO] [clean:clean]
>> [INFO] [site:attach-descriptor]
>> [INFO] [install:install]
>> [INFO] Installing D:\Geronimo\plugins\liferay\liferay-parent 
>> \pom.xml to
>> R:\.m2\org\apache\geronimo\plugins\liferay-parent\1.0-SNAPSHOT 
>> \liferay-parent-1.0-SNAPSHOT.pom
>> [INFO]
>> ---------------------------------------------------------------------- 
>> ------
>> [INFO] Building Unnamed -
>> org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
>> [INFO]    task-segment: [clean, install]
>> [INFO]
>> ---------------------------------------------------------------------- 
>> ------
>> [INFO] [clean:clean]
>> [INFO] Deleting directory
>> D:\Geronimo\plugins\liferay\liferay-parent\liferay-derby\target
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> Downloading:
>> http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
>> Downloading:
>> http://people.apache.org/repo/m2-incubating-repository//woodstox/ 
>> wstx-asl/3.2.1/wstx-asl-3.2.1.pom
>> Downloading:
>> http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx- 
>> asl-3.2.1.pom
>> Downloading:
>> http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx- 
>> asl-3.2.1.pom
>> [INFO] [car:validate-configuration]
>> log4j:WARN No appenders could be found for logger
>> (org.codehaus.mojo.pluginsupport.logging.Logging).
>> log4j:WARN Please initialize the log4j system properly.
>> [INFO] [car:prepare-plan]
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] error: Unexpected element: CDATA
>>
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: error:  
>> Unexpected
>> element: CDATA
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
>> (DefaultLifecycleExecutor.java:564)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif 
>> ecycle(DefaultLifecycleExecutor.java:480)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
>> (DefaultLifecycleExecutor.java:459)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand 
>> leFailures(DefaultLifecycleExecutor.java:311)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment 
>> s(DefaultLifecycleExecutor.java:278)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
>> (DefaultLifecycleExecutor.java:143)
>>         at org.apache.maven.DefaultMaven.doExecute 
>> (DefaultMaven.java:334)
>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
>> 125)
>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke 
>> (NativeMethodAccessorImpl.java:39)
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke 
>> (DelegatingMethodAccessorImpl.java:25)
>>         at java.lang.reflect.Method.invoke(Method.java:585)
>>         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: error:  
>> Unexpected
>> element: CDATA
>>         at
>> org.codehaus.mojo.pluginsupport.MojoSupport.execute 
>> (MojoSupport.java:137)
>>         at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo 
>> (DefaultPluginManager.java:443)
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
>> (DefaultLifecycleExecutor.java:539)
>>         ... 16 more
>> Caused by: org.apache.xmlbeans.XmlException: error: Unexpected  
>> element:
>> CDATA
>>         at
>> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3471)
>>         at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java: 
>> 706)
>>         at
>> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java: 
>> 690)
>>         at
>> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java: 
>> 677)
>>         at
>> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse 
>> (SchemaTypeLoaderBase.java:208)
>>         at org.apache.xmlbeans.XmlObject$Factory.parse 
>> (XmlObject.java:580)
>>         at
>> org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.doExecute 
>> (PlanProcessorMojo.java:154)
>>         at
>> org.codehaus.mojo.pluginsupport.MojoSupport.execute 
>> (MojoSupport.java:122)
>>         ... 18 more
>> Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
>>         at
>> org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError 
>> (Piccolo.java:1038)
>>         at
>> org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
>>         at
>> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
>>         ... 25 more
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>> [INFO] Total time: 10 seconds
>> [INFO] Finished at: Fri Feb 29 13:55:14 MST 2008
>> [INFO] Final Memory: 16M/30M
>> [INFO]
>> ---------------------------------------------------------------------- 
>> --
>>
>>
>> Thoughts?
>>
>> Jim
>> -- 
>> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15767482.html
>> Sent from the Apache Geronimo - Users mailing list archive at  
>> Nabble.com.
>>
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15768555.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
Can you post liferay-parent/liferay-derby/src/main/plan/plan.xml?  I  
think that is what xmlbeans is complaining about.

thanks
david jencks

On Feb 29, 2008, at 1:15 PM, Jim Foster wrote:

>
>
> djencks wrote:
>>
>>
>> So I found the schema and I think you need
>>
>>      <pluginRepositories>
>>
>>          <pluginRepository>
>>              <id>apache-snapshots</id>
>>              <name>Apache Snapshots Repository</name>
>>              <url>http://people.apache.org/repo/m2-snapshot-
>> repository</url>
>>              <layout>default</layout>
>>              <snapshots>
>>                  <enabled>true</enabled>
>>                  <updatePolicy>daily</updatePolicy>
>>                  <checksumPolicy>ignore</checksumPolicy>
>>              </snapshots>
>>              <releases>
>>                  <enabled>false</enabled>
>>              </releases>
>>          </pluginRepository>
>>
>>      </pluginRepositories >
>>
>>
>> thanks
>>
>> david jencks
>>
>>
>
>
> Hi David,
>
> The following reports my test results so far.
>
> In a word, we seem to be good until actually running the project.  
> Output to
> console for this step with -e switch is included, below.
>
> For the benefit of other readers of this discussion, the primary  
> reference
> doc is:
>
>   Constructing a special-purpose server using maven
>
> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
> +special-purpose+server+using+maven
>
>
> What I outline below follows the steps of the primary doc, step-for- 
> step.
>
>   Steps:
>   ------
>   [1] Preparation – find the artifacts
>   [2] Set up a parent maven project
>   [3] Repackage the liferay war
>   [4] Build a database plugin
>   [5] Build the liferay war plugin
>   [6] Build an assembly
>   [7] Run the project
>
>
>   Details:
>   --------
>   [1] Preparation – find the artifacts
>   [2] Set up a parent maven project
>   [3] Repackage the liferay war
>
>     Following your instructions in the primary doc were successful, no
> problems or modifications needed for the steps above.
>
>
>   [4] Build a database plugin
>
>     As you suggested in your post yesterday, I modified my  
> settings.xml to
> the following so as to access the archetype:
>
>       ...
>       <activeProfiles>
>         <activeProfile>profile-1</activeProfile>
>       </activeProfiles>
>       <profiles>
>         <profile>
>           <id>profile-1</id>
>           <pluginRepositories>
>             <pluginRepository>
>               <id>apache-snapshots</id>
>               <name>Apache Snapshots Repository</name>
>
> <url>http://people.apache.org/repo/m2-snapshot-repository</url>
>               <layout>default</layout>
>               <snapshots>
>                 <enabled>true</enabled>
>                 <updatePolicy>daily</updatePolicy>
>                 <checksumPolicy>ignore</checksumPolicy>
>               </snapshots>
>               <releases>
>                 <enabled>false</enabled>
>               </releases>
>             </pluginRepository>
>           </pluginRepositories>
>         </profile>
>       </profiles>
>       ...
>
>     This proved to be successful.
>
>     Once past the schema issue (as you suspected) the rest of your
> instructions in the primary doc were also successful, meaning
>
>       liferay-derby/pom.xml
>
>         and
>
>       liferay-derby/src/main/plan/plan.xml
>
>     were modified just as you have outlined in the primary doc.
>
>
>   [5] Build the liferay war plugin
>
>     These:
>
>       liferay-jetty/pom.xml
>
>         and
>
>       liferay-jetty/src/main/plan/plan.xml
>
>     were modified just as you have outlined in the primary doc.
>
>
>   [6] Build an assembly
>
>     Following your instructions in the primary doc were successful.
>
>
>   [7] Run the project
>
> Full output to the console:
> ---------------------------------------------------------------------- 
> ---------------------------------------------------------------------- 
> -----
> D:\Geronimo\plugins\liferay\liferay-parent>mvn -e clean install
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   liferay-parent
> [INFO]   Unnamed -
> org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
> [INFO]   Unnamed -
> org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
> [INFO]   Unnamed -
> org.apache.geronimo.plugins:geronimo-jetty-liferay:application- 
> assembly:1.0-SNAPSHOT
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] Building liferay-parent
> [INFO]    task-segment: [clean, install]
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] [clean:clean]
> [INFO] [site:attach-descriptor]
> [INFO] [install:install]
> [INFO] Installing D:\Geronimo\plugins\liferay\liferay-parent 
> \pom.xml to
> R:\.m2\org\apache\geronimo\plugins\liferay-parent\1.0-SNAPSHOT 
> \liferay-parent-1.0-SNAPSHOT.pom
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] Building Unnamed -
> org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
> [INFO]    task-segment: [clean, install]
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] [clean:clean]
> [INFO] Deleting directory
> D:\Geronimo\plugins\liferay\liferay-parent\liferay-derby\target
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> Downloading:
> http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository//woodstox/ 
> wstx-asl/3.2.1/wstx-asl-3.2.1.pom
> Downloading:
> http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx- 
> asl-3.2.1.pom
> Downloading:
> http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx- 
> asl-3.2.1.pom
> [INFO] [car:validate-configuration]
> log4j:WARN No appenders could be found for logger
> (org.codehaus.mojo.pluginsupport.logging.Logging).
> log4j:WARN Please initialize the log4j system properly.
> [INFO] [car:prepare-plan]
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [ERROR] BUILD ERROR
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] error: Unexpected element: CDATA
>
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: error:  
> Unexpected
> element: CDATA
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
> (DefaultLifecycleExecutor.java:564)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif 
> ecycle(DefaultLifecycleExecutor.java:480)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
> (DefaultLifecycleExecutor.java:459)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand 
> leFailures(DefaultLifecycleExecutor.java:311)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment 
> s(DefaultLifecycleExecutor.java:278)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
> (DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute 
> (DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
> 125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         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: error:  
> Unexpected
> element: CDATA
>         at
> org.codehaus.mojo.pluginsupport.MojoSupport.execute 
> (MojoSupport.java:137)
>         at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo 
> (DefaultPluginManager.java:443)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
> (DefaultLifecycleExecutor.java:539)
>         ... 16 more
> Caused by: org.apache.xmlbeans.XmlException: error: Unexpected  
> element:
> CDATA
>         at
> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3471)
>         at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java: 
> 706)
>         at
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java: 
> 690)
>         at
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java: 
> 677)
>         at
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse 
> (SchemaTypeLoaderBase.java:208)
>         at org.apache.xmlbeans.XmlObject$Factory.parse 
> (XmlObject.java:580)
>         at
> org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.doExecute 
> (PlanProcessorMojo.java:154)
>         at
> org.codehaus.mojo.pluginsupport.MojoSupport.execute 
> (MojoSupport.java:122)
>         ... 18 more
> Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
>         at
> org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError 
> (Piccolo.java:1038)
>         at
> org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
>         at
> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
>         ... 25 more
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Fri Feb 29 13:55:14 MST 2008
> [INFO] Final Memory: 16M/30M
> [INFO]
> ---------------------------------------------------------------------- 
> --
>
>
> Thoughts?
>
> Jim
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15767482.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>



Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

djencks wrote:
> 
> 
> So I found the schema and I think you need
> 
>      <pluginRepositories>
> 
>          <pluginRepository>
>              <id>apache-snapshots</id>
>              <name>Apache Snapshots Repository</name>
>              <url>http://people.apache.org/repo/m2-snapshot- 
> repository</url>
>              <layout>default</layout>
>              <snapshots>
>                  <enabled>true</enabled>
>                  <updatePolicy>daily</updatePolicy>
>                  <checksumPolicy>ignore</checksumPolicy>
>              </snapshots>
>              <releases>
>                  <enabled>false</enabled>
>              </releases>
>          </pluginRepository>
> 
>      </pluginRepositories >
> 
> 
> thanks
> 
> david jencks
> 
> 


Hi David,

The following reports my test results so far.

In a word, we seem to be good until actually running the project. Output to
console for this step with -e switch is included, below.

For the benefit of other readers of this discussion, the primary reference
doc is:

  Constructing a special-purpose server using maven
 
http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven

  
What I outline below follows the steps of the primary doc, step-for-step.

  Steps:
  ------
  [1] Preparation – find the artifacts
  [2] Set up a parent maven project
  [3] Repackage the liferay war
  [4] Build a database plugin
  [5] Build the liferay war plugin
  [6] Build an assembly
  [7] Run the project
  
  
  Details:
  --------
  [1] Preparation – find the artifacts
  [2] Set up a parent maven project
  [3] Repackage the liferay war

    Following your instructions in the primary doc were successful, no
problems or modifications needed for the steps above.
  
  
  [4] Build a database plugin
  
    As you suggested in your post yesterday, I modified my settings.xml to
the following so as to access the archetype:
  
      ...
      <activeProfiles>
        <activeProfile>profile-1</activeProfile>
      </activeProfiles>
      <profiles>
        <profile>
          <id>profile-1</id>
          <pluginRepositories>
            <pluginRepository>
              <id>apache-snapshots</id>
              <name>Apache Snapshots Repository</name>
             
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
              <layout>default</layout>
              <snapshots>
                <enabled>true</enabled>
                <updatePolicy>daily</updatePolicy>
                <checksumPolicy>ignore</checksumPolicy>
              </snapshots>
              <releases>
                <enabled>false</enabled>
              </releases>
            </pluginRepository>
          </pluginRepositories>
        </profile>
      </profiles>
      ...
    
    This proved to be successful.
    
    Once past the schema issue (as you suspected) the rest of your
instructions in the primary doc were also successful, meaning

      liferay-derby/pom.xml
      
        and
      
      liferay-derby/src/main/plan/plan.xml

    were modified just as you have outlined in the primary doc.
  
  
  [5] Build the liferay war plugin
  
    These:
  
      liferay-jetty/pom.xml
      
        and
      
      liferay-jetty/src/main/plan/plan.xml

    were modified just as you have outlined in the primary doc.
    
    
  [6] Build an assembly
  
    Following your instructions in the primary doc were successful.
    
  
  [7] Run the project

Full output to the console:
-------------------------------------------------------------------------------------------------------------------------------------------------
D:\Geronimo\plugins\liferay\liferay-parent>mvn -e clean install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   liferay-parent
[INFO]   Unnamed -
org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
[INFO]   Unnamed -
org.apache.geronimo.plugins:liferay-jetty:car:1.0-SNAPSHOT
[INFO]   Unnamed -
org.apache.geronimo.plugins:geronimo-jetty-liferay:application-assembly:1.0-SNAPSHOT
[INFO]
----------------------------------------------------------------------------
[INFO] Building liferay-parent
[INFO]    task-segment: [clean, install]
[INFO]
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing D:\Geronimo\plugins\liferay\liferay-parent\pom.xml to
R:\.m2\org\apache\geronimo\plugins\liferay-parent\1.0-SNAPSHOT\liferay-parent-1.0-SNAPSHOT.pom
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed -
org.apache.geronimo.plugins:liferay-derby:car:1.0-SNAPSHOT
[INFO]    task-segment: [clean, install]
[INFO]
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory
D:\Geronimo\plugins\liferay\liferay-parent\liferay-derby\target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [car:validate-configuration]
log4j:WARN No appenders could be found for logger
(org.codehaus.mojo.pluginsupport.logging.Logging).
log4j:WARN Please initialize the log4j system properly.
[INFO] [car:prepare-plan]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] error: Unexpected element: CDATA

[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: error: Unexpected
element: CDATA
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        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: error: Unexpected
element: CDATA
        at
org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:137)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
        ... 16 more
Caused by: org.apache.xmlbeans.XmlException: error: Unexpected element:
CDATA
        at
org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3471)
        at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:706)
        at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:690)
        at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:677)
        at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208)
        at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:580)
        at
org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.doExecute(PlanProcessorMojo.java:154)
        at
org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:122)
        ... 18 more
Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
        at
org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
        at
org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
        at
org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
        ... 25 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10 seconds
[INFO] Finished at: Fri Feb 29 13:55:14 MST 2008
[INFO] Final Memory: 16M/30M
[INFO]
------------------------------------------------------------------------


Thoughts?

Jim
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15767482.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Feb 28, 2008, at 5:47 PM, David Jencks wrote:

>
> On Feb 28, 2008, at 2:28 PM, Jim Foster wrote:
>
>>
>> Hi David,
>>
>>
>> djencks wrote:
>>>
>>> Well.... I wrote it monday and wednesday so you would have needed  
>>> a  time
>>> machine :-)
>>>
>>
>>
>> Oh...
>>
>> ...my time machine is still in the shop...
>>
>>
>>
>> djencks wrote:
>>>
>>> I forgot to deploy the snapshots.
>>>
>>> I've changed the archetype name from geronimo-module-archetype to
>>> geronimo-plugin-archetype and deployed a snapshot.  I also updated
>>> the wiki page to the new archetype name.  I think the (modified)
>>> instructions should now work, but you are definitely the guinea
>>> pig :-).  The archetypes should download automatically but I haven't
>>> tested this.
>>>
>>
>>
>> I don't mind playing the role of guinea pig at all if it helps in
>> establishing a solid procedure for building plugin support of  
>> third-party
>> apps...this sort of flexibility on top of Java EE 5 certification is
>> precisely why I chose Geronimo.
>>
>>
>> Looks like we need to do another availability check.
>>
>>
>
> <snip>
>
> this is why you need to try it out :-)
>
> I think this will stop being a problem once the archetypes are  
> actually released
>
> Meanwhile I think we need to add something in the base project  
> plan.... not quite sure what.  This is a first guess
>
>     <repositories>
>         <!--
>         NOTE: The default repositories are picked up by Genesis,  
> but need to
>               specify where Genesis lives to pick it up  any  
> additional repositories.
>         -->
>
>         <repository>
>             <id>apache-snapshots</id>
>             <name>Apache Snapshots Repository</name>
>             <url>http://people.apache.org/repo/m2-snapshot- 
> repository</url>
>             <layout>default</layout>
>             <snapshots>
>                 <enabled>true</enabled>
>                 <updatePolicy>daily</updatePolicy>
>                 <checksumPolicy>ignore</checksumPolicy>
>             </snapshots>
>             <releases>
>                 <enabled>false</enabled>
>             </releases>
>         </repository>
>
>     </repositories>
>
> if this doesn't work.... I think it wont... I think there is a  
> plugin-repositories element to try instead (same repository element  
> inside???)

So I found the schema and I think you need

     <pluginRepositories>

         <pluginRepository>
             <id>apache-snapshots</id>
             <name>Apache Snapshots Repository</name>
             <url>http://people.apache.org/repo/m2-snapshot- 
repository</url>
             <layout>default</layout>
             <snapshots>
                 <enabled>true</enabled>
                 <updatePolicy>daily</updatePolicy>
                 <checksumPolicy>ignore</checksumPolicy>
             </snapshots>
             <releases>
                 <enabled>false</enabled>
             </releases>
         </pluginRepository>

     </pluginRepositories >


thanks

david jencks

>
> I have to run but will try to look into this more later
>
> thanks
> david jencks
>
>
>>
>> Thanks!
>>
>>
>> Jim
>>
>> -- 
>> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
>> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15747596.html
>> Sent from the Apache Geronimo - Users mailing list archive at  
>> Nabble.com.
>>
>
>



Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Feb 28, 2008, at 2:28 PM, Jim Foster wrote:

>
> Hi David,
>
>
> djencks wrote:
>>
>> Well.... I wrote it monday and wednesday so you would have needed  
>> a  time
>> machine :-)
>>
>
>
> Oh...
>
> ...my time machine is still in the shop...
>
>
>
> djencks wrote:
>>
>> I forgot to deploy the snapshots.
>>
>> I've changed the archetype name from geronimo-module-archetype to
>> geronimo-plugin-archetype and deployed a snapshot.  I also updated
>> the wiki page to the new archetype name.  I think the (modified)
>> instructions should now work, but you are definitely the guinea
>> pig :-).  The archetypes should download automatically but I haven't
>> tested this.
>>
>
>
> I don't mind playing the role of guinea pig at all if it helps in
> establishing a solid procedure for building plugin support of third- 
> party
> apps...this sort of flexibility on top of Java EE 5 certification is
> precisely why I chose Geronimo.
>
>
> Looks like we need to do another availability check.
>
>

<snip>

this is why you need to try it out :-)

I think this will stop being a problem once the archetypes are  
actually released

Meanwhile I think we need to add something in the base project  
plan.... not quite sure what.  This is a first guess

     <repositories>
         <!--
         NOTE: The default repositories are picked up by Genesis, but  
need to
               specify where Genesis lives to pick it up  any  
additional repositories.
         -->

         <repository>
             <id>apache-snapshots</id>
             <name>Apache Snapshots Repository</name>
             <url>http://people.apache.org/repo/m2-snapshot- 
repository</url>
             <layout>default</layout>
             <snapshots>
                 <enabled>true</enabled>
                 <updatePolicy>daily</updatePolicy>
                 <checksumPolicy>ignore</checksumPolicy>
             </snapshots>
             <releases>
                 <enabled>false</enabled>
             </releases>
         </repository>

     </repositories>

if this doesn't work.... I think it wont... I think there is a plugin- 
repositories element to try instead (same repository element inside???)

I have to run but will try to look into this more later

thanks
david jencks


>
> Thanks!
>
>
> Jim
>
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15747596.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>



Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.
Hi David,


djencks wrote:
> 
> Well.... I wrote it monday and wednesday so you would have needed a  time
> machine :-)
> 


Oh... 

...my time machine is still in the shop...



djencks wrote:
> 
> I forgot to deploy the snapshots.
> 
> I've changed the archetype name from geronimo-module-archetype to  
> geronimo-plugin-archetype and deployed a snapshot.  I also updated  
> the wiki page to the new archetype name.  I think the (modified)  
> instructions should now work, but you are definitely the guinea  
> pig :-).  The archetypes should download automatically but I haven't  
> tested this.
> 


I don't mind playing the role of guinea pig at all if it helps in
establishing a solid procedure for building plugin support of third-party
apps...this sort of flexibility on top of Java EE 5 certification is
precisely why I chose Geronimo.


Looks like we need to do another availability check.

Full output to the console:
---------------------------------------------------------------------------------------------------
D:\Geronimo\plugins\liferay-parent>mvn archetype:create
-DarchetypeGroupId=org.apache.geronimo.buildsupport 
                                                                                     
-DarchetypeArtifactId=geronimo-plugin-archetype 
                                                                                     
-DarchetypeVersion=2.2-SNAPSHOT 
                                                                                     
-DgroupId=org.apache.geronimo.plugins
                                                                                     
-DartifactId=liferay-derby -Dversion=1.0-SNAPSHOT
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building liferay-parent
[INFO]    task-segment: [archetype:create] (aggregator-style)
[INFO]
----------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] **************************************************************
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
any resource loader.
[INFO] Velocimacro : error using  VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be 
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [archetype:create]
[INFO] Defaulting package to group ID: org.apache.geronimo.plugins
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.geronimo.buildsupport
ArtifactId: geronimo-plugin-archetype
Version: 2.2-SNAPSHOT

Reason: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport
-DartifactId=geronimo-plugin-archetype \
        -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:     mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport
-DartifactId=geronimo-plugin-archetype \
        -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \
         -Durl=[url] -DrepositoryId=[id]


 
org.apache.geronimo.buildsupport:geronimo-plugin-archetype:jar:2.2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Feb 28 14:58:40 MST 2008
[INFO] Final Memory: 4M/8M
[INFO]
------------------------------------------------------------------------

END
---------------------------------------------------------------------------------------------------


Thanks! 


Jim

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15747596.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
On Feb 28, 2008, at 9:04 AM, Jim Foster wrote:

>
> Hi David,
>
> Responses in-line.
>
>
> djencks wrote:
>>
>> Hi Jim,
>>
>> I think I have failed to communicate what I'm trying to tell you  
>> what to
>> do :-)
>>
>
>
> That would explain why I had the feeling that I wasn't connecting  
> all the
> dots...and which is why I took the time to explain all the details  
> on my
> end.
>
>
>
> djencks wrote:
>>
>> I've tried to explain in more detail here:
>>
>>
>> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
>> +special-purpose+server+using+maven
>>
>
>
> Now this is making sense.
>
> I wish I had this information a week ago.
>

Well.... I wrote it monday and wednesday so you would have needed a  
time machine :-)
>
>
>
> djencks wrote:
>>
>> Two things I'm not trying to do:
>> 1. show you how to deploy liferay on geronimo
>> 2. give you a maven project that builds a liferay plugin and assembly
>>
>> What I am trying to explain is how you can set up a maven project  
>> to build
>> liferay plugins and assemblies, with the help of the geronimo  
>> archetypes
>> for these kind of projects.
>>
>> It looks to me from what you are describing below that you are  
>> trying to
>> deploy liferay on geronimo.
>>
>> Although this might seem easier at first it's not automated and is  
>> a hard
>> way to get a plugin let alone a server.
>>
>> Automating it using maven records what you do in executable form and
>> should provide a simple way to track progress towards a working  
>> plugin and
>> something to update for new versions of liferay and geronimo.
>>
>
> Ok, I now understand where you are driving this.
>
> This sounds like a far superior approach.
>
>
> I have followed your instructions at your wiki page "Constructing a
> special-purpose server using maven", and all goes well until the  
> step: Build
> a database plugin.
>
> It appears that the archetype is not found.

I forgot to deploy the snapshots.

I've changed the archetype name from geronimo-module-archetype to  
geronimo-plugin-archetype and deployed a snapshot.  I also updated  
the wiki page to the new archetype name.  I think the (modified)  
instructions should now work, but you are definitely the guinea  
pig :-).  The archetypes should download automatically but I haven't  
tested this.

thanks
david jencks

>
> Full output to the console:
> ---------------------------------------------------------------------- 
> -----------------------------
> D:\Geronimo\plugins\liferay-parent>mvn archetype:create
> -DarchetypeGroupId=org.apache.geronimo.buildsupport \
>
> -DarchetypeArtifactId=geronimo-module-archetype \
>
> -DarchetypeVersion=2.2-SNAPSHOT \
>
> -DgroupId=org.apache.geronimo.plugins \
>
> -DartifactId=liferay-derby \
>
> -Dversion=1.0-SNAPSHOT
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] Building liferay-parent
> [INFO]    task-segment: [archetype:create] (aggregator-style)
> [INFO]
> ---------------------------------------------------------------------- 
> ------
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **************************************************************
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive:
> org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive:  
> org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive:  
> org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive:
> org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive:
> org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource  
> 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using  VM library template  
> VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to  
> find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro :  VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined  
> inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline  
> will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [archetype:create]
> [INFO] Defaulting package to group ID: org.apache.geronimo.plugins
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [ERROR] BUILD ERROR
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Failed to resolve artifact.
>
> GroupId: org.apache.geronimo.buildsupport
> ArtifactId: geronimo-module-archetype
> Version: 2.2-SNAPSHOT
>
> Reason: Unable to download the artifact from any repository
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>     mvn install:install-file - 
> DgroupId=org.apache.geronimo.buildsupport
> -DartifactId=geronimo-module-archetype \
>         -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:     mvn deploy:deploy-file - 
> DgroupId=org.apache.geronimo.buildsupport
> -DartifactId=geronimo-module-archetype \
>         -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \
>          -Durl=[url] -DrepositoryId=[id]
>
>
>
> org.apache.geronimo.buildsupport:geronimo-module-archetype:jar:2.2- 
> SNAPSHOT
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
>
>
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ---------------------------------------------------------------------- 
> --
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Thu Feb 28 09:45:26 MST 2008
> [INFO] Final Memory: 4M/8M
> [INFO]
> ---------------------------------------------------------------------- 
> --
>
> ---------------------------------------------------------------------- 
> -----------------------------
>
>
> Did I goof, or is something amiss?
>
> Jim
>
>
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15741053.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>



Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.
Hi David,

Responses in-line.


djencks wrote:
> 
> Hi Jim,
> 
> I think I have failed to communicate what I'm trying to tell you what to
> do :-)
> 


That would explain why I had the feeling that I wasn't connecting all the
dots...and which is why I took the time to explain all the details on my
end.



djencks wrote:
> 
> I've tried to explain in more detail here:
> 
>  
> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
> 


Now this is making sense.

I wish I had this information a week ago.




djencks wrote:
> 
> Two things I'm not trying to do:
> 1. show you how to deploy liferay on geronimo
> 2. give you a maven project that builds a liferay plugin and assembly
> 
> What I am trying to explain is how you can set up a maven project to build
> liferay plugins and assemblies, with the help of the geronimo archetypes
> for these kind of projects.
> 
> It looks to me from what you are describing below that you are trying to
> deploy liferay on geronimo.
> 
> Although this might seem easier at first it's not automated and is a hard
> way to get a plugin let alone a server.
> 
> Automating it using maven records what you do in executable form and
> should provide a simple way to track progress towards a working plugin and
> something to update for new versions of liferay and geronimo.
> 

Ok, I now understand where you are driving this.

This sounds like a far superior approach.


I have followed your instructions at your wiki page "Constructing a
special-purpose server using maven", and all goes well until the step: Build
a database plugin.

It appears that the archetype is not found.

Full output to the console:
---------------------------------------------------------------------------------------------------
D:\Geronimo\plugins\liferay-parent>mvn archetype:create
-DarchetypeGroupId=org.apache.geronimo.buildsupport \
                                                                                     
-DarchetypeArtifactId=geronimo-module-archetype \
                                                                                     
-DarchetypeVersion=2.2-SNAPSHOT \
                                                                                     
-DgroupId=org.apache.geronimo.plugins \
                                                                                     
-DartifactId=liferay-derby \
                                                                                     
-Dversion=1.0-SNAPSHOT
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building liferay-parent
[INFO]    task-segment: [archetype:create] (aggregator-style)
[INFO]
----------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] **************************************************************
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
any resource loader.
[INFO] Velocimacro : error using  VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be 
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [archetype:create]
[INFO] Defaulting package to group ID: org.apache.geronimo.plugins
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.geronimo.buildsupport
ArtifactId: geronimo-module-archetype
Version: 2.2-SNAPSHOT

Reason: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport
-DartifactId=geronimo-module-archetype \
        -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:     mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport
-DartifactId=geronimo-module-archetype \
        -Dversion=2.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \
         -Durl=[url] -DrepositoryId=[id]


 
org.apache.geronimo.buildsupport:geronimo-module-archetype:jar:2.2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Feb 28 09:45:26 MST 2008
[INFO] Final Memory: 4M/8M
[INFO]
------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------


Did I goof, or is something amiss?

Jim


-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15741053.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
Hi Jim,

I think I have failed to communicate what I'm trying to tell you what  
to do :-)  I've tried to explain in more detail here:

http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
+special-purpose+server+using+maven

Two things I'm not trying to do:
1. show you how to deploy liferay on geronimo
2. give you a maven project that builds a liferay plugin and assembly

What I am trying to explain is how you can set up a maven project to  
build liferay plugins and assemblies, with the help of the geronimo  
archetypes for these kind of projects.

It looks to me from what you are describing below that you are trying  
to deploy liferay on geronimo.  Although this might seem easier at  
first it's not automated and is a hard way to get a plugin let alone  
a server.  Automating it using maven records what you do in  
executable form and should provide a simple way to track progress  
towards a working plugin and something to update for new versions of  
liferay and geronimo.

thanks!
david jencks

On Feb 26, 2008, at 11:38 AM, Jim Foster wrote:

>
> Hi David,
>
> My responses are in-line.
>
>
> djencks wrote:
>>
>> I got the archetypes sort of working and made some progress on  
>> liferay.
>>
>> See https://issues.apache.org/jira/browse/GERONIMO-3871 and the  
>> attached
>> jar which contains the projects I came up with and some notes on  
>> what I
>> did.
>>
>> It would be great if you could imitate what I did to see if my
>> instructions make sense. I'm planning to write up something like  
>> this in
>> the docs.
>>
>
>
> Yes, your instructions make sense...up to the archetype part,  
> particularly
> what you mean by "Edit the poms and plans.".
>
> It may just be my lack of familiarity with Geronimo deployment  
> plans, but in
> the command line for the war file, you specify
>
>   groupId=com.liferay
>   artifactId=liferay-portal
>   version=4.4.1
>   packaging=war
>
> ...but looking at your editiion of geronimo-web.xml I see this:
>
>   <moduleId>
>     <groupId>liferay</groupId>
>     <artifactId>liferay-portal-tomcat</artifactId>
>     <version>4.4.1</version>
>     <type>car</type>
>   </moduleId>
>
> Shouldn't these by in sync? (meaning the artifactId)
>
>
> The only thing I don't see covered was the required derby-pool, but  
> I think
> we might agree that Shiva has that well covered.
>
> Eventually, what is really needed is an example of how to use a  
> database
> like MySQL or Oracle so one may use the Liferay database scripts to  
> populate
> it.
>
>
> Here is the writeup of my experience as feedback. Hopefully, this  
> may also
> help your documentation effort.
>
> I would greatly appreciate your comments/corrections.
>
>
> Summary:
> ------------
> I did the same as you outlined in the file
>
>   LIFERAY-README.txt
>
> found in your liferay-sample-project.jar of
>
>   https://issues.apache.org/jira/browse/GERONIMO-3871
>
> except that I used
>
>   Console > Repository => deploy the dependencies (jars)
>   Console > Deploy New => deploy the war
>
> Deployment of the liferay-portal-geronimo-derby-pool-4.4.1.car was  
> via the
> deploy tool.
>
> See Details, below.
>
>
> Result:
> --------
> Security-related issues were resolved if your geronimo-web.xml file is
> modified to point to where j2ee-security lives (see [4] below).
> However, a new problem emerges (see bottom of [4] below).
>
> See Details, below.
>
>
> Details:
> ---------
> The rest of this post details what is summarized above.
> I'm going to be verbose in outlining my steps-taken so as to be  
> sure we are
> staying in sync as to full context/assumptions.
>
> Sections below:
>
>   [1] versions
>   [2] liferay-portal-dependencies-4.4.1.zip
>   [3] liferay-portal-geronimo-derby-pool-4.4.1.car
>   [4] liferay-portal-4.4.1.war
>
> Bottom of post:
>
>   [geronimo-plugin.xml]
>   [geronimo-web.xml]
>
>
> [1] versions
>
>     • Geronimo version: The offical 2.1 release found at
> http://geronimo.apache.org/downloads.html
>     • OS: Windows XP, SP2, current with all hotfixes
>     • Apache version: 2.2.4
>     • Java version: 1.5.0_14
>
>
> [2] liferay-portal-dependencies-4.4.1.zip
>
>     • Used Console > Repository to deploy
>
>         - portal-kernel.jar
>         - portal-service.jar
>
>     • Group/Artifact/Version/Type was specified the same as you  
> stated in
> your LIFERAY-README.txt,
>       so added to the repository were:
>
>         com/liferay/
>                     portal-kernel/4.4.1/portal-kernel-4.4.1.jar
>                     portal-service/4.4.1/portal-service-4.4.1.jar
>
>
> [3] liferay-portal-geronimo-derby-pool-4.4.1.car
>
>     • Downloaded from
> http://sourceforge.net/project/showfiles.php?group_id=49260
>
>     • Extracted contents of the car file
>
>     • Modified the META-INF/geronimo-plugin.xml file as discussed  
> in Shiva's
> post of Feb 22, 2008; 05:14am
>
> (http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy- 
> Liferay-4.1.1-tt15437773s134.html)
>       File contents is at bottom of this post. See [geronimo- 
> plugin.xml].
>
>     • Regenerated the car file:
>
>         jar -cf liferay-portal-geronimo-derby-pool-4.4.1.car *
>
>     • Deployed that car file via the command line:
>
>         deploy --user system --password manager install-plugin
> liferay-portal-geronimo-derby-pool-4.4.1.car
>
>       Console output was:
>
>
> ---------------------------------------------------------------------- 
> -------------
>         Using GERONIMO_BASE:   D:\Geronimo\geronimo-tomcat6- 
> javaee5-2.1
>         Using GERONIMO_HOME:   D:\Geronimo\geronimo-tomcat6- 
> javaee5-2.1
>         Using GERONIMO_TMPDIR: var  emp
>         Using JRE_HOME:        D:\Java\jdk1.5.0_14\jre
>         Checking for status every 1000ms:
>         Downloading liferay/liferay-pool/4.4.1/car (65%)
>         Starting liferay/liferay-pool/4.4.1/car
>
>         **** Installation Complete!
>         Used existing: org.apache.derby/derby/10.2.2.0/jar
>         Used existing: org.apache.geronimo.configs/system-database// 
> car
>         Used existing: org.apache.geronimo.configs/transaction//car
>         Used existing: org.apache.geronimo.configs/j2ee-server//car
>
>         Downloaded 5687 kB in 5s (1137 kB/s)
>             Now starting liferay/liferay-pool/4.4.1/car...
>             Module liferay/liferay-pool/4.4.1/car is already running
>
> ---------------------------------------------------------------------- 
> -------------
>
>     • Database confirmation
>
>         The above is confirmed via Console> DB Manager.
>
>         The "Database List" contains the db "lportal", and "View  
> Tables"
> shows 109 tables in that database.
>
>
>
> [4] liferay-portal-4.4.1.war
>
>     • Downloaded from
> http://sourceforge.net/project/showfiles.php?group_id=49260
>
>     • Extracted contents of the war file
>
>     • Modified the META-INF/geronimo-web.xml file as discussed in  
> your post
> of Feb 21, 2008; 06:16pm
>
> (http://www.nabble.com/Re%3A-Geronimo-v2.1-Plan-Creator-%3D%3E- 
> Deploy-Liferay-4.4.1-tt15623755s134.html)
>       File contents is at bottom of this post. See [geronimo-web.xml].
>
>     • Observations:
>
>         1)  I note that the namespace specified for
>
>               gbean name="CredentialStore"
> (http://geronimo.apache.org/xml/ns/credentialstore-1.0)
>
>             does not exist.
>
>         2)  I note that you have this in the geronimo-web.xml:
>
>                 <dependency>
>                   <groupId>org.apache.geronimo.configs</groupId>
>                   <artifactId>j2ee-security</artifactId>
>                   <type>car</type>
>                 </dependency>
>
>             ...but I see that j2ee-security does not exist in the  
> configs
> directory.
>
>             It does exist in the framework directory, so shouldn't  
> the above
> be the following?
>
>                 <dependency>
>                   <groupId>org.apache.geronimo.framework</groupId>
>                   <artifactId>j2ee-security</artifactId>
>                   <type>car</type>
>                 </dependency>
>
>             My tests seem to confirm this.
>
>             If using
>
>               <groupId>org.apache.geronimo.configs</groupId>
>
>             one sees this:
>
>               ...
>               Caused by:
> org.apache.geronimo.kernel.repository.MissingDependencyException:  
> Missing
> dependency: org.apache.geronimo.configs/j2ee-security//car
>               at
> org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveI 
> nClassLoader(DefaultArtifactResolver.java:111)
>               at
> org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveI 
> nClassLoader(DefaultArtifactResolver.java:104)
>               at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolvePa 
> rentIds(SimpleConfigurationManager.java:473)
>               at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepth 
> First(SimpleConfigurationManager.java:431)
>               at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfi 
> guration(SimpleConfigurationManager.java:296)
>               ... 21 more
>               ...
>
>             Whereas the above error goes away using
>
>               <groupId>org.apache.geronimo.framework</groupId>
>
>
>     • Regenerated the war file:
>
>         jar -cf liferay-portal-4.4.1.war *
>
>     • Deployed that war file via the Console > Deploy New
>
>       Console output was:
>
>
> ---------------------------------------------------------------------- 
> -------------------------------------------
>       Install New Applications
>       Deployment failed:
>       Failed to load servlet class
> com.liferay.portal.kernel.servlet.PortalDelegatorServlet
>       Show full details
>
>       Failed to load servlet class
> com.liferay.portal.kernel.servlet.PortalDelegatorServlet
>       org.apache.geronimo.common.DeploymentException: Failed to  
> load servlet
> class com.liferay.portal.kernel.servlet.PortalDelegatorServlet
>         at
> org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverPOJOWebS 
> ervices(WARWebServiceFinder.java:116)
>         at
> org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverWebServi 
> ces(WARWebServiceFinder.java:58)
>         at
> org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.discoverWebServi 
> ces(JAXWSServiceBuilder.java:97)
>         at
> org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.findWebServices( 
> JAXWSServiceBuilder.java:80)
>         at
> org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicIni 
> tContext(AbstractWebModuleBuilder.java:364)
>         at
> org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext( 
> TomcatModuleBuilder.java:326)
>         at
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext 
> (SwitchingModuleBuilder.java:159)
>         at
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguratio 
> n(EARConfigBuilder.java:595)
>         at org.apache.geronimo.deployment.Deployer.deploy 
> (Deployer.java:254)
>         at org.apache.geronimo.deployment.Deployer.deploy 
> (Deployer.java:133)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke 
> (ReflectionMethodInvoker.java:34)
>         at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke 
> (GBeanOperation.java:124)
>         at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke 
> (GBeanInstance.java:867)
>         at
> org.apache.geronimo.kernel.basic.BasicKernel.invoke 
> (BasicKernel.java:239)
>         at
> org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDe 
> ploy(AbstractDeployCommand.java:116)
>         at
> org.apache.geronimo.deployment.plugin.local.DistributeCommand.run 
> (DistributeCommand.java:61)
>         at java.lang.Thread.run(Thread.java:595)
>       Caused by: java.lang.ClassNotFoundException:
> com.liferay.portal.kernel.servlet.PortalDelegatorServlet in  
> classloader
> liferay/liferay-portal-tomcat/4.4.1/car
>         at
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimized 
> Class(MultiParentClassLoader.java:428)
>         at
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass 
> (MultiParentClassLoader.java:278)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at
> org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverPOJOWebS 
> ervices(WARWebServiceFinder.java:109)
>         ... 20 more
>
> ---------------------------------------------------------------------- 
> -------------------------------------------
>
>
>       I'm stumped on this one.
>
>       If one opens up the portal-kernel-4.4.1.jar that was deployed  
> in step
> [2] above, one sees the PortalDelegatorServlet class right where it's
> supposed to be.
>
>       A classloader problem of some kind, perhaps?
>
>
>
>
> djencks wrote:
>>
>> As noted with the attachment the server won't actually start, it  
>> gets OOM
>> permgen errors even with 512m.
>>
>
> I don't get this far.
>
>
>
> djencks wrote:
>>
>> Where did the geronimo-web.xml come from?  Is it under an asl- 
>> compatible
>> license?  If so I'd like to use this as an example for the docs,
>> especially if we can get it to work.
>>
>> thanks
>> david jencks
>>
>
>
> I see that Peter has already answered these, so I will just add to his
> answers the following:
>
> geronimo-web.xml is but one of several application server  
> configurations in
> the WEB-INF directory of the liferay-portal-4.4.1.war.
> This includes
>
>     geronimo-web.xml
>     jboss-web.xml
>     jonas-web.xml
>     jrun-web.xml
>     resin-web.xml
>     rexip-web.xml
>     sun-web.xml
>     web-borland.xml
>     web-jetty.xml
>     weblogic.xml
>
>
>
> You may view a synopsis of Liferay's business philosophy at
>
>   http://www.liferay.com/web/guest/products/licensing
>
> This includes an explicit statement on the MIT license.
>
>
> Jim
>
>
>
> ******************************
> Attachments referenced above.
>
>   • [geronimo-plugin.xml]
>   • [geronimo-web.xml]
>
>
> ===============
> [geronimo-plugin.xml]
> ===============
> <?xml version="1.0" encoding="UTF-8"?>
> <geronimo-plugin xmlns="http://geronimo.apache.org/xml/ns/ 
> plugins-1.3">
> <name>liferay/liferay-pool/4.4.1/car</name>
> <module-id>liferay/liferay-pool/4.4.1/car</module-id>
> <category>Portal</category>
> <description>Liferay Pool is the JDBC connection pool used by Liferay
> Portal. The pool is backed by an embedded Derby database.</ 
> description>
> <url>http://www.liferay.com</url>
> <author>Liferay, Inc.</author>
> <license osi-approved="true">MIT</license>
>     <plugin-artifact>
>         <module-id>
>             <groupId>liferay</groupId>
>             <artifactId>liferay-pool</artifactId>
>             <version>4.4.1</version>
>             <type>car</type>
>         </module-id>
>         <geronimo-version>2.1</geronimo-version>
>         <jvm-version>1.5</jvm-version>
>         <dependency>
>             <groupId>org.apache.derby</groupId>
>             <artifactId>derby</artifactId>
>             <version>10.2.2.0</version>
>             <type>jar</type>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.geronimo.configs</groupId>
>             <artifactId>system-database</artifactId>
>             <type>car</type>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.geronimo.configs</groupId>
>             <artifactId>transaction</artifactId>
>             <type>car</type>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.geronimo.configs</groupId>
>             <artifactId>j2ee-server</artifactId>
>             <type>car</type>
>         </dependency>
>         <obsoletes>
>             <groupId>liferay</groupId>
>             <artifactId>liferay-pool</artifactId>
>             <type>car</type>
>         </obsoletes>
>     </plugin-artifact>
> </geronimo-plugin>
>
>
>
> ==============
> [geronimo-web.xml]
> ==============
> <?xml version="1.0"?>
> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
>     <environment>
>         <moduleId>
>             <groupId>liferay</groupId>
>             <artifactId>liferay-portal-tomcat</artifactId>
>             <version>4.4.1</version>
>             <type>car</type>
>         </moduleId>
>         <dependencies>
>             <dependency>
>                 <groupId>org.apache.geronimo.configs</groupId>
>                 <artifactId>j2ee-security</artifactId>
>                 <type>car</type>
>             </dependency>
>             <dependency>
>                 <groupId>org.apache.geronimo.configs</groupId>
>                 <artifactId>j2ee-server</artifactId>
>                 <type>car</type>
>             </dependency>
>             <dependency>
>                 <groupId>org.apache.geronimo.configs</groupId>
>                 <artifactId>javamail</artifactId>
>                 <type>car</type>
>             </dependency>
>             <dependency>
>                 <groupId>org.apache.geronimo.configs</groupId>
>                 <artifactId>sharedlib</artifactId>
>                 <type>car</type>
>             </dependency>
>             <dependency>
>                 <groupId>org.apache.geronimo.modules</groupId>
>                 <artifactId>geronimo-mail</artifactId>
>                 <type>jar</type>
>                 <import>classes</import>
>             </dependency>
>             <dependency>
>                 <groupId>liferay</groupId>
>                 <artifactId>liferay-pool</artifactId>
>                 <type>car</type>
>             </dependency>
> <!--
>             <dependency>
>                 <groupId>liferay</groupId>
>                 <artifactId>portal-kernel</artifactId>
>                 <type>jar</type>
>                 <import>classes</import>
>             </dependency>
>             <dependency>
>                 <groupId>liferay</groupId>
>                 <artifactId>portal-service</artifactId>
>                 <type>jar</type>
>                 <import>classes</import>
>             </dependency>
>             <dependency>
>                 <groupId>portlet-api</groupId>
>                 <artifactId>portlet-api</artifactId>
>                 <type>jar</type>
>                 <import>classes</import>
>             </dependency>
> -->
>         </dependencies>
>         <inverse-classloading />
>     </environment>
>
>     <context-root>/</context-root>
>
>     <security-realm-name>PortalRealm</security-realm-name>
>
>     <security use-context-handler="false"
> xmlns="http://geronimo.apache.org/xml/ns/security-2.0">
>       <default-subject>
>       <realm>PortalRealm</realm>
>       <id>default</id>
>       </default-subject>
>       <role-mappings>
>       <role role-name="users">
>         <principal class="com.liferay.portal.security.jaas.PortalRole"
> name="users" />
>       </role>
>       </role-mappings>
>     </security>
>
>     <!-- if you name the pool jdbc/LiferayPool you can omit this  
> mapping -->
>     <resource-ref>
>         <ref-name>jdbc/LiferayPool</ref-name>
>         <resource-link>LiferayPool</resource-link>
>     </resource-ref>
>
>     <!-- unless you have specific mail configuration I'd suggest  
> you use the
> built in mail/MailSession in the javamail plugin so you can omit this
> mapping -->
>     <resource-ref>
>         <ref-name>mail/MailSession</ref-name>
>         <resource-link>LiferayMailSession</resource-link>
>     </resource-ref>
>
>     <gbean name="CredentialStore"
> class="org.apache.geronimo.security.credentialstore.SimpleCredentialSt 
> oreImpl">
>       <xml-attribute name="credentialStore">
>         <credential-store
> xmlns="http://geronimo.apache.org/xml/ns/credentialstore-1.0">
>           <realm name="PortalRealm">
>             <subject>
>               <id>default</id>
>               <!-- you will have so set up the backing store  
> appropriately
> -->
>               <credential>
>
> <type>org.apache.geronimo.security.credentialstore.NameCallbackHandler 
> </type>
>                 <value>anonymous</value>
>               </credential>
>               <credential>
>
> <type>org.apache.geronimo.security.credentialstore.PasswordCallbackHan 
> dler</type>
>                 <value>anonymous</value>
>               </credential>
>             </subject>
>           </realm>
>         </credential-store>
>       </xml-attribute>
>     </gbean>
>
>     <gbean name="LiferayMailSession"
> class="org.apache.geronimo.mail.MailGBean">
>         <attribute name="transportProtocol">smtp</attribute>
>         <attribute name="host">localhost</attribute>
>     </gbean>
>
>     <gbean name="PortalRealm"
> class="org.apache.geronimo.security.realm.GenericSecurityRealm">
>         <attribute name="realmName">PortalRealm</attribute>
>         <reference name="ServerInfo">
>             <name>ServerInfo</name>
>         </reference>
> <!--
>         <reference name="LoginService">
>             <name>JaasLoginService</name>
>         </reference>
> -->
>         <xml-reference name="LoginModuleConfiguration">
>             <log:login-config
> xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0">
>                 <log:login-module control-flag="REQUIRED"
> wrap-principals="false">
>
> <log:login-domain-name>PortalRealm</log:login-domain-name>
>
> <log:login-module- 
> class>com.liferay.portal.security.jaas.ext.tomcat.PortalLoginModule</l 
> og:login-module-class>
>                 </log:login-module>
>             </log:login-config>
>         </xml-reference>
>     </gbean>
> </web-app>
>
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15673907.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.
Hi David,

My responses are in-line.


djencks wrote:
> 
> I got the archetypes sort of working and made some progress on liferay.
> 
> See https://issues.apache.org/jira/browse/GERONIMO-3871 and the attached
> jar which contains the projects I came up with and some notes on what I
> did.
> 
> It would be great if you could imitate what I did to see if my
> instructions make sense. I'm planning to write up something like this in
> the docs.
> 


Yes, your instructions make sense...up to the archetype part, particularly
what you mean by "Edit the poms and plans.".

It may just be my lack of familiarity with Geronimo deployment plans, but in
the command line for the war file, you specify
  
  groupId=com.liferay
  artifactId=liferay-portal
  version=4.4.1
  packaging=war

...but looking at your editiion of geronimo-web.xml I see this:

  <moduleId>
    <groupId>liferay</groupId>
    <artifactId>liferay-portal-tomcat</artifactId>
    <version>4.4.1</version>
    <type>car</type>
  </moduleId>

Shouldn't these by in sync? (meaning the artifactId)


The only thing I don't see covered was the required derby-pool, but I think
we might agree that Shiva has that well covered.

Eventually, what is really needed is an example of how to use a database
like MySQL or Oracle so one may use the Liferay database scripts to populate
it.


Here is the writeup of my experience as feedback. Hopefully, this may also
help your documentation effort.

I would greatly appreciate your comments/corrections.


Summary:
------------
I did the same as you outlined in the file 
  
  LIFERAY-README.txt

found in your liferay-sample-project.jar of 

  https://issues.apache.org/jira/browse/GERONIMO-3871
  
except that I used 

  Console > Repository => deploy the dependencies (jars)
  Console > Deploy New => deploy the war

Deployment of the liferay-portal-geronimo-derby-pool-4.4.1.car was via the
deploy tool.

See Details, below.


Result:
--------
Security-related issues were resolved if your geronimo-web.xml file is
modified to point to where j2ee-security lives (see [4] below).
However, a new problem emerges (see bottom of [4] below).

See Details, below.


Details:
---------
The rest of this post details what is summarized above.
I'm going to be verbose in outlining my steps-taken so as to be sure we are
staying in sync as to full context/assumptions.

Sections below:

  [1] versions
  [2] liferay-portal-dependencies-4.4.1.zip
  [3] liferay-portal-geronimo-derby-pool-4.4.1.car
  [4] liferay-portal-4.4.1.war

Bottom of post:

  [geronimo-plugin.xml]
  [geronimo-web.xml]
  

[1] versions

    • Geronimo version: The offical 2.1 release found at
http://geronimo.apache.org/downloads.html
    • OS: Windows XP, SP2, current with all hotfixes
    • Apache version: 2.2.4
    • Java version: 1.5.0_14


[2] liferay-portal-dependencies-4.4.1.zip

    • Used Console > Repository to deploy
    
        - portal-kernel.jar
        - portal-service.jar
      
    • Group/Artifact/Version/Type was specified the same as you stated in
your LIFERAY-README.txt,
      so added to the repository were:
    
        com/liferay/
                    portal-kernel/4.4.1/portal-kernel-4.4.1.jar
                    portal-service/4.4.1/portal-service-4.4.1.jar


[3] liferay-portal-geronimo-derby-pool-4.4.1.car
    
    • Downloaded from
http://sourceforge.net/project/showfiles.php?group_id=49260
    
    • Extracted contents of the car file
    
    • Modified the META-INF/geronimo-plugin.xml file as discussed in Shiva's
post of Feb 22, 2008; 05:14am
     
(http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tt15437773s134.html)
      File contents is at bottom of this post. See [geronimo-plugin.xml].
    
    • Regenerated the car file:
    
        jar -cf liferay-portal-geronimo-derby-pool-4.4.1.car *
    
    • Deployed that car file via the command line:
    
        deploy --user system --password manager install-plugin
liferay-portal-geronimo-derby-pool-4.4.1.car
        
      Console output was:
      
       
-----------------------------------------------------------------------------------
        Using GERONIMO_BASE:   D:\Geronimo\geronimo-tomcat6-javaee5-2.1
        Using GERONIMO_HOME:   D:\Geronimo\geronimo-tomcat6-javaee5-2.1
        Using GERONIMO_TMPDIR: var  emp
        Using JRE_HOME:        D:\Java\jdk1.5.0_14\jre
        Checking for status every 1000ms:
        Downloading liferay/liferay-pool/4.4.1/car (65%)
        Starting liferay/liferay-pool/4.4.1/car

        **** Installation Complete!
        Used existing: org.apache.derby/derby/10.2.2.0/jar
        Used existing: org.apache.geronimo.configs/system-database//car
        Used existing: org.apache.geronimo.configs/transaction//car
        Used existing: org.apache.geronimo.configs/j2ee-server//car

        Downloaded 5687 kB in 5s (1137 kB/s)
            Now starting liferay/liferay-pool/4.4.1/car...
            Module liferay/liferay-pool/4.4.1/car is already running
       
-----------------------------------------------------------------------------------
    
    • Database confirmation
    
        The above is confirmed via Console> DB Manager.
        
        The "Database List" contains the db "lportal", and "View Tables"
shows 109 tables in that database.



[4] liferay-portal-4.4.1.war
    
    • Downloaded from
http://sourceforge.net/project/showfiles.php?group_id=49260
    
    • Extracted contents of the war file
    
    • Modified the META-INF/geronimo-web.xml file as discussed in your post
of Feb 21, 2008; 06:16pm
     
(http://www.nabble.com/Re%3A-Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.4.1-tt15623755s134.html)
      File contents is at bottom of this post. See [geronimo-web.xml].
      
    • Observations:
     
        1)  I note that the namespace specified for 
        
              gbean name="CredentialStore" 
(http://geronimo.apache.org/xml/ns/credentialstore-1.0)
          
            does not exist.
        
        2)  I note that you have this in the geronimo-web.xml:
        
                <dependency>
                  <groupId>org.apache.geronimo.configs</groupId>
                  <artifactId>j2ee-security</artifactId>
                  <type>car</type>
                </dependency>
            
            ...but I see that j2ee-security does not exist in the configs
directory.
            
            It does exist in the framework directory, so shouldn't the above
be the following?
            
                <dependency>
                  <groupId>org.apache.geronimo.framework</groupId>
                  <artifactId>j2ee-security</artifactId>
                  <type>car</type>
                </dependency>
                
            My tests seem to confirm this.
            
            If using
            
              <groupId>org.apache.geronimo.configs</groupId>
              
            one sees this:
            
              ...
              Caused by:
org.apache.geronimo.kernel.repository.MissingDependencyException: Missing
dependency: org.apache.geronimo.configs/j2ee-security//car
              at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:111)
              at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:104)
              at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolveParentIds(SimpleConfigurationManager.java:473)
              at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:431)
              at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:296)
              ... 21 more
              ...
              
            Whereas the above error goes away using 
            
              <groupId>org.apache.geronimo.framework</groupId>
            
            
    • Regenerated the war file:
    
        jar -cf liferay-portal-4.4.1.war *
    
    • Deployed that war file via the Console > Deploy New
    
      Console output was:
      
     
-----------------------------------------------------------------------------------------------------------------
      Install New Applications
      Deployment failed:
      Failed to load servlet class
com.liferay.portal.kernel.servlet.PortalDelegatorServlet
      Show full details
      
      Failed to load servlet class
com.liferay.portal.kernel.servlet.PortalDelegatorServlet
      org.apache.geronimo.common.DeploymentException: Failed to load servlet
class com.liferay.portal.kernel.servlet.PortalDelegatorServlet
        at
org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverPOJOWebServices(WARWebServiceFinder.java:116)
        at
org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverWebServices(WARWebServiceFinder.java:58)
        at
org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.discoverWebServices(JAXWSServiceBuilder.java:97)
        at
org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.findWebServices(JAXWSServiceBuilder.java:80)
        at
org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext(AbstractWebModuleBuilder.java:364)
        at
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext(TomcatModuleBuilder.java:326)
        at
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext(SwitchingModuleBuilder.java:159)
        at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:595)
        at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
        at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
        at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
        at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
        at
org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
        at
org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
        at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.ClassNotFoundException:
com.liferay.portal.kernel.servlet.PortalDelegatorServlet in classloader
liferay/liferay-portal-tomcat/4.4.1/car
        at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:428)
        at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at
org.apache.geronimo.jaxws.builder.WARWebServiceFinder.discoverPOJOWebServices(WARWebServiceFinder.java:109)
        ... 20 more
     
-----------------------------------------------------------------------------------------------------------------
      
      
      I'm stumped on this one.
      
      If one opens up the portal-kernel-4.4.1.jar that was deployed in step
[2] above, one sees the PortalDelegatorServlet class right where it's
supposed to be.
      
      A classloader problem of some kind, perhaps?




djencks wrote:
> 
> As noted with the attachment the server won't actually start, it gets OOM
> permgen errors even with 512m.
> 

I don't get this far.



djencks wrote:
> 
> Where did the geronimo-web.xml come from?  Is it under an asl-compatible
> license?  If so I'd like to use this as an example for the docs,
> especially if we can get it to work.
> 
> thanks
> david jencks
> 


I see that Peter has already answered these, so I will just add to his
answers the following:

geronimo-web.xml is but one of several application server configurations in
the WEB-INF directory of the liferay-portal-4.4.1.war.
This includes

    geronimo-web.xml
    jboss-web.xml
    jonas-web.xml
    jrun-web.xml
    resin-web.xml
    rexip-web.xml
    sun-web.xml
    web-borland.xml
    web-jetty.xml
    weblogic.xml



You may view a synopsis of Liferay's business philosophy at

  http://www.liferay.com/web/guest/products/licensing

This includes an explicit statement on the MIT license.


Jim



******************************
Attachments referenced above.

  • [geronimo-plugin.xml]
  • [geronimo-web.xml]


===============
[geronimo-plugin.xml]
===============
<?xml version="1.0" encoding="UTF-8"?>
<geronimo-plugin xmlns="http://geronimo.apache.org/xml/ns/plugins-1.3">
<name>liferay/liferay-pool/4.4.1/car</name>
<module-id>liferay/liferay-pool/4.4.1/car</module-id>
<category>Portal</category>
<description>Liferay Pool is the JDBC connection pool used by Liferay
Portal. The pool is backed by an embedded Derby database.</description>
<url>http://www.liferay.com</url>
<author>Liferay, Inc.</author>
<license osi-approved="true">MIT</license>
    <plugin-artifact>
        <module-id>
            <groupId>liferay</groupId>
            <artifactId>liferay-pool</artifactId>
            <version>4.4.1</version>
            <type>car</type>
        </module-id>
        <geronimo-version>2.1</geronimo-version>
        <jvm-version>1.5</jvm-version>
        <dependency>
            <groupId>org.apache.derby</groupId>
            <artifactId>derby</artifactId>
            <version>10.2.2.0</version>
            <type>jar</type>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.configs</groupId>
            <artifactId>system-database</artifactId>
            <type>car</type>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.configs</groupId>
            <artifactId>transaction</artifactId>
            <type>car</type>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.configs</groupId>
            <artifactId>j2ee-server</artifactId>
            <type>car</type>
        </dependency>
        <obsoletes>
            <groupId>liferay</groupId>
            <artifactId>liferay-pool</artifactId>
            <type>car</type>
        </obsoletes>
    </plugin-artifact>
</geronimo-plugin>



==============
[geronimo-web.xml]
==============
<?xml version="1.0"?>
<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
    <environment>
        <moduleId>
            <groupId>liferay</groupId>
            <artifactId>liferay-portal-tomcat</artifactId>
            <version>4.4.1</version>
            <type>car</type>
        </moduleId>
        <dependencies>
            <dependency>
                <groupId>org.apache.geronimo.configs</groupId>
                <artifactId>j2ee-security</artifactId>
                <type>car</type>
            </dependency>
            <dependency>
                <groupId>org.apache.geronimo.configs</groupId>
                <artifactId>j2ee-server</artifactId>
                <type>car</type>
            </dependency>
            <dependency>
                <groupId>org.apache.geronimo.configs</groupId>
                <artifactId>javamail</artifactId>
                <type>car</type>
            </dependency>
            <dependency>
                <groupId>org.apache.geronimo.configs</groupId>
                <artifactId>sharedlib</artifactId>
                <type>car</type>
            </dependency>
            <dependency>
                <groupId>org.apache.geronimo.modules</groupId>
                <artifactId>geronimo-mail</artifactId>
                <type>jar</type>
                <import>classes</import>
            </dependency>
            <dependency>
                <groupId>liferay</groupId>
                <artifactId>liferay-pool</artifactId>
                <type>car</type>
            </dependency>
<!--
            <dependency>
                <groupId>liferay</groupId>
                <artifactId>portal-kernel</artifactId>
                <type>jar</type>
                <import>classes</import>
            </dependency>
            <dependency>
                <groupId>liferay</groupId>
                <artifactId>portal-service</artifactId>
                <type>jar</type>
                <import>classes</import>
            </dependency>
            <dependency>
                <groupId>portlet-api</groupId>
                <artifactId>portlet-api</artifactId>
                <type>jar</type>
                <import>classes</import>
            </dependency>
-->
        </dependencies>
        <inverse-classloading />
    </environment>
    
    <context-root>/</context-root>
    
    <security-realm-name>PortalRealm</security-realm-name>
    
    <security use-context-handler="false"
xmlns="http://geronimo.apache.org/xml/ns/security-2.0">
      <default-subject>
      <realm>PortalRealm</realm>
      <id>default</id>
      </default-subject>
      <role-mappings>
      <role role-name="users">
        <principal class="com.liferay.portal.security.jaas.PortalRole"
name="users" />
      </role>
      </role-mappings>
    </security>
  
    <!-- if you name the pool jdbc/LiferayPool you can omit this mapping -->
    <resource-ref>
        <ref-name>jdbc/LiferayPool</ref-name>
        <resource-link>LiferayPool</resource-link>
    </resource-ref>
    
    <!-- unless you have specific mail configuration I'd suggest you use the
built in mail/MailSession in the javamail plugin so you can omit this
mapping -->
    <resource-ref>
        <ref-name>mail/MailSession</ref-name>
        <resource-link>LiferayMailSession</resource-link>
    </resource-ref>

    <gbean name="CredentialStore"
class="org.apache.geronimo.security.credentialstore.SimpleCredentialStoreImpl">
      <xml-attribute name="credentialStore">
        <credential-store
xmlns="http://geronimo.apache.org/xml/ns/credentialstore-1.0">
          <realm name="PortalRealm">
            <subject>
              <id>default</id>
              <!-- you will have so set up the backing store appropriately
-->
              <credential>
               
<type>org.apache.geronimo.security.credentialstore.NameCallbackHandler</type>
                <value>anonymous</value>
              </credential>
              <credential>
               
<type>org.apache.geronimo.security.credentialstore.PasswordCallbackHandler</type>
                <value>anonymous</value>
              </credential>
            </subject>
          </realm>
        </credential-store>
      </xml-attribute>
    </gbean>

    <gbean name="LiferayMailSession"
class="org.apache.geronimo.mail.MailGBean">
        <attribute name="transportProtocol">smtp</attribute>
        <attribute name="host">localhost</attribute>
    </gbean>
    
    <gbean name="PortalRealm"
class="org.apache.geronimo.security.realm.GenericSecurityRealm">
        <attribute name="realmName">PortalRealm</attribute>
        <reference name="ServerInfo">
            <name>ServerInfo</name>
        </reference>
<!--
        <reference name="LoginService">
            <name>JaasLoginService</name>
        </reference>
-->
        <xml-reference name="LoginModuleConfiguration">
            <log:login-config
xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0">
                <log:login-module control-flag="REQUIRED"
wrap-principals="false">
                   
<log:login-domain-name>PortalRealm</log:login-domain-name>
                   
<log:login-module-class>com.liferay.portal.security.jaas.ext.tomcat.PortalLoginModule</log:login-module-class>
                </log:login-module>
            </log:login-config>
        </xml-reference>
    </gbean>
</web-app> 
        
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15673907.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@pmb.mine.nu>.
David Jencks wrote:
> I got the archetypes sort of working and made some progress on liferay.
>
> See https://issues.apache.org/jira/browse/GERONIMO-3871 and the 
> attached jar which contains the projects I came up with and some notes 
> on what I did.   It would be great if you could imitate what I did to 
> see if my instructions make sense.  I'm planning to write up something 
> like this in the docs.
>
> As noted with the attachment the server won't actually start, it gets 
> OOM permgen errors even with 512m.
>
>
> Where did the geronimo-web.xml come from?  Is it under an 
> asl-compatible license?  If so I'd like to use this as an example for 
> the docs, especially if we can get it to work.
The liferay portal is developed under MIT License ( 
http://en.wikipedia.org/wiki/MIT_License ) the source including the 
geronimo-web.xml file can be found at 
http://sourceforge.net/projects/lportal The geronimo-web.xml file can be 
viewed at 
http://lportal.svn.sourceforge.net/viewvc/lportal/portal/tags/4.4.1/portal-web/docroot/WEB-INF/

regards
   peter petersson
>
> thanks
> david jencks
>
> On Feb 22, 2008, at 7:45 AM, Jim Foster wrote:
>
>>
>>
>> Shiva Kumar H R wrote:
>>>
>>> On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu>
>>> wrote:
>>>
>>>>  Hi Jim
>>>>
>>>> I assume you are trying to install liferay in geronimo and not just
>>>> generate a new plan, with you do not need to, as Shiva have 
>>>> provided you
>>>> with one (the geronimo-web.xml).
>>>
>>> ...
>>>
>>> Looks like there is more to it than just that. I have been trying it 
>>> since
>>> yesterday and it is failing with below error:
>>>
>>> Installation FAILED: A plugin configuration must include one plugin
>>> artifact, not 0
>>>
>>> Any idea where is the source for
>>> liferay-portal-geronimo-derby-pool-4.4.1.car ?
>>>
>>> -- 
>>> Thanks,
>>> Shiva
>>>
>>>
>>
>> Hi Shiva,
>>
>> Let me pass on to you directly what I told Peter.
>>
>> I have an on-going discussion in process with David covering several
>> subtopics on this issue of running the Liferay portal in Geronimo.
>>
>> We are going to put a lid on these security issues, then move forward 
>> from
>> there...including addressing the Connector issue.
>>
>> Perhaps it would be best if we all knew what we were all saying to each
>> other? Please see the thread
>>
>>   "Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.4.1"
>>
>> started by djencks.
>>
>> The answer to your .car question is there.
>>
>>
>> Thanks!
>>
>> Jim
>>
>> -- 
>> View this message in context: 
>> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15634449.html 
>>
>> Sent from the Apache Geronimo - Users mailing list archive at 
>> Nabble.com.
>>
>
>


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by David Jencks <da...@yahoo.com>.
I got the archetypes sort of working and made some progress on liferay.

See https://issues.apache.org/jira/browse/GERONIMO-3871 and the  
attached jar which contains the projects I came up with and some  
notes on what I did.   It would be great if you could imitate what I  
did to see if my instructions make sense.  I'm planning to write up  
something like this in the docs.

As noted with the attachment the server won't actually start, it gets  
OOM permgen errors even with 512m.


Where did the geronimo-web.xml come from?  Is it under an asl- 
compatible license?  If so I'd like to use this as an example for the  
docs, especially if we can get it to work.

thanks
david jencks

On Feb 22, 2008, at 7:45 AM, Jim Foster wrote:

>
>
> Shiva Kumar H R wrote:
>>
>> On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu>
>> wrote:
>>
>>>  Hi Jim
>>>
>>> I assume you are trying to install liferay in geronimo and not just
>>> generate a new plan, with you do not need to, as Shiva have  
>>> provided you
>>> with one (the geronimo-web.xml).
>>
>> ...
>>
>> Looks like there is more to it than just that. I have been trying  
>> it since
>> yesterday and it is failing with below error:
>>
>> Installation FAILED: A plugin configuration must include one plugin
>> artifact, not 0
>>
>> Any idea where is the source for
>> liferay-portal-geronimo-derby-pool-4.4.1.car ?
>>
>> -- 
>> Thanks,
>> Shiva
>>
>>
>
> Hi Shiva,
>
> Let me pass on to you directly what I told Peter.
>
> I have an on-going discussion in process with David covering several
> subtopics on this issue of running the Liferay portal in Geronimo.
>
> We are going to put a lid on these security issues, then move  
> forward from
> there...including addressing the Connector issue.
>
> Perhaps it would be best if we all knew what we were all saying to  
> each
> other? Please see the thread
>
>   "Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.4.1"
>
> started by djencks.
>
> The answer to your .car question is there.
>
>
> Thanks!
>
> Jim
>
> -- 
> View this message in context: http://www.nabble.com/Geronimo-v2.1- 
> Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15634449.html
> Sent from the Apache Geronimo - Users mailing list archive at  
> Nabble.com.
>



Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.

Shiva Kumar H R wrote:
> 
> On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu>
> wrote:
> 
>>  Hi Jim
>>
>> I assume you are trying to install liferay in geronimo and not just
>> generate a new plan, with you do not need to, as Shiva have provided you
>> with one (the geronimo-web.xml).
> 
> ...
> 
> Looks like there is more to it than just that. I have been trying it since
> yesterday and it is failing with below error:
> 
> Installation FAILED: A plugin configuration must include one plugin
> artifact, not 0
> 
> Any idea where is the source for
> liferay-portal-geronimo-derby-pool-4.4.1.car ?
> 
> -- 
> Thanks,
> Shiva
> 
> 

Hi Shiva,

Let me pass on to you directly what I told Peter.

I have an on-going discussion in process with David covering several
subtopics on this issue of running the Liferay portal in Geronimo. 

We are going to put a lid on these security issues, then move forward from
there...including addressing the Connector issue.

Perhaps it would be best if we all knew what we were all saying to each
other? Please see the thread

  "Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.4.1"

started by djencks. 

The answer to your .car question is there.


Thanks!

Jim

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15634449.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <pe...@pmb.mine.nu> wrote:

>  Hi Jim
>
> I assume you are trying to install liferay in geronimo and not just
> generate a new plan, with you do not need to, as Shiva have provided you
> with one (the geronimo-web.xml).
>
> Aside from the security dependency issue you have that I hope **someone
> else** that are more familiar with the security (dependency) changes done
> between G v2.0.2 and v2.1 will help you with, there are a couple of more
> things to do:
>
> As the liferay-portal-geronimo-tomcat car is dependent (if you haven't
> changed the geronimo-web.xml regarding the db pool) on the
> liferay-portal-geronimo-derby-pool car, so to successfully install the
> liferay-portal-geronimo-tomcat car you have to install the derby pool
> **before** the liferay-portal-geronimo-tomcat car.
>
> After a smal tweak of the META-INF/geronimo-plugin.xml included in the
> derby-pool car file you should be able to install the db pool by issuing
>
> deploy --user <user> --password <passoword> install-plugin <derby pool car file>
>
> The geronimo-plugin.xml tweak consist of changing the version tag in the
> geronimo-plugin.xml to <version>2.1-SNAPSHOT</version> (omit -snapshot for
> released geronimo). The same command (as above) can then be used on the
> liferay-portal-geronimo-tomcat car (when the security dependency issue is
> fixed)
>

Looks like there is more to it than just that. I have been trying it since
yesterday and it is failing with below error:

Installation FAILED: A plugin configuration must include one plugin
artifact, not 0

Any idea where is the source for
liferay-portal-geronimo-derby-pool-4.4.1.car ?


> Maybe this link will be of some help to you even though it is a bit
> outdated http://wiki.liferay.com/index.php/Liferay_with_Geronimo
>
>  regards
>   peter petersson
>
>
>
> Jim Foster wrote:
>
> Shiva Kumar H R wrote:
>
>
>  There are two problems, both in Plan Creator feature:
> 1) Error message/Java Exceptions are suppressed by Plan Creator code and
> not
> shown to the user at all :-(
>
> With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
> remote
> connected via Eclipse (with a break point put at the beginning oforg.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
> function inside "plancreator-portlets" module), I found that we are
> getting
> following exception:
> org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
> Could not load servlet class: com.liferay.portal.servlet.MainServlet
>
> Instead of showing this error on Console, plan creator is currently
> suppressing it in an empty catch() block.
> *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850> <https://issues.apache.org/jira/browse/GERONIMO-3850>
> *is opened for this.
>
> 2) Secondly, I see that the class it is complaining "com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
> compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
> Creator has a current limitation :-( in resolving such classes. *
> GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
> opened for this.
>
> Due to these bugs/limitations, I am sorry to say that you will again have
> to
> create geronimo-web.xml by hand. I found one "geronimo-web.xml" insideliferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> from it and attached it in this mail. Please see if it works. (I guess it
> requires some pre-requisite db-pools to be deployed before the WAR can be
> deployed). Hope it helps.
>
> ...
>
>
>
>
>  Hi Shiva,
>
> Is there any new word on the origins of the security configuration errors we
> were seeing?
>
> I have spent a good deal of time this week reading everything I could get my
> hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
> developerworks.
> (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true).
>
> However, the most recent I could find that seemed relevant to this issue was
> on the wiki:
> http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
>
> However, this is an installation document, and provides little in the way of
> debugging guidelines, and I  am only now just far enough along in wrapping
> my head around all the technologies that make up Geronimo to get myself in
> trouble.
>
> Suggestions?
>
>
> Once past this, I would like your advise on how to bring up to date the
> Liferay-provided .car file for the derby pool. I looked at its contents, and
> I see that they are clearly wrong (my guess is that they were written forv1.1), but I am not quite sure how to go about fixing it so as to be in
> alignment with v2.1
>
> ...one step at a time though...first the security issue.
>
>
> Thank you for your time, patience, and advise.
>
> Jim
>
>
>
>
>
>
>
>


-- 
Thanks,
Shiva

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Peter Petersson <pe...@pmb.mine.nu>.
Hi Jim

I assume you are trying to install liferay in geronimo and not just 
generate a new plan, with you do not need to, as Shiva have provided you 
with one (the geronimo-web.xml).

Aside from the security dependency issue you have that I hope **someone 
else** that are more familiar with the security (dependency) changes 
done between G v2.0.2 and v2.1 will help you with, there are a couple of 
more things to do:

As the liferay-portal-geronimo-tomcat car is dependent (if you haven't 
changed the geronimo-web.xml regarding the db pool) on the 
liferay-portal-geronimo-derby-pool car, so to successfully install the 
liferay-portal-geronimo-tomcat car you have to install the derby pool 
**before** the liferay-portal-geronimo-tomcat car.
 
After a smal tweak of the META-INF/geronimo-plugin.xml included in the 
derby-pool car file you should be able to install the db pool by issuing

deploy --user <user> --password <passoword> install-plugin <derby pool car file>

The geronimo-plugin.xml tweak consist of changing the version tag in the 
geronimo-plugin.xml to <version>2.1-SNAPSHOT</version> (omit -snapshot 
for released geronimo). The same command (as above) can then be used on 
the liferay-portal-geronimo-tomcat car (when the security dependency 
issue is fixed)

Maybe this link will be of some help to you even though it is a bit 
outdated http://wiki.liferay.com/index.php/Liferay_with_Geronimo

 regards
  peter petersson
 

Jim Foster wrote:
>
> Shiva Kumar H R wrote:
>   
>> There are two problems, both in Plan Creator feature:
>> 1) Error message/Java Exceptions are suppressed by Plan Creator code and
>> not
>> shown to the user at all :-(
>>
>> With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
>> remote
>> connected via Eclipse (with a break point put at the beginning of
>> org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
>> function inside "plancreator-portlets" module), I found that we are
>> getting
>> following exception:
>>
>> org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
>> Could not load servlet class: com.liferay.portal.servlet.MainServlet
>>
>> Instead of showing this error on Console, plan creator is currently
>> suppressing it in an empty catch() block.
>> *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
>> *is opened for this.
>>
>> 2) Secondly, I see that the class it is complaining "
>> com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
>> compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
>> Creator has a current limitation :-( in resolving such classes. *
>> GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
>> opened for this.
>>
>> Due to these bugs/limitations, I am sorry to say that you will again have
>> to
>> create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
>> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
>> from it and attached it in this mail. Please see if it works. (I guess it
>> requires some pre-requisite db-pools to be deployed before the WAR can be
>> deployed). Hope it helps.
>>
>> ...
>>
>>
>>     
>
>
>
> Hi Shiva,
>
> Is there any new word on the origins of the security configuration errors we
> were seeing?
>
> I have spent a good deal of time this week reading everything I could get my
> hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
> developerworks.
> (http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true). 
>
> However, the most recent I could find that seemed relevant to this issue was
> on the wiki:
>
> http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html
>
> However, this is an installation document, and provides little in the way of
> debugging guidelines, and I  am only now just far enough along in wrapping
> my head around all the technologies that make up Geronimo to get myself in
> trouble.
>
> Suggestions?
>
>
> Once past this, I would like your advise on how to bring up to date the
> Liferay-provided .car file for the derby pool. I looked at its contents, and
> I see that they are clearly wrong (my guess is that they were written for
> v1.1), but I am not quite sure how to go about fixing it so as to be in
> alignment with v2.1
>
> ...one step at a time though...first the security issue.
>
>
> Thank you for your time, patience, and advise.
>
> Jim
>
>
>
>
>   


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.


Shiva Kumar H R wrote:
> 
> There are two problems, both in Plan Creator feature:
> 1) Error message/Java Exceptions are suppressed by Plan Creator code and
> not
> shown to the user at all :-(
> 
> With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and
> remote
> connected via Eclipse (with a break point put at the beginning of
> org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
> function inside "plancreator-portlets" module), I found that we are
> getting
> following exception:
> 
> org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
> Could not load servlet class: com.liferay.portal.servlet.MainServlet
> 
> Instead of showing this error on Console, plan creator is currently
> suppressing it in an empty catch() block.
> *GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
> *is opened for this.
> 
> 2) Secondly, I see that the class it is complaining "
> com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
> compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
> Creator has a current limitation :-( in resolving such classes. *
> GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
> opened for this.
> 
> Due to these bugs/limitations, I am sorry to say that you will again have
> to
> create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> from it and attached it in this mail. Please see if it works. (I guess it
> requires some pre-requisite db-pools to be deployed before the WAR can be
> deployed). Hope it helps.
> 
> ...
> 
> 



Hi Shiva,

Is there any new word on the origins of the security configuration errors we
were seeing?

I have spent a good deal of time this week reading everything I could get my
hands on, including a healthy chunk of the 120 Geronimo articles up at IBM's
developerworks.
(http://www.ibm.com/developerworks/views/opensource/libraryview.jsp?end_no=120&lcl_sort_order=asc&type_by=All+Types&sort_order=asc&start_no=1&show_all=true&sort_by=Date&search_by=&topic_by=Geronimo&search_flag=&show_abstract=true). 

However, the most recent I could find that seemed relevant to this issue was
on the wiki:

http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html

However, this is an installation document, and provides little in the way of
debugging guidelines, and I  am only now just far enough along in wrapping
my head around all the technologies that make up Geronimo to get myself in
trouble.

Suggestions?


Once past this, I would like your advise on how to bring up to date the
Liferay-provided .car file for the derby pool. I looked at its contents, and
I see that they are clearly wrong (my guess is that they were written for
v1.1), but I am not quite sure how to go about fixing it so as to be in
alignment with v2.1

...one step at a time though...first the security issue.


Thank you for your time, patience, and advise.

Jim




-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15621951.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.
Hi Shiva,

I'm sorry. I must have missed where in our discussion we changed from "Plan
Creator" to "Deploy New". I also do not see this process documented anywhere
at http://cwiki.apache.org/GMOxDOC21/, so please be patient with my
denseness, here.

I have done as you instructed:

[1] Console Navigation > Deploy New

    Install New Applications
    - Archive: 	specified liferay-portal-4.4.1.war (as it comes from
Liferay, no mods)
    - Plan: specified your edition of geronimo-web.xml

[2] Here are the results:

    Install New Applications
      Deployment failed:
      Unable to create configuration for deployment 

[3] Clicking the "Show Full Details" shows the following:

Unable to create configuration for deployment
org.apache.geronimo.common.DeploymentException: Unable to create
configuration for deployment
	at
org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:120)
	at
org.apache.geronimo.deployment.DeploymentContext.<init>(DeploymentContext.java:100)
	at
org.apache.geronimo.deployment.DeploymentContext.<init>(DeploymentContext.java:80)
	at
org.apache.geronimo.j2ee.deployment.EARContext.<init>(EARContext.java:68)
	at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:530)
	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
	at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
	at
org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
	at
org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
	at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.geronimo.kernel.config.LifecycleException: load of
liferay/liferay-portal-tomcat/4.4.1/car failed
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:299)
	at
org.apache.geronimo.deployment.DeploymentConfigurationManager.loadConfiguration(DeploymentConfigurationManager.java:115)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:286)
	at
org.apache.geronimo.deployment.DeploymentConfigurationManager.loadConfiguration(DeploymentConfigurationManager.java:111)
	at
org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:117)
	... 17 more
Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException:
Missing dependency: org.apache.geronimo.configs/j2ee-security//car
	at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:111)
	at
org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:104)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolveParentIds(SimpleConfigurationManager.java:473)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:431)
	at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:296)
	... 21 more



Am I still not "getting it"? or is there something else going on here we
need to focus on?

I am available and at your disposal for whatever need be on this end.


Jim





Shiva Kumar H R wrote:
> 
> Oh! no no, don't use "Plan Creator" for deploying your war. Use normal
> "Deploy New" portlet.
> 
> (You don't even have to edit your WAR and put new "geronimo-web.xml"
> inside
> it. Just specify it as 'Plan' in "Deploy New" portlet and it will override
> the old "geronimo-web.xml" inside your WAR).
> 
> -- 
> Thanks,
> Shiva
> 
> On Fri, Feb 15, 2008 at 4:39 PM, Jim Foster <jf...@tmtsaz.com> wrote:
> 
>>
>>
>>
>> There are two problems, both in Plan Creator feature:
>>
>> ...
>>
>> Due to these bugs/limitations, I am sorry to say that you will again have
>> to
>> create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
>> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
>> from it and attached it in this mail. Please see if it works. (I guess it
>> requires some pre-requisite db-pools to be deployed before the WAR can be
>> deployed). Hope it helps.
>>
>>
>> Hi Shiva,
>>
>> I have some feedback for you.
>>
>> There still seems to be problem. Here is what I did:
>>
>> [1] Uncompressed the liferay-portal-4.4.1.war file.
>>
>> [2] Replaced the existing geronimo-web.xml file with the edited version
>> you
>> supplied.
>>
>> [3] jar'd p the result for a new .war file
>>
>> [4] Repeated process with Plan Creator using that new .war file
>>
>> [5] Result: exactly the same error as in my opening post.
>>
>>
>> Thoughts?
>>
>>
>> Thanks, Shiva.
>>
>> Jim
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15499041.html
>> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15502316.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
Oh! no no, don't use "Plan Creator" for deploying your war. Use normal
"Deploy New" portlet.

(You don't even have to edit your WAR and put new "geronimo-web.xml" inside
it. Just specify it as 'Plan' in "Deploy New" portlet and it will override
the old "geronimo-web.xml" inside your WAR).

-- 
Thanks,
Shiva

On Fri, Feb 15, 2008 at 4:39 PM, Jim Foster <jf...@tmtsaz.com> wrote:

>
>
>
> There are two problems, both in Plan Creator feature:
>
> ...
>
> Due to these bugs/limitations, I am sorry to say that you will again have
> to
> create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
> liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
> from it and attached it in this mail. Please see if it works. (I guess it
> requires some pre-requisite db-pools to be deployed before the WAR can be
> deployed). Hope it helps.
>
>
> Hi Shiva,
>
> I have some feedback for you.
>
> There still seems to be problem. Here is what I did:
>
> [1] Uncompressed the liferay-portal-4.4.1.war file.
>
> [2] Replaced the existing geronimo-web.xml file with the edited version
> you
> supplied.
>
> [3] jar'd p the result for a new .war file
>
> [4] Repeated process with Plan Creator using that new .war file
>
> [5] Result: exactly the same error as in my opening post.
>
>
> Thoughts?
>
>
> Thanks, Shiva.
>
> Jim
>
> --
> View this message in context:
> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15499041.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.


There are two problems, both in Plan Creator feature:

... 

Due to these bugs/limitations, I am sorry to say that you will again have to
create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
from it and attached it in this mail. Please see if it works. (I guess it
requires some pre-requisite db-pools to be deployed before the WAR can be
deployed). Hope it helps.


Hi Shiva,

I have some feedback for you.

There still seems to be problem. Here is what I did:

[1] Uncompressed the liferay-portal-4.4.1.war file.

[2] Replaced the existing geronimo-web.xml file with the edited version you
supplied.

[3] jar'd p the result for a new .war file

[4] Repeated process with Plan Creator using that new .war file

[5] Result: exactly the same error as in my opening post.


Thoughts?


Thanks, Shiva.

Jim

-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15499041.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
There are two problems, both in Plan Creator feature:
1) Error message/Java Exceptions are suppressed by Plan Creator code and not
shown to the user at all :-(

With liferay-portal-4.4.1.war, when I ran Geronimo in debug mode and remote
connected via Eclipse (with a break point put at the beginning of
org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
function inside "plancreator-portlets" module), I found that we are getting
following exception:

org.apache.geronimo.common.DeploymentException: AbstractWebModuleBuilder:
Could not load servlet class: com.liferay.portal.servlet.MainServlet

Instead of showing this error on Console, plan creator is currently
suppressing it in an empty catch() block.
*GERONIMO-3850<https://issues.apache.org/jira/browse/GERONIMO-3850>
*is opened for this.

2) Secondly, I see that the class it is complaining "
com.liferay.portal.servlet.MainServlet" *does* exist, but inside a
compressed jar ("portal-impl.jar") in WEB-INF/lib directory of WAR. Plan
Creator has a current limitation :-( in resolving such classes. *
GERONIMO-3851 <https://issues.apache.org/jira/browse/GERONIMO-3851> *is
opened for this.

Due to these bugs/limitations, I am sorry to say that you will again have to
create geronimo-web.xml by hand. I found one "geronimo-web.xml" inside
liferay-portal-4.4.1.war itself. I have removed non-existing dependencies
from it and attached it in this mail. Please see if it works. (I guess it
requires some pre-requisite db-pools to be deployed before the WAR can be
deployed). Hope it helps.

-- 
Thanks,
Shiva

On Wed, Feb 13, 2008 at 6:17 PM, Shiva Kumar H R <sh...@gmail.com> wrote:

> Hi Jim,
> Looks like there is some problem. I am looking at it.
>
> --
> Thanks,
> Shiva
>
> On Feb 12, 2008 11:12 PM, Jim Foster <jf...@tmtsaz.com> wrote:
>
> >
> > Hello,
> >
> > I am attempting to use the "Plan Creator" feature of 2.1 using
> > liferay-portal-4.4.1.war as the target, but I am receiving a
> > security-related error (full text bottom of this post).
> >
> > Even though I have been using Geronimo for some time, the changes in 2.1
> > (which are all excellent) still leave me unsure of where the problem
> > lies:
> > Geronimo base, the deployment plan, or Liferay's distribution.
> >
> > For the record, I am using the code from svn, Revision 620253.
> >
> > Any advise would be most appreciated.
> >
> > Thank you for your time!
> >
> > Jim
> >
> >
> > From Plan Creator, following clicking on the "Deploy" button on the last
> > wizard screen.
> > =======================================================
> > org.apache.geronimo.common.DeploymentException:
> >
> >  web.xml for web app liferay/liferay-portal-4.4.1/4.4.1/war
> >
> > includes security elements but Geronimo deployment plan is not provided
> > or
> > does not
> > contain <security-realm-name> element necessary to configure security
> > accordingly.
> >
> > at
> >
> > org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext
> > (AbstractWebModuleBuilder.java:349)
> > at
> > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext(
> > TomcatModuleBuilder.java:326)
> > at
> > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext(
> > SwitchingModuleBuilder.java:159)
> > at
> > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(
> > EARConfigBuilder.java:595)
> > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
> > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(
> > ReflectionMethodInvoker.java:34)
> > at
> > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(
> > GBeanOperation.java:124)
> > at
> > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(
> > GBeanInstance.java:867)
> > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java
> > :239)
> > at
> >
> > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy
> > (AbstractDeployCommand.java:116)
> > at
> > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(
> > DistributeCommand.java:61)
> > at java.lang.Thread.run(Thread.java:595)
> > --
> > View this message in context:
> > http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15437773.html
> > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com
> > .
> >
> >
>
>

Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Jim Foster <jf...@tmtsaz.com>.


Hi Jim,
Looks like there is some problem. I am looking at it.

-- 
Thanks,
Shiva


Thank you, Shiva.
-- 
View this message in context: http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15459604.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

Posted by Shiva Kumar H R <sh...@gmail.com>.
Hi Jim,
Looks like there is some problem. I am looking at it.

-- 
Thanks,
Shiva

On Feb 12, 2008 11:12 PM, Jim Foster <jf...@tmtsaz.com> wrote:

>
> Hello,
>
> I am attempting to use the "Plan Creator" feature of 2.1 using
> liferay-portal-4.4.1.war as the target, but I am receiving a
> security-related error (full text bottom of this post).
>
> Even though I have been using Geronimo for some time, the changes in 2.1
> (which are all excellent) still leave me unsure of where the problem lies:
> Geronimo base, the deployment plan, or Liferay's distribution.
>
> For the record, I am using the code from svn, Revision 620253.
>
> Any advise would be most appreciated.
>
> Thank you for your time!
>
> Jim
>
>
> From Plan Creator, following clicking on the "Deploy" button on the last
> wizard screen.
> =======================================================
> org.apache.geronimo.common.DeploymentException:
>
>  web.xml for web app liferay/liferay-portal-4.4.1/4.4.1/war
>
> includes security elements but Geronimo deployment plan is not provided or
> does not
> contain <security-realm-name> element necessary to configure security
> accordingly.
>
> at
>
> org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext
> (AbstractWebModuleBuilder.java:349)
> at
> org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.initContext(
> TomcatModuleBuilder.java:326)
> at
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.initContext(
> SwitchingModuleBuilder.java:159)
> at
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(
> EARConfigBuilder.java:595)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> :39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(
> ReflectionMethodInvoker.java:34)
> at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(
> GBeanOperation.java:124)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java
> :867)
> at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java
> :239)
> at
> org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy
> (AbstractDeployCommand.java:116)
> at
> org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(
> DistributeCommand.java:61)
> at java.lang.Thread.run(Thread.java:595)
> --
> View this message in context:
> http://www.nabble.com/Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.1.1-tp15437773s134p15437773.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>