[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135901#comment-15135901
]
Ralph Goers commented on LOG4J2-548:
------------------------------------
No, Jboss does not use Apache Commons VFS. JBoss has its own custom protocols.
VFS is one VFSZIP is another. There used to be some documentation on it but the
only decent documentation I could quickly find now is
https://github.com/jbossas/jboss-vfs/blob/master/src/main/java/org/jboss/vfs/VFSUtils.java.
You can find lots of people experiencing problems with it as everything
requires custom code to support them.
I added support for VFSZip because I was working with webapps in JBoss at the
time. I've never used EARs so didn't run across this.
> Log4j 2.0 with JBoss EAP 6.2
> -----------------------------
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-rc1, 2.1
> Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler
> Reporter: Shehata
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message:
> "ERROR StatusLogger Could not search jar file
> 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core'
> for classes matching criteria: annotated with @Plugin file not found"
> after debugging the application found that the problem is located in :
> org.apache.logging.log4j.core.config.plugins.ResolverUtil
> method: findInPackage --> line number 247
> the protocol used in the jar is vfs not vfszip
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
