[
https://issues.apache.org/jira/browse/JUDDI-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008266#comment-15008266
]
Matthieu Ghilain commented on JUDDI-942:
----------------------------------------
If you mean the init function of the dynamically added servlet, yes it is fired
by the container. I would go for option B if it is compatible with servlet 2.0.
But wondering do you still want to support servlet 2.0 ^^?
>From a rapid google search:
*History*
Servlet API version Released Platform
Servlet 3.1 May 2013 JavaEE 7
Servlet 3.0 December 2009 JavaEE 6, JavaSE 6
Servlet 2.5 September 2005 JavaEE 5, JavaSE 5
Servlet 2.4 November 2003 J2EE 1.4, J2SE 1.3
> Automatic instantiation of UDDIClerkServlet
> -------------------------------------------
>
> Key: JUDDI-942
> URL: https://issues.apache.org/jira/browse/JUDDI-942
> Project: jUDDI
> Issue Type: Improvement
> Components: juddi-client
> Affects Versions: 3.3.1
> Reporter: Matthieu Ghilain
>
> It would be useful to not have to instantiate manually the UDDIClerkServlet
> when running in a Servlet 3.0 env. Would it be possible to add a class
> implementing ServletContextListener which would instantiate automatically the
> UDDIClerkServlet?
> Therefore the registration of services would be done automatically by adding
> the JUDDI annotations on the web services classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
