Re: Trouble Starting OpenXAVA 5.8.1 Portlet on JetSpeed 2.3.1

Thank You very much for your reply David.  I got the portlet to deploy
and start now.  The look and feel of the portlet appears to be
distorted, but at least this is a start.

However, I'm a bit surprised that there is very little recent activity
on JetSpeed 2 Project.  It seems like a fantastic product, and I'm
curious why there aren't more people using it.

What do you see as the future of JetSpeed 2?  Are you planning to
Integrate Pluto 3 into it?  Also, are there many people using it in
production today?

On 1/16/18, DavidSeanTaylor <[email protected]> wrote:
> Portlet apps packaged in war files can be directly deployed to Tomcat by
> copying the war file into the $TOMCAT/webapps/jetspeed/WEB-INF/deploy/
> directory. A  directory watcher that will automatically register and depl=
oy
> the app, see more info here:
>
> https://portals.apache.org/jetspeed-2/deployguide/guide-tomcat.html
> <https://portals.apache.org/jetspeed-2/deployguide/guide-tomcat.html>
>
> If you want to remotely control Tomcat via Jetspeed=E2=80=99s Portlet App=
lication
> Manager, you=E2=80=99ll need to set up a few properties in your override.=
properties
> (jetspeed.properties),
>
> #------------------------------------------------------------------------=
-------------------------------------
> # A P P L I C A T I O N S E R V E R M A N A G E R  (TOMCAT ONLY, INVOKED
> THROUGH J2-ADMIN PALM PORTLET)
> #----'-------------------------------------------------------------------=
-------------------------------------
> application.server.host=3Dlocalhost
> application.server.port=3D8080
> # Path to access the Tomcat manager, see:
> http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html
> # Note: For default Tomcat 6- this should be adjusted to: /manager
> application.server.manager.script.path=3D/manager/text
> # Tomcat user name/password having role "manager-script" for access to th=
e
> Tomcat Manager
> # By default these are undefined (disabled Tomcat Manager access)
> application.server.manager.name=3D
> application.server.manager.password=3D
>  the name and password must match Tomcat=E2=80=99s conf/tomcat-users.xml:
>
> <tomcat-users>
>   <role rolename=3D"manager-script"/>
>     <user username=3D"j2deployer" password=3D"xxxxx" roles=3D"manager-scr=
ipt"/>
> </tomcat-users>
>
>
>
>> On Jan 15, 2018, at 4:39 AM, Amarish Khopkar <[email protected]>
>> wrote:
>>
>> Hello,
>>
>> I am considering using JetSpeed 2 as the Integration Platform and
>> OpenXAVA
>> for constructing the portlets in an application that I am going to write=
.
>>
>> I have downloaded the latest version of JetSpeed 2 (2.3.1) and the lates=
t
>> version of Open XAVA (5.3.1).
>>
>> I was able to successfully deploy the 'MySchool' Module that comes with
>> OpenXAVA as a portlet on JetSpeed 2 without any errors on the console.
>>
>> However, when I click on the 'Start' link for this Portlet in the
>> Registry
>> Applications List in the Admin Section, it gives me the following error
>> and the portlet does not start.
>>
>> Failed to start application : /MySchool ,
>> message: The App Server does not seem to be configured for remote
>> application lifecycle management
>>
>> Again, there is no Stack Trace or Error Log in the JetSpeed Console.
>>
>> I searched online for this particular error but wasn't really able to
>> find
>> anything relevant.
>>
>> Can someone please point me in the right direction to fix this issue?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>