[ http://issues.apache.org/jira/browse/BEEHIVE-264?page=history ]
Rich Feit updated BEEHIVE-264:
------------------------------
Assign To: Daryl Olander (was: Rich Feit)
Looks good to me -- I have one question before closing this issue. You're
using Class.forName(), but isn't it the case that these classes might be user
classes? If so, I think we should use the thread context classloader, which
should fall back to whatever classloader NetUI is in, but which will also
include user classes even if NetUI is in a shared classloader.
> need to add the JSP tag prefix handler infrastructure to the netui-config file
> ------------------------------------------------------------------------------
>
> Key: BEEHIVE-264
> URL: http://issues.apache.org/jira/browse/BEEHIVE-264
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Eddie O'Neil
> Assignee: Daryl Olander
> Fix For: V1
>
> NetUI uses a set of prefixes which are written onto the "name" attribute of
> HTML tags. These prefixes correspond to tag handlers which can operate on
> request parameters when a form POSTs. The handlers are currently statically
> wired up, but they need to be explicitly configured in the netui-config.xml
> file.
> In a clustered environment when a node fails, the next node needs to have the
> prefix handlers pre-configured without having to run static blocks in the JSP
> tags. This requires initializing them from the XML file.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
