You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Torsten Curdt <tc...@apache.org> on 2004/12/14 20:04:45 UTC
[ANN] auto-compiling javaflow in trunk
Hey, folks!
I just committed the auto-compiling javaflow into trunk.
Since it's quite a big change I thought I go for trunk
first. (although it was initially developed with/for 2.1)
I changed the default Servlet to the ParanoidServlet
inside the web.xml. Feel free to change that ...but
I thought it might be better for people who want to
give it a quick try.
Due to the big change the GroovyFlow in scratchpad
had to go. But it should be quite easy to re-add this
through a jci compiler implementation. Sorry, I did
not have the time to do that yet.
Both javaflow and jci are now external maven projects.
If it's ok for the folks at jakarta both projects will
find their home inside the jakarta sandbox. (At least
that's what we agreed on at the ApacheCon). For now I
added the source distribution to our repo as well.
I've put them into the javaflow block as zip-archives.
Does anyone know ...do I just propose the projects
for the sandbox? AFAIU every apache committer can
get commit access. What's the process for that?
Or do I need some jakarta committer to sponsor the
projects?
There is quite a TODO list for all three projects,
jci, javaflow and the cocoon integration. (still need
to write down some of that) So if anyone would like to
help out - that would be great.
It's important that this does not end up in a one man
show. That being said: javaflow is no black magic!
there are quite some things to improve even without
touching the byte code rewriting. IMO the general flow
(also javascript) integration also needs some polishing.
There are some areas we could benefit from those two
projects. Some potentially usecases:
* auto-compilation of components
* simplification of the XSP infrastructure
I promise to do the TODOs ASAP but currently I am
awfully busy.
Glad I finally made it to commit the stuff :o)
Enjoy!
cheers
--
Torsten
PS: For those who tried it: yeah - I know ...the logging
is the first thing on the TODO list ;-)
Re: Auto-Compling classes located in packages
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
> I'm doing wrong because classes in other packages work well.
^^^^^
the already existing packages
needed for the javaflow samples
--
Reinhard
Re: Auto-Compling classes located in packages
Posted by Torsten Curdt <tc...@apache.org>.
Hm... this works for me as well
* changed dir /home/tcurdt/dev/cocoon-trunk/build/webapp/WEB-INF/src
* created dir /home/tcurdt/dev/cocoon-trunk/build/webapp/WEB-INF/src/test
* created file
/home/tcurdt/dev/cocoon-trunk/build/webapp/WEB-INF/src/test/Test.java
storing class test.Test
parsing test.Test
saving test.Test class information in BCEL repository
0 errors, 0 warnings
Please restart cocoon and send me the output of the CCL.
> BTW, I changed the FlowscriptInterpreter to use the thread classloader
> instead of the former implementation of the compiling classloader. Right?
That should be cool.
cheers
--
Torsten
Auto-Compling classes located in packages
Posted by Reinhard Poetz <re...@apache.org>.
While working with the new auto-compiling classloader I came across a problem:
- I created a new package "yyy" in WEB-INF/src
- Then I added the class "Reinhard"
At the console I get following error message:
------------------------------------------------------------------------------------
* created dir F:\os\cocoon\trunk\build\webapp\WEB-INF\src\yyy
* created file F:\os\cocoon\trunk\build\webapp\WEB-INF\src\yyy\Reinhard.java
removing resource xxx\Reinhard
yyy\Reinhard.java (16) : The declared package does not match the expected packag
e
yyy\Reinhard.java (21) : The public type Reinhard must be defined in its own fil
e
2 errors, 0 warnings
removing resource yyy\Reinhard
reloading
------------------------------------------------------------------------------------
Here the class:
------------------------------------------------------------------------------------
package yyy;
public class Reinhard {
public void test() {
System.out.println("Reinhard!");
}
}
------------------------------------------------------------------------------------
Adding a class at the root directory works well. I don't understand what I'm
doing wrong because classes in other packages work well.
- o -
BTW, I changed the FlowscriptInterpreter to use the thread classloader instead
of the former implementation of the compiling classloader. Right?
--
Reinhard
Re: [ANN] auto-compiling javaflow in trunk
Posted by Torsten Curdt <tc...@apache.org>.
>>> Mmmh... AFAIK jakarta sandbox is open to jakarta committers.
>>
>>
>>
>> Once it was that way... then when I was still contributing there there
>> has been consensus on opening to any APache committer.
>>
>> I don't remember the final "formal" outcome, but AFAIK there should
>> not be major problems in getting access to the sandbox :-)
>>
>
> especially with the offer you make :-)
I asked over at general@jakarta and it's open for *any* apache
committer. ...and the first reactions were very positive. So if everyone
over here in cocoon land is fine I will try to move the code (which is
currently in svn as zip archive) ASAP. (restrictions of getting karma
and spare time apply)
cheers
--
Torsten
Re: [ANN] auto-compiling javaflow in trunk
Posted by Reinhard Poetz <re...@apache.org>.
Nicola Ken Barozzi wrote:
> Sylvain Wallez wrote:
> ...
>
>> Mmmh... AFAIK jakarta sandbox is open to jakarta committers.
>
>
> Once it was that way... then when I was still contributing there there
> has been consensus on opening to any APache committer.
>
> I don't remember the final "formal" outcome, but AFAIK there should not
> be major problems in getting access to the sandbox :-)
>
especially with the offer you make :-)
--
Reinhard
Re: [ANN] auto-compiling javaflow in trunk
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Sylvain Wallez wrote:
...
> Mmmh... AFAIK jakarta sandbox is open to jakarta committers.
Once it was that way... then when I was still contributing there there
has been consensus on opening to any APache committer.
I don't remember the final "formal" outcome, but AFAIK there should not
be major problems in getting access to the sandbox :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [ANN] auto-compiling javaflow in trunk
Posted by Torsten Curdt <tc...@apache.org>.
<snip/>
> Thanks a lot, Santa :-)
I do have a bit of a beard but ;-)
<snip/>
>> Both javaflow and jci are now external maven projects.
>
>
>
> Maven? Do you mean Gump?
No, I mean maven ;-)
You need maven to build them.
<snip/>
>> Does anyone know ...do I just propose the projects
>> for the sandbox? AFAIU every apache committer can
>> get commit access. What's the process for that?
>> Or do I need some jakarta committer to sponsor the
>> projects?
>
>
>
> Mmmh... AFAIK jakarta sandbox is open to jakarta committers.
Hm.... I heart a different story at the ApacheCon :-/
I will ask over at jakarta.
cheers
--
Torsten
Re: [ANN] auto-compiling javaflow in trunk
Posted by Sylvain Wallez <sy...@apache.org>.
Torsten Curdt wrote:
> Hey, folks!
>
> I just committed the auto-compiling javaflow into trunk.
> Since it's quite a big change I thought I go for trunk
> first. (although it was initially developed with/for 2.1)
Thanks a lot, Santa :-)
> I changed the default Servlet to the ParanoidServlet
> inside the web.xml. Feel free to change that ...but
> I thought it might be better for people who want to
> give it a quick try.
>
> Due to the big change the GroovyFlow in scratchpad
> had to go. But it should be quite easy to re-add this
> through a jci compiler implementation. Sorry, I did
> not have the time to do that yet.
>
> Both javaflow and jci are now external maven projects.
Maven? Do you mean Gump?
> If it's ok for the folks at jakarta both projects will
> find their home inside the jakarta sandbox. (At least
> that's what we agreed on at the ApacheCon). For now I
> added the source distribution to our repo as well.
> I've put them into the javaflow block as zip-archives.
>
> Does anyone know ...do I just propose the projects
> for the sandbox? AFAIU every apache committer can
> get commit access. What's the process for that?
> Or do I need some jakarta committer to sponsor the
> projects?
Mmmh... AFAIK jakarta sandbox is open to jakarta committers.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }