[
https://issues.jboss.org/browse/JBIDE-10618?page=com.atlassian.jira.plugi...
]
Jonathan Fuerth commented on JBIDE-10618:
-----------------------------------------
I wouldn't say the creation of a dynamically configured deployment descriptor for AS7
is a zero-change proposition. Plus, it's likely going to require a patch to AS7 to
expose WEB-INF/classes as a configurable resource-root.
Remember, the only reason we have to hide these classes from the webapp classloader is
because we are working around a deficiency in Eclipse JDT/WTP. Users don't have to
know how to run their app server to run with this agent, because the client classes the
agent would be trying to hide are not in the .war they are deploying. The agent is only
required as a workaround when launching from WTP, and this is something JBT can take care
of when it launches the server.
The big advantage of the agent approach is that it will work with any app server. All you
have to do is activate the agent in the VM.
GWT's client classes deployed to App Server
-------------------------------------------
Key: JBIDE-10618
URL:
https://issues.jboss.org/browse/JBIDE-10618
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: GWT, JBossAS/Servers, maven
Reporter: Burr Sutter
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: Screen Shot 2012-01-11 at 9.27.48 PM.png
When using Run-As, Add-Remove or other WTP-based deployment mechanisms on a GWT app - the
client Java classes are deployed to the server (under WEB-INF) - these .java files are
supposed to be converted to .js files and not deployed.
--
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