Menu
▾
▴
springframework-rcp-dev — Spring Rich Client developer list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(37) |
Jun
(141) |
Jul
(111) |
Aug
(91) |
Sep
(79) |
Oct
(151) |
Nov
(161) |
Dec
(93) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(40) |
Feb
(60) |
Mar
(43) |
Apr
(90) |
May
(31) |
Jun
(114) |
Jul
(35) |
Aug
(112) |
Sep
(305) |
Oct
(151) |
Nov
(122) |
Dec
(103) |
| 2006 |
Jan
(65) |
Feb
(57) |
Mar
(475) |
Apr
(276) |
May
(482) |
Jun
(134) |
Jul
(127) |
Aug
(188) |
Sep
(271) |
Oct
(220) |
Nov
(74) |
Dec
(41) |
| 2007 |
Jan
(121) |
Feb
(50) |
Mar
(36) |
Apr
(11) |
May
(31) |
Jun
(12) |
Jul
(73) |
Aug
(41) |
Sep
(59) |
Oct
(33) |
Nov
(60) |
Dec
(111) |
| 2008 |
Jan
(139) |
Feb
(49) |
Mar
(87) |
Apr
(43) |
May
(10) |
Jun
(25) |
Jul
(114) |
Aug
(17) |
Sep
(25) |
Oct
(199) |
Nov
(94) |
Dec
(45) |
| 2009 |
Jan
(36) |
Feb
(14) |
Mar
(29) |
Apr
(32) |
May
(49) |
Jun
(18) |
Jul
(68) |
Aug
(34) |
Sep
(34) |
Oct
(11) |
Nov
(10) |
Dec
(14) |
| 2010 |
Jan
(35) |
Feb
(12) |
Mar
(23) |
Apr
(17) |
May
(4) |
Jun
(1) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
|
Nov
(10) |
Dec
|
| 2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2012 |
Jan
(2) |
Feb
(1) |
Mar
(8) |
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
(3) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(8) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(3) |
Dec
(4) |
| 2014 |
Jan
(2) |
Feb
(2) |
Mar
(3) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(15) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Craig H. (JIRA) <no...@sp...> - 2008-03-05 09:44:05
|
Document upgrade path for custom StatusBar implementations
----------------------------------------------------------
Key: RCP-546
URL: http://jira.springframework.org/browse/RCP-546
Project: Spring Framework Rich Client Project
Issue Type: Task
Components: Documentation
Environment: All
Reporter: Craig Holbrook
Priority: Minor
In release 0.2.1 the org.springframework.richclient.progress.StatusBarCommandGroup was used for specifying StatusBar implementations. In the latest snapshot, this has now been replaced by the org.springframework.richclient.application.statusbar.StatusBar interface. A concrete implementation of this interface is required by the ApplicationLifecycleAdvisor.
The documentation needs to be updated to advise the user on the correct upgrade path, and references to the deprecated StatusBarCommandGroup need to also be updated / removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. <jh...@sc...> - 2008-03-05 09:39:37
|
Hi, As you may know, we had planned to have a Spring Richclient 1.0 release somewhere at the end of Januari. It's March already and no release has been pushed out. Don't start to panic just yet, I'll let you in on the details. Somewhere in Januari I contacted the people of SpringSource to discuss the position of Spring Richclient within the Spring universe. As we're in different parts of the world, it takes some time to schedule a meeting online and contact the right people, thus time was creeping past the previously set release date. Our goal with this meetings was to not only discuss the present and future of the project but also the involvement of SpringSource. The outcome is the following. Current codebase: We have set a new target date for the release: March 17. All bugs should be fixed while documentation will be provided as needed. We don't want this to delay the release date anymore and interfere with our future plans. If documentation is requested at some point, we'll provide this on the developer blog. This release will have maintenance updates as requested. Future plans: We've decided to start a new codebase and re-brand the project to Spring Desktop. One of the reasons behind this is the possibility to update the existing core techniques after some research. The current codebase core is about two years old, quite stable but not state-of-the-art anymore. Another reason is that this allows us to start with the modularity in mind and review the existing codebase. We're doing some research in several areas right now and plan to start with the codebase right after the Spring Richclient 1.0 release. We'll take advantage of this new start to shift to the SpringSource infrastructure (svn) as well. The aim is to align Spring Desktop 1.0 (mind the name!) with the next big Spring release train somewhere in October. SpringSource will help us out by providing the infrastructure, being involved in the defining of the project (scope/roadmap) and devoting some time for research and coding. They've made it clear that they find this project to be valuable and want to align it with the future Spring release. I hope this clears things up and removes any doubt about where this project stands and is heading towards. ps: if you're enchanted by these words don't hesitate to pull up your sleeves and help us out by sending in patches/documentation or just by providing us with your feedback at the forum (http://forum.springframework.org/forumdisplay.php?f=28) or the developers maillist (spr...@li...). Kind Regards, Jan **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm |
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 19:04:12
|
[ http://jira.springframework.org/browse/RCP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-308.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
After examining the defaultFormModel, I noticed that there are two types of exceptions that can originate from the conversion or the beanwrapper that can be seen as binding errors. I've refined the catch level to only catch these two types. Additionally the log level is set to warn to indicate a possible problem.
Fixed in:
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1997
> DefaultFormModel should log exception as a warning or error
> -----------------------------------------------------------
>
> Key: RCP-308
> URL: http://jira.springframework.org/browse/RCP-308
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Affects Versions: 0.2.0
> Reporter: Benoit Xhenseval
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
>
> As discussed in http://forum.springframework.org/showthread.php?t=23797
> DefaultFormModel catches an exception on line 286 but simply logs it as a debug.
> It is probably better to log it as a warning or error.
> so I suggest replacing:
> ...
> }
> catch (Exception e) {
> logger.debug("Exception occurred setting value", e);
> raiseBindingError(this, value, e);
> }
> by
> ...
> }
> catch (Exception e) {
> logger.warn("Exception occurred setting value", e);
> raiseBindingError(this, value, e);
> }
> Thank you
> Benoit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 14:29:12
|
[ http://jira.springframework.org/browse/RCP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32803 ]
Jan Hoskens commented on RCP-308:
---------------------------------
As I've mentioned on the list (http://thread.gmane.org/gmane.comp.java.springframework.rcp.devel/4997) I still think we should have a Binding exception to filter out the specific exceptions and log these as warnings. Any other exceptions should be thrown up.
I'll have a look at this.
> DefaultFormModel should log exception as a warning or error
> -----------------------------------------------------------
>
> Key: RCP-308
> URL: http://jira.springframework.org/browse/RCP-308
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Affects Versions: 0.2.0
> Reporter: Benoit Xhenseval
>
> As discussed in http://forum.springframework.org/showthread.php?t=23797
> DefaultFormModel catches an exception on line 286 but simply logs it as a debug.
> It is probably better to log it as a warning or error.
> so I suggest replacing:
> ...
> }
> catch (Exception e) {
> logger.debug("Exception occurred setting value", e);
> raiseBindingError(this, value, e);
> }
> by
> ...
> }
> catch (Exception e) {
> logger.warn("Exception occurred setting value", e);
> raiseBindingError(this, value, e);
> }
> Thank you
> Benoit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 14:21:09
|
[ http://jira.springframework.org/browse/RCP-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-438.
---------------------------
Assignee: Jan Hoskens (was: Peter De Bruycker)
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed in
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1996
Thanks for the patch
> Inline validation of Integer fields
> -----------------------------------
>
> Key: RCP-438
> URL: http://jira.springframework.org/browse/RCP-438
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Affects Versions: 0.2.1
> Reporter: Danie Roux
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
> Attachments: RCP-438.patch
>
> Original Estimate: 0d
> Remaining Estimate: 0d
>
> Validation does not execute after initial key-press.
> For example:
> Fails validation
> a9999
> .09js
> Passes validation
> 9aaaa
> 1.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 13:50:05
|
[ http://jira.springframework.org/browse/RCP-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-467.
---------------------------
Assignee: Jan Hoskens (was: Peter De Bruycker)
Resolution: Fixed
Fix Version/s: 1.0.0
Moved samples to correct subdirs.
One exception is the petclinic. I opted to have the groupId include the postfix petclinic and subprojects to start with petclinic-xxx. This reflects a real situation of spring-rcp usage except for the parent relation between the petclinic and the spring-richclient-samples artifact.
> the links to checkout the sample petclinic does not work
> --------------------------------------------------------
>
> Key: RCP-467
> URL: http://jira.springframework.org/browse/RCP-467
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Samples
> Reporter: Bart Van den Abeele
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
>
> http://spring-rich-c.sourceforge.net/spring-richclient-samples/source-repository.html
> In this page there is a corrupt link to checkout the petclinic-sample with svn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 09:15:05
|
[ http://jira.springframework.org/browse/RCP-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32785 ]
Jan Hoskens commented on RCP-467:
---------------------------------
I would think it better to move the samples to their correct dir would fix all problems regarding urls. The one mentioned is already fixed because we've moved all projects under spring-richclient to the correct named dirs. Only the samples are still in their old location.
I'll move the samples to the dirs as expected by the maven convention.
> the links to checkout the sample petclinic does not work
> --------------------------------------------------------
>
> Key: RCP-467
> URL: http://jira.springframework.org/browse/RCP-467
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Samples
> Reporter: Bart Van den Abeele
> Assignee: Peter De Bruycker
> Priority: Minor
>
> http://spring-rich-c.sourceforge.net/spring-richclient-samples/source-repository.html
> In this page there is a corrupt link to checkout the petclinic-sample with svn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 08:37:12
|
[ http://jira.springframework.org/browse/RCP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32783 ]
Jan Hoskens commented on RCP-309:
---------------------------------
I think it would be better to have the whole site generated at a specific versioned url. This way all documentation is archived for each RCP version and keeps being consistent. We could then forward 'http://spring-rich-c.sourceforge.net' to the latest release.
Latest release can add a link to the previously generated apidocs (or whatever is needed). A new release can generate its site and only when everything is in order, the forwarding is to be changed to the new version.
So I'm adding the ${project.version} variable to the site deployment url.
> Archive the website for each release
> ------------------------------------
>
> Key: RCP-309
> URL: http://jira.springframework.org/browse/RCP-309
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.1.0
> Reporter: Larry Streepy
> Assignee: Geoffrey De Smet
>
> Original issue:
> 1. Look at the deployed RCP website on sourceforge at http://spring-rich-c.sourceforge.net, nevigate to any of the module, support for example.
> 2. On that page, navigate to the javadocs.
> 3. Note the title Spring richclient support 0.2.0-SNAPSHOT API instead of Spring richclient support 0.1.0-SNAPSHOT API
> New issue:
> Archive the website on every release and place a link in site.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 07:38:05
|
[ http://jira.springframework.org/browse/RCP-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-526.
---------------------------
Assignee: Jan Hoskens
Resolution: Cannot Reproduce
Fix Version/s: 1.0.0
I cannot reproduce the problem. It does look like the lockup is caused by the glazedlist lock as previously mentioned.
Please reopen if you can attach a sample that reproduces this.
> Application locking up during startup
> -------------------------------------
>
> Key: RCP-526
> URL: http://jira.springframework.org/browse/RCP-526
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Application Framework
> Affects Versions: 0.2.1
> Environment: Command line using Java 1.6_03
> Eclipse 3.3 running Java 1.6_03
> Java Web Start using Java 1.6_03
> Reporter: Ron Johnson
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
>
> I'm seeing my application lock up randomly during startup. I'm using the TabbedApplicationPage, and after getting a stack trace I can see that its locking during the call to DefaultApplicationWindow.setActivePage. I see this occur from the command line, in the Eclipse IDE and as a Java Web Start download. I'm using Java 1.6_03 and I see this occur in all three environments (command line, Eclipse 3.3, and Java Web Start). Any idea what may be causing this?
> "main" prio=6 tid=0x00a30400 nid=0xe18 waiting on condition [0x00c5f000..0x00c5fe54]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x02e59e48> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
> at java.util.concurrent.locks.LockSupport.park(Unknown Source)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown Source)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(Unknown Source)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(Unknown Source)
> at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(Unknown Source)
> at ca.odell.glazedlists.impl.java15.LockAdapter.lock(J2SE50LockFactory.java:74)
> at ca.odell.glazedlists.swing.EventTableModel.getRowCount(EventTableModel.java:162)
> at javax.swing.JTable.getRowCount(Unknown Source)
> at javax.swing.plaf.basic.BasicTableUI.createTableSize(Unknown Source)
> at javax.swing.plaf.basic.BasicTableUI.getPreferredSize(Unknown Source)
> at javax.swing.JComponent.getPreferredSize(Unknown Source)
> at javax.swing.ScrollPaneLayout.layoutContainer(Unknown Source)
> at java.awt.Container.layout(Unknown Source)
> at java.awt.Container.doLayout(Unknown Source)
> at java.awt.Container.validateTree(Unknown Source)
> at java.awt.Container.validateTree(Unknown Source)
> at java.awt.Container.validateTree(Unknown Source)
> at java.awt.Container.validateTree(Unknown Source)
> at java.awt.Container.validateTree(Unknown Source)
> at java.awt.Container.validate(Unknown Source)
> - locked <0x034978c0> (a java.awt.Component$AWTTreeLock)
> at org.springframework.richclient.application.support.DefaultApplicationWindow.setActivePage(DefaultApplicationWindow.java:48)
> at org.springframework.richclient.application.support.AbstractApplicationWindow.showPage(AbstractApplicationWindow.java:194)
> at org.springframework.richclient.application.support.AbstractApplicationWindow.showPage(AbstractApplicationWindow.java:161)
> at org.springframework.richclient.application.Application.openWindow(Application.java:148)
> at org.springframework.richclient.application.Application.start(Application.java:210)
> at org.springframework.richclient.application.ApplicationLauncher.launchMyRichClient(ApplicationLauncher.java:223)
> at org.springframework.richclient.application.ApplicationLauncher.<init>(ApplicationLauncher.java:103)
> at com.vzbi.cpemgr.dc.app.CPEManagerClient.main(CPEManagerClient.java:63)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 07:32:06
|
[ http://jira.springframework.org/browse/RCP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32772 ]
Jan Hoskens commented on RCP-376:
---------------------------------
This is a direct consequence of the fact that multiple applicationwindows can exist. This was fixed by having the commands.xml parsed anew on each creation of a new window. Commands needing the applicationwindow would then get the correct applicationwindow injected because of their separated commands context. Note that using the applicationWindowAware interface on any object outside of the commands.context won't work.
Currently these are the possible solutions I can think of:
1) remove the applicationWindowAware interface. Always use the Application.getInstance().getActiveWindow(). Any object needing the window can get the active one at that time. No multiple instances needed.
2) add something like an ApplicationWindowScope that instantiates the object again with the correct window. Note that we'll have multiple instances and that each instance should be kept in a kind of 'session' of the ApplicationWindow so that it can be created/retrieved correctly by the scope. When an object implementing the ApplicationWindowAware interface is needed, the scope looks in the ApplicationWindow 'session' to see if an object with that id already exists, if not one is created and returned, otherwise the object found is returned.
Currently I tend to lean towards 1) as this seems the easiest way: no need for multiple instances, no need for a 'session' storage at applicationWindow level. Note that even with the ApplicationWindowScope a call to getActiveWindow() is probably needed. I'll let this thought ripe for another day before I actually make the changes.
> null application window
> -----------------------
>
> Key: RCP-376
> URL: http://jira.springframework.org/browse/RCP-376
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Ryan Sonnek
>
> My action command executor extends the ApplicationWindowAwareCommand, yet when I run the command, I get a null pointer exception.
> how does the application window get initialized on my object?
> public class ApplicationWindowProgressMonitorActionCommandExecutor extends ApplicationWindowAwareCommand implements ActionCommandExecutor {
> private final ParameterizableActionCommandExecutor delegate;
> public ApplicationWindowProgressMonitorActionCommandExecutor(ParameterizableActionCommandExecutor delegate) {
> this.delegate = delegate;
> }
> protected void doExecuteCommand() {
> BusyIndicator.showAt(getApplicationWindow().getControl());
> getProgressMonitor().taskStarted(getText(), StatusBar.UNKNOWN);
> delegate.execute(getParameters());
> BusyIndicator.clearAt(getApplicationWindow().getControl());
> getProgressMonitor().done();
> }
> private ProgressMonitor getProgressMonitor() {
> return getApplicationWindow().getStatusBar().getProgressMonitor();
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-03 18:23:06
|
[ http://jira.springframework.org/browse/RCP-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-538.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
patch applied.
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1985
> Invalid link (dialogs:wizards) in spring-richclient-manual
> ----------------------------------------------------------
>
> Key: RCP-538
> URL: http://jira.springframework.org/browse/RCP-538
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 1.0.0
> Reporter: Robert Munteanu
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: wizards.diff
>
>
> The chapter id dialogs:wizards causes both Firefox / Opera / W3M to attempt to locate a 'dialog' handler.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-03 18:15:09
|
[ http://jira.springframework.org/browse/RCP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-543.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
When using the PropertyConstraintProvider and a null property is provided to the RulesValidator all properties should be checked. This was lacking and because of the recently committed change that emptied the messages upon validating the whole object, no new messages were added.
Additionally several visual components (backing pages etc) were triggering the form validation. This should not be necessary as the validation is triggered upon value change of each valueModel and upon validator change. Any object using validation results/events should therefor initialize correctly and then only listen to changes (thus no explicit triggering of validate()).
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1984
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1983
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1981
> LoginForm accepts empty username/password --> NPE
> -------------------------------------------------
>
> Key: RCP-543
> URL: http://jira.springframework.org/browse/RCP-543
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Affects Versions: 1.0.0
> Environment: Linux
> Reporter: Johannes Schneider
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
>
> The rules that require a username/password are not applied immediately.
> If the form is opened and ok clicked immediatly a NPE is thrown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-03-03 15:09:07
|
[ http://jira.springframework.org/browse/RCP-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32743 ]
Lieven Doclo commented on RCP-545:
----------------------------------
this needs java5 by the way
> Provide a binder for Enum values that displays a list of radio buttons
> ----------------------------------------------------------------------
>
> Key: RCP-545
> URL: http://jira.springframework.org/browse/RCP-545
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Binding System
> Reporter: Lieven Doclo
> Attachments: EnumRadioButtonBinder.java, EnumRadioButtonBinding.java
>
>
> This can be useful in some situations, see Designing interfaces (limited choices)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-03-03 15:07:05
|
[ http://jira.springframework.org/browse/RCP-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lieven Doclo updated RCP-545:
-----------------------------
Attachment: EnumRadioButtonBinding.java
EnumRadioButtonBinder.java
java files for the binder/binding
> Provide a binder for Enum values that displays a list of radio buttons
> ----------------------------------------------------------------------
>
> Key: RCP-545
> URL: http://jira.springframework.org/browse/RCP-545
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Binding System
> Reporter: Lieven Doclo
> Attachments: EnumRadioButtonBinder.java, EnumRadioButtonBinding.java
>
>
> This can be useful in some situations, see Designing interfaces (limited choices)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-03-03 15:05:15
|
Provide a binder for Enum values that displays a list of radio buttons
----------------------------------------------------------------------
Key: RCP-545
URL: http://jira.springframework.org/browse/RCP-545
Project: Spring Framework Rich Client Project
Issue Type: New Feature
Components: Binding System
Reporter: Lieven Doclo
This can be useful in some situations, see Designing interfaces (limited choices)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-03 12:05:10
|
[ http://jira.springframework.org/browse/RCP-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-544.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed typo
> Wrong LoginCommand javadoc comment
> ----------------------------------
>
> Key: RCP-544
> URL: http://jira.springframework.org/browse/RCP-544
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Command System
> Reporter: Stevo Slavic
> Assignee: Jan Hoskens
> Priority: Trivial
> Fix For: 1.0.0
>
>
> Instead of:
> * <pre>
> * <bean id="placeholderConfigurer"
> * class="org.springframework.beans.factory.config.PropertiesPlaceholderConfigurer"/>
> *
> it should be:
> * <pre>
> * <bean id="placeholderConfigurer"
> * class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
> *
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Nils O. (JIRA) <no...@sp...> - 2008-03-02 10:41:07
|
[ http://jira.springframework.org/browse/RCP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32722 ]
Nils Olsson commented on RCP-508:
---------------------------------
Hi (I just noticed this jira issue)
I was in a need for a more advanced toolbar, so I search the forum but I didn't find any solution so I made my own [RCP-542]. I don't know if that solution gets obsolete when this patch is applied or if the combination of the patches will make the handling of the toolbar even more developer friendly, maybe you guys can have a look.
> Improve configurability of toolbar creation
> -------------------------------------------
>
> Key: RCP-508
> URL: http://jira.springframework.org/browse/RCP-508
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Command System
> Affects Versions: 0.2.1
> Reporter: Jonny Wray
> Assignee: Peter De Bruycker
> Attachments: spring-rcp-support-relative.patch.txt, spring-rcp-support.patch
>
>
> In attempting to integrate the Jide action framework into Spring RCP I've come across a number of places where the configuration of the toolbars could be improved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Stevo S. (JIRA) <no...@sp...> - 2008-03-01 20:32:07
|
Wrong LoginCommand javadoc comment
----------------------------------
Key: RCP-544
URL: http://jira.springframework.org/browse/RCP-544
Project: Spring Framework Rich Client Project
Issue Type: Bug
Components: Command System
Reporter: Stevo Slavic
Priority: Trivial
Instead of:
* <pre>
* <bean id="placeholderConfigurer"
* class="org.springframework.beans.factory.config.PropertiesPlaceholderConfigurer"/>
*
it should be:
* <pre>
* <bean id="placeholderConfigurer"
* class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Johannes S. (JIRA) <no...@sp...> - 2008-02-29 12:41:10
|
LoginForm accepts empty username/password --> NPE
-------------------------------------------------
Key: RCP-543
URL: http://jira.springframework.org/browse/RCP-543
Project: Spring Framework Rich Client Project
Issue Type: Bug
Affects Versions: 1.0.0
Environment: Linux
Reporter: Johannes Schneider
The rules that require a username/password are not applied immediately.
If the form is opened and ok clicked immediatly a NPE is thrown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Nils O. (JIRA) <no...@sp...> - 2008-02-26 20:00:23
|
[ http://jira.springframework.org/browse/RCP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nils Olsson updated RCP-542:
----------------------------
Attachment: RCP-542.patch
> Create more advanced toolbars by adding components.
> ---------------------------------------------------
>
> Key: RCP-542
> URL: http://jira.springframework.org/browse/RCP-542
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Command System
> Reporter: Nils Olsson
> Priority: Minor
> Attachments: RCP-542.patch
>
>
> By adding this patch it will be possible to add Components to the toolbar through a CommandGroupFactoryBean.
> <bean id="toolBar" class="org.springframework.richclient.command.CommandGroupFactoryBean">
> <property name="members">
> <list>
> <ref bean="yourComponent"/>
> </list>
> </property>
> </bean>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Nils O. (JIRA) <no...@sp...> - 2008-02-26 19:58:24
|
Create more advanced toolbars by adding components.
---------------------------------------------------
Key: RCP-542
URL: http://jira.springframework.org/browse/RCP-542
Project: Spring Framework Rich Client Project
Issue Type: Improvement
Components: Command System
Reporter: Nils Olsson
Priority: Minor
By adding this patch it will be possible to add Components to the toolbar through a CommandGroupFactoryBean.
<bean id="toolBar" class="org.springframework.richclient.command.CommandGroupFactoryBean">
<property name="members">
<list>
<ref bean="yourComponent"/>
</list>
</property>
</bean>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-02-26 10:11:24
|
[ http://jira.springframework.org/browse/RCP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32512 ]
Jan Hoskens commented on RCP-508:
---------------------------------
I'm going to change the return type of all methods in the ButtonFactory to AbstractButton. JCheckBox and JRadioButton both may have a custom implementation that don't extend them.
> Improve configurability of toolbar creation
> -------------------------------------------
>
> Key: RCP-508
> URL: http://jira.springframework.org/browse/RCP-508
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Command System
> Affects Versions: 0.2.1
> Reporter: Jonny Wray
> Assignee: Peter De Bruycker
> Attachments: spring-rcp-support-relative.patch.txt, spring-rcp-support.patch
>
>
> In attempting to integrate the Jide action framework into Spring RCP I've come across a number of places where the configuration of the toolbars could be improved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-02-26 08:00:26
|
[ http://jira.springframework.org/browse/RCP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-541.
---------------------------
Assignee: Jan Hoskens
Resolution: Duplicate
Fix Version/s: 1.0.0
As described in the comment by Jonny Wray, this is covered by another issue (RCP-508) therefor marking & closing issue as duplicate.
> ButtonFactory should return AbstractButton
> ------------------------------------------
>
> Key: RCP-541
> URL: http://jira.springframework.org/browse/RCP-541
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Binding System
> Affects Versions: 1.0.0
> Reporter: Johannes Schneider
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
> Attachments: Button.patch
>
>
> org.springframework.richclient.factory.ButtonFactory#createToggleButton should return an AbstractButton.
> This is necessary to return own implementations (e.g. JideToggleButton) that don't extend JToggleButton.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-02-26 07:58:24
|
[ http://jira.springframework.org/browse/RCP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32507 ]
Jan Hoskens commented on RCP-541:
---------------------------------
(copied from maillist, originally by Jonny Wray)
Johannes,
This is covered by a previous issue, and associated patches I created
http://jira.springframework.org/browse/RCP-508
that addresses both this and some other aspects of toolbar
configurability. I came at this while attempting to integrate some of
the JIDE action framework concepts.
Jonny
> ButtonFactory should return AbstractButton
> ------------------------------------------
>
> Key: RCP-541
> URL: http://jira.springframework.org/browse/RCP-541
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Binding System
> Affects Versions: 1.0.0
> Reporter: Johannes Schneider
> Attachments: Button.patch
>
>
> org.springframework.richclient.factory.ButtonFactory#createToggleButton should return an AbstractButton.
> This is necessary to return own implementations (e.g. JideToggleButton) that don't extend JToggleButton.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jonny W. <jwr...@gm...> - 2008-02-25 22:29:34
|
Johannes, This is covered by a previous issue, and associated patches I created http://jira.springframework.org/browse/RCP-508 that addresses both this and some other aspects of toolbar configurability. I came at this while attempting to integrate some of the JIDE action framework concepts. Jonny On Feb 25, 2008, at 1:31 PM, Johannes Schneider (JIRA) wrote: > > [ http://jira.springframework.org/browse/RCP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Johannes Schneider updated RCP-541: > ----------------------------------- > > Attachment: Button.patch > >> ButtonFactory should return AbstractButton >> ------------------------------------------ >> >> Key: RCP-541 >> URL: http://jira.springframework.org/browse/RCP-541 >> Project: Spring Framework Rich Client Project >> Issue Type: Improvement >> Components: Binding System >> Affects Versions: 1.0.0 >> Reporter: Johannes Schneider >> Attachments: Button.patch >> >> >> org >> .springframework >> .richclient.factory.ButtonFactory#createToggleButton should return >> an AbstractButton. >> This is necessary to return own implementations (e.g. >> JideToggleButton) that don't extend JToggleButton. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the > administrators: http://jira.springframework.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
406 messages has been excluded from this view by a project administrator.
