Dynamic Discovery on WebSphere 4.0.7

Question

Hi all,
I wrote my pluggable navigation and I modified the LoginHTML, LoginModel and LoginControl. Then I put the navigation and the modified login code in one .jar file and I added it in the CustomActivitySpace.xml.
On a machine running Tomcat all is discovered well. On another machine running WebSphere 4.0.7 only the pluggable navigation is discovered well. I mean that I can choose it from the subportal manager and it works. On the contrary the login code modifications aren't discovered well.
I'm using Plumtree 5.0.2 (Java version).
Do you have suggestions?
Thank you,
Alberto

Answer 1

It sounds to me like you are using HotSwap debugging on Tomcat, which doesn't require dynamic discovery. This is not in any way supported by our product. Tomcat allows you to replace any Java code with new code, without re-compiling. This is not what Dynamic Discovery is. This will not work on any application server other than Tomcat, including .NET, Websphere, and Weblogic. Dynamic Discovery only allows you to replace certain components in the portal, such as Models, Views, Controls, Activity Spaces, and PEIs, among others. LoginHTML is just a helper class used by the LoginSpace and LoginPortlet LoginViews. In order to properly dynamically discover this customization so that it will work on other platforms, a custom LoginView must be created that uses your new LoginHTML class.
-- Don