Re: [struts] [S2.1.1] How to use an Interceptor from a plugin?

[Piero Sartini]

 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 part 
of the module. There are some interfaces that have to be implemented from the 
main application.

Now, my problem is how to configure this. Is it possible to use the 
struts2-mechanism of bean and constant without writing an own 
BeanSelectionProvider?

Piero

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [struts] [S2.1.1] How to use an Interceptor from a plugin?

[Jeromy Evans]

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 file?


-Dale
You're right there's no benefit in this case.  In general, the advantage 
of the plugin is that it can define beans and set constants within the 
Xwork Container (in addition to defining default packages).


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [struts] [S2.1.1] How to use an Interceptor from a plugin?

[Dale Newfield]

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]