Hi Thomas & Gerhard,

thanks for your quick reply. You're right - the problem occurs when weld loads 
the classes. So I thought about excluding the classes from weld-scanning in 
beans.xml. Unfortunately that doesn't work - has anyone tried this before? 
Otherwise I'll ask at JBoss.

I found the description of the weld feature here:
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/Exclude_Beans_From_the_Scanning_Process.html

Sample beans.xml for excluding:
<beans xmlns="http://java.sun.com/xml/ns/javaee"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xmlns:weld="http://jboss.org/schema/weld/beans";
        xsi:schemaLocation="
          http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/beans_1_0.xsd
          http://jboss.org/schema/weld/beans 
http://jboss.org/schema/weld/beans_1_1.xsd";>
        <weld:scan>
                <weld:exclude
                        
name="org.apache.deltaspike.jsf.impl.scope.window.ClientWindowAdapter" />
                <weld:exclude
                        
name="org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow" />
                <weld:exclude
                        
name="org.apache.deltaspike.jsf.impl.listener.request.JsfClientWindowAwareLifecycleWrapper"
 />
        </weld:scan>
</beans>

Regards,
Thomas



________________________________________
Von: Gerhard Petracek <[email protected]>
Gesendet: Mittwoch, 04. Juni 2014 15:37
An: [email protected]
Betreff: Re: Disable JSF 2.2 Features in Deltaspike

@thomas a.:
no - the server produces that log-output way earlier.

@thomas s.:
if there is no way to influence the server-output, you can file a ticket
for as7.

regards,
gerhard



2014-06-04 15:31 GMT+02:00 Thomas Andraschko <[email protected]>:

> Hi,
>
> it may be possible if we provide a Extension to veto our JSF 2.2 artifacts
> if JSF2.2 is not available.
>
> WDYT Gerhard?
>
> Regards,
> Thomas
>
>
> 2014-06-04 15:25 GMT+02:00 Stemmer Thomas <[email protected]>:
>
> > Hi,
> >
> > I'm running on JBoss 7.x with JSF 2.1. With Deltaspike 0.6+ I get a lot
> of
> > info/warn messages from jboss classloading (like
> >
> http://mail-archives.apache.org/mod_mbox/deltaspike-users/201403.mbox/%3ccafychvq__lbr0einu_ifkxar+tmqcsnnyqtfeqmxk5thuy5...@mail.gmail.com%3E
> > )
> >
> > Is there any chance to disable the 2.2 Features?
> >
> > For DefaultClientWindow I tried the following, but that doesn't help as
> > the classloader still tries to load the JSF 2.2 classes.
> > @Specializes
> > public class ClientWindow extends DefaultClientWindow {
> >     @Override
> >     public boolean isClientWindowRenderModeEnabled(FacesContext
> > facesContext) {
> >         return false;
> >     }
> > }
> >
> >
> >
> > Thanks,
> > regards Thomas
> >
>

Reply via email to