On 11 May 2011 10:23, Paul Merlin <eskatos_at_n0pe.org> wrote:
> Quoting Richard Kolb <rjdkolb_at_gmail.com>:
> > I know I am replying on a very old mail
>
> Sure, back from the past :)
>
:)
Yes, me moaning about the same issue again.
>
>
> > I created an issue so the below can be documented - and now it is :)
> >
> > And now that the below can be fixed :
> > http://java.net/jira/browse/GLASSFISH-16604
>
> In my understanding it's not something that can be fixed at all.
> As a JEE developer/architect/whatever you just have to keep it in mind
> while
> writing code and worse, while reading the code of the libraries you want to
> use
>
Yes, I understand it is a fundamental issue.
Currently as a developer I hit the issue every few hours and I am sure
millions of other Java developers get the same thing. On the quality alias I
often see reports of this.
By the way, your email is what was used to document the issue :
http://java.net/jira/browse/GLASSFISH-13053
...
>
> Indeed, I agree that having it documented clearly in all JEE books and
> related products manuals would be nice.
>
How about NetBeans and Eclipse warning you before it happens and asking for
a restart ?
>
> BTW I believe that OSGi can suffer from the very same issue.
>
Ouch. Did not know that.
regards
Richard.