[ http://issues.apache.org/jira/browse/JS2-477?page=all ]
Ate Douma closed JS2-477:
-------------------------
Resolution: Won't Fix
First of all, I really can't see this as a problem with priority "Blocker"!
Secondly, I can't reproduce it :)
Now, maybe some fixed something since 2.0-FINAL (I've tested with 2.1-dev
trunk)
but anyways, its hardly possible to reproduce a problem without (much) more
input, stacktraces, logfiles etc.
Please understand that a portal is a complex application which needs to be
given some time to startup.
This will *never* be a problem in production, only for developers too eager to
start hitting the browser ;-)
Furthermore, the portal can't *wait* for each and every possible portlet
application to have started before it accepts requests.
It simply can't, because it doesn't know which portlet applications are
supposed to start, and even if it did, should the whole
portal have to wait if *one* portlet application is missing or fails to start?
I don't think so.
I honestly would prefer user to discuss these problems on the mailing lists
first instead of "dumping" them in JIRA...
> PortletRegistry Error
> ---------------------
>
> Key: JS2-477
> URL: http://issues.apache.org/jira/browse/JS2-477
> Project: Jetspeed 2
> Type: Bug
> Components: Portlet Registry
> Versions: 2.0-FINAL
> Environment: W2K, VM 5.0, Tomcat 5.5.12, MySQL 4.1
> Reporter: Michael Gustav Simon
> Priority: Blocker
>
> If I deploy jetspeed with j2:quickStart and the first requst is before
> registering all portlets,
> the following PortletException will be thrown "Failed to find the Portlet
> Registry on portlet initialization".
> After restart the servletcontainer the portal will work without any problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
