[
https://issues.jboss.org/browse/AS7-6697?page=com.atlassian.jira.plugin.s...
]
Ales Justin commented on AS7-6697:
----------------------------------
> For this type of resource loader, it is better just to add the
JAR using JarFileResourceLoader, which does not require permissions at load time and is
much faster anyway.
I had this initially - see git history #2 vs #3 commit on this Seam2Processor class, but I
had to change it to VFS.
The problem is I don't remember atm why. :-)
My vague memory thinks it has to do with Seam scanner expecting VFS kind of url.
Let me then try with ResourceRoot(s).
Seam2Processor will not have permissions to its added resource
loader
---------------------------------------------------------------------
Key: AS7-6697
URL:
https://issues.jboss.org/browse/AS7-6697
Project: Application Server 7
Issue Type: Bug
Components: Server
Reporter: David Lloyd
Assignee: Ales Justin
Labels: security
Fix For: 8.0.0.Alpha1
The {{Seam2Processor}} class adds a {{VFSResourceLoader}} to the deployment in order to
copy certain Seam classes into it. The problem is that the {{VFSResourceLoader}} will
fail at runtime with a permission exception because there is no corresponding
{{VirtualFilePermission}}.
For this type of resource loader, it is better just to add the JAR using
{{JarFileResourceLoader}}, which does not require permissions at load time and is much
faster anyway.
If you must use {{VFSResourceLoader}}, then instead of creating and adding the resource
loader yourself, add a {{ResourceRoot}} to the deployment context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira