OK, 100 xslt params would be too complicated as xslt params.
I have 2 more options though :)
1. Option with pure xml/xsl
How about making properties a raw xml data (with xml serializer, not txt),
e.g.
value1
value2
...
valueN
and in subsequent XSLT use:
and each pa
On Fri, 2014-01-17 at 16:44 +0100, gelo1234 wrote:
> How about a workaround that puts those properties values into XSL
> params and transform with standard XSLTransformer not
> i18nTransformer ?
mmh, it seems quite complicated. The properties file is more than one
hundred lines long. How can I pas
How about a workaround that puts those properties values into XSL params
and transform with standard XSLTransformer not i18nTransformer ?
Where do you need those properties in pipeline ?
Greetings,
Greg
2014/1/17 Alberto Brosich
>
> Yes, it's really simple.
> The source file is an xml file wi
Yes, it's really simple.
The source file is an xml file with a sqltransformer query. The query is
simple: just a select to a specific table (or view) with a where condition.
Then an xsl transformer convert the xml to txt with a pair of key and value for
every row.
That's all.
Can you show here your full original Cocoon pipeline ? Do you store
property files content or property filenames inside db ?
Greetings,
Greg
2014/1/17 Alberto Brosich
>
> Hi,
>
> I'm migrating a 2.1 cocoon application to 3.0, using beta1-SNAPSHOT
> because I need the sql transformer.
> As I wr
Looking deepest in the apidocs I gather that's no way to use a pipeline
as bundle for i18n transformer in cocoon 3.
In fact it uses a ResourceBundle object that needs physical files.
In 2.1 version there is org.apache.cocoon.environment.SourceResolver in
the setup() method. I suppose it is able t
Hi Alberto,
Yes, servlet-service is used if acting as a transformer or a serializer. If
you use generator, there is no need to specify servlet-service.
I used servlet:/ protocol in many generator cases and from within
XIncludeTransformer (x:xinclude) but not as a map:parameter so far.
Greetings,
Hi Greg,
I already took a look to the sample sitemap and I found the following
example:
Second match uses "servlet:" protocol. The "internal-only/simple-xml"
match is used as source of data.
So I suppos
Thank you Javier :)
That is getting even more interesting to me. I mean osgi-compliance of
cocoon :) I will take a look at this port.
Greetings,
Greg
PS:
Do you use (english?) Xavier name too ?
I used to write my nick Gelo in mails, but afaik gelo means "ice" in
portuguese while im rather hot ;)
2014/1/16 gelo1234
> Hi Salu2,
>
> Thanks for clarifying this.
>
> Now I got interested in cocoon-osgi, but it seems like rather old stuff
> (and uses old spring release).
> Any plans to reactivate this subproject ? It would be awesome to see
> cocoon integrated with
> e.g. Karaf with Blueprint c
Hello Alberto,
One more thing is that any map:transform or map:serialize must have:
type="servlet-service" with servlet:/ protocol.
Greetings,
Greg
2014/1/17 gelo1234
> Hello Alberto,
>
> Have you defined
>
>
>
> with:
> ?
>
> Otherwise:
>
>
> value="servlet:/translations_{jexl:cocoon.requ
Hello Alberto,
Have you defined
with:
?
Otherwise:
will not work as expected.
Take a look at C3 samples sitemap.xmap [1] which shows correct definition
of service consumer.
Greetings,
Greg
[1]
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/s
Hi,
I'm migrating a 2.1 cocoon application to 3.0, using beta1-SNAPSHOT
because I need the sql transformer.
As I wrote in the subject, I'm need to specify an internal pipeline as
bundle for the i18n transformer, because the properties file has to be
derived from database. Using a plain file it wo
13 matches
Mail list logo
