RE: [Trinidad] Using Spring Web Flow with Trinidad?
Adam,
Thanks for the response. Your hunch is right. Sprig Web Flow makes use
of the following:
org.springframework.webflow.executor.jsf.FlowNavigat
ionHandler
org.springframework.webflow.executor.jsf.DelegatingFl
owVariableResolver
org.springframework.webflow.executor.jsf.FlowPhaseListen
er
Thanks for pointing me in the right direction. I will spend some time
trying to see what the wrapping order is, etc.
Regards,
Graeme.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Sunday, 29 July 2007 4:12 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Using Spring Web Flow with Trinidad?
On 7/27/07, Graeme Steyn <[EMAIL PROTECTED]> wrote:
> I am currently looking at introducing some form of conversation state
> management into an existing Trinidad-1.2.1/Facelets-1.1.12 web
> application that currently makes use of Trinidad's Dialog Framework.
> Ultimately, I would like to prevent issues that can occur if the use
> starts multiple conversations and data is stored in session scope. I
> would also like to restrict their ability to access the workflow by
> directly entering a URL for one of the pages in the middle of the
> workflow, instead of going through the designated start page. We are
> already making use of Spring in many areas and Spring Web Flow would
be a natural extension to try use.
>
> - Has anyone attempted to use Spring Web Flow with Trinidad?
>
> - Are there any common integration issues/pitfalls?
>
> - Is it worth looking at Spring Web Flow, or would the use of
> pageFlowScope and phaseListeners for a custom solution be easier?
>
> The first thing that came to mind was the Dialog Framework-Spring Web
> Flow interaction. I am not sure how this would work or if it would
> even work. A quick initial attempt resulted in the following error:
>
> javax.faces.el.EvaluationException:
> /views/lastSchoolSearch.xhtml @172,55
> actionListener="#{lastSchoolSearch.done}":
java.lang.IllegalStateException:
> popView(): No view has been pushed.
>
> Dialogue gets displayed based on the following transitions, but fails
> when returning.
My hunch is that "dialog:" is not actually really launching the dialog.
As for why, I'd wonder how Spring Web Flow is installing. My guess is
that it's a NavigationHandler wrapper (is that accurate?) and if so,
for "dialog:" to magically work you'd have to make sure that the
Trinidad "dialog:"
ViewHandler wrapper wraps the SWF ViewHandler wrapper, not the other way
around.
-- Adam
>
> view="/views/educationHistory.xhtml">
>
>
>
>
>
>
> view="/views/lastSchoolSearch.xhtml">
>
>
> Any feedback would be great. Thank you in advance..
Re: subForm semantics
Sub forms have to be nested. They only exclude data from other subForms, not from the form. 1 2 3 4 1: always submitted 2: submitted if "a" is specified 3: submitted if "b" is specified 4: submitted if "c" is specified I've only used it a little bit, but I think that is how it works. On 7/27/07, Gary Jackson <[EMAIL PROTECTED]> wrote: > > Now I'm really confused. I've tried using subForm two different ways: > with the subForm scope limiting validation to the contents when inner > actions occur and subForm scope excluding validation caused by outside > actions. Either way, subForm is doing nothing for me. > > My current kit is the same from this file, plus the other various things > that I need for my webapp: > > http://people.apache.org/~werpu/tomahawk-sandbox-examples.war > > Here is the relevant clause from my web.xml where I configure my taglib > files: > > > Tag libraries for facelets > facelets.LIBRARIES > > > /WEB-INF/tomahawk.taglib.xml;/WEB-INF/sandbox.taglib.xml;/WEB-INF/facelets/tags/glcf.taglib.xml > > > > Here are the entire contents of my sandbox.taglib.xml file: > > > "-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN" >"http://java.sun.com/dtd/facelet-taglib_1_0.dtd";> > > > http://myfaces.apache.org/sandbox > > subForm > > org.apache.myfaces.SubForm > org.apache.myfaces.SubForm > > > > > If it's relevant, the place where I am using is inside of a > JSF core element. > > Gary Jackson wrote: > > > > As I understand it, subForm works like this: > > > > > > > > > > > > > > > > > > > > When the "Submit Inner" button is pressed, everything is validated. > > > > When the "Submit Outer" button is pressed, everything except those > > components inside the "inner" subForm are validated. > > > > Assuming this is true, how do I get the inverse behavior? That is, I > > want things inside the subForm to be validated when the "Submit Inner" > > button is pressed, but nothing else? > > > > -- > Gary >
Re: [Trinidad] Using Spring Web Flow with Trinidad?
On 7/27/07, Graeme Steyn <[EMAIL PROTECTED]> wrote:
> I am currently looking at introducing some form of conversation state
> management into an existing Trinidad-1.2.1/Facelets-1.1.12 web application
> that currently makes use of Trinidad's Dialog Framework. Ultimately, I
> would like to prevent issues that can occur if the use starts multiple
> conversations and data is stored in session scope. I would also like to
> restrict their ability to access the workflow by directly entering a URL for
> one of the pages in the middle of the workflow, instead of going through the
> designated start page. We are already making use of Spring in many areas
> and Spring Web Flow would be a natural extension to try use.
>
> - Has anyone attempted to use Spring Web Flow with Trinidad?
>
> - Are there any common integration issues/pitfalls?
>
> - Is it worth looking at Spring Web Flow, or would the use of pageFlowScope
> and phaseListeners for a custom solution be easier?
>
> The first thing that came to mind was the Dialog Framework-Spring Web Flow
> interaction. I am not sure how this would work or if it would even work. A
> quick initial attempt resulted in the following error:
>
> javax.faces.el.EvaluationException:
> /views/lastSchoolSearch.xhtml @172,55
> actionListener="#{lastSchoolSearch.done}": java.lang.IllegalStateException:
> popView(): No view has been pushed.
>
> Dialogue gets displayed based on the following transitions, but fails when
> returning.
My hunch is that "dialog:" is not actually really launching
the dialog. As for why, I'd wonder how Spring Web Flow
is installing. My guess is that it's a NavigationHandler
wrapper (is that accurate?) and if so, for "dialog:" to magically
work you'd have to make sure that the Trinidad "dialog:"
ViewHandler wrapper wraps the SWF ViewHandler wrapper,
not the other way around.
-- Adam
>
> view="/views/educationHistory.xhtml">
>
>
>
>
>
>
> view="/views/lastSchoolSearch.xhtml">
>
>
>
> Any feedback would be great. Thank you in advance..
Re: Tomahawk JSCookMenu Navigation Validation
OK found it - immediate="true" does it ChrisC wrote: > > Hi > > I have a JSCookMenu in a JSP which is then included in many pages using > so I have a common menu for them all. > Some of the pages are forms for input with validation=true for the fields. > If I click on the menu to take me away from one of these form pages the > validation prevents it. > That is I get the error messages "xyz is required". > In these cases where submit has not been clicked I do not want the > validation. > Any ideas? > > Many thanks > > Chris > > TC 5.5 Tomahawk 1.1.13 > -- View this message in context: http://www.nabble.com/Tomahawk-JSCookMenu-Navigation-Validation-tf4159384.html#a11841995 Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: Using MyFaces in RAD 6.0
Any help on this ? Atleast point me in the right direction. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 2:55 PM To: users@myfaces.apache.org Subject: Using MyFaces in RAD 6.0 Hi All, I would want to know the steps to integrate the MyFaces Tomahawk component to my existing RAD 6.0 JSF project. I have experience in using eclipse where I just added the jars to the classpath and was able to use them right away(dint even have to add the filters). But in RAD I get error when I add the jar into the buildpath. I need the tomahawk component so that I can use the t:column's groupBy attribute and achieve a grouping table. Thanks, Dilip This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
Re: [TRINIDAD] Skinning in a portlet environment
But you'd need to do this check in every renderer then, right? I
wonder if this is good performance wise.
regards,
Martin
On 7/27/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
> One way would be to have something along those line:
>
> CoreRenderer.java
>
> public void encodeBegin(FacesContext context, UIComponent component)
> {
> if (isPortlet(context) && !isXhtmlRootElement() && !isStyleSheetCopied())
>{
> pushStyleSheet(context);
>}
>
> // Do normal processing
> }
>
> protected abstract boolean isXhtmlRootElement();
>
> Then we would simply have to make isXhtmlRootElement() return true for
> document, head and body renderers and false for the others. But it's not
> extremely clean.
>
>
> Regards,
>
> ~ Simon
>
>
> On 7/27/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Sure, it would be better for the user if it works out of the box.
> >
> > As much as I think, I don't find a central place where to put it, though.
> >
> > Ideas anyone?
> >
> > regards,
> >
> > Martin
> >
> > On 7/27/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
> > > Hello Martin,
> > >
> > > Yeah I thought about a new component and we actually already have
> > > that could be slightly altered to do that work, but I
> > > would prefer a way not involving any action from users.
> > >
> > >
> > > On 7/27/07, Martin Marinschek < [EMAIL PROTECTED]> wrote:
> > > > Hi Simon,
> > > >
> > > > true. The form-render was good for my nice small example, but is no
> > > > general solution of course.
> > > >
> > > > I wonder if this would mandate a special component which does nothing
> > > > but adding the stylesheet to the head?
> > > >
> > > > Eventually, the component could be generalized, so that all kinds of
> > > > stylesheets can be added, if a link is provided and the stylesheet
> > > > hasn't been added so far - I think this solution might be interesting
> > > > for the portlet-developer in general.
> > > >
> > > > regards,
> > > >
> > > > Martin
> > > >
> > > > On 7/27/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
> > > > > Issue with #3 is not very hard, we already have a RenderingContext
> that
> > > can
> > > > > be used for that. We could probably hook that code in CoreRenderer
> or
> > > > > XhtmlRenderer. The only issue left then would be to not have
> document,
> > > head
> > > > > and body renderer to execute it. Placing it in FormRenderer only
> does
> > > not
> > > > > seems right in case your page does not contain a form at all or use
> a
> > > basic
> > > > > JSF form (extremely unlikely though).
> > > > >
> > > > >
> > > > > On 7/27/07, Martin Marinschek < [EMAIL PROTECTED]> wrote:
> > > > > > For the discussion on if and how to integrate this into Trinidad -
> I
> > > > > > see three cases:
> > > > > >
> > > > > > 1) people only want basic skinning, Trinidad uses simple.portlet,
> and
> > > > > > emits portlet-standard compliant skinning hooks
> > > > > >
> > > > > > 2) people want normal Trinidad skinning, portlet container
> provides
> > > > > > CSS file in the head, Trinidad doesn't have to do anything
> (especially
> > > > > > not switch to portlet-standard compliant skinning hooks)
> > > > > >
> > > > > > 3) people want Trinidad skinning, portlet container does not
> provide
> > > > > > the CSS file, Trinidad portlet needs to add the CSS file with
> > > > > > JavaScript itself. Issue to solve: CSS file needs to be added only
> > > > > > once.
> > > > > >
> > > > > > regards,
> > > > > >
> > > > > > Martin
> > > > > >
> > > > > > On 7/27/07, Martin Marinschek < [EMAIL PROTECTED] >
> wrote:
> > > > > > > Hi Simon, Scott,
> > > > > > >
> > > > > > > I've made skinning work now in any container - this is the code
> that
> > > > > > > I've used, for other users as a reference. We should carry on
> the
> > > > > > > discussion if and how to integrate this into Trinidad itself,
> > > though.
> > > > > > >
> > > > > > > regards,
> > > > > > >
> > > > > > > Martin
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > use a binding attribute on your tr:form:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > provide a getter for this form in your backing-bean:
> > > > > > >
> > > > > > > public CoreForm getForm() {
> > > > > > > CoreForm coreForm = new MyCoreForm();
> > > > > > > return coreForm;
> > > > > > > }
> > > > > > >
> > > > > > > write the class MyCoreForm, extending Trinidad's CoreForm - with
> > > that,
> > > > > > > you should be good.
> > > > > > >
> > > > > > > public static class MyCoreForm extends CoreForm {
> > > > > > > @Override
> > > > > > > public void encodeBegin(FacesContext context) throws
> > > IOException
> > > > > {
> > > > > > >
> > > > > > > StyleContext styleContext = ((CoreRenderingContext)
> > > > > > > RenderingContext.getCurrentInstance
> > > > > ()).getStyleContext();
> > > > > > > String uri =
> > > > > > >
> > > > >
> > > styleContext.getStyleProvider
> ().getStyleSheetURI
[Trinidad] Understanding Trinidad Skinning?
We are trying to create our own custom skin for Trinidad and I have a basic question: First, where do the defaults for a paticular element come from? For example, we are trying to skin "af:column::header-text". When we remove the color element, a default of #669966 is put into the transformed skin. I found the skin selector documentation, is the another doc describing how skins works and their default values? I have css people working on defining the skin and they are having a slow time trying to figure this out. Second, the skin selector documentation states that it is not up-to-date. Where can I find updated info - source code only? Thanks, Chris
