This is a new one on me - but then I have only used
1.3 with jboss-jetty. The fact that Jetty doesn't even
appear on the stack-trace leads me to concur with your
diagnosis that it is the J2EEDeployer.
Perhaps this has already been fixed, what version of
JBoss are you using ?
Jules
--- Martin Klang <[EMAIL PROTECTED]> wrote: >
>
> to answer my previous question (which still hasn't
> appeared on the list :)
>
> the error goes away when using jdk1.3 (.01). so i'm
> assuming it's a
> problem with the deployer needing jdk1.3+ to work.
> hmm, that's a shame.
> come to think of it this rings a bell -> isn't there
> some way of manually
> deploying and circumventing the problem? cos' it's
> just the autodeployer
> that fails like this right?
>
> jules - you might want to add to the readme that
> deployment will fail with
> jdk < 1.3.
>
>
> /m
>
>
>
> --
>
--------------------------------------------------------------
> To subscribe:
> [EMAIL PROTECTED]
> To unsubscribe:
> [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
