Re: suggestion for 3.0 perheps?

Martin Cooper wrote:
> It seems to me that you could do this yourself. You could have a servlet in
> your web app that watches for changes in .bean files, and regenerates the
> .java files. Resin should take over from there, no?

This is actually something I'd like to add to 3.0. I don't know how it
should be configured, though.

There's basically two parts of the problem: dependency and make. Both
could be handled by special beans, similar to the way ant works,
although the ant tasks don't quite do the right thing.

-- Scott

>
> --
> Martin Cooper
>
>
>
>>-----Original Message-----
>>From: Christian Andersson [mailto:ca@xxx.no]
>>Sent: Saturday, August 31, 2002 2:26 PM
>>To: resin-interest@xxx.com
>>Subject: suggestion for 3.0 perheps?
>>
>>
>>Hi there, I was wondering if it is possible to configure
>>resin to check
>>for changes in files and execute some function in a class if it is...
>>
>>in resin ther already is some of these
>>.jsp -> .java -> .class for changed .jsp pages
>>.java -> .class for changed .java files in
>>"classes" folder
>>
>>what I would like to have also is
>>
>>.bean -> .java -> .class
>>
>>if the .bean file is changed a new .java file is to be
>>generated and a
>>new .class file is to be compiled and used...
>>(the .bean file is an ordinary .xml file that defines the
>>properties in
>>a a bean, and some more information)
>>
>>I do this manually now, so it is not a big problem, but if
>>resin can do
>>this in the current version, that would be great, if it
>>cannot, is this
>>something that could be usefull to implement in resin 3.0?
>>
>>If this is something that would be interesting for 3.0 (and does not
>>exist in the current version) then i might have some ideas
>>(if they are
>>good or not I do not know)
>>
>>when the "generator" that produces the .java file recieves
>>information
>>that a file has been changed, it should generate the file, and then
>>return to resin a set of information... since the generator might
>>generate several .java files it should return info on every
>>.java file
>>it generates so that resin can build a list of which file
>>corresponds to
>>which .java file... it should also tell resin if it needs to restart
>>the application to get the new .java/class working...
>>
>>well that is it, but I guess that this could spring some ideas in for
>>yourself...
>>
>>/Christian Andersson
>>
>>
>
>
Received on Tue 03 Sep 2002 13:52:54 -0700