Loading/unloading of modules is tricky. It's something an application
server can do, but not necessarily an application framework like
Tapestry.
Notice the leaky abstractions around components, to support reloading
(and transformation) of them. The reloading requires a special class
loader, and t
Interesting, espscially
https://issues.apache.org/jira/browse/TAPESTRY-1904 and
https://issues.apache.org/jira/browse/TAPESTRY-1679.
I've another question. Do you think there's a need for loading/
unloading modules? This would add a very powerful feature the Java world
does leak in comparison
You can see that there are a few issues in JIRA to make the IoC stuff
(even) more refactoring-safe.
On Sun, May 4, 2008 at 11:06 PM, Michael Gerzabek
<[EMAIL PROTECTED]> wrote:
> Thank you Howard,
>
> It was a typo after a refactoring (DatabaseManager |->
> DatabaseUpdateManager). I didn't check
Thank you Howard,
It was a typo after a refactoring (DatabaseManager |->
DatabaseUpdateManager). I didn't check the update textual occurences in
eclipse.
Lewis Ship schrieb:
The most common case for this is that the module class defining the
service, or the module class containing the contr
The most common case for this is that the module class defining the
service, or the module class containing the contribution to the
service, is not being loaded. Please refer to the docs on how to
ensure that modules are loaded.
On Tue, Apr 29, 2008 at 2:10 AM, Michael Gerzabek
<[EMAIL PROTECTED]
Hi,
I've a Service that extends ApplicationInitializerFilter:
public interface DatabaseUpdateManager extends
ApplicationInitializerFilter {
public void update() throws SQLException;
}
I made it a service because I thought then it would be easy to collect
contributions from other modules.
