[jira] Resolved: (SHALE-404) EL in cond attribute of is not properly resolved
[
https://issues.apache.org/struts/browse/SHALE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar resolved SHALE-404.
-
Resolution: Duplicate
Seems we have a race condition opening tickets here :-) Closing this as it
duplicates SHALE-403 opened few minutes ago.
> EL in cond attribute of is not properly resolved
> -
>
> Key: SHALE-404
> URL: https://issues.apache.org/struts/browse/SHALE-404
> Project: Shale
> Issue Type: Bug
> Components: Dialog
>Affects Versions: 1.1.0-SNAPSHOT
>Reporter: Paul Spencer
>
> I suspect that SCXML is not getting the properties from dialog.data because
> the value of dialog.data.leased is always
> false.
> ***
> * Value of dialog.data fields
> ***
>leased = Boolean.TRUE
> ***
> * Dialog configuration for the stat Page 1
> ***
>
>
>
>
>cond="${outcome eq 'next' and dialog.data.leased}" target="page2" />
>cond="${outcome eq 'next' and not dialog.data.leased}" target="review"
> />
>cond="${outcome eq 'cancel'}" />
>
> ***
> * Logging
> ***
> outcome = next
> _eventdata = null
> _eventdatamap = {faces.outcome=null}
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'next' and dialog.data.leased} = false
> _ALL_NAMESPACES = null
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'next' and not dialog.data.leased} = true
> _ALL_NAMESPACES = null
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'cancel'} = false
> _ALL_NAMESPACES = null
> _eventdata = null
> _eventdatamap = null
> Current States: [review]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHALE-404) EL in cond attribute of is not properly resolved
[
https://issues.apache.org/struts/browse/SHALE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar reassigned SHALE-404:
---
Assignee: Rahul Akolkar
> EL in cond attribute of is not properly resolved
> -
>
> Key: SHALE-404
> URL: https://issues.apache.org/struts/browse/SHALE-404
> Project: Shale
> Issue Type: Bug
> Components: Dialog
>Affects Versions: 1.1.0-SNAPSHOT
>Reporter: Paul Spencer
> Assigned To: Rahul Akolkar
>
> I suspect that SCXML is not getting the properties from dialog.data because
> the value of dialog.data.leased is always
> false.
> ***
> * Value of dialog.data fields
> ***
>leased = Boolean.TRUE
> ***
> * Dialog configuration for the stat Page 1
> ***
>
>
>
>
>cond="${outcome eq 'next' and dialog.data.leased}" target="page2" />
>cond="${outcome eq 'next' and not dialog.data.leased}" target="review"
> />
>cond="${outcome eq 'cancel'}" />
>
> ***
> * Logging
> ***
> outcome = next
> _eventdata = null
> _eventdatamap = {faces.outcome=null}
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'next' and dialog.data.leased} = false
> _ALL_NAMESPACES = null
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'next' and not dialog.data.leased} = true
> _ALL_NAMESPACES = null
> _ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
> =http://www.w3.org/2005/07/scxml}
> ${outcome eq 'cancel'} = false
> _ALL_NAMESPACES = null
> _eventdata = null
> _eventdatamap = null
> Current States: [review]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-404) EL in cond attribute of is not properly resolved
EL in cond attribute of is not properly resolved
-
Key: SHALE-404
URL: https://issues.apache.org/struts/browse/SHALE-404
Project: Shale
Issue Type: Bug
Components: Dialog
Affects Versions: 1.1.0-SNAPSHOT
Reporter: Paul Spencer
I suspect that SCXML is not getting the properties from dialog.data because the
value of dialog.data.leased is always
false.
***
* Value of dialog.data fields
***
leased = Boolean.TRUE
***
* Dialog configuration for the stat Page 1
***
***
* Logging
***
outcome = next
_eventdata = null
_eventdatamap = {faces.outcome=null}
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'next' and dialog.data.leased} = false
_ALL_NAMESPACES = null
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'next' and not dialog.data.leased} = true
_ALL_NAMESPACES = null
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'cancel'} = false
_ALL_NAMESPACES = null
_eventdata = null
_eventdatamap = null
Current States: [review]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-403) Back the root Context used for SCXML dialogs with the application VariableResolver
[ https://issues.apache.org/struts/browse/SHALE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39947 ] Rahul Akolkar commented on SHALE-403: - ShaleDialogELContext committed to trunk (r501972) and 1_0_X branch (r501974). > Back the root Context used for SCXML dialogs with the application > VariableResolver > -- > > Key: SHALE-403 > URL: https://issues.apache.org/struts/browse/SHALE-403 > Project: Shale > Issue Type: Improvement > Components: Dialog >Affects Versions: 1.0.4 >Reporter: Rahul Akolkar > Assigned To: Rahul Akolkar > Fix For: 1.0.5-SNAPSHOT, 1.1.0-SNAPSHOT > > > This allows for using arbitrary EL expressions (beyond calling action state > MBEs) within the SCXML document used to describe the dialog. > Reported by Paul Spencer on the Shale user mailing > list in this thread: > http://www.nabble.com/Need-help-with-SCXML-transition-cond-syntax.-tf3144134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-403) Back the root Context used for SCXML dialogs with the application VariableResolver
Back the root Context used for SCXML dialogs with the application VariableResolver -- Key: SHALE-403 URL: https://issues.apache.org/struts/browse/SHALE-403 Project: Shale Issue Type: Improvement Components: Dialog Affects Versions: 1.0.4 Reporter: Rahul Akolkar Assigned To: Rahul Akolkar Fix For: 1.0.5-SNAPSHOT, 1.1.0-SNAPSHOT This allows for using arbitrary EL expressions (beyond calling action state MBEs) within the SCXML document used to describe the dialog. Reported by Paul Spencer on the Shale user mailing list in this thread: http://www.nabble.com/Need-help-with-SCXML-transition-cond-syntax.-tf3144134.html -- 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
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39946 ] Hermod Opstvedt commented on SHALE-402: --- I did this with the jsf-ibm.jar file from the WAS 6.1 installation in RAD 7 (...\IBM\SDP70\runtimes\base_v61\optionalLibraries\IBM\JWL). I'll look at you file and see what you have in there. > 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 > Attachments: html_extended-2.0-config.xml, ibm-config.xml > > > 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] Updated: (SHALE-402) clay xml bindings for ibm jsf components
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Wynn updated SHALE-402: Attachment: ibm-config.xml This is the version I generated with my script. For the most part it matches what you have, but there are some differences. I think we may have been generating off of different versions of jsf-ibm.jar. The version of jsf-ibm.jar that I used was taken from RAD version 7. > 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 > Attachments: html_extended-2.0-config.xml, ibm-config.xml > > > 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] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype-5.patch Removed unused chain-config.xml file > Clay starter Maven archetype > > > Key: SHALE-391 > URL: https://issues.apache.org/struts/browse/SHALE-391 > Project: Shale > Issue Type: New Feature > Components: Clay >Affects Versions: 1.0.3 >Reporter: Hermod Opstvedt > Attachments: ClayStarterArchetype.patch, > shale-clay-starter-archetype.zip, shaleclaystarterarchetype-3.patch, > shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype-5.patch, > shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch > > > A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype-4.patch The packagename of the managed beans in the faces-config.xml was not being set to the name specified for the -DpackageName parameter when running the archetype. Also there was a duplicate name for the managed beans. > Clay starter Maven archetype > > > Key: SHALE-391 > URL: https://issues.apache.org/struts/browse/SHALE-391 > Project: Shale > Issue Type: New Feature > Components: Clay >Affects Versions: 1.0.3 >Reporter: Hermod Opstvedt > Attachments: ClayStarterArchetype.patch, > shale-clay-starter-archetype.zip, shaleclaystarterarchetype-3.patch, > shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype.patch, > shaleclaystarterarchetype.patch > > > A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype-3.patch Minor cleanups. Removed reference to the removed validator stuff, Altered the name of produced build to be equal to the given artifactId. > Clay starter Maven archetype > > > Key: SHALE-391 > URL: https://issues.apache.org/struts/browse/SHALE-391 > Project: Shale > Issue Type: New Feature > Components: Clay >Affects Versions: 1.0.3 >Reporter: Hermod Opstvedt > Attachments: ClayStarterArchetype.patch, > shale-clay-starter-archetype.zip, shaleclaystarterarchetype-3.patch, > shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch > > > A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-402) clay xml bindings for ibm jsf components
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-402: -- Attachment: html_extended-2.0-config.xml This is the generated Clay config file for the IBM faces components. Take a look at it and see if it matches what you have. > 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 > Attachments: html_extended-2.0-config.xml > > > 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.
