There's a problem with JSTL where an application that is using it must
currently include a dependency in the Geronimo deployment plan against
the jstl jar (see my note to dev entitled "getting at META-INF in a
dependent jar" and GERONIMO-2650) .....
<dep:dependencies>
...
<dep:dependency>
<dep:groupId>jstl</dep:groupId>
<dep:artifactId>jstl</dep:artifactId>
</dep:dependency>
...
</dep:dependencies>
Joe
Matt Hogstrom wrote:
It looks like we have the makings of the M2 milestone that has been
talked about. Dave and Dain made a huge chunk of code available so that
one can deploy and use (in limited ways) EJB 3.0. Very impressed gents,
kudos to the two of you.
As we did for M1 I'd like to go ahead and branch tomorrow afternoon so
we can tidy this release up without disrupting the continuous
development on trunk. I'll pull in fixes to address the release as
appropriate so that the server runs and we can show users a peek at a
semi-stable environment.
Remember this is a milestone and not a general release in terms of it is
a view of the work in progress so fit and finish is coming :)
Here are the major items I know about and limitations. Please comment
where I'm in a ditch or on another planet.
EJB 3.0
- Ability to deploy beans
- Dependency injection still not functional but external plans can be used.
- WebServices not plugged in yet.
- Simple apps are possible
- No guarantees on old EJB 2.1 apps at this point and for CMP will
definitely require some refactoring for deployment.
POJO WebServices available
The remainder of the stack as previously delivered is available as well.
JSF is currently broken (was working in M1)
Other stuff in terms of functionality and limitations?
Feedback welcome :)
Excellent work all.
Matt Hogstrom
[EMAIL PROTECTED]
"Have you noticed since everyone has a camcorder these days no one talks
about seeing UFOs like they used to?"
