If you don't intend to have your application's package extend the
package defined in your plugin (which doesn't scale to multiple
plugins), what's the benefit of having this be a plugin as opposed to
just a .jar file?
I hoped that the plugin architecture will help me with the configuration
Dale Newfield wrote:
Jeromy Evans wrote:
You're following the right approach.
If you don't intend to have your application's package extend the
package defined in your plugin (which doesn't scale to multiple
plugins), what's the benefit of having this be a plugin as opposed to
just a .jar
Hello,
I am trying to write an authentication plugin for struts2. Goal is to reuse it
across several projects so a plugin seems the way to go..
There is an Interceptor defined in struts-plugin.xml, lets call it
AuthenticationInterceptor. Problem is that I am not able to use it in my main
You're following the right approach.
Is the interceptor defined in your package?
Normally either the plugin defines a package in struts-plugin.xml and
your application extends that package, or your application needs to
define the interceptor with an interceptor name=... tag. Also don't
Am Mittwoch, 27. Februar 2008 01:59:36 schrieb Jeromy Evans:
You're following the right approach.
..
In any case, the approach works so you probably just have a minor config
error. Post your config (struts-plugin.xml and struts.xml) if the
statement above doesn't help.
Thank you, that
Jeromy Evans wrote:
You're following the right approach.
If you don't intend to have your application's package extend the
package defined in your plugin (which doesn't scale to multiple
plugins), what's the benefit of having this be a plugin as opposed to
just a .jar file?
-Dale
6 matches
Mail list logo
