[
https://issues.jboss.org/browse/JBIDE-9893?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9893:
------------------------------------
The following are artifact adapters handling ear projects:
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.066 Loaded
moduleArtifactAdapter: org.eclipse.jst.j2ee.server.ear1
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.066 Loaded
moduleArtifactAdapter: org.eclipse.jst.j2ee.server.ear2
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.066 Loaded
moduleArtifactAdapter: org.eclipse.jst.j2ee.server.ear3
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.067 Loaded
moduleArtifactAdapter: org.eclipse.jst.jee.server.ear1
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.067 Loaded
moduleArtifactAdapter: org.eclipse.jst.jee.server.ear2
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.067 Loaded
moduleArtifactAdapter: org.eclipse.jst.jee.server.ear3
org.eclipse.wst.server.core /extension_point 19/10/11 14:37.27.067 Loaded
moduleArtifactAdapter: org.eclipse.jst.jee.server.ear4
They use two classes with different entry methods based on the selection. The two classes
are:
org.eclipse.jst.j2ee.internal.deployables.EnterpriseDeployableArtifactAdapterFactory
org.eclipse.jst.jee.ui.internal.deployables.EnterpriseDeployableArtifactAdapterFactory
These two classes are almost identical clones of each other. The different entry points
all lead to the following method:
protected static IModuleArtifact createModuleObject(IModule module) {
if (module != null) {
return new NullModuleArtifact(module);
}
return null;
}// createDeployableObject
As you can see... ear projects have always returned either null, or a NullModuleArtifact.
Regardless of whether the project exists or not, EAR projects have never ever had any
legitimate 'run as -> run on server' action associated with it.
To contrast, the classes associated with web resources are very vibrant and have lots of
code in it with many different possible artifact returns. WebDeployableArtifactUtil shows
it can return WebResource, EJBBean, and NullModuleArtifact, depending on the selection.
I maintain my position that runnign an ear on the server has never ever had any specific
action associated with it and this is neither a bug nor a regression.
Browser is not opened for EAR projects
--------------------------------------
Key: JBIDE-9893
URL:
https://issues.jboss.org/browse/JBIDE-9893
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Windows XP, JBDS 5.0.0.M3, Server which comes with IDE, Seam 2.2
booking example EAR (with tutorial)
Reporter: Dmitry Geraskov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta1
1. Create an ear project (i.e. Seam Web Project wizard with Ear or use seam2 ear booking
example)
2. Right click on created project -> Run as->Run on Server
Nothing in logs or ui.
War's works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira