Re: Look-and-feel approach with views

[Alexander Smirnoff]

That exactly what I mean on functional level, but unfortunately, this kind
connection in Cocoon causes an exception:

Original exception : java.lang.RuntimeException: Problem in
getTransformer:Error in creating Transform Handler
 at
org.apache.cocoon.transformation.TraxTransformer.setConsumer(TraxTransformer
.java:279)
 at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.connectPipeline(
AbstractEventPipeline.java:216)
 at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.process(Abstract
EventPipeline.java:106)
 at
org.apache.cocoon.components.pipeline.AbstractStreamPipeline.process(Abstrac
tStreamPipeline.java:140)
 at
org.apache.cocoon.www.file_.C_.java.tomcat.webapps.gwvas.WEB_INF.conf.sitema
p_xmap.wildcardMatchN400063(sitemap_xmap.java:752)
 at
org.apache.cocoon.www.file_.C_.java.tomcat.webapps.gwvas.WEB_INF.conf.sitema
p_xmap.process(sitemap_xmap.java:568)
 at
org.apache.cocoon.www.file_.C_.java.tomcat.webapps.gwvas.WEB_INF.conf.sitema
p_xmap.process(sitemap_xmap.java:521)


> I suggest that there is an easier approach to solve your look&feel issue.
>
> Assuming that the L&F is supported by means of some transformation, then
why
> not use the following sitemap construct:
>
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
>
> That way, look and feel is handled in a single location and there is no
need
> to extend the sitemap language.
>
> Hope this helps,
> Adrian
> (I haven't tested the above, but I want to illustrate the idea)
>
> - Original Message -
> From: Alexander Smirnoff <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, November 26, 2001 11:20 PM
> Subject: Re: Look-and-feel approach with views
>
>
> > OK. Then how could I implement dynamically "look-and-feel" based on user
> > credentials (customer-id, user_id) ? I see only one possible way:
> inserting
> > action for each XSL transformation in each pipeline... That approach
makes
> > sitemap look even more ugly...
> >
> > Comments are follows,
> > Alex.
> > ----- Original Message -
> > From: "giacomo" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, November 26, 2001 5:50 PM
> > Subject: Re: Look-and-feel approach with views
> >
> >
> > > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> > >
> > > > OK. I've got it.
> > > >
> > > > Well, is it possible to trigger the view from inside sitemap? What
> about
> > > > Passing parameters?
> > > >
> > > > I think the idea of breaking pipeline and continuing it from another
> > > > "resource"-like pipeline ("view") from labeled predefined point is
> very
> > > > powerful. Imagine having the same long chain of transformations
> through
> > > > group or even all of pipelines in the sitemap! From my point of view
> it
> > > > makes sitemap more unreadable. From the other side, if you have some
> > > > "resource"-like view which could be processed from any pipeline and
> > being
> > > > "returned" to the point of entry will make readability of sitemap
more
> > > > easy...
> > > >
> > > > Something like that:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > This is just a random thought. Sorry for being naive if this is the
> > > > case...Probably there are some workaround which I don't know, - I'll
> be
> > glad
> > > > to comprehend.
> > >
> > > I can't see what your approach is good for. Views aren't made for
> > > skinning. They are for producing view in the sense of schema, meta
data,
> > > links etc. but not for green or red. If you like to use it that way,
> yes,
> > > your sitemap might look ugly then.
> >
> > So what would be more elegant approach ? Use actions in each
> transformation
> > point in sitemap?
> >
> > >
> > > Your proposed enhancement is only giving another programmers view
> > > into the sitemap which isn't what we initially wanted and is what
> > > we like to get fixed in the future.
> >
> > The only propos

Re: Look-and-feel approach with views

[Alexander Smirnoff]

Thanks Cris for suggestion.

> On 26.Nov.2001 -- 06:20 PM, Alexander Smirnoff wrote:
> > OK. Then how could I implement dynamically "look-and-feel" based on user
> > credentials (customer-id, user_id) ? I see only one possible way:
inserting
> > action for each XSL transformation in each pipeline... That approach
makes
> > sitemap look even more ugly...
>
> It depends a bit on how complex the differences for each user are. You
> might get away with
>
>  

With this kind of redirection is throwing an exception while connecting
Piplines (Cocoon 2.1 cvs HEAD branch):

Original exception : java.lang.RuntimeException: Problem in
getTransformer:Error in creating Transform Handler
 at
org.apache.cocoon.transformation.TraxTransformer.setConsumer(TraxTransformer
.java:279)
 at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.connectPipeline(
AbstractEventPipeline.java:216)
 at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.process(Abstract
EventPipeline.java:106)
 at
org.apache.cocoon.components.pipeline.AbstractStreamPipeline.process(Abstrac
tStreamPipeline.java:140)
 at
org.apache.cocoon.www.file_.C_.java.tomcat.webapps.gwvas.WEB_INF.conf.sitema
p_xmap.wildcardMatchN400065(sitemap_xmap.java:782)

This type of exception gave me a wrongful impression that you cannot "break"
the pipeline and "connect" with another one from the "transformation point".
I don't know, the lack of clear rules in documentation cause me huge headake
while debugging such stuff.

But apparently redirect-to IS working ! So I guess this will be the right
answer. Thanks, Cris.

>
> in every subpipeline. Or, if there are many subpipelines, you could
> create a resource that does the styling (and serializing) and
>
>  
>
> or, for more complex stylings even
>
>  
>
> in every pipeline where it's applicable.
>
> In addition, you could use selectors to chose between different
> look+feels based on some user parameter.
>
> HTH.
>
> 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
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
>
> 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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: Look-and-feel approach with views

[Adrian Geissel]

I suggest that there is an easier approach to solve your look&feel issue.

Assuming that the L&F is supported by means of some transformation, then why
not use the following sitemap construct:














That way, look and feel is handled in a single location and there is no need
to extend the sitemap language.

Hope this helps,
Adrian
(I haven't tested the above, but I want to illustrate the idea)

- Original Message -
From: Alexander Smirnoff <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 11:20 PM
Subject: Re: Look-and-feel approach with views


> OK. Then how could I implement dynamically "look-and-feel" based on user
> credentials (customer-id, user_id) ? I see only one possible way:
inserting
> action for each XSL transformation in each pipeline... That approach makes
> sitemap look even more ugly...
>
> Comments are follows,
> Alex.
> - Original Message -
> From: "giacomo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, November 26, 2001 5:50 PM
> Subject: Re: Look-and-feel approach with views
>
>
> > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> >
> > > OK. I've got it.
> > >
> > > Well, is it possible to trigger the view from inside sitemap? What
about
> > > Passing parameters?
> > >
> > > I think the idea of breaking pipeline and continuing it from another
> > > "resource"-like pipeline ("view") from labeled predefined point is
very
> > > powerful. Imagine having the same long chain of transformations
through
> > > group or even all of pipelines in the sitemap! From my point of view
it
> > > makes sitemap more unreadable. From the other side, if you have some
> > > "resource"-like view which could be processed from any pipeline and
> being
> > > "returned" to the point of entry will make readability of sitemap more
> > > easy...
> > >
> > > Something like that:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > This is just a random thought. Sorry for being naive if this is the
> > > case...Probably there are some workaround which I don't know, - I'll
be
> glad
> > > to comprehend.
> >
> > I can't see what your approach is good for. Views aren't made for
> > skinning. They are for producing view in the sense of schema, meta data,
> > links etc. but not for green or red. If you like to use it that way,
yes,
> > your sitemap might look ugly then.
>
> So what would be more elegant approach ? Use actions in each
transformation
> point in sitemap?
>
> >
> > Your proposed enhancement is only giving another programmers view
> > into the sitemap which isn't what we initially wanted and is what
> > we like to get fixed in the future.
>
> The only proposition I made is to manipulate sitemap in orthogonal fashion
> like views do. Why not?
> I do understand...
>
> What are the tradeoffs?
>
> >
> > Giacomo
> >
> > >
> > > Thanks,
> > > Alex.
> > >
> > >
> > > - Original Message -
> > > From: "giacomo" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Monday, November 26, 2001 2:46 PM
> > > Subject: Re: Look-and-feel approach with views
> > >
> > >
> > > > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> > > >
> > > > > I'm using 2.0rc1, but even if I put label="xsltran" into
> 
> > > > > declaration this doesnt work either...
> > > > >
> > > > > I feel that I misundersatnd the concept. It seems, for example, in
> > > webapp
> > > > > sitemap.xconf (in HEAD branch) the view declaration like:
> > > > >
> > > > > 
> > > > >
> > > > > 
> > > > >
> > > > > never executes... Otherwise it supposed to be executed for every
> pipline
> > > > > after last component in pipline... So I'm really confused...
> > > >
> > > > If you don't request that view it will never be executed :) use a
> > > >
> > > > http://localhost:8080

Re: Look-and-feel approach with views

[Christian Haul]

On 26.Nov.2001 -- 06:20 PM, Alexander Smirnoff wrote:
> OK. Then how could I implement dynamically "look-and-feel" based on user
> credentials (customer-id, user_id) ? I see only one possible way: inserting
> action for each XSL transformation in each pipeline... That approach makes
> sitemap look even more ugly...

It depends a bit on how complex the differences for each user are. You
might get away with 

 

in every subpipeline. Or, if there are many subpipelines, you could
create a resource that does the styling (and serializing) and

 

or, for more complex stylings even

 

in every pipeline where it's applicable.

In addition, you could use selectors to chose between different
look+feels based on some user parameter.

HTH.

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

-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: Look-and-feel approach with views

[giacomo]

On Mon, 26 Nov 2001, Alexander Smirnoff wrote:

> OK. Then how could I implement dynamically "look-and-feel" based on user
> credentials (customer-id, user_id) ? I see only one possible way: inserting
> action for each XSL transformation in each pipeline... That approach makes
> sitemap look even more ugly...

I don't get what you want to achieve. Can you give a sample?

Giacomo

>
> Comments are follows,
> Alex.
> - Original Message -
> From: "giacomo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, November 26, 2001 5:50 PM
> Subject: Re: Look-and-feel approach with views
>
>
> > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> >
> > > OK. I've got it.
> > >
> > > Well, is it possible to trigger the view from inside sitemap? What about
> > > Passing parameters?
> > >
> > > I think the idea of breaking pipeline and continuing it from another
> > > "resource"-like pipeline ("view") from labeled predefined point is very
> > > powerful. Imagine having the same long chain of transformations through
> > > group or even all of pipelines in the sitemap! From my point of view it
> > > makes sitemap more unreadable. From the other side, if you have some
> > > "resource"-like view which could be processed from any pipeline and
> being
> > > "returned" to the point of entry will make readability of sitemap more
> > > easy...
> > >
> > > Something like that:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > This is just a random thought. Sorry for being naive if this is the
> > > case...Probably there are some workaround which I don't know, - I'll be
> glad
> > > to comprehend.
> >
> > I can't see what your approach is good for. Views aren't made for
> > skinning. They are for producing view in the sense of schema, meta data,
> > links etc. but not for green or red. If you like to use it that way, yes,
> > your sitemap might look ugly then.
>
> So what would be more elegant approach ? Use actions in each transformation
> point in sitemap?
>
> >
> > Your proposed enhancement is only giving another programmers view
> > into the sitemap which isn't what we initially wanted and is what
> > we like to get fixed in the future.
>
> The only proposition I made is to manipulate sitemap in orthogonal fashion
> like views do. Why not?
> I do understand...
>
> What are the tradeoffs?
>
> >
> > Giacomo
> >
> > >
> > > Thanks,
> > > Alex.
> > >
> > >
> > > - Original Message -
> > > From: "giacomo" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Monday, November 26, 2001 2:46 PM
> > > Subject: Re: Look-and-feel approach with views
> > >
> > >
> > > > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> > > >
> > > > > I'm using 2.0rc1, but even if I put label="xsltran" into
> 
> > > > > declaration this doesnt work either...
> > > > >
> > > > > I feel that I misundersatnd the concept. It seems, for example, in
> > > webapp
> > > > > sitemap.xconf (in HEAD branch) the view declaration like:
> > > > >
> > > > > 
> > > > >
> > > > > 
> > > > >
> > > > > never executes... Otherwise it supposed to be executed for every
> pipline
> > > > > after last component in pipline... So I'm really confused...
> > > >
> > > > If you don't request that view it will never be executed :) use a
> > > >
> > > > http://localhost:8080/cocoon/welcome?cocoon-view=links
> > > >
> > > > and you'll get all the links in the welcome page as response.
> > > >
> > > > Giacomo
> > > >
> > > > >
> > > > > Thanks,
> > > > > Alex.
> > > > >
> > > > > > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> > > > > >
> > > > > > > Hi everyone,
> >

Re: Look-and-feel approach with views

[Alexander Smirnoff]

OK. Then how could I implement dynamically "look-and-feel" based on user
credentials (customer-id, user_id) ? I see only one possible way: inserting
action for each XSL transformation in each pipeline... That approach makes
sitemap look even more ugly...

Comments are follows,
Alex.
- Original Message -
From: "giacomo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 5:50 PM
Subject: Re: Look-and-feel approach with views


> On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
>
> > OK. I've got it.
> >
> > Well, is it possible to trigger the view from inside sitemap? What about
> > Passing parameters?
> >
> > I think the idea of breaking pipeline and continuing it from another
> > "resource"-like pipeline ("view") from labeled predefined point is very
> > powerful. Imagine having the same long chain of transformations through
> > group or even all of pipelines in the sitemap! From my point of view it
> > makes sitemap more unreadable. From the other side, if you have some
> > "resource"-like view which could be processed from any pipeline and
being
> > "returned" to the point of entry will make readability of sitemap more
> > easy...
> >
> > Something like that:
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > This is just a random thought. Sorry for being naive if this is the
> > case...Probably there are some workaround which I don't know, - I'll be
glad
> > to comprehend.
>
> I can't see what your approach is good for. Views aren't made for
> skinning. They are for producing view in the sense of schema, meta data,
> links etc. but not for green or red. If you like to use it that way, yes,
> your sitemap might look ugly then.

So what would be more elegant approach ? Use actions in each transformation
point in sitemap?

>
> Your proposed enhancement is only giving another programmers view
> into the sitemap which isn't what we initially wanted and is what
> we like to get fixed in the future.

The only proposition I made is to manipulate sitemap in orthogonal fashion
like views do. Why not?
I do understand...

What are the tradeoffs?

>
> Giacomo
>
> >
> > Thanks,
> > Alex.
> >
> >
> > - Original Message -
> > From: "giacomo" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, November 26, 2001 2:46 PM
> > Subject: Re: Look-and-feel approach with views
> >
> >
> > > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> > >
> > > > I'm using 2.0rc1, but even if I put label="xsltran" into

> > > > declaration this doesnt work either...
> > > >
> > > > I feel that I misundersatnd the concept. It seems, for example, in
> > webapp
> > > > sitemap.xconf (in HEAD branch) the view declaration like:
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > > never executes... Otherwise it supposed to be executed for every
pipline
> > > > after last component in pipline... So I'm really confused...
> > >
> > > If you don't request that view it will never be executed :) use a
> > >
> > > http://localhost:8080/cocoon/welcome?cocoon-view=links
> > >
> > > and you'll get all the links in the welcome page as response.
> > >
> > > Giacomo
> > >
> > > >
> > > > Thanks,
> > > > Alex.
> > > >
> > > > > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > I'm trying to use Views for setting look and feel based on
specific
> > user
> > > > > > logged on the web site. So far I cannot even make very basic
view
> > > > working:
> > > > > >
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >   ...
> > > > > >   
> > > >

Re: Look-and-feel approach with views

[giacomo]

On Mon, 26 Nov 2001, Alexander Smirnoff wrote:

> OK. I've got it.
>
> Well, is it possible to trigger the view from inside sitemap? What about
> Passing parameters?
>
> I think the idea of breaking pipeline and continuing it from another
> "resource"-like pipeline ("view") from labeled predefined point is very
> powerful. Imagine having the same long chain of transformations through
> group or even all of pipelines in the sitemap! From my point of view it
> makes sitemap more unreadable. From the other side, if you have some
> "resource"-like view which could be processed from any pipeline and being
> "returned" to the point of entry will make readability of sitemap more
> easy...
>
> Something like that:
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
> 
>
> This is just a random thought. Sorry for being naive if this is the
> case...Probably there are some workaround which I don't know, - I'll be glad
> to comprehend.

I can't see what your approach is good for. Views aren't made for
skinning. They are for producing view in the sense of schema, meta data,
links etc. but not for green or red. If you like to use it that way, yes,
your sitemap might look ugly then.

Your proposed enhancement is only giving another programmers view
into the sitemap which isn't what we initially wanted and is what
we like to get fixed in the future.

Giacomo

>
> Thanks,
> Alex.
>
>
> - Original Message -
> From: "giacomo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, November 26, 2001 2:46 PM
> Subject: Re: Look-and-feel approach with views
>
>
> > On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
> >
> > > I'm using 2.0rc1, but even if I put label="xsltran" into 
> > > declaration this doesnt work either...
> > >
> > > I feel that I misundersatnd the concept. It seems, for example, in
> webapp
> > > sitemap.xconf (in HEAD branch) the view declaration like:
> > >
> > > 
> > >
> > > 
> > >
> > > never executes... Otherwise it supposed to be executed for every pipline
> > > after last component in pipline... So I'm really confused...
> >
> > If you don't request that view it will never be executed :) use a
> >
> > http://localhost:8080/cocoon/welcome?cocoon-view=links
> >
> > and you'll get all the links in the welcome page as response.
> >
> > Giacomo
> >
> > >
> > > Thanks,
> > > Alex.
> > >
> > > > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > I'm trying to use Views for setting look and feel based on specific
> user
> > > > > logged on the web site. So far I cannot even make very basic view
> > > working:
> > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > >   ...
> > > > >   
> > > > > 
> > > > >  > > src="content/xml/welcome.xml"/>
> > > > > 
> > > > >  > > src="stylesheets/xsl/welcome1.xsl"/>
> > > > > 
> > > > >   
> > > > >   ...
> > > > > 
> > > > > 
> > > > > 
> > > >
> > > > What version are you using? In the current 2.0 and HEAD branches of
> the
> > > > CVS there isn't a map:label anymore. So you need to specify it this
> way:
> > > >
> > > >  
> > > > label"xsltran"/>
> > > >
> > > >
> > > >  
> > > >
> > > > Giacomo
> > > >
> > > > >
> > > > > this falls through "welcome1.xsl", but not through "welcome.xsl"
> which
> > > > > suppose to be called from the "xsltran" view...
> > > >

Re: Look-and-feel approach with views

[Alexander Smirnoff]

OK. I've got it.

Well, is it possible to trigger the view from inside sitemap? What about
Passing parameters?

I think the idea of breaking pipeline and continuing it from another
"resource"-like pipeline ("view") from labeled predefined point is very
powerful. Imagine having the same long chain of transformations through
group or even all of pipelines in the sitemap! From my point of view it
makes sitemap more unreadable. From the other side, if you have some
"resource"-like view which could be processed from any pipeline and being
"returned" to the point of entry will make readability of sitemap more
easy...

Something like that:


















This is just a random thought. Sorry for being naive if this is the
case...Probably there are some workaround which I don't know, - I'll be glad
to comprehend.

Thanks,
Alex.


- Original Message -
From: "giacomo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 2:46 PM
Subject: Re: Look-and-feel approach with views


> On Mon, 26 Nov 2001, Alexander Smirnoff wrote:
>
> > I'm using 2.0rc1, but even if I put label="xsltran" into 
> > declaration this doesnt work either...
> >
> > I feel that I misundersatnd the concept. It seems, for example, in
webapp
> > sitemap.xconf (in HEAD branch) the view declaration like:
> >
> > 
> >
> > 
> >
> > never executes... Otherwise it supposed to be executed for every pipline
> > after last component in pipline... So I'm really confused...
>
> If you don't request that view it will never be executed :) use a
>
> http://localhost:8080/cocoon/welcome?cocoon-view=links
>
> and you'll get all the links in the welcome page as response.
>
> Giacomo
>
> >
> > Thanks,
> > Alex.
> >
> > > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I'm trying to use Views for setting look and feel based on specific
user
> > > > logged on the web site. So far I cannot even make very basic view
> > working:
> > > >
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > 
> > > > 
> > > > 
> > > >   ...
> > > >   
> > > > 
> > > >  > src="content/xml/welcome.xml"/>
> > > > 
> > > >  > src="stylesheets/xsl/welcome1.xsl"/>
> > > > 
> > > >   
> > > >   ...
> > > > 
> > > > 
> > > > 
> > >
> > > What version are you using? In the current 2.0 and HEAD branches of
the
> > > CVS there isn't a map:label anymore. So you need to specify it this
way:
> > >
> > >  
> > >
> > >
> > >
> > >  
> > >
> > > Giacomo
> > >
> > > >
> > > > this falls through "welcome1.xsl", but not through "welcome.xsl"
which
> > > > suppose to be called from the "xsltran" view...
> > > >
> > > > What is my mistake?
> > > >
> > > > Thanks,
> > > > Alexander Smirnoff
> > > >
> > > >
> > >
> -
> > > > 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]>
> > >
> >
> >
> > -
> > 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]>
>


-
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]>

Re: Look-and-feel approach with views

[giacomo]

On Mon, 26 Nov 2001, Alexander Smirnoff wrote:

> I'm using 2.0rc1, but even if I put label="xsltran" into 
> declaration this doesnt work either...
>
> I feel that I misundersatnd the concept. It seems, for example, in webapp
> sitemap.xconf (in HEAD branch) the view declaration like:
>
> 
>
> 
>
> never executes... Otherwise it supposed to be executed for every pipline
> after last component in pipline... So I'm really confused...

If you don't request that view it will never be executed :) use a

http://localhost:8080/cocoon/welcome?cocoon-view=links

and you'll get all the links in the welcome page as response.

Giacomo

>
> Thanks,
> Alex.
>
> > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> >
> > > Hi everyone,
> > >
> > > I'm trying to use Views for setting look and feel based on specific user
> > > logged on the web site. So far I cannot even make very basic view
> working:
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >   ...
> > >   
> > > 
> > >  src="content/xml/welcome.xml"/>
> > > 
> > >  src="stylesheets/xsl/welcome1.xsl"/>
> > > 
> > >   
> > >   ...
> > > 
> > > 
> > > 
> >
> > What version are you using? In the current 2.0 and HEAD branches of the
> > CVS there isn't a map:label anymore. So you need to specify it this way:
> >
> >  
> >
> >
> >
> >  
> >
> > Giacomo
> >
> > >
> > > this falls through "welcome1.xsl", but not through "welcome.xsl" which
> > > suppose to be called from the "xsltran" view...
> > >
> > > What is my mistake?
> > >
> > > Thanks,
> > > Alexander Smirnoff
> > >
> > >
> > > -
> > > Please check that your question has not already been answered in the
> > > FAQ before posting. 
> > >
> > > 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. 
> >
> > 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. 
>
> 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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: Look-and-feel approach with views

[Alexander Smirnoff]

Here is my confusion sources compiled with Cocoon2 CVS HEAD branch.

It seems that in this really simple case View MUST work, but it doesnt - I'm
still getting welcome1.xsl transformation.

I feel that I missed something big.

Thanks for help,
Alex.
- Original Message -
From: "Alexander Smirnoff" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 12:28 PM
Subject: Re: Look-and-feel approach with views


> I'm using 2.0rc1, but even if I put label="xsltran" into 
> declaration this doesnt work either...
>
> I feel that I misundersatnd the concept. It seems, for example, in webapp
> sitemap.xconf (in HEAD branch) the view declaration like:
>
> 
>
> 
>
> never executes... Otherwise it supposed to be executed for every pipline
> after last component in pipline... So I'm really confused...
>
> Thanks,
> Alex.
>
> > On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
> >
> > > Hi everyone,
> > >
> > > I'm trying to use Views for setting look and feel based on specific
user
> > > logged on the web site. So far I cannot even make very basic view
> working:
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >   ...
> > >   
> > > 
> > >  src="content/xml/welcome.xml"/>
> > > 
> > >  src="stylesheets/xsl/welcome1.xsl"/>
> > > 
> > >   
> > >   ...
> > > 
> > > 
> > > 
> >
> > What version are you using? In the current 2.0 and HEAD branches of the
> > CVS there isn't a map:label anymore. So you need to specify it this way:
> >
> >  
> >
> >
> >
> >  
> >
> > Giacomo
> >
> > >
> > > this falls through "welcome1.xsl", but not through "welcome.xsl" which
> > > suppose to be called from the "xsltran" view...
> > >
> > > What is my mistake?
> > >
> > > Thanks,
> > > Alexander Smirnoff
> > >
> > >
> > > -
> > > 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]>
> >
>
>
> -
> 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]>
>



http://apache.org/cocoon/sitemap/1.0";>







true
false
false































sitemap_xmap.java
Description: Binary data

-
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]>

Re: Look-and-feel approach with views

[Alexander Smirnoff]

I'm using 2.0rc1, but even if I put label="xsltran" into 
declaration this doesnt work either...

I feel that I misundersatnd the concept. It seems, for example, in webapp
sitemap.xconf (in HEAD branch) the view declaration like:


   


never executes... Otherwise it supposed to be executed for every pipline
after last component in pipline... So I'm really confused...

Thanks,
Alex.

> On Fri, 23 Nov 2001, Alexander Smirnoff wrote:
>
> > Hi everyone,
> >
> > I'm trying to use Views for setting look and feel based on specific user
> > logged on the web site. So far I cannot even make very basic view
working:
> >
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> > 
> >   ...
> >   
> > 
> > 
> > 
> > 
> > 
> >   
> >   ...
> > 
> > 
> > 
>
> What version are you using? In the current 2.0 and HEAD branches of the
> CVS there isn't a map:label anymore. So you need to specify it this way:
>
>  
>
>
>
>  
>
> Giacomo
>
> >
> > this falls through "welcome1.xsl", but not through "welcome.xsl" which
> > suppose to be called from the "xsltran" view...
> >
> > What is my mistake?
> >
> > Thanks,
> > Alexander Smirnoff
> >
> >
> > -
> > Please check that your question has not already been answered in the
> > FAQ before posting. 
> >
> > 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. 
>
> 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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: Look-and-feel approach with views

[giacomo]

On Fri, 23 Nov 2001, Alexander Smirnoff wrote:

> Hi everyone,
>
> I'm trying to use Views for setting look and feel based on specific user
> logged on the web site. So far I cannot even make very basic view working:
>
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
>   ...
>   
> 
> 
> 
> 
> 
>   
>   ...
> 
> 
> 

What version are you using? In the current 2.0 and HEAD branches of the
CVS there isn't a map:label anymore. So you need to specify it this way:

 
   
   
   
 

Giacomo

>
> this falls through "welcome1.xsl", but not through "welcome.xsl" which
> suppose to be called from the "xsltran" view...
>
> What is my mistake?
>
> Thanks,
> Alexander Smirnoff
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
>
> 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. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>