6:14 p.m.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Ales Justin
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned JBAS-8035:
-------------------------------
Assignee: Marius Bogoevici (was: Ales Justin)
Reassign to Marius.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on JBAS-8035:
---------------------------------
Stan, it seems a little odd that the JSF API is not on the classpath for the app server...
(Agreed about JSF implementation for sure)
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:06 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert commented on JBAS-8035:
------------------------------------
I think it only seems odd because we were doing it wrong in the past. Having JSF
available globally led to some weird issues for applications that weren't even using
JSF.
The idea with the JSF Deployer is that any WAR should be allowed to choose its JSF
implementation or to choose no implementation at all.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert commented on JBAS-8035:
------------------------------------
Pete, I think I misunderstood you. You are saying that we can have the JSF API globally
available, but not the impl. In theory I think that would work but I'm very hesitant
to have the Mojarra version available globally and end up mixing, for instance, Mojarra
2.0 API with MyFaces 1.1 impl. Also, it doesn't seem right that web teir API's
would be available outside the web tier.
For the Weld Deployer, I think the solution is to move weld-jboss-webteir.jar out of the
weld.deployer root. Then make sure that this jar is added to each deployment that needs
it individually.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:39 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Ales Justin updated JBAS-8035:
------------------------------
Priority: Blocker (was: Major)
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on JBAS-8035:
---------------------------------
Yes, we can definitely make it work with the weld-jboss-webtier.jar being added only to
deployments that need JSF.
However I think we have uncovered a bigger problem with removing the jsf-api.jar from the
server classpath. This is pretty unusual, no other part of JBoss AS doesn't expose
it's API this way. Therefore I think this will surprise users - which is never a good
thing.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Marius Bogoevici commented on JBAS-8035:
----------------------------------------
If we move weld-int-webtier.jar to lib-int we need to separate the JSP listeners from
JSF.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:51 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert commented on JBAS-8035:
------------------------------------
Perhaps we need to have a wider discussion about this. Certainly it is a tradeoff. I
don't see why anyone should expect a web tier API to be available outside the web
tier. Plus it solves some old problems and gives users lots of flexibility with new
choices over how they deploy and configure their applications.
Some of these problems address past complaints from the Seam/Weld teams. For instance,
had the JSF Deployer been in place you would have been able to develop against
JSF2+JBossAS immediately (without hacking). You can also, for instance, benchmark the
same WAR against both Mojarra and MyFaces. Switching implementations is just a matter of
changing one context-param in web.xml.
In short, my argument is that this is well worth it. I want JBoss AS to be the best
platform for JSF. The JSF Deployer allows you to do things that no other container can
touch.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert commented on JBAS-8035:
------------------------------------
Pete and Marius,
Just got back from a long run where I think better. I realized that I've already
implemented a compromise. I discovered last week that Seam apps would fail if the Seam
jars were packaged at the EAR level. Since many Seam EARs are packaged this way it would
break backward compatibility. So for any deployment with a JSF WAR, we add the JSF jars
to all parent deployments. This way, JSF jars are available to both the WAR and the EAR.
This is already done and should address your concerns since application developers
won't notice any difference.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Ales Justin commented on JBAS-8035:
-----------------------------------
> This way, JSF jars are available to both the WAR and the EAR.
This is already done and should address your concerns since application developers
won't notice any difference.
This directly calls for CCE; e.g. passing JSF info / context from web / UI layer to
Seam's business logic
Or are you saying you exclude JSF from the .war it came with, and only place it into top
level .ear classpath?
As this would then somehow work, but imo this is a hack.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert commented on JBAS-8035:
------------------------------------
Right now I'm adding it to both WAR and EAR. I didn't get a CCE, but if you think
there is some scenario where this could happen then it's easy enough to change that
logic.
Don't you think it's less of a hack than making JSF globally available to every
deployment? The old way we did this was the hack. Every WAR had to call the JSF context
listener and load JSF classes, even if it wasn't using JSF.
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:25 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Marius Bogoevici resolved JBAS-8035.
------------------------------------
Fix Version/s: 6.0.0.M4
Resolution: Done
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
Fix For: 6.0.0.M4
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-8035) Weld Deployer not working with new JSF Deployer
[
https://jira.jboss.org/browse/JBAS-8035?page=com.atlassian.jira.plugin.sy...
]
Pete Muir closed JBAS-8035.
---------------------------
Weld Deployer not working with new JSF Deployer
-----------------------------------------------
Key: JBAS-8035
URL: https://jira.jboss.org/browse/JBAS-8035
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Marius Bogoevici
Priority: Blocker
Fix For: 6.0.0.M4
I think this will require Weld Deployer changes, so assigning to Ales for now.
I've integrated the JSF Deployer into AS but now the Weld tests are failing. If you
deploy a Weld app you will see:
18:58:51,956 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weld-numberguess]]
Exception sending context initialized event to listener
instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
: java.lang.NoClassDefFoundError: javax/faces/application/ApplicationFactory
The JSF deployer is much more selective about adding JSF to the classpath. It looks like
JSF is probably trying to load
org.jboss.weld.integration.webtier.jsf.WeldApplicationFactory that is defined in
weld.deployer/lib-int/faces/META-INF/faces-config.xml. I think what happens is that this
WeldApplicationFactory is loaded from weld.deployer/weld-jboss-int-webteir.jar. Then it
references a JSF core class and it can't find it because the classloader for that
doesn't see JSF.
The tricky part is that you can't just add JSF to the classloader for that jar. Each
WAR can have a different JSF Implementation if it wants. So this sort of thing must be
done for each individual deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5833
days inactive
5909
days old
13 comments
4 participants
participants (4)
-
Ales Justin (JIRA) -
Marius Bogoevici (JIRA)
-
Pete Muir (JIRA)
-
Stan Silvert (JIRA)