RE: CastorTransformer and CastorSourceConverter
Stephan Michels wrote: > > > Okay, then yet-another-block ;-) > > I can also provide some components for Castor. We should really consider > to move the 'blocks' into an own CVS repository. > > Similar to Avalon? > Whatever we decide, we should wait until we have released 2.1; otherwise we would run into problems with the distribution of 2.1. Carsten
RE: CastorTransformer and CastorSourceConverter
On Fri, 18 Jul 2003, Carsten Ziegeler wrote: > Stephan Michels wrote: > > > > > > Same from me, can we move the CastorSourceConverter into the main tree, > > and also the CastorTransformer? They are very useful in my current > > application. > > No, please not into the main trunk, it's already overcrowded with things > that don't belong to the core. > Now making an own block out of it seems not to be the best idea; we already > have many (too many) small blocks consisting of only a single class. > Now, what about making an "additional" blocks and moving things there? > This is the e.g. the way ant does it with additional tasks. Okay, then yet-another-block ;-) I can also provide some components for Castor. We should really consider to move the 'blocks' into an own CVS repository. Similar to Avalon? Stephan.
RE: CastorTransformer and CastorSourceConverter
Stephan Michels wrote: > > > Same from me, can we move the CastorSourceConverter into the main tree, > and also the CastorTransformer? They are very useful in my current > application. No, please not into the main trunk, it's already overcrowded with things that don't belong to the core. Now making an own block out of it seems not to be the best idea; we already have many (too many) small blocks consisting of only a single class. Now, what about making an "additional" blocks and moving things there? This is the e.g. the way ant does it with additional tasks. > > BTW, shouldn't it called > org/apache/cocoon/components/persistence > instead of > org/apache/cocoon/components/persistance > Yepp :) Carsten
RE: CastorTransformer and CastorSourceConverter
On Wed, 16 Jul 2003, Carsten Ziegeler wrote: > Reinhard Pötz wrote: > > > > In the scratchpad we have a CastorTransformer. I'm not sure but I think > > that it is a rather long time there. Is it in use and stable and is it > > time to move it in the main trunk or can we remove it. > > > > I also found a CastorSourceConverter in the portal framework. What are > > the differences? Can they be unified? > > > I don't now the CastorTransformer, but the CastorSourceConverter. The > converter > is an avalon component that "converts" io streams from and to java objects. > So, you can read an xml file using castor and get the mapped objects and > vice > versa. I guess, this is a more general approach then the transformer. > > In general, I guess as well that they can somehow be unified, e.g. the > transformer > could use the source converter. > I think there is also a patch for the transformer in bugzilla. Same from me, can we move the CastorSourceConverter into the main tree, and also the CastorTransformer? They are very useful in my current application. BTW, shouldn't it called org/apache/cocoon/components/persistence instead of org/apache/cocoon/components/persistance ? Stephan.
RE: CastorTransformer and CastorSourceConverter
From: Carsten Ziegeler > Reinhard Pötz wrote: > > > > In the scratchpad we have a CastorTransformer. I'm not sure but I > > think that it is a rather long time there. Is it in use and > stable and > > is it time to move it in the main trunk or can we remove it. > > > > I also found a CastorSourceConverter in the portal > framework. What are > > the differences? Can they be unified? > > > I don't now the CastorTransformer, but the > CastorSourceConverter. The converter is an avalon component > that "converts" io streams from and to java objects. So, you > can read an xml file using castor and get the mapped objects > and vice versa. I guess, this is a more general approach then > the transformer. > > In general, I guess as well that they can somehow be unified, > e.g. the transformer could use the source converter. I think > there is also a patch for the transformer in bugzilla. Thank you Carsten! Cheers, Reinhard
RE: CastorTransformer and CastorSourceConverter
Reinhard Pötz wrote: > > In the scratchpad we have a CastorTransformer. I'm not sure but I think > that it is a rather long time there. Is it in use and stable and is it > time to move it in the main trunk or can we remove it. > > I also found a CastorSourceConverter in the portal framework. What are > the differences? Can they be unified? > I don't now the CastorTransformer, but the CastorSourceConverter. The converter is an avalon component that "converts" io streams from and to java objects. So, you can read an xml file using castor and get the mapped objects and vice versa. I guess, this is a more general approach then the transformer. In general, I guess as well that they can somehow be unified, e.g. the transformer could use the source converter. I think there is also a patch for the transformer in bugzilla. Carsten
