Hi Craig,

 

It would be such a useful thing if you could get this into Creator.

 

What would it take for me to get access to the nightly builds?

 

Thanks

rjs

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 2:41 AM
To: MyFaces Discussion
Subject: Re: can someone post a small working example of using my faces with the Struts Shale <s:token>?

 

 

On 2/27/06, Santiago, Ray <[EMAIL PROTECTED]> wrote:

Cool, can you also show me the correct way to add it to a JSC2 created page?


<face color="red">
I guess this is something I should really be supporting, given my role on both Shale and Creator :-).
</face>

Look for an enhancement in a future nightly build of Creator that adds a "component import" library for the fundamental Shale tags (including <s:token>).  There's no technical hurdles to this all working easily ... just needs a little bit of packaging.

Craig

 

I just don't see anything like the following in the created page; I know I have to add this somehow.

 

<%@ taglib prefix="s" uri="http://struts.apache.org/shale/core" %>

 

 

Thanks

rjs

 


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]]
Sent: Friday, February 24, 2006 8:21 PM
To: MyFaces Discussion
Subject: Re: can someone post a small working example of using my faces with the Struts Shale <s:token>?

 

 

On 2/24/06, Santiago, Ray < [EMAIL PROTECTED]> wrote:

Thanks


The "Use Cases" example application uses this feature on quite a few screens -- for example, on "profile/logon.jsp".  If you try to submit twice, you will get a validation error on the second post.  So, all you need to do is provide an <h:messages> or equivalent component to display the error message.

Source code for this app is in the Shale source bundles.  There is also a separate WAR for this (and all the other apps) in the nightly builds directory:

  http://cvs.apache.org/builds/struts/nightly/struts-shale/

Craig

 

rjs

This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.

The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
 


aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received

this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.
 
 

 

This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be

aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.
 

 

This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.

Reply via email to