Hi,
some of the set-back
jboss.net features (advanced xdoclet support, uddi server) have just been
reactivated in head (together with a revamped documentation also to be found
under http://www.jboss.org/developers/projects/jboss/dotnet).
The external-service
redeployment problem due to apache commons hanging on to a disposed application
classloader has also been fixed (commons-discovery is initialised upon starting
of the axis service such that no application classloader will be cached
there).
There is still a
problem with axis meta-data sometimes referring to cycled classes (I
love their caches, if not caches in general ;-( and leading to
illegalarguments and such. Left also remains the whole WS4EE part, because that must go
through some rearchitecturing before ...
Best,
CGJ
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
