Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Scout/NewAndNoteworthy/5.0"

(Replaced content with "The Scout documentation has been moved to https://eclipsescout.github.io/.")
 
(17 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{ScoutPage|cat=Release 5.0}}
+
The Scout documentation has been moved to https://eclipsescout.github.io/.
 
+
This page shows what you need to know about the new Eclipse [[Scout/Release/Mars| Scout 5.0]] release shipped with Eclipse [[Mars]] (Release: Wednesday, June 24, 2015).
+
 
+
 
+
== M1  ==
+
*Planned Scout Version: 4.1
+
*Release Date: August 22, 2014 (Build Date: August 20)
+
 
+
=== [RAP] Multisession Coockiestore Enabled by default ===
+
{{Bug|441555}}
+
The multisession coockie store for Scout RAP introduced with Scout 4.0 ([[Scout/NewAndNoteworthy/4.0#Multisession_Cookiestore]]) is now enabled by default.
+
 
+
== M2  ==
+
*Planned Scout Version: 4.1
+
*Release Date: October 03, 2014 (Build Date: October 01)
+
 
+
=== SDK: new entity from the Package Explorer ===
+
{{Bug|439334}}. You can now create Scout entity (Codes, Form Fields, Columns, Menus…) directly from the Package Explorer View. You now have these items directly in the context menu.
+
 
+
[[File:ScoutSDK_New_Entity_From_Package_Explorer.png]]
+
 
+
== M3  ==
+
*Planned Scout Version: 4.2
+
*Release Date: November 14, 2014 (Build Date: November 12)
+
 
+
=== [JAX-WS] JAX-WS support for Java 1.8 ===
+
{{Bug|446478}} adds support for Java 1.8 by moving Java runtime-depending code into fragments. Products using org.eclipse.scout.jaxws216 must be extended by one of the following fragments:
+
  Java 1.6, 1.7 -> org.eclipse.scout.jaxws216.'''jre16'''.fragment
+
  Java 1.8      -> org.eclipse.scout.jaxws216.'''jre18'''.fragment
+
 
+
Add the following two properties to your config.ini if you are using an OSGi runtime that is not already defining the execution environment for Java 1.8 (prior Luna release):
+
  org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6,JavaSE-1.7,JavaSE-1.8
+
  org.osgi.framework.system.capabilities.extra=osgi.ee; osgi.ee="JavaSE";version:List<Version>="1.8"
+
 
+
=== Servlet 3.1 support ===
+
{{Bug|433736}} adds basic support for running Scout with a servlet 3.1. New servlet 3.1 features are used yet.
+
 
+
For an existing project add one of the following plugins to your server product file:
+
  servlet 2.5-3.0 -> org.eclipse.scout.rt.server.servlet25
+
  servlet 3.1 -> org.eclipse.scout.rt.server.servlet31
+
 
+
=== Distinguish between left-click and right-click on table row ===
+
{{Bug|443490}} It is now possible to distinguish between left and right-clicks on table rows with :
+
AbstractTable.execRowClick(ITableRow, MouseButton)
+
 
+
=== SDK: new entity from the Java Editor ===
+
You can now create Scout entity (Codes, Form Fields, Columns, Menus…) directly from the Java Editor. You just need to open the Proposal Window (CTRL+Space) and look at the end of the list. If you do not want to scroll down, simply press the “Up-Arrow” Key, you will jump there immediately.
+
 
+
[[File:ScoutSDK_New_Entity_From_Java_Proposal.png]]
+
 
+
== M4  ==
+
*Planned Scout Version: 4.2
+
*Release Date: December 19, 2014 (Build Date: December 17)
+
 
+
=== Empty Checkboxes ===
+
{{Bug|416043}} Default behaviour for checkbox changed (AbstractBooleanField and AbstractCheckBox): A boolean field is considered empty if unchecked. Previously it was considered empty, if it did not contain any value.
+
 
+
=== ServerJobService ===
+
{{Bug|448572}} It is now possible to customize server jobs. ServerJob creation in Scout is now always done with IServerJobService.createJobFactory.
+
 
+
The server session class could previously be configured in some services (jaxws,clustersync,offlinedispatcher...) or was retrieved by naming convention. These configurations have been consolidated and use now the configuration in org.eclipse.scout.rt.server.ServerJobService#serverSessionClassName. Old properties are still read for legacy support. Please server config.ini to
+
 
+
org.eclipse.scout.rt.server.ServerJobService#serverSessionClassName=<fully qualified ServerSession name>
+
 
+
e.g.
+
 
+
org.eclipse.scout.rt.server.ServerJobService#serverSessionClassName=org.eclipsescout.helloworld.server.ServerSession
+
 
+
=== Exceptions in Pages===
+
{{Bug|452266}} Exceptions in AbstractPage#execPageActivated and AbstractPage#execPageDeactivated are now also handled by IExceptionHandlerService.
+
 
+
=== MailUtility Cleanup ===
+
{{Bug|454416}} MailUtility was moved to the subpackage mail. Methods were cleaned and signatures were changed from array ([]) to java.util.List.
+
 
+
=== Deprecate execLoadTableData() in table pages ===
+
{{Bug|444210}} <code>execLoadTableData()</code> in {{ScoutLink|Concepts|TablePage}} is now deprecated. The recommended way is to update to {{ScoutLink|Concepts|TablePageData}} for your table and to use <code>importPageData(..)</code> in the <code>execLoadData(SearchFilter)</code> method.
+
 
+
If you do not want switch to the TablePageData pattern immediately, a migration path might be to use the new <code>importTableData(Object[][])</code> method  in the <code>execLoadData(SearchFilter)</code> method.
+
Code like this:
+
<source lang="java">
+
@Override
+
protected Object[][] execLoadTableData(SearchFilter filter) throws ProcessingException {
+
  PersonSearchFormData searchFormData;
+
  //initialize searchFormData depending on the filter
+
  return SERVICES.getService(IStandardOutlineService.class).getPersonTableData(searchFormData);
+
}
+
</source>
+
 
+
Needs to be updated to something like this:
+
<source lang="java">
+
@Override
+
protected void execLoadData(SearchFilter filter) throws ProcessingException {
+
  PersonSearchFormData searchFormData;
+
  //initialize searchFormData depending on the filter
+
  importTableData(SERVICES.getService(IStandardOutlineService.class).getPersonTableData(searchFormData));
+
}
+
</source>
+
 
+
=== New system property for external configuration file ===
+
Scout supports the specification of an external configuration file in the system properties.
+
When loading the configuration Scout is retrieving the value of the system property with the key <code>external.configuration.file</code>.
+
If the value is set Scout will add the specified path to the path list of the external configurations.
+
 
+
This allows specifying the path of the config.ini in the pom.xml so that the configuration can be used with Maven Tycho.
+
(This is a workaround for the Tycho Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=356193)
+
 
+
== M5  ==
+
*Planned Scout Version: 5.0
+
*Release Date: February 06, 2015 (Build Date: February 04)
+
 
+
== M6  ==
+
*Planned Scout Version: 5.0
+
*Release Date: March 27, 2015 (Build Date: March 25)
+
 
+
== M7  ==
+
*Planned Scout Version: 5.0
+
*Release Date: May 08 , 2015 (Build Date: May 06)
+
 
+
== RC1  ==
+
*Planned Scout Version: 5.0
+
*Release Date: May 22, 2015 (Build Date: May 20)
+
 
+
== RC2  ==
+
*Planned Scout Version: 5.0
+
*Release Date: May 29, 2015 (Build Date: May 27)
+
 
+
== RC3  ==
+
*Planned Scout Version: 5.0
+
*Release Date: June 05, 2015 (Build Date:  June 03)
+
 
+
== RC4  ==
+
*Planned Scout Version: 5.0
+
*Release Date: June 12, 2015 (Build Date: June 10)
+

Latest revision as of 10:31, 18 March 2024

The Scout documentation has been moved to https://eclipsescout.github.io/.

Back to the top