I thought about your options.
Solution 1 seems to have the same problem as i18n transformer: use a
pipeline as parameter for transformers. In this case is a parameter of
the xsl transformer.
Solution 2 in my case is not useful because i18n data is added in more
than one place in the pipeline.
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
Hello Alberto,
Have you defined
map:match pattern=translations_*.properties
with:
map:generate type=service-consumer/ ?
Otherwise:
map:parameter name=bundle
value=servlet:/translations_{jexl:cocoon.request.lang}.properties /
will not work as expected.
Take a look at C3 samples sitemap.xmap
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 gelo1...@gmail.com
Hello Alberto,
Have you defined
map:match pattern=translations_*.properties
with:
map:generate
Hi Greg,
I already took a look to the sample sitemap and I found the following
example:
map:match pattern=internal-only/simple-xml
map:generate src=sax-pipeline/simple.xml /
map:transform src=sax-pipeline/simple.xslt
map:parameter name=myParam
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.
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
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 abros...@ogs.trieste.it
Hi,
I'm migrating a 2.1 cocoon application to 3.0, using beta1-SNAPSHOT
because I need the sql
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.
map:pipeline
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 abros...@ogs.trieste.it
Yes, it's really simple.
The source
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 pass
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.
properties
key1value1/key1
key2value2/key2
...
keyNvalueN/keyN
12 matches
Mail list logo
