Hi, the issue is that right now i have build the
system i�m working on to use the autodeployer feature
(that is to copy all the .jar in the deploy/ dir). I
think i�ll have to switch to another method later.
The problem i�m facing is this: when i create a bean
and "hot deploy it" (just copying it) everything works
great, but if i update it (copy another .jar to the
deploy dir with the same name) the console logger
tells me that it was deployed, and that the name was
bound, but when i run the bean i can see is still the
old one, no matter how many times i "update" it.
I don�t know if this is supposed to work this way, but
this came up when i upgraded to 2.0betaProd-01,
--- Rickard �berg <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Francisco Andrades wrote:
> > How can i enable the "autodeployer" in a
> production
> > system?
>
> Well, the autodeployer is always enabled. It's just
> that it might be
> better to use some of the other deployment tools
> that we are working on
> for production use.
>
> /Rickard
>
> --
> Rickard �berg
=====
One ring to rule them all, one ring to find them
one ring to bring them all and in the darkness bind them
... in the land of Mordor where the shadows lie
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
