> I have the following use case. I have a cache
> (subclass of java.util.Map) into which I put keys and
> values (which all have to be serializable). Let's
> take an example:
> Cache c;
> c.put("name", "Bela Ban");
> Whenever I put a new entry, it will be replicated to
> all cache instances. Caches can be in different
> processes, on different machines etc.
> Now consider a class Person with attrs name and age
> that I put into the cache:
> Person p=new Person("Bela Ban, 37);
> cache.put("bela", p);
> Now the entry will be replicated to all instances of
> the replicated cache. But when someone does
> the new value of p's age will not be replicated
> unless we put the item back into the cache:
> c.put("bela", p);
> See my problem ? If people forget to invoke the put()
> method, the values in the caches are going to become
Don't understand what would be the difference between intercepting methods and interception fields here.
Just do this.
public class CacheInterceptor
public Object invoke(Invocation invocation) ...
Method method = invocation.getMethod();
Object rtn = invocation.invokeNext();
> Now one could argue that this it is the programmer's
> fault, but it would be nice to take care of these
> things automatically.
> Another nice aspect would be that we would know
> exactly which field have changed, and therefore only
> replicated the field which actually changed, *not*
> the entire object. We currently replicate the entire
> object in HTTPSession replication and in clustering
> (stateful session beans).
I think this could be done as long as the app developer follows the getter/setter semantic.
Nukes integrates with JSPWiki, you can search "wiki" in the nukes user forum
this site uses a modified version of jspwiki.
here are two links on the topic
there have been other discussions about buiilding a native wiki module, but no one has taken up the task. this wiki does have some issues (ie: it doesn't always properly save a page), so "buyer beware" :)
hrm... since i want to setup a wiki myself, maybe i should look into a native nukes module.
i'll take a look at xwiki and see what the possibilities are.
julien: didn't you say that bill wrote a parser for wiki html tags, where can i find that?
+1 for a real wiki module
where is that wiki parser so i can look into it - i should be able to hook into the existing html module as a base for the version history.
There is no written parser yet.
Actually the wiki parser must be integrated through the parser stack framework sitting in the common module.
Then the HTML module must be capable to interpret some files with a specialized content type "text/wiki" and render it. That would be an internal content type and the real content type is "text/html".
The interest of the parser stack integration is the unified use of this framework and the reuse accross different modules like news and of course the forum.
There is a offline wiki module in JBoss cvs (I think Scott Stark wrote that). Alternatively, you could consider looking at radeox.