> OK ... got it!
>
> In order to change the default context in Jetspeed2 ... I still had to
take
> all the steps I outlined in my previous email (see below), but I had to
> perform them immediately after running Maven's "quickStart" task.
> Apparently, J2 does some type of initialization that "hard-codes" the
> context into the database ...

Indeed J2 does this! I had the problem that my own, Struts-based portlet
simply did not show any contents when I deployed it the first time. (I only
could see the Portlet title and the maximize/minimize etc. icons). The
JPetstore portlet (Struts-based, too), however showed content and I could
not see any differences between both of them, until ...

I looked at the database! J2 stores a lot of portlet and other information
here, so initialization, once done for a Portlet is only done in a "reduced"
manner on each following startup. That at least is my impression so far. It
helps, to run the Maven "quickStart" task, which - besides other tasks -
clears the database and refills the initial values. You may as well extract
the appropriate SQL scripts for your database and run them manually.


> in a place/manner I haven't yet identified for the
> portlets.  This happens the very first time you start-up J2.  So, the
moral
> of the story ... make your context change before you start J2 for the very
> first time ... or else, you're up the proverbial creek! ;-)

Apparently my own Portlet was not made up correctly in the first place, when
J2 registered it in the database and after correcting the mistakes it wasn't
re-initialized correctly, 'cause J2 finds some information in the database
and "skips initial deployment" (-> this you see in the "Logs").

Cleaning and reinitializing the database could solve you're webapp context
problem, too. Though it is a rather bad solution. Maybe one can find the
tables and fields that need to be cleared, to make J2 startup the next time
from scratch.

Sven.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to