[
https://jira.codehaus.org/browse/MEAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306306#comment-306306
]
Sean Gurevich edited comment on MEAR-146 at 8/15/12 1:35 PM:
-------------------------------------------------------------
The jars need to be placed under APP-INF/lib of the EAR for newer versions of
WebLogic to pick up libraries shared between WAR and EJB JAR, within the same
application. The defaultLibBundleDir configuration option in Maven EAR plugin
allows for putting all common libs under this specified directory. It also has
the side effect of adding the library-directory element to the application.xml.
An empty library-directory element would mean an empty defaultLibBundleDir
argument, which would not package the common JARs where they need to be for
WebLogic. Or do you have something else in mind?
An alternative would be to provide an argument that works the same as
"<defaultLibBundleDir>APP-INF/lib</defaultLibBundleDir>", but does not add the
library-directory entry. Or an additional argument to override adding
library-directory to the application.xml when using defaultLibBundleDir. The
WebLogic-specific argument is certainly not the only approach to accomplish
this.
was (Author: seanpublic):
The jars need to be placed under APP-INF/lib of the EAR for newer versions
of WebLogic to pick up libraries shared between WAR and EJB JAR, within the
same application. The defaultLibBundleDir configuration option in Maven EAR
plugin puts all common libs under this specified directory. It also has the
side effect of adding the library-directory element to the application.xml.
An empty library-directory element would mean an empty defaultLibBundleDir
argument, which would not package the common JARs where they need to be for
WebLogic. Or do you have something else in mind?
An alternative would be to provide an argument that works the same as
"<defaultLibBundleDir>APP-INF/lib</defaultLibBundleDir>", but does not add the
library-directory entry. Or an additional argument to override adding
library-directory to the application.xml when using defaultLibBundleDir. The
WebLogic-specific argument is certainly not the only approach to accomplish
this.
> Expose parameter to not write library-directory element in application.xml
> --------------------------------------------------------------------------
>
> Key: MEAR-146
> URL: https://jira.codehaus.org/browse/MEAR-146
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.7
> Environment: Oracle WebLogic
> Reporter: Alex Halovanic
> Priority: Minor
> Fix For: 2.8
>
> Attachments: ear-remove-librarydirectory-IT.patch,
> ear-remove-librarydirectory-IT.patch, ear-remove-librarydirectory.patch,
> ear-remove-librarydirectory.patch
>
>
> The current handling of defaultLibBundleDir leads to some issues on Oracle
> Weblogic 10+. The Ear plugin currently sets library-directory to the value
> of defaultLibBundleDir in the application.xml for EARs v5+. Some of Oracle's
> classloading features break (specifically "Generic File Loading") when this
> element is set. defaultLibBundleDir has to be set to APP-INF/lib since this
> is the magic library folder for WebLogic.
> The patch adds a parameter to prevent setting library-directory for cases
> like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
