hi everybody,
I'm a little disapointed by all theses xml languages we can found around
which nearly all do the same things.
1) Last time i wanted to construct a project with maven and i found jelly.
it had a rich tag library, handle jexl expressions, and can handle xpath
through tag's libraries.
> This has also been discussed in detail:
> http://marc.theaimsgroup.com/?t=10493079564&r=4&w=2
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104998241710064&w=2
> http://marc.theaimsgroup.com/?t=10501653644&r=1&w=2
> http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=1051784364292
> I'm working on refactoring JXTG so that it will be easier to support and
> develop. I'm aware about that you have access the request object etc
Great ! Don't know if i can help (time), but if you have a road map or
something like that, i would be happy to contribute.
> differently depending on
hi,
What about giving access to the servicemanager inside jxtg. We could add,
that way, various macros to access components directly (authentication,
sourceresolver, session, ...).
regards
Daniel Fagerstrom wrote:
> During the "JXTG 2.0 (just say no!)" (you find links to it in
> http://wiki.apache.org/cocoon/Templates), many people where negative to
> the idea of developing JXTG in a "taglib" direction. We decided that
> JXTG should focus on templating and that more programatic stuf
Leszek Gawron wrote:
> BURGHARD Éric wrote:
>> hi,
>>
>> What about giving access to the servicemanager inside jxtg. We could add,
>> that way, various macros to access components directly (authentication,
>> sourceresolver, session, ...).
>>
>> reg
Daniel Fagerstrom wrote:
>> It's strange, because I think that sylvain, with his cforms jx macros
>> shows how usefull could be a taglib for templating purpose.
>
> We are certainly going to keep macros. The question was rather if we
> should have some mechanisms so that it would be easy to add o
Daniel Fagerstrom wrote:
>
> ...
>
> But it wasn't clear to me what the use case does.
>
>> I also had several
>> cases where I wanted the numbering to be consistent across several
>> forEach calls and also had to implement hacks.
>
Couldn't say better :-). That's a good abstract of what this
Daniel Fagerstrom wrote:
> You should care:
> http://marc.theaimsgroup.com/?t=11021071981&r=2&w=2, at least if you
> want to avoid extensive flaming ;)
>
Thanks for the warning. But i don't see any differences :-( Do you ?
Sylvain's macro had namespace too (mazzocchi 2nd condition).
targetNam
Glen Ezkovich wrote:
> I think the important thing to remember is that JXTG should be used for
> injecting data. Regardless of whether it is called directly through the
> sitemap or through flow it should allow access in a consistent way to
> session, request and other objects that are necessary t
Stefano Mazzocchi a écrit
>
> The problem is to separate concerns. We aim to have a template language
> that we can give to graphic designers and therefore they will be given
> the page and the variables that contain the dynamic data they need to
> present. No other information is required for th
Stefano Mazzocchi wrote:
> BURGHARD Éric wrote:
>
>> WAIMS (where am i missing something ? :-)
>
> XSP was designed to achieve exactly what you are describing. Sure it has
> some limitations and the use of xslt to generate java code is not
> exactly appealing, but
Daniel Fagerstrom wrote:
> Instruction Access
> ==
>
> What objects should instructions and macros be able to access? Curently
> for the needs of the JXTG instructions, the instructions has access to a
> ExpressionContext that contains the FOM "view" that is available in
> express
Daniel Fagerstrom wrote:
>>Ok. So what about turning on the ability to pass dom inside sitemap
>>parameters ?
>>
>>1) pipeline more clear
>>
>>
>>
>>
>>
>>
> I don't get why you are so obsessed with being able to do everything
> from the sitemap. Once, when the community started to develop Coc
Daniel Fagerstrom wrote:
> I have never disputed that things might be clumsy now, I just think we
> should focus on getting the flowscript way better, instead of adding
> things that makes the sitemap more of a programming language, by
So how could you propose to add some kind of flow action (con
Reinhard Poetz wrote:
> Two days ago, I wrote about my usecase for chained input modules. Daniel
> answered, that in his opinion this looks like voodoo and suggested to have
> a global action that is executed for every request. Wouldn't this be the
> solution for passing objects to the view layer
Stefano Mazzocchi wrote:
>
> My girlfriend tells me that sometimes it seems like I argue for the sake
> of arguing.., that I would take the other side no matter what... and
> that in a single conversation I might argue about why something is black
> and then argue about the same thing is white on
Hi,
Is it possible to trigger the validate process just after a binding without
submitting ? Let me explain.
We have a huge model with many validation rules. It's used by authentified
users to edit/change their own data. Because it's huge we need to save the
submitted data even if they are not va
just for information,
i've achieved some template migration from jxtg (2.2-dev) to
xslt 2.0 (saxon8) and record a 7 to 10 factor speed increase on the same
pages (cache desactivated).
the templates (jx+jpath) were transformed (for the biggest part) by a simple
xslt 2.0 stylesheet. Common construc
>
> An important point: which JXTG are you using? The original one, or the
> new implementation in trunk?
It's a quite old now 2.2-dev, so i think this is not the refactored one. I
will try to update to current trunk, and retest.
We use macros and sometime evalBody (i've already heard about macr
Daniel Fagerstrom wrote:
> If you want to help making JXTG faster you need to submit more
> information. We need examples that reproduce this behaviour with the
> JXTG template and the corresponding XSLT. We also need to know exactly
> what version of 2.2 you used. How did you measure preformance?
Hi,
It is said in the docs that we can use viewData in event handler to access
the data pass through showForm. I saw some messages that said it was
broken. Apparently it doesn't work here. If it's a removed feature what's
the current way of doing this ?
regards
>
> Uh? It's not removed. What do you mean by "doesn't work here"? Any error
> message?
>
Excuse me for the fuzzyness of the previous message.
I'm using Forms.js v3 and cocoon-2.2-dev (not the latest trunk). The error
message is "viewData is not defined".
Apparently the cocoon.flow.context is
Hi,
By looking at the XMLSerializer source code, i just realized that the
serialization was driven in fact by an xsl transformation (with no
stylesheet). So i wondered, why not giving this serialization a real
stylesheet ? That way i could overcome all the limitations of the actual
XMLSerializer.
>
> - handle the processing instruction by serializing
> straight XML for those browsers that do support it, and process on the
> server for others.
>
great idea !
>>By extension, why not having an XSLGenerator and an XSLReader ?
>>
>>
>
> Hmm... you're starting to build pipelines-in-one-com
Thorsten Scherler wrote:
> On Tue, 2005-08-02 at 11:25 +0200, Antonio Fiol Bonnín wrote:
>> Hello,
>>
>> I am finding a problem with empty elements when serving content with
>> the text/html content type on Firefox.
>
>> For example, collapsed empty div elements cause havoc in firefox. A
>> poss
> What XMLSerializer are you talking about? The one in the serializers
> block or the default one?
>
org.systheo.cocoon.serialization.XMLSerializer
>> I wrote a much more powerfull solution: the XSLSerializer, which let you
>> control the serialization through an xsl stylesheet (an so use the
>>
Kees Broenink wrote:
> Éric,
>
> I tried your solution described below but it does not solve the
> problem...
>
>
>
> will return:
>
>
BURGHARD Éric wrote:
>> What XMLSerializer are you talking about? The one in the serializers
>> block or the default one?
>>
>
umh, i went to quickly :-), this is
org.apache.cocoon.serialization.XMLSerializer
> 1. I was talking about the concept, not implementation details. And from
> that POV a stylesheet should not influence the pipeline. IMO It's plain
> wrong to set the output format in the stylesheet.
>
> 2. But yes, I was missing the most important point in your approach
> thinking that any styles
>
> I agree with Joerg here; by providing the author with the ability to use
> any .xsl for serialization, you're allowing the serializer to control
> not only how the model is serialized, but to modify the model itself
> (which is the role of transformers). This essentially removes the
> distinc
>> I don't understand here. How could i modify a model with an xsl
>> transformation (and by extension an xsl serialization) ? XSL is for
>> generating views from a sax representation of a model (not to be confused
>> with the model itself. It's generated at the beginning of the pipeline by
>> the
>
> Of course serializers do transformations, you already wrote it: from SAX
> to bytes. But there is one important difference: The behaviour of a
> serializer (and at the end the output) is absolutely predictable. If you
> feed the same SAX events into a specific serializer you will always get
>
>
> You know what I meant: A serializer just changes the representation of
> the data but does not change the data itself - while this is of course
> not true for the transformers. When you setup your pipeline it is a
> 1:1-relation of SAX input to byte output and does not depend on anything
> els
> I was not wondering, I saw your request exaclty as a "virtual
> serializers" usecase. This is something we want to address for cocoon 2.2.
>
Ok ;-). So 'Is this a virtual component ?' was not a question (i'm joking).
Thanks for (re)joining this discussion.
> I believe, I understand your point:
> 2 points:
>
> 1-Nobody is telling you cannot use your own serializers.
> 2- I agree the current standard serializer has bugs. I tried to fix
> them. I met problems into xalan internals and well, it is a very
> long story. Few weeks ago, I spent most part of 15 nights trying to fix
> that (w
> Why not collapse the entire pipeline into a single component as well, that
> would eliminate a massive amount of bugs and testing time of the Sitemap
> ;o)
>
It's a brillant idea, but it's yours :-D
> Componentization with semantically well-defined contracts in between, is a
> far better than l
Niclas Hedhman wrote:
> On Monday 08 August 2005 01:22, BURGHARD Éric wrote:
>
>> standard serializers are bugged.
>
> If we have bugs in the serializers, then let's address it.
> If we need more "types" of serializers, then we address that.
>
Read my ans
> From Vadim and Eric: Many (most?) serializers are not reversible and
> therefore there should be no prohibition on yet another seemingly useful
> serializer based upon XSLT and its output element.
>
In fact, if i try to summarize this thread, we are just talking about
implementation language.
Hi,
I don't want to just start another thread on this already prolific subject
(was: Suggestion for XHTMLSerializer). Many interesting POV were explained,
and i think that the final idea is that the TraxSerializer simply allow you
to write your serializer in XSL (java seems to be the only possibil
Berin Loritsch wrote:
> It seems that a huge hole in documentation exists on the site. As I was
> training one of my crew on how to write a reader (adapting a servlet we
> had) I found I couldn't refer to one nice page. Not even the JavaDocs
> really help all that much. I didn't even know about
Hi,
Don't know if you heard about Trac (http://trac.edgewall.com/trac) but it's
IMHO the best tool for bug tracking/project management. Specially if you
use subversion repositories.
Trac is a mix of a Wiki + WebSVN + Bugzilla. It's written in python.
It's bright and lightweight:
- entirely base
BURGHARD Éric wrote:
> Hi,
>
> Don't know if you heard about Trac (http://trac.edgewall.com/trac) but
> it's IMHO the best tool for bug tracking/project management. Specially if
> you use subversion repositories.
>
oops. sorry for this url. this
Hi,
I tryed jira when i was looking for a bug-tracking system for my project,
and finally prefered bugzilla for its simplicity (well my project is not as
big as cocoon), even if i found it quite ugly compared to jira.
Then i found Trac[1], i think it could be valuable for cocoon if you look
for a
Hi,
Since i'm using xsl2 for all my forms, i'm looking for a way to enable ajax
in FormsGenerator. After quickly looking through sources, i found that this
feature seems to be planned in the FormsGenerator (FIXME comments).
At first glance, i thought that this would be just a matter of copy and
p
Hi,
I found that the loc namespace and several attributes are inserted during
the binding phase (inser-node). Theses informations are apparently usefull
for cocoon stack traces, but IMHO they should disapear during form.save().
I'm not sure. Is this a bug or feature ?
Regards
Sylvain Wallez wrote:
> BURGHARD Éric wrote:
>
>>Hi,
>>
>>I found that the loc namespace and several attributes are inserted during
>>the binding phase (inser-node). Theses informations are apparently usefull
>>for cocoon stack traces, but IMHO they should di
Sylvain Wallez wrote:
>>Since i'm using xsl2 for all my forms, i'm looking for a way to enable
>>ajax in FormsGenerator.
>>
>
> Interesting. Can you explain how you use XSLT 2 and the FormGenerator?
>
Of course. For now it's not exactly compatible with the template language.
The main difference
Bertrand Delacretaz wrote:
> Le 20 sept. 05, à 10:57, Carsten Ziegeler a écrit :
>> ...The LinkService accepts a boolean argument indicating if you want a
>> secure link. If this is set to true then the service switches to https.
>> As I said yesterday, we could create relative links if the procot
Bertrand Delacretaz wrote:
> Le 21 sept. 05, à 14:04, BURGHARD Éric a écrit :
>> If i understand correctly, the request.getServerName() is not
>> useable for
>> absolutisation since it names the server in his local environnement..
>
> Did you follow Vadim'
Grzegorz Tañczyk wrote:
> Hello Andreas,
>
> If You are using Tomcat then try to set up timeouts(connection,
> read, upload and others if there are any) in server.xml.
>
I've experienced the same kind of bugs which only seems to occur with a
httpd + tomcat configuration.
I've switch from m
Hi,
Thanks to you (i'm just a follower :-), i switch my building scripts from
jelly+ant to a better maven 2 build cycle model. maven was on my todo list
since a long time, and i must admit that it has overcome my expectations.
To help the jelly migration i wrote an archetype for writing quickly g
Jorg Heymans wrote:
>
> BURGHARD Éric wrote:
>>
>> Perhaps it could be usefull for you, so you can find the sources on a svn
>> repository (the server is not always online: no-ip rulez :-)
>>
>
> I'll have a look at this, thanks!
>
I've just
Hi,
I've just commited a set of tools [1] for maven (plugin, extensions and
archetype) that should ease your migration from ant to maven.
A lot of people here should know groovy, but let me explains (i discover
this language one week ago).
It's all about writing plugins for maven with the groovy
Daniel Fagerstrom wrote:
>
> What do you think about moving block dependecy handling from block.xml
> to pom.xml? It means reduced flexibilty as block dependencies becomes
> direct instead of indirect as in the current schema. OTH it reduce
> complexity and fullfills our current use cases. If we
Bertrand Delacretaz wrote:
> I think we must keep the existing bricks-cms as is as an example of
> ant-based builds for 2.1.x, and create a separate Mavenized version -
> it will be clearer than mixing up both things, and the
> application-specific code is very small anyway, so duplication won't b
>
> It's not *one* jar, an important feature of the bricks-cms build is
> picking up required blocks, and compiling only those. Later, the build
> applies the required *.x* patch files to the Cocoon configs, as is
> currently required in 2.1.x. An alternate build must handle all of
> this, in addi
>>
>> IMHO it's not worth writing much stuff for mavenizing 2.1.x, this is
>> coming in 2.2, very close to being ready IIUC.
>>
It has already worked when ant and maven coexisted. Now it's in a kind of
stale state (priority is on the core, and blocks are no more constructed).
My app work with 2.2
Hi,
I'm using eXist XQueryGenerator in a simple pipeline. It works correctly
when i call it directly from my browser with correct parameters.
Now this pipeline is called from
o.a.c.w.a.c.PipelineAuthenticator.authenticate(PipelineAuthenticator.java:145)
during a flow flogin and i've got an except
BURGHARD Éric wrote:
> Hi,
>
> I'm using eXist XQueryGenerator in a simple pipeline. It works correctly
> when i call it directly from my browser with correct parameters.
>
> Now this pipeline is called from
>
o.a.c.w.a.c.PipelineAuthenticator.authenticate(Pipe
Hi !
I'm writing a new source module.
I set-up some new pipelines with this module in the generator and everything
is working correctly, ... well not exactly
When i try to cinclude the xml from these pipelines in another pipeline i
get an exception (unable to find the xml serializer component fr
Luigi Bai wrote:
> You need to make sure there is a serializer with the name "xml" declared
> in your sitemap.xmap file (or a parent sitemap) before you use your source
> module.
>
thanks for your answer,
the xml serializer is effectively declared in my main sitemap ;-(. It's not
the default one
Hi,
I just discover a really usefull plugin [1] for m2 that allow you to
- update dependencies to the latest versions available
- lookup conflicts (same packages but differents versions) and handle
exclusions
- edit pom from the console
I also try to graph the depencies [2] of my project (which i
Hi again,
I just finished a css engine which we use in our project which can help you
to virtualize all your css in a pipeline, and handle browser specificities
in a clean way (no more css syntax hacking). Perhaps it could be valuable
for others.
Here is the description:
- it's xml syntax
- it ha
Hi everybody,
I just wonder if it's planned to be able to pass dom parameters in a
TraxTransformation ?
We use qui often here, cinclude | xinclude enclosed in a tag
to drive our xsl transformations with non flat datas. (eg association
lists). We could use document() inside xslt, but the changing
65 matches
Mail list logo
