[jetty-dev] [jira] (JETTY-1495) JETTY-129 is not resolved.

"Leena (JIRA)" <[email protected]>
Newsgroups gmane.comp.java.jetty.general
Message-ID <1086492202.52475.1331816283040.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
    [ https://jira.codehaus.org/browse/JETTY-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294194#comment-294194 ] 

Leena commented on JETTY-1495:
------------------------------

Hi Alex, I just went through the solution you provided at http://forum.springsource.org/showthread.php?122876-Root-Application-Context-loading-after-Dispatcher-Context&p=405003#post405003.
But I do not think I will able to use that as I am not using spring-mvc (Dispatcher Servlet) instead I am using Jersey (another Front Controller)

@Jan: Can you please fix this issue in Jetty ASAP. 
                
> JETTY-129 is not resolved. 
> ---------------------------
>
>                 Key: JETTY-1495
>                 URL: https://jira.codehaus.org/browse/JETTY-1495
>             Project: Jetty
>          Issue Type: Bug
>          Components: Servlet
>            Reporter: Leena
>            Assignee: Jan Bartel
>         Attachments: HelloServlet.java, OneServletContext.java, TestApp.zip
>
>
> There is already a bug (JETTY-129)logged about 'ServletContextListeners called after servlets are initialized'
> http://jira.codehaus.org/browse/JETTY-129.
>  It is mentioned, It is fixed in 6.0.2, 6.1.0pre0. I am using jetty-servlet (8.1.1.v20120215). But it is still there.
> Is this bug fixed?

--
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.