[jira] Commented: (SHALE-402) clay xml bindings for ibm jsf components

[Ryan Wynn (JIRA)]

[ 
https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39919
 ] 

Ryan Wynn commented on SHALE-402:
-

I have a version that I created with my own tool.  Then I edited by hand to fix 
some of the mistakes.  I tested it briefly with clay 1.04 and it worked fine 
for the set of components I tested. 

If you could run the Tld2ClayConfig tool I would be happy to compare it to my 
version.



 clay xml bindings for ibm jsf components
 

 Key: SHALE-402
 URL: https://issues.apache.org/struts/browse/SHALE-402
 Project: Shale
  Issue Type: New Feature
  Components: Clay
Affects Versions: 1.0.4
 Environment: All
Reporter: Ryan Wynn
Priority: Minor

 Clay bindings for ibm jsf components.  Much like the tomahawk bindings this 
 xml file allows clay to weave ibm's extended component library (jsf-ibm.jar) 
 into the view.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SHALE-402) clay xml bindings for ibm jsf components

[Hermod Opstvedt (JIRA)]

[ 
https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39920
 ] 

Hermod Opstvedt commented on SHALE-402:
---

I will run it later to night. You can run it your self as part of the Maven 
build. It is all in the sandbox, along with a test application.

 clay xml bindings for ibm jsf components
 

 Key: SHALE-402
 URL: https://issues.apache.org/struts/browse/SHALE-402
 Project: Shale
  Issue Type: New Feature
  Components: Clay
Affects Versions: 1.0.4
 Environment: All
Reporter: Ryan Wynn
Priority: Minor

 Clay bindings for ibm jsf components.  Much like the tomahawk bindings this 
 xml file allows clay to weave ibm's extended component library (jsf-ibm.jar) 
 into the view.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SHALE-216) possibility to skip token validation when necessary

[Veit Guna (JIRA)]

[ 
https://issues.apache.org/struts/browse/SHALE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39924
 ] 

Veit Guna commented on SHALE-216:
-

Got a workaround this. I just remove the token from the component tree when 
business validation fails and the form should be redisplayed. This seems to 
work for me. So now I can do business validations (action is called) after form 
validations and let the token be regenerated on business errors. It won't be 
handled as submitted anymore.

Is there another way to solve this?


 possibility to skip token validation when necessary
 -

 Key: SHALE-216
 URL: https://issues.apache.org/struts/browse/SHALE-216
 Project: Shale
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.0.3-SNAPSHOT
 Environment: Myfaces 1.1.2
Reporter: Veit Guna
 Fix For: TBD


 I'm using the shale token tag to avoid duplicate form submits. It works so 
 far.
 Now I have this usecase:
 - An input form is generated with fields for an address (street, areacode, 
 city etc.)
 - The token tag is placed in the bottom of the form to avoid re-submit
 - There are some validators in the form, that validate areacode in 
 combination with city
 - Is the city not unique when submitting, a warning msg is added to the 
 facescontext and the possible cities are presented in a selectbox to choose 
 from (javascript auto-submit)
 - After choosing the right city (the form is submitted automatically by JS), 
 another check looks for multiple areacodes for that city and displays them in 
 another selectbox with an additional msg in the facescontext that the user 
 has to select one.
 - When the user selects the areacode (JS auto-submit), the form is 
 re-displayed without any msg (because, everything is fine now)
 - Here is the problem: re-displaying the page without an queued error msg in 
 the facescontext will mark the form as-sent.
 - So finally when the user wants to submit the form (after correcting his 
 input), the tag doesn't allow sending the form again.
 It would be nice, if it would be possible to skip a validation for the 
 token for re-displaying a page or to generate a new token when re-displaying 
 without
 validation errors.
 One solution would be to add an additional msg to the facescontext, when 
 validation of areacode+city is finally ok. But perhaps the component could 
 offer a solution to this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.