Comments on: Modular Web Applications with SpringSource Slices

By: Ben Hale

Ben Hale — Mon, 15 Mar 2010 11:22:40 +0000

@Alexi

You are correct that we're moving Slices from a prototype over to a proper project at the moment and during this time we've taken a step back to work on some of the interesting use-cases we identified. As you've seen we are working on bringing the concept of a 'service registry' to applications outside of OSGi, but I would hesitate to refer to it as lightweight OSGi (specifically, Slices does not address runtime modularity at all).

Because some of the features from the prototype require base functionality like a service registry to work, they will necessarily come after the low-level infrastructure being created for Slices. Rest assured that before long modular web application behavior will return to Slices in both OSGi and non-OSGi environments. I encourage you to keep an eye on this blog as well as the Slices JIRA (https://jira.springsource.org/browse/SLICE) for details about when these features are ready.

Thanks for your interest in the project, and I hope that you're as excited as I am to see what will come.

By: alexi

alexi — Fri, 12 Mar 2010 02:37:51 +0000

As I know, slice will become a standalone spring project (not depend on osgi) since spring dm server will move to eclipse foundation. I do find the latest source code begin to support deploying slice into standard web container such as tomcat. But from the sample, I can not find modular "WEB" application. I mean a standard war as a slice which can be attached to the host webapp. It is more like a lightweight osgi container (we can define service as slice(bundle), and other slice or webapp can refer the servie).

By: dan

dan — Thu, 11 Mar 2010 17:01:43 +0000

is the license free? lib/dm-server-license.html says it is non-redistributable

By: Chandler

Chandler — Mon, 08 Mar 2010 11:33:05 +0000

How can I package slices-api.jar from the slices source dir ?
I am getting that error as it is missing during installation of slices into spring dm.

Thanks

By: alexi

alexi — Mon, 08 Feb 2010 08:13:23 +0000

I defined http url intercept in applicationContext.xml.It works when I access directly a protected page in the slice by inputting its address in the browser's address box.

But the security tag defined in jsp page does not work. After debugging, I find it used the root webapplicationContext instead of the slice's.

By: Alexi

Alexi — Sun, 07 Feb 2010 04:48:07 +0000

By the way it is possible to define another authentication provider? It is possible that a sub module (a slice) may need to check authorities against another source.

By: Alexi

Alexi — Sun, 07 Feb 2010 04:44:48 +0000

Obviously the blog forbid me pasting code. Here is the simple one.
s:intercept-url pattern="/" access="isAuthenticated()

By: Alexi

Alexi — Sun, 07 Feb 2010 04:43:43 +0000

By: Alexi

Alexi — Sun, 07 Feb 2010 04:40:39 +0000

@Andy, thanks for your reply. When I try to define security attributes in a slice's application context, it does not work. Here is my configuration.

Since it is a modular framework, obviously http access control should be defined in the slices as above. Did I miss something? As you said, slices does not support listeners and filters locally. I suppose the only thing I need to configure is the above lines. I do try to add listeners and filter springSecurityFilterChain, it does not work.

By: Andy Wilkinson

Andy Wilkinson — Tue, 26 Jan 2010 10:12:24 +0000

@Alexi, yes, a host and its slices share the same HTTP session. The HTTP session is partitioned to prevent naming clashes. This means that a Slice cannot overwrite an entry that was set by its host but, in the absence of a Slice specific value having been set, a Slice will get the Host's value.