[jira] [Commented] (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
[ https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372982#comment-14372982 ] Nuno G. de M commented on DELTASPIKE-856: - AHAH, NOW i know why you cannot reproduce the issue!! I just spotted on your print screen a nice little M on top of the project. You have imported as a maven project. I am not allowed to use the Maven Plugin for eclipse. Instead, we are using the eclipse:eclipse plugin to configure the projects as normal regular eclipse projects. Maven is allowed for regular command line build outside of eclipse and in continuous integration (e.g. Jenkins). So now we know why the issue was not reproducible. Many thanks, Nuno. > 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)
[jira] [Commented] (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
[ https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372975#comment-14372975 ] Nuno G. de M commented on DELTASPIKE-856: - Hi There, I've just tested the setup on linux on my personal pc (Untu 14 LTS edition). URL for print screens: https://drive.google.com/file/d/0B_dEiNBGUsxqTm9IU3BjYS1nME0/view?usp=sharing - downloaded eclipse - downloaded sun JDK 7 to install weblogic - downloaded JRE 8 to run OEPE eclipse plugin - installed OEPE Add when I select the application to deploy, It is still expandable on the jee impl module. Another thing is that the OEPE plugin is only able to deploy the application as an exploded WAR. The default mode of deployment (virtual application) does not work. Due to the exception listed bellow. I expect that in this case, the issue is the OEPE plugin itself, since the same application can be deployed in exploded war bz the same plugin. It can also be deployed to weblogic using netbeans deploy plugin, or it can be deployed to glassfish using the eclipse plugin for glassfish. In exploded war the exception is the following. java.lang.IllegalStateException: Could not find beans for Type=class org.apache.deltaspike.core.impl.scope.window.WindowBeanHolder and qualifiers:[] at org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:153) at org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension.initializeDeltaSpikeContexts(DeltaSpikeContextExtension.java:85) at org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension$Proxy$_$$_WeldClientProxy.initializeDeltaSpikeContexts(DeltaSpikeContextExtension$Proxy$_$$_WeldClientProxy.java) Well, in any case, it looks like there is something special in the jar file, most likely some META/INF file, that somehow leads eclipse to see it as special. I've also tried to run the eclipse:eclipse command with an older version of the plugin: mvn org.apache.maven.plugins:maven-eclipse-plugin:2.6:eclipse Did not make any visible difference. Kind regards, Nuno. > 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 creati
[jira] [Created] (DELTASPIKE-862) document JsfMessage
Gerhard Petracek created DELTASPIKE-862: --- Summary: document JsfMessage Key: DELTASPIKE-862 URL: https://issues.apache.org/jira/browse/DELTASPIKE-862 Project: DeltaSpike Issue Type: Task Components: JSF-Module Affects Versions: 1.3.0 Reporter: Gerhard Petracek Assignee: Rafael Benevides Fix For: 1.3.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-861) RequestDispatcher#forward is redirecting instead of frwarding if I add Deltaspike
[
https://issues.apache.org/jira/browse/DELTASPIKE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-861.
-
Resolution: Not a Problem
> RequestDispatcher#forward is redirecting instead of frwarding if I add
> Deltaspike
> -
>
> Key: DELTASPIKE-861
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-861
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.3.1
> Environment: jboss-eap-6
> glassfish-4
>Reporter: FAICAL BOUTAOUNTE
>
> I'm deploying a web application into JBoss EAP6 and Glassfish 4, every thing
> works as expected till the point where I add deltaskpike jars to the projet.
> Once deltaskpike enabled, the following code inside a servlet:
> request.getServletContext().getRequestDispatcher("/faces/page.xhtml").forward(request,
> response);
> will send a redirect response (HTTP: 302) to the browser instead of
> forwarding on the server side. if I remove deltaskpike jars from the
> application the dispatcher forward works as expected.
> Is Deltaspike modifying the default behaviour of RequestDispatcher ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (DELTASPIKE-861) RequestDispatcher#forward is redirecting instead of frwarding if I add Deltaspike
[
https://issues.apache.org/jira/browse/DELTASPIKE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek closed DELTASPIKE-861.
---
> RequestDispatcher#forward is redirecting instead of frwarding if I add
> Deltaspike
> -
>
> Key: DELTASPIKE-861
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-861
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.3.1
> Environment: jboss-eap-6
> glassfish-4
>Reporter: FAICAL BOUTAOUNTE
>
> I'm deploying a web application into JBoss EAP6 and Glassfish 4, every thing
> works as expected till the point where I add deltaskpike jars to the projet.
> Once deltaskpike enabled, the following code inside a servlet:
> request.getServletContext().getRequestDispatcher("/faces/page.xhtml").forward(request,
> response);
> will send a redirect response (HTTP: 302) to the browser instead of
> forwarding on the server side. if I remove deltaskpike jars from the
> application the dispatcher forward works as expected.
> Is Deltaspike modifying the default behaviour of RequestDispatcher ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-861) RequestDispatcher#forward is redirecting instead of frwarding if I add Deltaspike
[
https://issues.apache.org/jira/browse/DELTASPIKE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-861:
Assignee: (was: Christian Kaltepoth)
> RequestDispatcher#forward is redirecting instead of frwarding if I add
> Deltaspike
> -
>
> Key: DELTASPIKE-861
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-861
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.3.1
> Environment: jboss-eap-6
> glassfish-4
>Reporter: FAICAL BOUTAOUNTE
>
> I'm deploying a web application into JBoss EAP6 and Glassfish 4, every thing
> works as expected till the point where I add deltaskpike jars to the projet.
> Once deltaskpike enabled, the following code inside a servlet:
> request.getServletContext().getRequestDispatcher("/faces/page.xhtml").forward(request,
> response);
> will send a redirect response (HTTP: 302) to the browser instead of
> forwarding on the server side. if I remove deltaskpike jars from the
> application the dispatcher forward works as expected.
> Is Deltaspike modifying the default behaviour of RequestDispatcher ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-859) Injection of @Named @MessageBundle works only with @Named injection point
[
https://issues.apache.org/jira/browse/DELTASPIKE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-859:
Fix Version/s: 1.3.1
> Injection of @Named @MessageBundle works only with @Named injection point
> -
>
> Key: DELTASPIKE-859
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-859
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
>Affects Versions: 1.3.0
>Reporter: Tomas Remes
>Assignee: Mark Struberg
> Fix For: 1.3.1
>
>
> If you want to inject e.g following message bundle:
> {code}
> @Named
> @MessageBundle
> public interface AppMessages {
> {code}
> then you would need to specify @Named qualifier on your injection point as
> well. I believe this is not intended behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-859) Injection of @Named @MessageBundle works only with @Named injection point
[
https://issues.apache.org/jira/browse/DELTASPIKE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-859.
-
Resolution: Fixed
> Injection of @Named @MessageBundle works only with @Named injection point
> -
>
> Key: DELTASPIKE-859
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-859
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
>Affects Versions: 1.3.0
>Reporter: Tomas Remes
>Assignee: Mark Struberg
> Fix For: 1.3.1
>
>
> If you want to inject e.g following message bundle:
> {code}
> @Named
> @MessageBundle
> public interface AppMessages {
> {code}
> then you would need to specify @Named qualifier on your injection point as
> well. I believe this is not intended behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-860) documentation says "@LoggedIn User user", but that's impossible
[
https://issues.apache.org/jira/browse/DELTASPIKE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372823#comment-14372823
]
The Alchemist commented on DELTASPIKE-860:
--
@[~rsmeral]: Done. The PR is available at
https://github.com/apache/deltaspike/pull/23.
> documentation says "@LoggedIn User user", but that's impossible
> ---
>
> Key: DELTASPIKE-860
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-860
> Project: DeltaSpike
> Issue Type: Bug
> Components: Documentation
>Reporter: The Alchemist
>Assignee: Rafael Benevides
>Priority: Minor
>
> h3. Documentation Snippet
> http://deltaspike.apache.org/documentation/security.html
> {noformat}
> Create the Authorizer
> @ApplicationScoped
> public class CustomAuthorizer
> {
> @Secures
> @CustomSecurityBinding
> public boolean doSecuredCheck(InvocationContext invocationContext,
> BeanManager manager, @LoggedIn User user) throws Exception
> {
> return user.isLoggedIn(); // perform security check
> }
> }
> {noformat}
> h3. Compilation Error
> {noformat}
> The annotation @LoggedIn is disallowed for this location
> {noformat}
> h3. Explanation?
> I think it's because {{LoggedIn}} is missing a {{@Target}} of {{PARAMETER}}.
> {code:java,title=LoggedIn.java}
> @Retention(value = RetentionPolicy.RUNTIME)
> @Target({ ElementType.TYPE, ElementType.METHOD })
> @Documented
> @SecurityBindingType
> public @interface LoggedIn {
> {code}
> h3. Conclusion
> Not sure if this is supposed to work, given that {{LoggedIn}} is part of
> PicketLink, not DeltaSpike.
> Is there a workaround for this type of situation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-860) documentation says "@LoggedIn User user", but that's impossible
[
https://issues.apache.org/jira/browse/DELTASPIKE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
The Alchemist updated DELTASPIKE-860:
-
Priority: Minor (was: Major)
> documentation says "@LoggedIn User user", but that's impossible
> ---
>
> Key: DELTASPIKE-860
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-860
> Project: DeltaSpike
> Issue Type: Bug
> Components: Documentation
>Reporter: The Alchemist
>Assignee: Rafael Benevides
>Priority: Minor
>
> h3. Documentation Snippet
> http://deltaspike.apache.org/documentation/security.html
> {noformat}
> Create the Authorizer
> @ApplicationScoped
> public class CustomAuthorizer
> {
> @Secures
> @CustomSecurityBinding
> public boolean doSecuredCheck(InvocationContext invocationContext,
> BeanManager manager, @LoggedIn User user) throws Exception
> {
> return user.isLoggedIn(); // perform security check
> }
> }
> {noformat}
> h3. Compilation Error
> {noformat}
> The annotation @LoggedIn is disallowed for this location
> {noformat}
> h3. Explanation?
> I think it's because {{LoggedIn}} is missing a {{@Target}} of {{PARAMETER}}.
> {code:java,title=LoggedIn.java}
> @Retention(value = RetentionPolicy.RUNTIME)
> @Target({ ElementType.TYPE, ElementType.METHOD })
> @Documented
> @SecurityBindingType
> public @interface LoggedIn {
> {code}
> h3. Conclusion
> Not sure if this is supposed to work, given that {{LoggedIn}} is part of
> PicketLink, not DeltaSpike.
> Is there a workaround for this type of situation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-860) documentation says "@LoggedIn User user", but that's impossible
[
https://issues.apache.org/jira/browse/DELTASPIKE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
The Alchemist updated DELTASPIKE-860:
-
Component/s: Documentation
> documentation says "@LoggedIn User user", but that's impossible
> ---
>
> Key: DELTASPIKE-860
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-860
> Project: DeltaSpike
> Issue Type: Bug
> Components: Documentation
>Reporter: The Alchemist
>Assignee: Rafael Benevides
>
> h3. Documentation Snippet
> http://deltaspike.apache.org/documentation/security.html
> {noformat}
> Create the Authorizer
> @ApplicationScoped
> public class CustomAuthorizer
> {
> @Secures
> @CustomSecurityBinding
> public boolean doSecuredCheck(InvocationContext invocationContext,
> BeanManager manager, @LoggedIn User user) throws Exception
> {
> return user.isLoggedIn(); // perform security check
> }
> }
> {noformat}
> h3. Compilation Error
> {noformat}
> The annotation @LoggedIn is disallowed for this location
> {noformat}
> h3. Explanation?
> I think it's because {{LoggedIn}} is missing a {{@Target}} of {{PARAMETER}}.
> {code:java,title=LoggedIn.java}
> @Retention(value = RetentionPolicy.RUNTIME)
> @Target({ ElementType.TYPE, ElementType.METHOD })
> @Documented
> @SecurityBindingType
> public @interface LoggedIn {
> {code}
> h3. Conclusion
> Not sure if this is supposed to work, given that {{LoggedIn}} is part of
> PicketLink, not DeltaSpike.
> Is there a workaround for this type of situation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-861) RequestDispatcher#forward is redirecting instead of frwarding if I add Deltaspike
[
https://issues.apache.org/jira/browse/DELTASPIKE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372730#comment-14372730
]
FAICAL BOUTAOUNTE commented on DELTASPIKE-861:
--
I've figured out what it was, forward is working as expected it forwards me to
my page correctly. The problem is that I'm forwarding to a JSF page without
passing the window ID parameter which redirect me to the same page and add the
meeting param.
> RequestDispatcher#forward is redirecting instead of frwarding if I add
> Deltaspike
> -
>
> Key: DELTASPIKE-861
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-861
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.3.1
> Environment: jboss-eap-6
> glassfish-4
>Reporter: FAICAL BOUTAOUNTE
>Assignee: Christian Kaltepoth
>
> I'm deploying a web application into JBoss EAP6 and Glassfish 4, every thing
> works as expected till the point where I add deltaskpike jars to the projet.
> Once deltaskpike enabled, the following code inside a servlet:
> request.getServletContext().getRequestDispatcher("/faces/page.xhtml").forward(request,
> response);
> will send a redirect response (HTTP: 302) to the browser instead of
> forwarding on the server side. if I remove deltaskpike jars from the
> application the dispatcher forward works as expected.
> Is Deltaspike modifying the default behaviour of RequestDispatcher ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-861) RequestDispatcher#forward is redirecting instead of frwarding if I add Deltaspike
[
https://issues.apache.org/jira/browse/DELTASPIKE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-861:
Assignee: Christian Kaltepoth
> RequestDispatcher#forward is redirecting instead of frwarding if I add
> Deltaspike
> -
>
> Key: DELTASPIKE-861
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-861
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.3.1
> Environment: jboss-eap-6
> glassfish-4
>Reporter: FAICAL BOUTAOUNTE
>Assignee: Christian Kaltepoth
>
> I'm deploying a web application into JBoss EAP6 and Glassfish 4, every thing
> works as expected till the point where I add deltaskpike jars to the projet.
> Once deltaskpike enabled, the following code inside a servlet:
> request.getServletContext().getRequestDispatcher("/faces/page.xhtml").forward(request,
> response);
> will send a redirect response (HTTP: 302) to the browser instead of
> forwarding on the server side. if I remove deltaskpike jars from the
> application the dispatcher forward works as expected.
> Is Deltaspike modifying the default behaviour of RequestDispatcher ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
