springframework-rcp-dev — Spring Rich Client developer list

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-624) migrate pom dependencies to come from the SpringSource Enterprise Bundle Repository

[Geoffrey De S. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50523#action_50523 ] 

Geoffrey De Smet commented on RCP-624:
--------------------------------------

-1 on this change

This change says we have to do something like this:
{code}
     <dependency>
-      <groupId>junit</groupId>
-      <artifactId>junit</artifactId>
+      <groupId>org.junit</groupId>
+      <artifactId>com.springsource.org.junit</artifactId>
     </dependency>
{code}

The advantage is that makes us OSGi ready by using the spring OSGi maven-repistory hack. The disadvantage is that is screws up maven entirely :(
That's because maven doesn't see that junit:junit equals org.junit:com.springsource.org.junit, which gives a total mess with projects depending on us that don't use that spring OSGi maven-repistory hack.
Wait for maven 3 to fix the OSGi story.
Let the the spring OSGi maven-repistory hack become obsolete.
In december 2009 the maven lead said maven 3 would be released this month (january 2010).
Everybody will be happy then :) both OSGi users and non-OSGi users.

> migrate pom dependencies to come from  the SpringSource Enterprise Bundle Repository
> ------------------------------------------------------------------------------------
>
>                 Key: RCP-624
>                 URL: https://jira.springsource.org/browse/RCP-624
>             Project: Spring Rich Client Project
>          Issue Type: Refactoring
>          Components: Build System
>    Affects Versions: 1.1.1
>            Reporter: Ryan Ovrevik
>            Assignee: Lieven Doclo
>            Priority: Minor
>         Attachments: spring-richclient-poms.patch
>
>
> Update all poms to retrieve dependencies from the SpringSource Enterprise Bundle Repository. This seems like a reasonable precondition for updating the project(s) to utilize spring3.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-624) migrate pom dependencies to come from the SpringSource Enterprise Bundle Repository

[Ryan O. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Ovrevik updated RCP-624:
-----------------------------

    Attachment: spring-richclient-poms.patch

Added spring enterprise repositories
Updated to utilize spring version 2.5.6.SEC01
Replaced all possible dependencies with corresponding spring-managed dependencies and removed resulting necessary exclusions (verified with dependency:tree)
Added exclusions for remaining spring-binding dependency not available in spring repository.


> migrate pom dependencies to come from  the SpringSource Enterprise Bundle Repository
> ------------------------------------------------------------------------------------
>
>                 Key: RCP-624
>                 URL: https://jira.springsource.org/browse/RCP-624
>             Project: Spring Rich Client Project
>          Issue Type: Refactoring
>          Components: Build System
>    Affects Versions: 1.1.1
>            Reporter: Ryan Ovrevik
>            Assignee: Lieven Doclo
>            Priority: Minor
>         Attachments: spring-richclient-poms.patch
>
>
> Update all poms to retrieve dependencies from the SpringSource Enterprise Bundle Repository. This seems like a reasonable precondition for updating the project(s) to utilize spring3.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-627) update version of the spring-binding dependency to 2+

[Ryan O. (JIRA) <no...@sp...>]

update version of the spring-binding dependency to 2+
-----------------------------------------------------

                 Key: RCP-627
                 URL: https://jira.springsource.org/browse/RCP-627
             Project: Spring Rich Client Project
          Issue Type: Improvement
          Components: Build System, Core
    Affects Versions: 1.1.0
            Reporter: Ryan Ovrevik
            Assignee: Lieven Doclo
            Priority: Minor


Updating spring-binding to a version 2+ is a key dependency that prevents cleanly updating to spring framework 3 and the spring enterprise repository.

Another intermediate (admittedly dirty) possibility might be to merge the needed components from spring-binding version 1 into RCP and pulling the remaining dependencies from spring-binding version 2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-626) VLDocking integration broken

[Adam A. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Armistead updated RCP-626:
-------------------------------

    Attachment: RCP-626_1.patch

Downgraded logger lines to debug, clearing docking desktop before calling super.showPage, changed conditional to check for null oldPage, and removed extraneous casting.

> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch, RCP-626_1.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-626) VLDocking integration broken

[Adam A. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50373#action_50373 ] 

Adam Armistead commented on RCP-626:
------------------------------------

I have downgraded the logging lines to debug and am clearing the dockables before calling super.showPage().  As for calling oldPage.close() I will change the conditional to if(oldPage != null) which is probably more accurate and remove the casting.

> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-626) VLDocking integration broken

[Rogan D. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50372#action_50372 ] 

Rogan Dawes commented on RCP-626:
---------------------------------

Well, maybe not remove, but maybe downgrade to debug or some lesser level?

> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-626) VLDocking integration broken

[Adam A. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50370#action_50370 ] 

Adam Armistead commented on RCP-626:
------------------------------------

There are only 2 logging lines at the info level in my code. One when an application window is created and one when an application page is created.  Should I get rid of both of them?

I will look into and test calling the close method to see why I did it that way.

> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-623) Add ResizeWeight support to VLDocking

[Rogan D. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50367#action_50367 ] 

Rogan Dawes commented on RCP-623:
---------------------------------

Code looks obviously correct. Please apply.

> Add ResizeWeight support to VLDocking
> -------------------------------------
>
>                 Key: RCP-623
>                 URL: https://jira.springsource.org/browse/RCP-623
>             Project: Spring Rich Client Project
>          Issue Type: Improvement
>          Components: Integration
>    Affects Versions: 1.1.0
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>            Priority: Minor
>         Attachments: RCP-623.patch
>
>
> VLDocking should be able to support resize weight on the dock key. Adding this support is trivial and should only require adding a resizeWeight property to VLDockingViewDescriptor with get/set methods and to set the assigned resizeWeight to the DockKey in the ViewDescriptorDockable constructor.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-626) VLDocking integration broken

[Rogan D. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50366#action_50366 ] 

Rogan Dawes commented on RCP-626:
---------------------------------

The code looks fine, although there are perhaps a few too many logging lines at info level.

You might also want to clear the floating dockables before calling super.showPage(), rather than after.

Finally, this seems unnecessary:

{quote}
+    // Saves the layout for the current page before displaying the new one.
+    if(oldPage instanceof VLDockingApplicationPage) {
+      ((VLDockingApplicationPage)oldPage).close();
+    }
{quote}

ApplicationPage specifies .close() anyway, so there is no need for the conditional and casting.


> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-626) VLDocking integration broken

[Adam A. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Armistead updated RCP-626:
-------------------------------

    Attachment: RCP-626.patch

I removed the page listener and associated layout saving code in the VLDockingApplicationPageFactory as this was causing the desktop layout to be saved once for each page created.  Pages are saved when closed anyway.  Which works on a show page command and when closing the application.

I created a VLDockingApplicationWindowFactory and VLDockingApplicationWindow that interact with the VLDockingApplicationPage to load and save layouts and clear the docking desktop when a new page is shown.

I removed loading the initial layout from the createControl method in the VLDockingApplicationPage as this was attempting to layout floating dockables whose position is dependent on the main window before the docking desktop was added to the window.  This was pulled out and put in the loadInitialLayout method which is called from VLDockingApplicationWindow during a show page command AFTER the docking desktop is added to the main window.

To configure the VLDocking support the only thing that needs to be done differently is in the ApplicationContext xml file you must specify a VLDockingApplicationWindowFactory bean and reference this with an idref tag in the application services.

> VLDocking integration broken
> ----------------------------
>
>                 Key: RCP-626
>                 URL: https://jira.springsource.org/browse/RCP-626
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-626.patch
>
>
> In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-626) VLDocking integration broken

[Adam A. (JIRA) <no...@sp...>]

VLDocking integration broken
----------------------------

                 Key: RCP-626
                 URL: https://jira.springsource.org/browse/RCP-626
             Project: Spring Rich Client Project
          Issue Type: Bug
            Reporter: Adam Armistead
            Assignee: Lieven Doclo


In the VLDocking integrations each application page is its own DockingDesktop instance.  Pages are not being saved and loaded correctly resulting in floating dockables remaining on screen after showing a new page that should not show the floating dockable as a view.  Floating dockables are not positioned correctly when a page is shown, and when closing a page it is saved once for each page created, so if you create 5 application pages and close one of them it is saved 5 times in a row.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-625) AbstractApplicationWindow createPage method uses confusing variable name

[Adam A. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Armistead updated RCP-625:
-------------------------------

    Attachment: RCP-625.patch

> AbstractApplicationWindow createPage method uses confusing variable name
> ------------------------------------------------------------------------
>
>                 Key: RCP-625
>                 URL: https://jira.springsource.org/browse/RCP-625
>             Project: Spring Rich Client Project
>          Issue Type: Refactoring
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>         Attachments: RCP-625.patch
>
>
> The createPage method in the AbstractApplicationWindow get the ApplicationPageFactory from the registered application services and assigns it to a variable with the confusing name of "windowFactory" and uses it to create a new application page.  The variable should probably be named "pageFactory".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-625) AbstractApplicationWindow createPage method uses confusing variable name

[Adam A. (JIRA) <no...@sp...>]

AbstractApplicationWindow createPage method uses confusing variable name
------------------------------------------------------------------------

                 Key: RCP-625
                 URL: https://jira.springsource.org/browse/RCP-625
             Project: Spring Rich Client Project
          Issue Type: Refactoring
            Reporter: Adam Armistead
            Assignee: Lieven Doclo


The createPage method in the AbstractApplicationWindow get the ApplicationPageFactory from the registered application services and assigns it to a variable with the confusing name of "windowFactory" and uses it to create a new application page.  The variable should probably be named "pageFactory".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] Jennifer Lopez Naked

[Press c. <tyf...@gm...>]

"Love Don't Cost a Thing" clip special edition with NAKED Jennifer
Lopez! Just look!
http://yy.vc/naked

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-624) migrate pom dependencies to come from the SpringSource Enterprise Bundle Repository

[Ryan O. (JIRA) <no...@sp...>]

migrate pom dependencies to come from  the SpringSource Enterprise Bundle Repository
------------------------------------------------------------------------------------

                 Key: RCP-624
                 URL: https://jira.springsource.org/browse/RCP-624
             Project: Spring Rich Client Project
          Issue Type: Refactoring
          Components: Build System
    Affects Versions: 1.1.1
            Reporter: Ryan Ovrevik
            Assignee: Lieven Doclo
            Priority: Minor


Update all poms to retrieve dependencies from the SpringSource Enterprise Bundle Repository. This seems like a reasonable precondition for updating the project(s) to utilize spring3.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-589) ApplicationPage: add showView(String id, Object input)

[Christian H. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50001#action_50001 ] 

Christian Heilmann commented on RCP-589:
----------------------------------------

With commit r2144 the method ApplicationPage.showView(ViewDescriptor viewDescriptor) was removed. This method is necessary for showing dynamically created views (see bug RCP-363 that is about the same issue for pages) and was available in RCP 1.0.

What's the suggested way to show dynamically created views? Could you please re-add this method?


> ApplicationPage: add showView(String id, Object input)
> ------------------------------------------------------
>
>                 Key: RCP-589
>                 URL: https://jira.springsource.org/browse/RCP-589
>             Project: Spring Rich Client Project
>          Issue Type: Improvement
>            Reporter: Peter De Bruycker
>            Assignee: Peter De Bruycker
>
> add showView(String id, Object input) to ApplicationPage
> A setInput method would be added to the View interface, with an empty implementation in AbstractView. Concrete implementations could then implement this method to update its state. This method would be called by the showView method in the ApplicationPage

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-623) Add ResizeWeight support to VLDocking

[Adam A. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Armistead updated RCP-623:
-------------------------------

    Attachment: RCP-623.patch

> Add ResizeWeight support to VLDocking
> -------------------------------------
>
>                 Key: RCP-623
>                 URL: https://jira.springsource.org/browse/RCP-623
>             Project: Spring Rich Client Project
>          Issue Type: Improvement
>          Components: Integration
>    Affects Versions: 1.1.0
>            Reporter: Adam Armistead
>            Assignee: Lieven Doclo
>            Priority: Minor
>         Attachments: RCP-623.patch
>
>
> VLDocking should be able to support resize weight on the dock key. Adding this support is trivial and should only require adding a resizeWeight property to VLDockingViewDescriptor with get/set methods and to set the assigned resizeWeight to the DockKey in the ViewDescriptorDockable constructor.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-623) Add ResizeWeight support to VLDocking

[Adam A. (JIRA) <no...@sp...>]

Add ResizeWeight support to VLDocking
-------------------------------------

                 Key: RCP-623
                 URL: https://jira.springsource.org/browse/RCP-623
             Project: Spring Rich Client Project
          Issue Type: Improvement
          Components: Integration
    Affects Versions: 1.1.0
            Reporter: Adam Armistead
            Assignee: Lieven Doclo
            Priority: Minor


VLDocking should be able to support resize weight on the dock key. Adding this support is trivial and should only require adding a resizeWeight property to VLDockingViewDescriptor with get/set methods and to set the assigned resizeWeight to the DockKey in the ViewDescriptorDockable constructor.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] Have You Seen

[Valeria <oli...@gm...>]

Hi to my group friends! Have You seen this new video?
http://shrtb.us/21332

[Springframework-rcp-dev] My wedding video

[Celicia J. <sau...@gm...>]

Hi to all. Here isour wedding video.
Happy New Year!
http://tpal.us/wedding2

[Springframework-rcp-dev] A joke

[Anna F <plu...@gm...>]

O-ha-ha
What are they doing?
PS Just a joke, but so funny :)
http://snipurl.com/tx2r6

[Springframework-rcp-dev] Ite Horse white As the first plume of t

[Vidinha A. <re...@dc...>]

Aketh wood or weald, How long she stood on the roof of the world As he
stood on my shield. "The new wild world forgetteth her As foam fades on
the sea, How long she stood with her foot on Man As he with his foot on
me. "No more shall the brown men of the south Move like the ants in
lines, To quiet men with olives Or madden men with vines. "No more shall
the white towns of the south, Where Tiber and Nilus run, Sitting around
a secret sea Worship a secret sun. "The blind gods roar for Rome fallen,
And forum and garland gone, For the ice of the north is broken, And the
sea of the north comes on. "The blind gods roar and rave and dream Of
all cities under the sea, For the heart of the north is broken, And the
blood of the north is free. "Down from the dome of the world we come,
Rivers on rivers down, Under us swirl the sects and hordes And the high
dooms we drown. "Down from the dome of the world and down, Struck flying
as a skiff On a river in spate is spun and swirled Until we come to the
end of the world That breaks short, like a cliff. "And when we come to
the end of the world For me, I count it fit To take the leap like a good
river, Shot shrieking over it. "But whatso hap at the end of the world,
Where Nothing is struck and sounds, It is not, by 

[Springframework-rcp-dev] Short joke for You

[Helga M. <mit...@gm...>]

One short joke clip to cheer Your up!
http://www.tcp3.com/helga-4315

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-622) ListBinding with SingleSelectionMode does not work with spring-binding 1.0.5

[Andreas K. (JIRA) <no...@sp...>]

     [ https://jira.springsource.org/browse/RCP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Kuhtz updated RCP-622:
------------------------------

    Attachment: patch-622.diff

I think this is the patch for this problem.

> ListBinding with SingleSelectionMode does not work with spring-binding 1.0.5
> ----------------------------------------------------------------------------
>
>                 Key: RCP-622
>                 URL: https://jira.springsource.org/browse/RCP-622
>             Project: Spring Rich Client Project
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Christian Heilmann
>            Assignee: Lieven Doclo
>         Attachments: patch-622.diff
>
>
> spring richclient has a dependency to spring-binding in version 1.0.5
> The class ListBinding is catching IllegalArgumentException in the method isPropertyConversionExecutorAvailable(), but in spring-binding 1.0.5 the IllegalArgumentException was replaced by a ConversionException, and so the ListBinding with single-selection does not work with spring-binding 1.0.5.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Created: (RCP-622) ListBinding with SingleSelectionMode does not work with spring-binding 1.0.5

[Christian H. (JIRA) <no...@sp...>]

ListBinding with SingleSelectionMode does not work with spring-binding 1.0.5
----------------------------------------------------------------------------

                 Key: RCP-622
                 URL: https://jira.springsource.org/browse/RCP-622
             Project: Spring Rich Client Project
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.1.0
            Reporter: Christian Heilmann
            Assignee: Lieven Doclo


spring richclient has a dependency to spring-binding in version 1.0.5

The class ListBinding is catching IllegalArgumentException in the method isPropertyConversionExecutorAvailable(), but in spring-binding 1.0.5 the IllegalArgumentException was replaced by a ConversionException, and so the ListBinding with single-selection does not work with spring-binding 1.0.5.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira