Ryan Wynn (JIRA | 1 Jun 14:51 2007
Picon

Commented: (SHALE-444) Eclipse Plugin


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

Ryan Wynn commented on SHALE-444:
---------------------------------

md5sum - b038c63fced4b25024c5d41f995296e9

> Eclipse Plugin
> --------------
>
>                 Key: SHALE-444
>                 URL: https://issues.apache.org/struts/browse/SHALE-444
>             Project: Shale
>          Issue Type: New Feature
>          Components: Clay
>         Environment: Any environment supported by Eclipse
>            Reporter: Ryan Wynn
>         Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse.  Create a visual editor targeted towards creating/maintaining clay
component metadata.  Support autodetection of clay component definitions in the workspace.  Allow
component extension through drag and drop from a component palette.  Provide autocompletion of managed
bean names and methods.  Support both visual and text modes.
>   

--

-- 
(Continue reading)

Rahul Akolkar (JIRA | 5 Jun 22:04 2007
Picon

Commented: (SHALE-423) Subdialog not returning to calling dialog


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

Rahul Akolkar commented on SHALE-423:
-------------------------------------

Can you try with the latest nightly (20070605 or later) or build from source?

> Subdialog not returning to calling dialog
> -----------------------------------------
>
>                 Key: SHALE-423
>                 URL: https://issues.apache.org/struts/browse/SHALE-423
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Per Jansson
>
> When calling a subdialog from any other dialog, the sub dialog does not return attention to the calling
dialog. In my example use case a common confirm page is to be shown (using subdialog) before returning to
calling dialog and continue.
> ......
> ......
>                  <action name="prepareConfirmTransferAction" method="#{performTransferUseCaseBean.prepareConfirmTransfer}">
>                         <transition outcome="success" target="confirmTransferSub"/>
>                         <transition outcome="failure" target="performTransferView"/>
(Continue reading)

Rahul Akolkar (JIRA | 5 Jun 22:06 2007
Picon

Commented: (SHALE-386) Have to execute action twice to return to calling dialog


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

Rahul Akolkar commented on SHALE-386:
-------------------------------------

Can you try with the latest nightly (20070605 or later) or build from source?

> Have to execute action twice to return to calling dialog
> --------------------------------------------------------
>
>                 Key: SHALE-386
>                 URL: https://issues.apache.org/struts/browse/SHALE-386
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I have to run an action twice to be returned to the calling dialog.
> Steps to recreate:
> Click on Go to Dialog 1
> Click on Go to Dialog 2
> Click on Cancel
> Expect to go to "Returned from subdialog" screen instead am presented with the same screen.
(Continue reading)

Ryan Lubke (JIRA | 5 Jun 22:18 2007
Picon

Commented: (SHALE-445) 'org.apache.shale.remoting.LOGGER' is not a valid managed-bean-name


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

Ryan Lubke commented on SHALE-445:
----------------------------------

For now, I've created a private Schema for 1.1 documents and relaxed the restriction of
managed-bean-name.  This seems to work ok.  

However, this should be kept in mind if the shale faces-config documents are moved to 1.2 or beyond, the
managed-bean-name will not be valid.

> 'org.apache.shale.remoting.LOGGER' is not a valid managed-bean-name
> -------------------------------------------------------------------
>
>                 Key: SHALE-445
>                 URL: https://issues.apache.org/struts/browse/SHALE-445
>             Project: Shale
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: linux 2.6.x kernel
> JDK 1.5/1.6
>            Reporter: Ryan Lubke
>
> In order to portably support the validation of both DTD and Schema-based faces-config documents in the RI,
> we've had to take the approach or transforming any 1.0/1.1 documents to 1.2 and perform schema validation
> (there is no portable way to validate using both schema and dtd).
> Doing so has brought up an interesting issue when deploying to a container when validation is enabled.
(Continue reading)

Nick Gomm (JIRA | 7 Jun 14:44 2007
Picon

Commented: (SHALE-386) Have to execute action twice to return to calling dialog


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

Nick Gomm commented on SHALE-386:
---------------------------------

Checked with 20070606 nightly build and still have same problem.

> Have to execute action twice to return to calling dialog
> --------------------------------------------------------
>
>                 Key: SHALE-386
>                 URL: https://issues.apache.org/struts/browse/SHALE-386
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I have to run an action twice to be returned to the calling dialog.
> Steps to recreate:
> Click on Go to Dialog 1
> Click on Go to Dialog 2
> Click on Cancel
> Expect to go to "Returned from subdialog" screen instead am presented with the same screen.
(Continue reading)

Rahul Akolkar (JIRA | 7 Jun 20:21 2007
Picon

Commented: (SHALE-386) Have to execute action twice to return to calling dialog


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

Rahul Akolkar commented on SHALE-386:
-------------------------------------

Thanks for trying out the fix. We discovered on the user list that the nightly you mention does not contain
the latest source with the fix (and it turns out neither does today's nightly). The lag will need to be
investigated, so I cannot say when the change will be picked up (unless you can build the trunk).

> Have to execute action twice to return to calling dialog
> --------------------------------------------------------
>
>                 Key: SHALE-386
>                 URL: https://issues.apache.org/struts/browse/SHALE-386
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I have to run an action twice to be returned to the calling dialog.
> Steps to recreate:
> Click on Go to Dialog 1
> Click on Go to Dialog 2
(Continue reading)

Craig McClanahan (JIRA | 7 Jun 20:37 2007
Picon

Commented: (SHALE-386) Have to execute action twice to return to calling dialog


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

Craig McClanahan commented on SHALE-386:
----------------------------------------

Figured out what was going on with the nightly builds.  The "svn update" statement in the nightly build
script was wedged by the fact that it had coredumped a while back, so the build process was just rebuilding
out of date sources over and over again.  I have cleaned this up, so tonight's (20070608) nightly build will
match the current trunk code.  Sorry for the problems.

> Have to execute action twice to return to calling dialog
> --------------------------------------------------------
>
>                 Key: SHALE-386
>                 URL: https://issues.apache.org/struts/browse/SHALE-386
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I have to run an action twice to be returned to the calling dialog.
> Steps to recreate:
> Click on Go to Dialog 1
(Continue reading)

Paul Spencer (JIRA | 8 Jun 20:10 2007
Picon

Commented: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml


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

Paul Spencer commented on SHALE-446:
------------------------------------

Per Hermod, this is not a Shale issue.  You may ignore the patch and close this issue.

Paul Spencer

> Build fails on virgin system because the Cobertura version need to be set in pom.xml
> ------------------------------------------------------------------------------------
>
>                 Key: SHALE-446
>                 URL: https://issues.apache.org/struts/browse/SHALE-446
>             Project: Shale
>          Issue Type: Bug
>    Affects Versions: 1.1.0-SNAPSHOT
>            Reporter: Paul Spencer
>         Attachments: shale-446.patch
>
>
> Building Shale on a system for the first time will fail because the Cobertura plugin was not found.  Adding a
version number resolves the problem. 

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Wendy Smoak (JIRA | 8 Jun 20:25 2007
Picon

Commented: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml


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

Wendy Smoak commented on SHALE-446:
-----------------------------------

Actually, we should add version numbers for all plugins.

See http://www.nabble.com/-IMPORTANT--Maven-2-Plugin-Auto-Versioning-Considered-Dangerous-t3560426s177.html

> Build fails on virgin system because the Cobertura version need to be set in pom.xml
> ------------------------------------------------------------------------------------
>
>                 Key: SHALE-446
>                 URL: https://issues.apache.org/struts/browse/SHALE-446
>             Project: Shale
>          Issue Type: Bug
>    Affects Versions: 1.1.0-SNAPSHOT
>            Reporter: Paul Spencer
>         Attachments: shale-446.patch
>
>
> Building Shale on a system for the first time will fail because the Cobertura plugin was not found.  Adding a
version number resolves the problem. 

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Nick Gomm (JIRA | 11 Jun 11:45 2007
Picon

Commented: (SHALE-386) Have to execute action twice to return to calling dialog


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

Nick Gomm commented on SHALE-386:
---------------------------------

Tested using 20070610 and it worked as expected.  Thanks.

> Have to execute action twice to return to calling dialog
> --------------------------------------------------------
>
>                 Key: SHALE-386
>                 URL: https://issues.apache.org/struts/browse/SHALE-386
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>         Environment: Windows XP, Weblogic 8.1, snapshot 20070103
>            Reporter: Adam A. Koch
>         Attachments: bwa.war
>
>
> I have to run an action twice to be returned to the calling dialog.
> Steps to recreate:
> Click on Go to Dialog 1
> Click on Go to Dialog 2
> Click on Cancel
> Expect to go to "Returned from subdialog" screen instead am presented with the same screen.
(Continue reading)


Gmane