Re: changes to maven archetypes, alpha1 - alpha2
Jos Snellings wrote:
With pleasure.
By the way, I am starting to write a prototype for an application with
the latest version. Yes, I am willing to take due changes in available
classes.
Here's a question:
- will there be an alpha-3 phase?
Yes. Although I consider the code as rather stable, we need more
community involvement (your mails are very helpful by the way!) before
we are ready to move on.
The only technical issue is that I want to rework the pipeline API once
again in order to support typed results. Currently a pipeline always
writes into an OutputStream and if you need something else (e.g. a
SAXBuffer, a business object, etc.) you have to work around by producing
some side effect.
- can you use some help in assembling the last nuts and bolts?
Yes, that is very appreciated! It would be great if you had a look into
the existing documentation or if you could event help with writing
additional one.
I am really pleased with the direction cocoon-3 took. It would be nice
to have 3.0.0 out early 2009.
I plan to create the release artifacts for alpha-2 by the end of the month.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinh...@apache.org
RE: Unbalanced tags not triggering endTransformingElement in Transformer
Hello again! I think I was wrong, unbalanced tags do not seem to cause it. Here is sample input XML for my transformer: rowset xmlns=http://www.vishay.com/rowspan/1.0; row P1000abc/P1000 P1001def/P1001 T8400 img src=small.jpgimg/img brbr/br a href=javascript:void(0) onClick=foo(42)Enlarge/a /T8400 The elements inside T8400 (img, br, a) do not trigger endTransformingElement() but they do trigger startTransformingElement(). And again: This is only a problem if the input XML is coming from another Cocoon processing step. It is not a problem if the input XML is read from file system (with FileGenerator). This is actually the most confusing part for me. If input comes from a file, they do generate the end events. Any pointers for me? Thanks, Alexander From: Lochschmied, Alexander Sent: Donnerstag, 19. November 2009 14:23 To: 'dev@cocoon.apache.org' Subject: RE: Unbalanced tags not triggering endTransformingElement in Transformer To avoid confusion, please swap the pattern values of my example; OK should be NOT_OK and vice versa. Let me call br/ unbalanced element as opposed to br/br. I'm extending AbstractSAXTransformer and noticed that unbalanced elements do not trigger endTransformingElement(...) if the source (or generator) is cocoon:/something. Example: 1. Unbalanced tags do NOT trigger endTransformingElement(...) map:match pattern=NOT_OK map:generate src=cocoon:/something/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match 2. Unbalanced tags do trigger endTransformingElement(...) map:match pattern=OK map:generate src=same_something_as_above_but_now_as_a_file.xml/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match Can somebody explain what I could possibly be missing or is that a bug in Cocoon? Thanks, Alexander From: Lochschmied, Alexander Sent: Donnerstag, 19. November 2009 13:46 To: dev@cocoon.apache.org Subject: Unbalanced tags not triggering endTransformingElement in Transformer Hello! Let me call br/ unbalanced element as opposed to br/br. I'm extending AbstractSAXTransformer and noticed that unbalanced elements do not trigger endTransformingElement(...) if the source (or generator) is cocoon:/something. Example: 1. Unbalanced tags do NOT trigger endTransformingElement(...) map:match pattern=OK map:generate src=cocoon:/something/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match 2. Unbalanced tags do trigger endTransformingElement(...) map:match pattern= NOT_OK map:generate src=same_something_as_above_but_now_as_a_file.xml/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match Can somebody explain what I'm could possibly be missing or is that a bug in Cocoon? Thanks, Alexander Alexander Lochschmied Web Programmer - Internet and Commerce IT Global Web Services Information Technology Phone:+49 92 8771 2682 Fax +49 92 8771 2545 Website: www.vishay.com http://www.vishay.com/ Vishay Electronic GmbH Geheimrat-Rosenthal-Str. 100 D-95100 Selb Amtsgericht/County Court Hof HRB 2894, Geschäftsführer/Managing Directors: Sieglinde Janker-Buecherl, Arnold Rohr
RE: Unbalanced tags not triggering endTransformingElement in Transformer
It's resolved. My elements didn't have the right namespace. I still don't understand why there is a difference between source being a file VS other processing step though. From: Lochschmied, Alexander Sent: Freitag, 20. November 2009 10:31 To: 'dev@cocoon.apache.org' Subject: RE: Unbalanced tags not triggering endTransformingElement in Transformer Hello again! I think I was wrong, unbalanced tags do not seem to cause it. Here is sample input XML for my transformer: rowset xmlns=http://www.vishay.com/rowspan/1.0; row P1000abc/P1000 P1001def/P1001 T8400 img src=small.jpgimg/img brbr/br a href=javascript:void(0) onClick=foo(42)Enlarge/a /T8400 The elements inside T8400 (img, br, a) do not trigger endTransformingElement() but they do trigger startTransformingElement(). And again: This is only a problem if the input XML is coming from another Cocoon processing step. It is not a problem if the input XML is read from file system (with FileGenerator). This is actually the most confusing part for me. If input comes from a file, they do generate the end events. Any pointers for me? Thanks, Alexander From: Lochschmied, Alexander Sent: Donnerstag, 19. November 2009 14:23 To: 'dev@cocoon.apache.org' Subject: RE: Unbalanced tags not triggering endTransformingElement in Transformer To avoid confusion, please swap the pattern values of my example; OK should be NOT_OK and vice versa. Let me call br/ unbalanced element as opposed to br/br. I'm extending AbstractSAXTransformer and noticed that unbalanced elements do not trigger endTransformingElement(...) if the source (or generator) is cocoon:/something. Example: 1. Unbalanced tags do NOT trigger endTransformingElement(...) map:match pattern=NOT_OK map:generate src=cocoon:/something/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match 2. Unbalanced tags do trigger endTransformingElement(...) map:match pattern=OK map:generate src=same_something_as_above_but_now_as_a_file.xml/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match Can somebody explain what I could possibly be missing or is that a bug in Cocoon? Thanks, Alexander From: Lochschmied, Alexander Sent: Donnerstag, 19. November 2009 13:46 To: dev@cocoon.apache.org Subject: Unbalanced tags not triggering endTransformingElement in Transformer Hello! Let me call br/ unbalanced element as opposed to br/br. I'm extending AbstractSAXTransformer and noticed that unbalanced elements do not trigger endTransformingElement(...) if the source (or generator) is cocoon:/something. Example: 1. Unbalanced tags do NOT trigger endTransformingElement(...) map:match pattern=OK map:generate src=cocoon:/something/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match 2. Unbalanced tags do trigger endTransformingElement(...) map:match pattern= NOT_OK map:generate src=same_something_as_above_but_now_as_a_file.xml/ map:transform type=custom-transformer/ map:serialize type=xml/ /map:match Can somebody explain what I'm could possibly be missing or is that a bug in Cocoon? Thanks, Alexander Alexander Lochschmied Web Programmer - Internet and Commerce IT Global Web Services Information Technology Phone:+49 92 8771 2682 Fax +49 92 8771 2545 Website: www.vishay.com http://www.vishay.com/ Vishay Electronic GmbH Geheimrat-Rosenthal-Str. 100 D-95100 Selb Amtsgericht/County Court Hof HRB 2894, Geschäftsführer/Managing Directors: Sieglinde Janker-Buecherl, Arnold Rohr
Re: Unbalanced tags not triggering endTransformingElement in Transformer
Lochschmied, Alexander wrote: It’s resolved. My elements didn’t have the right namespace. I still don’t understand why there is a difference between source being a file VS other processing step though. Maybe I'm stating the obvious, but from a SAX point of view there's no difference between balanced and unbalanced elements. An element with no children elements nor embedded text is just a startElement() immediately followed by an endElement() for the same tag. Sylvain -- Sylvain Wallez - http://bluxte.net
Re: changes to maven archetypes, alpha1 - alpha2
Being able to type pipeline output is certainly a good idea. I have the existing documentation as an eclipse project and there is litte doubt that I will have a couple of interesting articles to write after my first experience of application writing. OK, shall I make a request to apache.org? Cheers, Jos On Fri, 2009-11-20 at 10:10 +0100, Reinhard Pötz wrote: Jos Snellings wrote: With pleasure. By the way, I am starting to write a prototype for an application with the latest version. Yes, I am willing to take due changes in available classes. Here's a question: - will there be an alpha-3 phase? Yes. Although I consider the code as rather stable, we need more community involvement (your mails are very helpful by the way!) before we are ready to move on. The only technical issue is that I want to rework the pipeline API once again in order to support typed results. Currently a pipeline always writes into an OutputStream and if you need something else (e.g. a SAXBuffer, a business object, etc.) you have to work around by producing some side effect. - can you use some help in assembling the last nuts and bolts? Yes, that is very appreciated! It would be great if you had a look into the existing documentation or if you could event help with writing additional one. I am really pleased with the direction cocoon-3 took. It would be nice to have 3.0.0 out early 2009. I plan to create the release artifacts for alpha-2 by the end of the month.
