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

[Jim Foster]

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:
> 
>  
>  
>  
> 
> which makes that module try to load stuff (such as activemq) from the  
> module before trying parent classloaders such as activemq-broker
> 
> and
> 
> 
>  
>  org.apache.activemq
>  activemq-core
>  jar
>  4.1.1
>  
> 
> 
> in liferay-jetty/pom.xml
> 
> and
> 
>  
>  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:


...

com.liferay
portal-kernel
${liferayVersion}


com.liferay
portal-service
${liferayVersion}

...

==
[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 apach

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

[Jim Foster]

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.
>>> 
>>>
>>>
>>>> [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:
>>
>> 
>> org.apache.geronimo.genesis.config
>> project-config
>> 1.3
>> 
>>
>>
>> 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.

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

[Jim Foster]

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.
> 
> 
> 
>> [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:


org.apache.geronimo.genesis.config
project-config
1.3



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.

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

[Jim Foster]

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

[Jim Foster]

djencks wrote:
> 
> 
> On Mar 4, 2008, at 9:48 AM, Jim Foster wrote:
> 
> 
> 
>> [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/)

 

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

[Jim Foster]

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

[Jim Foster]

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
>>>>>
>>>>>  
>>>>>
>>>>>
>>>>
>>>> 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

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

[Jim Foster]

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
>>>
>>>  
>>>
>>>
>>
>> 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

[Jim Foster]

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
> 
>  
> 
> 

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

[Jim Foster]

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:
--


http://geronimo.apache.org/xml/ns/j2ee/connector-1.2";>



   
javax.sql.DataSource

jdbc/LiferayPool
liferay
liferay
liferay



10
0











--

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
>>>
>>>  
>>>
>>>  
>>>  apache-snapshots
>>>  Apache Snapshots Repository
>>>  http://people.apache.org/repo/m2-snapshot-
>>> repository
>>>  default
>>>  
>>>  true
>>>  daily
>>>  ignore
>>>  
>>>  
>>>  false
>>>  
>>>  
>>>
>>>  
>>>
>>>
>>> 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:
>>
>>   ...
>>   
>> profile-1
>>   
>>   
>> 
>>   profile-1
>>   
>> 
>>   apache-snapshots
>>   Apache Snapshots Repository
>>
>> http://people.apache.org/repo/m2-snapshot-repository
>>   default
>>   
>> true
>> daily
>> ignore
>>   
>>   
>> false
>>   
>> 
>>   
>> 
>>   
>>   ...
>>
>> 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
>>
>>

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

[Jim Foster]

djencks wrote:
> 
> 
> So I found the schema and I think you need
> 
>  
> 
>  
>  apache-snapshots
>  Apache Snapshots Repository
>  http://people.apache.org/repo/m2-snapshot- 
> repository
>  default
>  
>  true
>  daily
>  ignore
>  
>  
>  false
>  
>  
> 
>  
> 
> 
> 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:
  
  ...
  
profile-1
  
  

  profile-1
  

  apache-snapshots
  Apache Snapshots Repository
 
http://people.apache.org/repo/m2-snapshot-repository
  default
  
true
daily
ignore
  
  
false
  

  

  
  ...

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

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

[Jim Foster]

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 \

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

[Jim Foster]

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] Velocima

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

[Jim Foster]

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:

  
liferay
liferay-portal-tomcat
4.4.1
car
  

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
   
-

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

[Jim Foster]

Shiva Kumar H R wrote:
> 
> On Fri, Feb 22, 2008 at 3:46 PM, Peter Petersson <[EMAIL PROTECTED]>
> 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

[Jim Foster]

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.4.1

[Jim Foster]

Hi David,

Responses below, inline.



djencks wrote:
> 
> Hi Jim,
> 
> I think how to fix the deployment problems might be described in one of
> the two features I actually documented.
> 
> http://cwiki.apache.org/GMOxDOC21/configuring-run-as-and-default-subjects-and-principal-role-mapping.html
> 


  And here I thought I had read every single page of GMOxDOC21...
  
  This is an excellent read, though some of it goes "swoosh" over my head.
  It will take another read or two in order for me to digest it all.



djencks wrote:
> 
> I'm attaching an updated plan with what look like plausible changes.
> 

  Looks good.

  In your edition of the deployment plan vis-a-vis the one currently in the
Liferay distro, 
  I note that your modifications may be summarized as

[1] namespace modified from "web-1.1" to "web-2.0.1"

[2] dependencies:
j2ee-security
j2ee-server
javamail
rmi-naming   <= removed
sharedlib
geronimo-mail
liferay-pool

[3] security tag modified
  
[4] gbean name="CredentialStore" is new
  
  
  Did I miss anything?
  
  I also note that the namespace specified for the CredentialStore does not
seem to exist,
  meaning http://geronimo.apache.org/xml/ns/credentialstore-1.0.
  
  

djencks wrote:
> 
> I haven't been able to figure out what you are trying to deploy with this
> plan from the 4.4.1 downloads, so I'll wait for more input from you.
> 

  If you visited the bundled packages page of Liferay referenced above, then
you see that they are trying to be all things to all people, meaning
supporting just about every platform/configuration possible.
  
  A noble, if not ambitous effort.
  
  However, this means that the good folks at Liferay are busy with other
things other than staying current with the rapid development of Geronimo.
  
  For example, their current disto bundle for Geronimo is stuck at v1.1, and
I don't anticipate that changing anytime soon.
  
  That being the case, I wish to assume responsibility myself for syncing
deployment of the Liferay portal onto the Geronimo application server.
  
  This means determining what is needed to bring the original
Liferay-created deployment plans up to speed with current Geronimo
requirements.
  
  From what I can determine so far (and please correct me if I am wrong),
that means modifications to:
  
- The geronimo deployment plan (in liferay-portal-4.4.1.war)
- The JDBC connection pool (in
liferay-portal-geronimo-derby-pool-4.4.1.car)




djencks wrote:
> 
> I think the Roller plugin provides a good model for what you might end up
> with in terms of a reproducible plugin/server build environment.
> 
> svn co https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk
> 
> This shows how to construct switchable database plugins (derby and mysql)
> and constructs roller plugins for jetty and tomcat, and shows how to
> assemble servers around these plugins.
> 
> The archetypes I've started should help a lot with setting up projects
> like this.
> 
> thanks
> david jencks
> 


  This is perfect!
  
  I will endeavor to study your Roller plugin model today.
  
  ...and don't worry, I'm not shy when it comes to questions.
  
  From what I have read from you so far, I have the impression that your are
eager for informed feedback.
  


Jim


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

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

[Jim Foster]

Hi David,

Responses below, inline.


djencks wrote:
> 
> Jim,
> 
> Is liferay 4.4.1 available on a maven repo?
> 

  Unfortunately, no.



djencks wrote:
> 
> If not where can I find it?
> 

  Liferay has several sources:

  [1] Bundled distributions are at
  http://www.liferay.com/web/guest/downloads/portal
  
  [2] The Additional Files page at
http://www.liferay.com/web/guest/downloads/additional has links for:
  
  - a war distribution of the portal itself
  
  - a dependencies collection of jars: portal-kernel, portal-service,
portlet 
(which I don't think are needed for Geronimo)

  - liferay-portal-geronimo-derby-pool-4.4.1.car
(which must be deployed first, according to the site, and contains
the ra.xml file which we would need to update for v2.1)

  - manual database population scripts
  
  [3] Individual liferay components are also listed on sourceforge at
  http://sourceforge.net/project/showfiles.php?group_id=49260




djencks wrote:
> 
> Is liferay normally built with maven?  I snagged the plan off an earlier
> mail...
> 

  No.
  
  If you browse the SVN repository at 
  
https://lportal.svn.sourceforge.net/svnroot/lportal/

  you will see build.xml files in the directories, so the answer seems
apparent that they are sticking with ant.




djencks wrote:
> 
> By far the easiest way to create a g 2.1 plugin is with maven.
> 

  I hear that. Maven is the only way...period. Whatever I can do to assist
this effort, please do not hesitate to ask. 
  
  I am by no means a maven guru, but I can certainly hold my own, and I am
willing to do any grunt work by way of testing, or anything else that you
deem appropriate. 
  
 


djencks wrote:
> 
> I'm starting a maven archetype to make it easy to set up a maven project
> to generate a plugin.  This seems like a good test case.
> 
> thanks
> david jencks
> 

  This is good to hear.
  
  With Geronimo v2.1 being made up almost entirely of plugins now, combined
with the momentum behind OSGi-ifying Geronimo, a solid plugin procedure
needs to be established. 
  

Jim


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

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

[Jim Foster]

djencks wrote:
> 
> Jim,
> 
> Is liferay 4.4.1 available on a maven repo?  If not where can I find it? 
> Is liferay normally built with maven?  I snagged the plan off an earlier
> mail...
> 
> By far the easiest way to create a g 2.1 plugin is with maven.  I'm
> starting a maven archetype to make it easy to set up a maven project to
> generate a plugin.  This seems like a good test case.
> 
> thanks
> david jencks
> 
> 


Hi David,

I think this is an excellent suggestion!

When one thinks of application server usage, a Portal environment is usually
hovering near the top of use-case scenarios, followed closely by CMS, so if
we were to take Liferay as a first use-case and make it a model, we would be
solving many problems at once: your archetype development, a use-case model
suitable for public consumption, and solving my particular development
situation.

I need to step away right now, but I will follow-up again to this thread and
provide you with all the information you require so that we can work
together on getting this accomplished.


Thanks!

Jim


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

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

[Jim Foster]

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
> *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  *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

[Jim Foster]

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.(DeploymentContext.java:100)
at
org.apache.geronimo.deployment.DeploymentContext.(DeploymentContext.java:80)
at
org.apache.geronimo.j2ee.deployment.EARContext.(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 <[EMAIL PROTECTED]> 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
>

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

[Jim Foster]

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

[Jim Foster]

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.

Geronimo v2.1 Plan Creator => Deploy Liferay 4.1.1

[Jim Foster]

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  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: OpenLaszlo as a Geronimo plugin

[Jim Foster]

Hi Jay,

I am so glad you decided to share your experience on this issue as you are
right on the money.

Once I downloaded and deployed 4.1, it worked as expected.

As to what changed, hard to say as there is nothing at all in the
release-notes or README of the download.

Again, thanks for sharing!


Jim




Jay D. McHugh-2 wrote:
> 
> Hey Jim,
> 
> I tried deploying the 4.0.9 version and got similar issues.
> 
> But, I got the nightly 4.1 build and deployed that.
> 
> It does initially bring up the 'quick links' page.  But if you click on 
> the flash link in:
> 'If this is the first time you've run OpenLaszlo or you are looking for 
> an introduction, please try Laszlo Explorer (Flash) (DHTML).'
> 
> Then it brings up the Laszlo Explorer correctly.
> 
> I don't know what they changed - but the nightly works where the 
> 'release' doesn't.
> 
> Hope that helps,
> 
> 
> Jay
> 
> 
> Jim Foster wrote:
>> Hi Viet,
>> 
>> I tried both avenues that you suggested.
>> 
>> [1] Console Navigation > Deploy New
>> 
>> [2] Command line of
>> geronimo-tomcat6-jee5-2.0.2\bin>java -jar ./deployer.jar -u system -p
>> manager deploy [path to openlaszlo-4.0.9.war]
>> 
>> 
>> In both cases, the .war seemed to deploy just fine, but both cases yield
>> the
>> following in the navigator frame of laszlo-explorer:
>> 
>> Error: explore-nav.lzx:5:28: datatype library
>> "http://www.w3.org/2001/XMLSchema-datatypes"; not recognized
>> 
>> 
>> Still seems to me something with the schema.
>> 
>> For what it's worth, I deployed the same openlaszlo-4.0.9.war file to a
>> baseline installation of Tomcat 5.5.25, and it worked just fine.
>> 
>> Thoughts?
>> 
>> 
>> Jim
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/OpenLaszlo-as-a-Geronimo-plugin-tp15187608s134p15231931.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: OpenLaszlo as a Geronimo plugin

[Jim Foster]

Hi Viet,

I tried both avenues that you suggested.

[1] Console Navigation > Deploy New

[2] Command line of
geronimo-tomcat6-jee5-2.0.2\bin>java -jar ./deployer.jar -u system -p
manager deploy [path to openlaszlo-4.0.9.war]


In both cases, the .war seemed to deploy just fine, but both cases yield the
following in the navigator frame of laszlo-explorer:

Error: explore-nav.lzx:5:28: datatype library
"http://www.w3.org/2001/XMLSchema-datatypes"; not recognized


Still seems to me something with the schema.

For what it's worth, I deployed the same openlaszlo-4.0.9.war file to a
baseline installation of Tomcat 5.5.25, and it worked just fine.

Thoughts?


Jim
-- 
View this message in context: 
http://www.nabble.com/OpenLaszlo-as-a-Geronimo-plugin-tp15187608s134p15211830.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: OpenLaszlo as a Geronimo plugin

[Jim Foster]

Hi Viet,

Thanks for your reply.

I downloaded the Dev Kit .war file from http://www.openlaszlo.org/download
and put it in the Geronimo deploy folder, but it does not seem to deploy,
correctly.

For your info, what I saw on startup is included at the bottom of this post
as "Geronimo startup console".

There does not seem to be anything wrong on startup, but I see two things
wrong in the Server Console straight out of the gate:

[1] Going to Console Navigation > Web App WARs and selecting the link for
/openlaszlo-4.0.9 shows a screen void of the usual OpenLaszlo
navigator...just an HTML version of "OpenLaszlo Quick Index".

[2] Selecting the calendar component on that "OpenLaszlo Quick Index" screen
yields an error stating the following:

  calendar.lzx:5:28: datatype library
"http://www.w3.org/2001/XMLSchema-datatypes"; not recognized


Any ideas as to what I am doing wrong? or is there indeed an impedance
mismatch in the XML schema?

Also, congrats on becoming a new committer on the Geronimo project!

Again, your advise is much appreciated!

Jim



Geronimo startup console

Booting Geronimo Kernel (in Java 1.5.0_14)...
Module  1/38 org.apache.geronimo.configs/rmi-naming/2.0.2/car  
started in   .938s
Module  2/38 org.apache.geronimo.configs/j2ee-server/2.0.2/car 
started in   .313s
Module  3/38 org.apache.geronimo.configs/transaction/2.0.2/car 
started in  1.532s
Module  4/38 org.apache.geronimo.configs/j2ee-security/2.0.2/car   
started in   .000s
Module  5/38 org.apache.geronimo.configs/axis/2.0.2/car
started in   .563s
Module  6/38 org.apache.geronimo.configs/axis2/2.0.2/car   
started in  9.500s
Module  7/38 org.apache.geronimo.configs/openejb/2.0.2/car 
started in   .000s
Module  8/38 org.apache.geronimo.configs/j2ee-corba-yoko/2.0.2/car 
started in  1.750s
Module  9/38 org.apache.geronimo.configs/system-database/2.0.2/car 
started in   .000s
Module 10/38 org.apache.geronimo.configs/activemq-broker/2.0.2/car 
started in   .000s
Module 11/38 org.apache.geronimo.configs/activemq-ra/2.0.2/car 
started in   .641s
Module 12/38 org.apache.geronimo.configs/jasper/2.0.2/car  
started in   .000s
Module 13/38 org.apache.geronimo.configs/myfaces/2.0.2/car 
started in   .015s
Module 14/38 org.apache.geronimo.configs/tomcat6/2.0.2/car
10:02:35,312 ERROR [[/]] "Restricted listeners property file not found
 started in  2.797s
Module 15/38 org.apache.geronimo.configs/geronimo-gbean-deployer/2.0.2/car 
started in   .484s
Module 16/38 org.apache.geronimo.configs/j2ee-deployer/2.0.2/car   
started in   .562s
Module 17/38 org.apache.geronimo.configs/connector-deployer/2.0.2/car  
started in   .203s
Module 18/38
org.apache.geronimo.configs/persistence-jpa10-deployer/2.0.2/car   started
in   .156s
Module 19/38 org.apache.geronimo.configs/openejb-deployer/2.0.2/car
started in   .203s
Module 20/38 org.apache.geronimo.configs/client-deployer/2.0.2/car 
started in   .172s
Module 21/38 org.apache.geronimo.configs/axis2-deployer/2.0.2/car  
started in   .218s
Module 22/38 org.apache.geronimo.configs/axis-deployer/2.0.2/car   
started in   .812s
Module 23/38 org.apache.geronimo.configs/javamail/2.0.2/car
started in   .078s
Module 24/38 org.apache.geronimo.configs/sharedlib/2.0.2/car   
started in   .016s
Module 25/38 org.apache.geronimo.configs/tomcat6-deployer/2.0.2/car
started in   .406s
Module 26/38 org.apache.geronimo.configs/jasper-deployer/2.0.2/car 
started in   .031s
Module 27/38 org.apache.geronimo.configs/myfaces-deployer/2.0.2/car
started in   .063s
Module 28/38 org.apache.geronimo.configs/welcome-tomcat/2.0.2/car  
started in   .312s
Module 29/38 org.apache.geronimo.configs/dojo-tomcat/2.0.2/car 
started in   .109s
Module 30/38 org.apache.geronimo.configs/webconsole-tomcat/2.0.2/car   
started in  3.156s
Module 31/38 org.apache.geronimo.configs/remote-deploy-tomcat/2.0.2/car
started in   .141s
Module 32/38 org.apache.geronimo.configs/hot-deployer/2.0.2/car
started in   .375s
Module 33/38 org.apache.geronimo.configs/mejb/2.0.2/car
started in   .468s
Module 34/38 org.apache.geronimo.configs/jsr88-rar-configurer/2.0.2/car
started in   .031s
Module 35/38 org.apache.geronimo.configs/ca-helper-tomcat/2.0.2/car
started in   .172s
Module 36/38 sample.applications/HelloWorldApp/2.0/war 
started in   .281s
Module 37/38 org.apache.geronimo.samples/inventory-ear/2.0-SNAPSHOT/ear
started in   .406s
Module 38/38
org.apache.geronimo.configs/jsp-examples-tomcat/2.0.2-SNAPSHO