Michael Gloegl wrote:
I finally managed to integrate my tutorial into the hibernate reference
manual. I committed it as a seperate chapter, feel free however to move
the stuff around as you want.
Sorry that this took longer than expected, reformating this with xdoclet
was more effort than I tho
Sorry that this took longer than expected, reformating this with xdoclet
was more effort than I thought.
docbook of course, not xdoclet :)
--
Michael Gloegl mail: [EMAIL PROTECTED]
www: http://www.gloegl.de
phone: +49 (0)176 24 111 070
-
Hi everybody,
I finally managed to integrate my tutorial into the hibernate reference
manual. I committed it as a seperate chapter, feel free however to move
the stuff around as you want.
Sorry that this took longer than expected, reformating this with xdoclet
was more effort than I thought.
M
BEA has a history of users prepending to the classpath. For example, here is
how users are told to configure the latest WebLogic to work with their oldest
sqlserver driver
(http://e-docs.bea.com/wls/docs81/mssqlserver4/install_jmsq4.html#413811):
> Microsoft SQL Server is bundled with your WebLo
Max Rydahl Andersen wrote:
Their usual strategy is to repackage the third party libs into
weblogic.*, so they basically don't have to. antlr isn't.
Weblogic sucks big time then! Can this really be true that they dont
have proper isolation ?!
And yes - if weblogic really is that bad then repacka
Their usual strategy is to repackage the third party libs into
weblogic.*, so they basically don't have to. antlr isn't.
Weblogic sucks big time then! Can this really be true that they dont
have proper isolation ?!
And yes - if weblogic really is that bad then repackaging antlr will be
their on
Max Rydahl Andersen wrote:
hi,
Not keen on fixing antlr ? Why not - its the least we can do for them ,)
I mean moving it to org.hibernate.antlr, we can fix it :-)
But anyhow I have a hard time understanding why it should not work in
weblogic as
long as the application is packaged correctly!? Dont
hi,
Not keen on fixing antlr ? Why not - its the least we can do for them ,)
But anyhow I have a hard time understanding why it should not work in
weblogic as
long as the application is packaged correctly!? Dont weblogic have proper
classloader
isolation ?
And yes - if weblogic really is that ba
I'm really *not* keen on that, but for now the best solutions seems to
repackage antlr in our own subpackage.
Any pros and cons.
Even if BEA is reactive, their userbase won't migrate until... some time.
Max Rydahl Andersen wrote:
Hi guys,
I've confirmed that antlr has 11 instances of class.fornam
