[jetty-dev] [jira] (JETTY-1486) Dependency jar files are no longer scanned for .tld files with jetty-maven-plugin

"Jan Bartel (JIRA)" <[email protected]>
Newsgroups gmane.comp.java.jetty.general
Message-ID <1888762860.44662.1330495802981.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
     [ https://jira.codehaus.org/browse/JETTY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel resolved JETTY-1486.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 7.6.2

Hi Leonard,

Yes, you're right, 7.6.x does not work! That was my fault, I was overwriting the attribute org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern in the startup of the plugin (attempting to make sure that all the jars that we distribute with jetty that have tlds get scanned - unfortunately I forgot about jsf!).

So now I have added in a pattern for the common jsf impls: myfaces and the jsf from sun, so from jetty-7.6.2 onwards you won't have to set any attributes or anything. Just ensure that the jsf jars are on the *plugin* classpath, not the webapp's classpath.

If you have other jars that need to be scanned, then you'll need to specify their pattern in a context xml file, but these will now be *additive* to the patterns defined inside the plugin startup. In other words, if you have a new dependency jar foo-123.jar that contains tlds that you want scanned, then you would put the following in your context xml file:

<Call name="setAttribute">
<Arg>org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern</Arg>
<Arg>.*/.*foo-[^/]*\.jar$</Arg>
</Call>

The plugin implementation will take care of adding in all the other standard patterns.

cheers
Jan

                
> Dependency jar files are no longer scanned for .tld files with jetty-maven-plugin
> ---------------------------------------------------------------------------------
>
>                 Key: JETTY-1486
>                 URL: https://jira.codehaus.org/browse/JETTY-1486
>             Project: Jetty
>          Issue Type: Bug
>          Components: Maven
>    Affects Versions: 7.5.4, 7.6.0
>            Reporter: Leonardo Uribe
>            Assignee: Jan Bartel
>             Fix For: 7.6.2
>
>         Attachments: myfaces-helloworld20.zip
>
>
> Checking some archetypes for MyFaces Core project I notice the latest version of jetty does not work.
> MyFaces has a listener entry in a .tld file, and that is not loaded or scanned anymore
> I'll attach a example webapp for this one. Just type mvn clean -PjettyConfig jetty:run. With jetty 7.4.5.v20110725 works but if you change maven.jetty.plugin.version property inside the pom to 7.6.0.v20120127 it does not, throwing a ClassNotFoundException. Later, I added myfaces jars as dependencies for the plugin but the tlds are not scanned, so myfaces listener is not loaded and another exception occur (Factory not loaded). Later if I add:
> <listener>
>   <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
> </listener>
> Into web.xml the app works, but contextPath is not added. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.