On 11.Mar.2003 -- 05:15 PM, Lionel Crine wrote:
>
> >Yes. Shouldn't be too big, though, unless you have enough memory.
> >
> >> 2/In the xsp page, haow can I get attribute from the DOM object in the
> >> session ?
> >> Like that : <xsp-session:get-attribute name="the_object_in_the DOM"/>
> >
> >Retrieve the object and use e.g. jxpath or the dom java api on it.
>
> I'm confused ?
> Here is what I understand :
> 1/ get the DOM from the session with xsp tag ?
> 2/manipulate the DOM with jxpath or DOM api.
Exactly. Check the jxpath logicsheet for example.
> >> 3/If I want the xsp generator to retreive the DOMsessionelement from my
> >> custom transfomer, should I use a resource ?
> >Wait - you want to generate your XSP from a session attribute? Doesn't
> >sound too good to me. Remember that it needs to be compiled everytime
> >it changes.... Apart from that, a source seems to be right.
>
>
> for now I have :
> <map:match pattern="search">
> <map:generate type="customRequest"/> -> create sax events
> <map:transform type="customQuery">
> </map:transform>
> <map:transform type="xslt" src="proto/xsl/documents.xsl"/>
> <map:serialize type="html"/>
> </map:match>
>
> and I want :
>
> 1/ this first pipeline generate a DOM object in a session.
>
>
> <map:match pattern="search">
> <map:generate type="customRequest"/> -> create sax events from
> a form
> first possibility :
> <map:transform type="customQuery"/> -> get the result of the
> request and put it in a DOM into a session
> second possibility :
> <map:transform type="writeDOMsession">
> <map:parameter name="dom-name" value="result"/>
> <map:parameter name="dom-root-element" value="docs"/> docs is
> the root element of the sax event which comes from the first transformer.
> </map:transform>
> <xml:serialize/>
> </map:match>
>
>
> 2/ this second pipeline get the DOM, so I could manipulate the result in
> the xsp page.
> <map:match pattern="xsppage">
> <map:generate type="serverpages" src="anyxsp.xsp"/> -> Get, I
> don't know how the DOM session object
> <map:transform type="xslt" src="demo/documents.xsl"/>
> <map:serialize/>
> </map:match>
>
> Furthermore, I don't know how to link the two pipeline!
You need to put a link on the first pipeline's result that points to
the second and hope that the user requests it (or force it via refresh
/ javascript / whatever).
Perhaps it would be simpler to manipulate the DOM -- to be precise the
resulting XML -- with XSL rather than XSP?
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
