Change to WCI registration proposal
by Matt Wringe
There have been a couple of issues arising from the ordering of portlets
and servlets being out of sync. For example see
https://issues.jboss.org/browse/GTNPC-76
This isn't really a bug, since the ordering of when portlets and
servlets are initialized is not suppose to be guaranteed. But I have a
couple of changes to wci which will allow for this behaviour (see patch
attached to GTNPC-76)
Basically there are 2 new features which when used together will provide
ordering between portlets and servlets.
1) by using a context-parameter in the web.xml, we can tell the native
wci implementation to not register the specific webapp.
2) you can now manually add an application to the wci native
implementation.
To control ordering:
- add in the context-parameter so the native implementation doesn't
register the webapplication (and therefor PC doesn't know about it)
- specify the generic GateInServlet in the web.xml and use the
load-on-startup value to control ordering against other servlets. The
GateInServlet will manually register itself to the native
implementation.
Any objections?
12 years, 11 months
CRaSH beta24
by Julien Viet
was released yesterday, what's new ?
- a few bug fixes were made
- Jackrabbit implementation is now supported as an external contribution
- configuration of important stuff (like connector ports) is done from a property file and can be overridden by JVM system properties (it was possible for a few version but was not explicitly mentionned)
- the izpack installer got improved a bit
- jars are now deployed in Maven Central which makes it easier to consume in some products
The documentation online looks now very cool: http://vietj.github.com/crash/ and is trivial to produce thanks to wikbook and GitHub maven integration (basically "mvn site -Pgithub deploys the doc in website based on GitHub gh-pages API).
We aim to release a final release within a couple of month to close the CRaSH 1.0 chapter after two years.
enjoy
Julien
12 years, 11 months