Community
Participate
Working Groups
At least in the specific case of JBoss, having a Runtime that is completely seperate from the Server is problematic. JBoss has different configurations which may or may not include any number of services. Some of these services implement J2EE APIs, etc, and we use them to fill classpath containers. For instance, for javax.servlet APIs , you find the JAR here: $JBOSS_HOME/server/$JBOSS_CONFIGURATION_NAME/lib/javax.servlet.jar The JBoss configuration name is stored as part of the IServer's configuration, and is needed when computing the classpath container for the runtime of that Server. Currently, I have worked around this by associating a Server with a Runtime through the JBoss server's getAdapter method, but the problem comes when we try to associate a JBoss runtime with a Web/J2EE project. To render a Web/J2EE project's classpath containers from a runtime, the server adapter is required to implement RuntimeTargetHandlerDelegate, yet there is absolutely no Server contextual information (nor is it ever prompted for by the user). I'd like to be able to specify that my runtime is tied to a specific server instance, and thus retrieve that server instance from within my runtime if needed (via an adapter would be fine). In the meantime, does anyone have suggestions for a workaround? Half of the J2EE APIs are unavailable to my runtime unless I can tie the server instance back to it.. is there a wizard page i can insert into the Web/EJB project wizards to specify "which" server ?
My initial description was a little confusing, maybe I can make it a little more generic and a little less wordy. Basically, I want to be able to tie certain contextual information to my runtime that will be different from server to server. Right now, a single Runtime is associated with all servers of a certain type, and this is disallowing me from providing a dynamic runtime based on the Server's configuration. I'd like to be able to create a new runtime for *every* server instance (maybe as an optional flag in the plugin.xml), and when this option is enabled, be able to retrieve the Runtime/Server bi-directionally i.e. Server.getAdapter(IRuntime.class), Runtime.getAdapter(IServer.class)..
Added to Hot List at the request of Max Rydahl Andersen and set priority to P2. Tim, pls target for 1.0.1 or 1.5. Thx.
Moving to 1.5 as per WTP build call.
changing target from 1.5 M2 to 1.5 M6 to reflect new numbering scheme as we join Collisto train.
Any headway/info on this bug? It seems to be scheduled for WTP 1.5M6 but there hasn't been any feedback on the validity of such a feature.
03/10: Ted to setup the meeting to discuss this item.
Per the discussion around server architecture, this is not an doable item for 1.5. Therefore, I'm removing this from the hot list. If anyone disagrees with this, please explain why this is still a hot issue for 1.5. Thanks.
This bug is 1.5 years old and I believe should be removed. I believe Marshall will agree.
repealing request as it's old.
Closing old bugs.
