[
https://issues.jboss.org/browse/JBIDE-10473?page=com.atlassian.jira.plugi...
]
Juergen Zimmermann commented on JBIDE-10473:
--------------------------------------------
Yes, Max, it does. However, in the past adding a jar to the default classpath worked out
of the box which is broken for 7.1 (JBIDE-10463).
AS7.1 default classpath entries missing critical jboss ejb jar
--------------------------------------------------------------
Key: JBIDE-10473
URL:
https://issues.jboss.org/browse/JBIDE-10473
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Max Rydahl Andersen
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: JBIDE-10473.patch
The as7.1 runtime type's default list of classpath jars does not include a critical
folder / jar, specifically modules/org/jboss/ejb3/main/*.jar, which includes support for
the @SecurityDomain annotation. Without this, users must fiddle with classpaths and search
for jars manually.
A workaround, as noted in JBIDE-10463, is to add the folder / fileset to the list of
default classpath entries for the runtime type. However, due to that specific bug, a
workspace restart will be required for these changes to take effect.
--
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