Skip to main content

Differences between Glassfish trunk and JSR 315 API

2 replies [Last post]
fwolff
Offline
Joined: 2008-12-02
Points: 0

Hi,

I'm wondering why the JSR WebServletContextListener annotation is named WebListener in Glassfish and why AsyncContext.forward(...) methods are named AsyncContext.dispatch(...)?

Does it mean that the spec will follow the current Glassfish API or the opposite?

Thanks for any reply,
Franck.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
fwolff
Offline
Joined: 2008-12-02
Points: 0

Thanks!

Jan Luehe

On 04/21/09 03:13 PM, webtier@javadesktop.org wrote:
> Hi,
>
> I'm wondering why the JSR WebServletContextListener annotation is named WebListener in Glassfish and why AsyncContext.forward(...) methods are named AsyncContext.dispatch(...)?
>
> Does it mean that the spec will follow the current Glassfish API or the opposite?
>
> Thanks for any reply,
>

The javax.servlet APIs in GlassFish v3's web/javax.servlet module
are the most up-to-date and will be reflected in the soon-to-be-released
final draft of the spec.

Jan

> Franck.
> [Message sent by forum member 'fwolff' (fwolff)]
>
> http://forums.java.net/jive/thread.jspa?messageID=343147
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: webtier-help@glassfish.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: webtier-help@glassfish.dev.java.net