|Re: [scout-dev] Release Notes Eclipse Scout Trunk (Juno, 3.8.0)|
When renaming the fragment bundles, why don’t we use a consistent naming scheme?
Maybe I’m just missing the rule behind the chosen naming scheme?
When adding more and more database engines and versions, a clean naming scheme would be desirable.
The names of the Fragments had to be renamed:
The names include the full version if necessary. The full version is now after the name with build-qualifier.
The version in the name conflicted with the version from the build.
If you already checked out the new fragments you have to check them out again. If you already changed your products and features you have to correct them.
You are receiving this e-Mail because you are subscribed to Eclipse Scout Trunk.
If you are not using ServletFilters you can ignore this e-Mail.
In reference to Bug 361256 (http://bugs.eclipse.org/bugs/show_bug.cgi?id=361256) the following fragments were created:
Authentication of Scout web projects (RAP, Wicket) has to be done in the 'client-server' part where the 'org.eclipse.scout.rt.server' bundle
is not accessible. So all security filters have been moved to the 'org.eclipse.scout.http.servletfilter' bundle. Since scout does also provide
datasource security filters JDBC connections have to get accessed from the server and servletfilter bundle. In case of 'org.eclipse.scout.http.servletfilter'
a ClassNotFound exception of the jdbc driver gets thrown.
Moved all jdbc driver jars to separate fragments having the 'system.bundle' as host bundle. Fragments to the system bundle can be accessed from
every bundle in the osgi.
Add the corresponding jdbc driver fragment to your product file.
E.g. having the 'com.bsiag.scout.rt.server.jdbc.oracle11g2' bundle you need also 'com.oracle.oracle11g.jdbc_11.2.0.fragment' in your product files.
Release: Juno, 3.8.0
Update Site: http://download.eclipse.org/scout/nightly/update/
Description: S/MIME cryptographic signature