Thanks for quick reply, Gary. I should have been more verbose, however, I
thought this behaviour (printing raw jsp instead of html) was a very simple
simptom of a simple problem.
I am putting a clay component into a working JSF application (I need to be
able to assemble a page dynamically from several components instead of
including jsp's and such). This is the snippet of this jsp page
......
<%@ include file="createProject.jsp"%>
......
<clay:clay id="tabs" jsfid="RUNTIME" shapeValidator="#{
myViewController.createList}" managedBeanName="myViewController"/>
......
In createList method I am populating an HtmlPanelGroup with the commandLink
children. Every commandLink in this page has an action attribute pointing to
this very jsp page and a number of parameters identifying a bean (from the
list) I need to display instead of the list. That bean display, btw, is
handled by the included page createProject.jsp. So I have no navigation, the
beans I need to display have been properly instantiated when accessed in a a
pure jsf context (using jsf commandLink elements with the same parameters),
so I assume that all of the mappings in web.xml etc are OK.
Thanks.
Z.
On 1/25/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> >From: xzuma <[EMAIL PROTECTED]>
> >
> > Hello,
> >
> > I just started implementing my shale-clay application (looking at
> rolodex
> > example) and upon creating a command link in my view controller,
>
> Do you mean that you have an action method in the view controller? Or,
> are you binding a JSF control to an instance in your view controller? If
> you are using action binding, your clay html template might look like
> options 1 or 2:
>
> 1) <a [EMAIL PROTECTED] allowBody=true>Next Page</a>
> 2) <a jsfid=nextPageCommand>Next Page</a>
>
> There are eleven implicitly mapped HTML elements to JSF components. The
> first option show an implied binding of a submit button with a jsf command
> link.
>
> The action in your view controller might look like this:
> public String next() {
> return "next";
> }
>
> >I can see
> > the link on the html page, but when I click it, the next page is blank
> and
> > the source code shows only the jsp code of one of the subviews of the
> target
> > jsp page.
>
> It sounds like your navigation rules are correct in your faces-config.xml.
> Are you sure you are seeing html from the target page? Can you access
> the target page directly from the browser /examples/targetpage.faces?
>
> What are the mappings for the faces servlet in the web.xml?
>
> >I am not familiar with the phases in shale that much, so I think
> > it is a very simple issue, which will require only a moment of
> > somebody-more-experienced-than-I's attention.
>
> Shale doesn't add any phases to the standard JSF lifecycle. It adds
> callback
> events extending the standard lifecycle that are fired on the
> ViewController
> associated with the page.
>
> Are you familiar with JavaServer Faces? Shale is built on top of JSF.
> Knowing about vanilla JSF will help understand Shale.
>
>
> >
> > Thanks.
> >
> > Zuma
> >
>
> Gary
>
