Ok, after reading this, and your previous response, I
can now articulate my problem better.
It seems the XSP allows you to create reusable sections
of code (logicsheets) and to embed Java, the result
is auto-generated code which is an instance of Generator.
I was hoping that XSP could also be used to define a code-generated
instance of Transformer. The way things are now, it seems that
only Generators can be coded up using XSP -- not Transformers.
In other words, I must write my Transformer entirely in Java.
Thanks for your help,
-Chris
Vadim Gritsenko wrote:
>
> > From: Chris Wolf [mailto:[EMAIL PROTECTED]]
> >
> > I looked over most of the examples, including this one,
> > before posting. It's not really what I want to do, that
> > just seems to be using another pipline as an imput source,
>
> But it sounds like what you need: Generate XML -> Use it as XSP source
> -> XSL -> Serialize.
>
> > effectively establishing alias URI's.
>
> Alias??? Alias should result in same result, but this produces *very*
> different result. Please compare:
>
> http://localhost:8080/cocoon/sub/xsp-cocoon
> http://localhost:8080/cocoon/sub/xsp-source
>
> > I was hoping to use embedded java to perform what would
> > otherwise be done with XSLT.
>
> It's called "Transformer" then.
> http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/java/org/apache/cocoon
> /transformation/Transformer.java?rev=1.4&content-type=text/vnd.viewcvs-m
> arkup
>
> Implement, declare in the sitemap, use.
>
> > I will look into "xinclude" it it will work for
> > a dynamic datasource.
>
> It does work.
>
> Vadim
>
> > Thanks,
> >
> > -Chris
> >
> >
> > Vadim Gritsenko wrote:
> > >
> > > One line for you:
> > >
> > > http://localhost:8080/cocoon/sub/xsp-cocoon
> > >
> > > Other samples might be useful too.
> > >
> > > PS Why not use xsp, then xinclude your xml and xslt as necessary?
> > >
> > > Vadim
> > >
> > > --
> > > Resistance is futile.
> > >
> > > > From: Chris Wolf [mailto:[EMAIL PROTECTED]]
> > > >
> > > >
> > > > I am working on a project where we have a datasource
> > > > which produces XML based on certain parameters. I would
> > > > like to use this as input to an XSP page which defines
> > > > overall content structure (semantics) then, finally,
> > > > apply a stylsheet appropriate for the invoking client.
> > > >
> > > >
> > > > Problem: It seems that a pipeline must start
> > > > with one, and only one Generator. The problem is
> > > > that if I create an implementation of Generator
> > > > which produces the XML, then I cannot use XSP
> > > > (since the XSP code handler is itself a Generator).
> > > >
> > > > I then tried to implement the XML generator from an
> > > > XSP page by invoking a method using xsp:expr, but then
> > > > the whole document is treated as a single string.
> > > >
> > > > What I would like to do is some thig like:
> > > >
> > > > Ideas anyone?
> > > >
> > > > +---------------+
> > > > | XML Generator |
> > > > +------+--------+
> > > > |
> > > > v
> > > > +---------------+
> > > > | XSP structure |
> > > > +------+--------+
> > > > |
> > > > +------v-----------+
> > > > | XSL presentation |
> > > > +------+-----------+
> > > > |
> > > > +------v--------+
> > > > | Serializer |
> > > > +---------------+
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
