[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Luis Canales (JIRA)
[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ]
Luis Canales updated WFLY-9708:
-------------------------------
Description:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
_java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
was:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
_java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
> Wildfly 11.0.0.Final JSF 1.2 configuration error
> ------------------------------------------------
>
> Key: WFLY-9708
> URL: https://issues.jboss.org/browse/WFLY-9708
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 11.0.0.Final
> Reporter: Luis Canales
> Assignee: Martin Kouba
> Priority: Optional
> Attachments: log.txt
>
>
> Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
> _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
> If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Luis Canales (JIRA)
[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ]
Luis Canales updated WFLY-9708:
-------------------------------
Description:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
_java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
was:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
> Wildfly 11.0.0.Final JSF 1.2 configuration error
> ------------------------------------------------
>
> Key: WFLY-9708
> URL: https://issues.jboss.org/browse/WFLY-9708
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 11.0.0.Final
> Reporter: Luis Canales
> Assignee: Martin Kouba
> Priority: Optional
> Attachments: log.txt
>
>
> Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
> _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
> If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Luis Canales (JIRA)
[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ]
Luis Canales updated WFLY-9708:
-------------------------------
Description:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0 so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
was:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0 so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) an deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
> Wildfly 11.0.0.Final JSF 1.2 configuration error
> ------------------------------------------------
>
> Key: WFLY-9708
> URL: https://issues.jboss.org/browse/WFLY-9708
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 11.0.0.Final
> Reporter: Luis Canales
> Assignee: Martin Kouba
> Priority: Optional
> Attachments: log.txt
>
>
> Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0 so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
> java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
> If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Luis Canales (JIRA)
[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ]
Luis Canales updated WFLY-9708:
-------------------------------
Description:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
was:
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0 so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
> Wildfly 11.0.0.Final JSF 1.2 configuration error
> ------------------------------------------------
>
> Key: WFLY-9708
> URL: https://issues.jboss.org/browse/WFLY-9708
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 11.0.0.Final
> Reporter: Luis Canales
> Assignee: Martin Kouba
> Priority: Optional
> Attachments: log.txt
>
>
> Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
> java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
> If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Luis Canales (JIRA)
Luis Canales created WFLY-9708:
----------------------------------
Summary: Wildfly 11.0.0.Final JSF 1.2 configuration error
Key: WFLY-9708
URL: https://issues.jboss.org/browse/WFLY-9708
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, JSF
Affects Versions: 11.0.0.Final
Reporter: Luis Canales
Assignee: Martin Kouba
Priority: Optional
Attachments: log.txt
Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF 2.0 so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) an deploy a JSF1.2 application, I get this error:
java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper
If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9707) Remove JASPI module
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-9707:
--------------------------------------
Summary: Remove JASPI module
Key: WFLY-9707
URL: https://issues.jboss.org/browse/WFLY-9707
Project: WildFly
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 12.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3519) Add JASPI Module
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFCORE-3519:
----------------------------------------
Summary: Add JASPI Module
Key: WFCORE-3519
URL: https://issues.jboss.org/browse/WFCORE-3519
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 4.0.0.Alpha6
(Copy from WildFly)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9620) ServletContext.getResourceAsStream, for deployments which have (Java EE) servlet overlays, serves files which are outside of the deployment
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9620?page=com.atlassian.jira.plugin.... ]
Stuart Douglas updated WFLY-9620:
---------------------------------
Security: (was: Security Issue)
> ServletContext.getResourceAsStream, for deployments which have (Java EE) servlet overlays, serves files which are outside of the deployment
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9620
> URL: https://issues.jboss.org/browse/WFLY-9620
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.2.Final, 10.1.0.Final, 11.0.0.Final
> Reporter: Laurent ROUSSEL
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 12.0.0.Alpha1
>
>
> A user has reported in the forums that there appears to be an issue (since 9.0.x till present 11.0.0 WildFly releases) where files like `/etc/passwd` are served by the web container to the clients, when the client requests a crafted URL against a Java EE deployment which has (Java EE) servlet overlays. Please see the referenced forum thread[1] for more details.
> Although, the steps noted in that thread involves Spring framework and gets triggered in a very specific way, the root cause appears to be the call to `ServletContext.getResourceAsInputStream` (which is what the spring framework ends up calling with a path like "/../../../../../../../..//etc/passwd", ends up actually serving the resource even if the path is outside the scope of the deployment to which the servlet context belongs.
> I could reproduce this against the latest WildFly in a simple test case that's here [2]
> [1] https://developer.jboss.org/thread/276826
> [2] https://github.com/jaikiran/wildfly/commit/ed05258aa824ab91a52ef6554e9707...
> P.S: The credit for reporting this issue should go to Laurent Roussel who reported this in the forum thread, but I don't have access to change the "Reporter" field of the JIRA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9706) Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-9706?page=com.atlassian.jira.plugin.... ]
Erich Duda updated WFLY-9706:
-----------------------------
Summary: Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1 (was: Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values is not -1)
> Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9706
> URL: https://issues.jboss.org/browse/WFLY-9706
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> This Jira is reaction to WFLY-9433.
> The WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases.
> As it is proposed in JBEAP-14110, this change should be done in 2 steps:
> * only WARN the user if the parameter is not valid (a negative value other than -1)
> * in next release, reject the parameter
> I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months