You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2006/02/13 12:17:26 UTC

RAD with blocks

Giacomo Pati wrote:

> Just to let you know.
> 
> I was corrected by Reinhart.

Reinhard
        ^ ;-)

> The RAD works with the 
> cocoon-trunk/cocoon-block-deployer/cocoon-deployer-plugin-demo module 
> (and not the one I was using for my tests as mentioned above). Also one 
> needs to have Eclipse auto-build enabled so that changed resources will 
> be copied over to the target directory (which isn't that pretty IMHO but 
> maybe this can be fixed anyhow as Eclipse isn't the only IDE used in the 
> world ;-)

Basically I agree with you but as soon as the ReloadingClassloader is integrated 
I don't see a reason not to use it at development time which makes 
auto-compilation mandatory. I'm an Eclipse user, but don't support IDEA and 
Netbeans auto-compilation either?

BTW, if somebody is interested in working on making blocks reality and is 
looking for a manageable task, he can do the integration of the 
ReloadingClassloader into the blocks-fw. If so, just let me know (so that we 
don't duplicate our efforts).

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: RAD with blocks

Posted by Giacomo Pati <gi...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 13 Feb 2006, Reinhard Poetz wrote:

> Date: Mon, 13 Feb 2006 13:44:12 +0100
> From: Reinhard Poetz <re...@apache.org>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: Re: RAD with blocks
> 
> Giacomo Pati wrote:
>
>> >  Basically I agree with you but as soon as the ReloadingClassloader is 
>> >  integrated I don't see a reason not to use it at development time which 
>> >  makes auto-compilation mandatory. I'm an Eclipse user, but don't support 
>> >  IDEA and Netbeans auto-compilation either?
>>
>>
>>  Well, from a users POV an XML, XSLT, sitemap file is a totally different
>>  thing than a class file (which he obviously knows to be compiled first
>>  before being usable).
>
> I'd say that we should wait for user feedback on this. The thing is that I 
> hesitate to make too many things configureable, but sure, if configurations 
> are required, we can add them.
>
> Currently cocoon:simple-deploy points to ./target/classes. We can make this 
> configureable so that people can point to ./src/java/resources. The only 
> thing that I really want to avoid is the possibility to set two locations for 
> a block, one for the compiled Java classes and one for the resources (smells 
> like FS ...).

No, it's not FS. It's not for distributable artifacts and not for life 
deployment, Just for development.

- -- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD8IKhLNdJvZjjVZARAh7lAKCM4ilDgrrEP66Y32Nm4Kt2ZcX6vQCgr2cr
Cxpl3NcnSbM/zBIeDPJPbzc=
=7YaH
-----END PGP SIGNATURE-----

Re: RAD with blocks

Posted by Reinhard Poetz <re...@apache.org>.
Giacomo Pati wrote:

>> Basically I agree with you but as soon as the ReloadingClassloader is 
>> integrated I don't see a reason not to use it at development time 
>> which makes auto-compilation mandatory. I'm an Eclipse user, but don't 
>> support IDEA and Netbeans auto-compilation either?
> 
> 
> Well, from a users POV an XML, XSLT, sitemap file is a totally different 
> thing than a class file (which he obviously knows to be compiled first 
> before being usable).

I'd say that we should wait for user feedback on this. The thing is that I 
hesitate to make too many things configureable, but sure, if configurations are 
required, we can add them.

Currently cocoon:simple-deploy points to ./target/classes. We can make this 
configureable so that people can point to ./src/java/resources. The only thing 
that I really want to avoid is the possibility to set two locations for a block, 
one for the compiled Java classes and one for the resources (smells like FS ...).

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: RAD with blocks

Posted by Giacomo Pati <gi...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 13 Feb 2006, Reinhard Poetz wrote:

> Date: Mon, 13 Feb 2006 12:17:26 +0100
> From: Reinhard Poetz <re...@apache.org>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: RAD with blocks
> 
> Giacomo Pati wrote:
>
>>  Just to let you know.
>>
>>  I was corrected by Reinhart.
>
> Reinhard
>        ^ ;-)

Oops, I'm so sorry (one should write names by heart)

>
>>  The RAD works with the
>>  cocoon-trunk/cocoon-block-deployer/cocoon-deployer-plugin-demo module (and
>>  not the one I was using for my tests as mentioned above). Also one needs
>>  to have Eclipse auto-build enabled so that changed resources will be
>>  copied over to the target directory (which isn't that pretty IMHO but
>>  maybe this can be fixed anyhow as Eclipse isn't the only IDE used in the
>>  world ;-)
>
> Basically I agree with you but as soon as the ReloadingClassloader is 
> integrated I don't see a reason not to use it at development time which makes 
> auto-compilation mandatory. I'm an Eclipse user, but don't support IDEA and 
> Netbeans auto-compilation either?

Well, from a users POV an XML, XSLT, sitemap file is a totally different 
thing than a class file (which he obviously knows to be compiled first 
before being usable).

- -- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD8G15LNdJvZjjVZARArneAJ4+5VT3T6EEtx8rEv3R7A1UVKVSxACgz0wV
mTx5Q5A6lkdihRALGh+aCfk=
=DXj3
-----END PGP SIGNATURE-----

Re: RAD with blocks

Posted by Daniel Fagerstrom <da...@nada.kth.se>.
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>
>> Just to let you know.
>>
>> I was corrected by Reinhart.
>
> Reinhard
>        ^ ;-)
>
>> The RAD works with the 
>> cocoon-trunk/cocoon-block-deployer/cocoon-deployer-plugin-demo module 
>> (and not the one I was using for my tests as mentioned above). Also 
>> one needs to have Eclipse auto-build enabled so that changed 
>> resources will be copied over to the target directory (which isn't 
>> that pretty IMHO but maybe this can be fixed anyhow as Eclipse isn't 
>> the only IDE used in the world ;-)
>
> Basically I agree with you but as soon as the ReloadingClassloader is 
> integrated I don't see a reason not to use it at development time 
> which makes auto-compilation mandatory. I'm an Eclipse user, but don't 
> support IDEA and Netbeans auto-compilation either?
>
> BTW, if somebody is interested in working on making blocks reality and 
> is looking for a manageable task, he can do the integration of the 
> ReloadingClassloader into the blocks-fw. If so, just let me know (so 
> that we don't duplicate our efforts).
>
RT: When we move to OSGi the Cocoon "platform" will contain the same 
basic standard OSGi framework and service bundles as Eclipse (or maybe 
from Felix). And a Cocoon block will basically be a bundle, and such can 
be developed with the plug-in development environment in Eclipse. Maybe 
Eclipse auto build is gathered in a few plug-ins, in that case we could 
just reuse them for Cocoon development. Anyone who knows how it works in 
Eclipse?

/Daniel