On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
Limitations:
- Undeploying an ejb module will not remove it's beans. The
server has to be restarted to deploy the same module again.
Ok, I've implemented undeploy and verified it works using the
calculator sample app. I can
Ok, have clarified this in the release notes..
Thanks
-Dave-
Dain Sundstrom wrote:
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
- Deployment with no ejb-jar.xml or openejb-jar (just need a
geronimo-openejb.xml for all the geronimo-specific deployment stuff)
To be clear, the
Thanks... Have made the updates...
Is there anything that should be added to the limitations section? Do
we fully support EJB 3.0?
-Dave-
David Blevins wrote:
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
Limitations:
- Undeploying an ejb module will not remove it's
David,
Did this change make it into the 2.0-M2 branch and the image that Matt
is creating for a vote?
Joe
David Blevins wrote:
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
Limitations:
- Undeploying an ejb module will not remove it's beans. The
server has to be
Two issues here -
1) Dain's fixes are in trunk. They have not been merged with the M2
changes yet. So at the moment, the M2 has these limitations.
2) This is a bigger issue. I don't see the Release Notes in the
unpacked server !!!
Cheers
Prasad
On 1/26/07, Kevan Miller [EMAIL PROTECTED]
Ok, have added back the restriction regarding undeploying ejb modules
for 2.0-M2. Attaching the latest release notes to this email. Please
verify the eol characters are in the correct format..
Matt will add the Release Notes to the official build.
-Dave-
Prasad Kashyap wrote:
Two issues
On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
Thanks... Have made the updates...
Is there anything that should be added to the limitations section?
One of the things I mentioned in another email is that MDBs are
completely untested and should be assumed non-functional.
Do we
David Blevins wrote:
On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
Thanks... Have made the updates...
Is there anything that should be added to the limitations section?
One of the things I mentioned in another email is that MDBs are
completely untested and should be assumed
Thanks... Have included the MDB restriction in the latest attachment.
BTW, The version in the 2.0-M2 branch is quite stale.
Can someone please refresh the copy at:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.0-M2/RELEASE-NOTES-2.0-M2.TXT
with the included attachment.
All
On Jan 26, 2007, at 12:21 PM, Bill Stoddard wrote:
David Blevins wrote:
On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
Thanks... Have made the updates...
Is there anything that should be added to the limitations section?
One of the things I mentioned in another email is that MDBs
On 1/26/07, Dave Colasurdo [EMAIL PROTECTED] wrote:
Thanks... Have included the MDB restriction in the latest attachment.
BTW, The version in the 2.0-M2 branch is quite stale.
Can someone please refresh the copy at:
I'm helping Hernan update the Release Notes for 2.0-M2.
Can folks please provide feedback for the EJB Content that gets
documented in the Release Notes.
Here is the current content..
- EJB 3.0 (via OpenEJB project)
Supported:
- JPA (Custom Provider, App-managed, Container-managed)
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
- Deployment with no ejb-jar.xml or openejb-jar (just need a
geronimo-openejb.xml for all the geronimo-specific deployment stuff)
To be clear, the geronimo-openejb.xml file is only required if you
have some geronimo specific stuff that
13 matches
Mail list logo
