[
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek closed DELTASPIKE-856.
---------------------------------------
> Eclipse deployment to container add remove view shows
> deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic
> we get a double jar file
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-856
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.2.1
> Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id:
> I20140606-1215, WTP plugin Version:
> 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
> Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build
> id: 20131017041352
> Reporter: Nuno G. de M
> Assignee: Rafael Benevides
> Attachments: Screenshot 2015-03-13 18.05.21.png, Screenshot
> 2015-03-16 12.42.13.png
>
>
> There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar
> .
> This project dependency alone, unlike every other project dependency, it is
> displayed itself by eclipse Add & Remove view to an application server as if
> it were a module itself of the war application to be deployed.
> When a user, for example, configures weblogic 12.1.2 server to take in
> deployments as exploded war files, what ends up happening after the
> deployment goes through is that we see within
> Weblogic Domain > AdminServer > temp > mydeployment > war> Web-inf/lib
> we see the jar dependency twice.
> First we see the correct and expected dependency:
> deltaspike-jsf-module-impl-ee6-1.2.1.jar
> But then we have a second file in the lib folder called:
> deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
> This appears to be releated to the Add & Remove view of eclipse, since
> normally under the project war file itself we only see other open project
> modules.
> I am pasting in this post an url to a google driver sample application that
> you can use to simulate the scenario.
> The zip file will contain both a sample application that I have once before
> submitted to you already (regarding the view access scoped beans) and
> document file illustrating the issue in my IDE.
> To simulate the issue simply:
> (a) create a domain
> (b) do mvn eclipse:eclipse and import the project
> (c) Configure your weblogic domain to accept exploded war deployment
> (d) click on add and remove on the domain you want to deploy to and see that
> the JEE6 impl appears as a module.
> (e) deploy, and look at what happens within the weblogic deployment folder
> URL:
> https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
> It is not yet clear if this phenomena may be creating problems for us when we
> use eclipse to run the deployment.
> In the sample application we have no issues.
> Thank you for your support,
> My kindest regards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
