Vladimir Figurov wrote:
Hello!
I try use jetspeed2. I - beginner in jetspeed2
I have a next little questions:
Ferst question:
-How make UNdeploy the old or error portlet, without running maven
quickStart allways??:
I read in
http://wiki.apache.org/portals/Jetspeed2/DeployingCustomPortlets,
chapter Undeployment what need simple DELETE .war from
WEB-INF/deploy. But, I looking what after I placed a war in this
catalog, J2 deleting himself this war, modify his and placed
MyApp-modify.war in /webapps. Thus, I have already nothing to
delete in the catalogue "deploy"
The Wiki information is outdated with the new M2 release. Undeployment
now can (and for the moment: must) be performed directly from the portal
using the new Portlet Application Lifecycle Manager (PALM) which you can
access if you login as admin. You can also stop/start portlet applications
from there which is handy if you need to restart after a manual change to
a configuration file or class files for example.
If I shall remove in manual /webapps/MyApp-modify.war and
/webapps/MyApp, and then I shall put new WAR - J2 whence pulls
out old.
And next question:
-after change [EMAIL PROTECTED] in jetspeed/WEB-INF/pages/default-page.psml
and stay old [EMAIL PROTECTED] - J2 was run the old MyApp with [EMAIL PROTECTED] #
newName ?!!
This is a know issue (we're going to work on that soon).
The mapping of a fragment id with a pa::portlet definition is stored in the
database
(table PORTLET_ENTITY).
You can remove the entry from the database but then you'll have to restart
Jetspeed.
The easiest solution right now is also using a unique new fragment id when you
change
the configuration.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
