On Jan 25, 2007, at 8:17 PM, leonard flournoy wrote:
Here's the scenario, when I deploy an application using --offline
and then start the server, it dies badly because of an error in the
newly deployed application. This is not an error on within the
geronimo core, just an application deplo
Here's the scenario, when I deploy an application using --offline and then
start the server, it dies badly because of an error in the newly deployed
application. This is not an error on within the geronimo core, just an
application deployed but not started. Has anyone else had this experience?
Michael C. wrote:
We removed all references to the sun mail.jar file in the geronimo classpath
and i removed the GBEAN references from the geronimo email plan and left
only the geronimo mail dependency jars. We undeployed the old plan and
redeployed the new and ran the application. We recieved
We removed all references to the sun mail.jar file in the geronimo classpath
and i removed the GBEAN references from the geronimo email plan and left
only the geronimo mail dependency jars. We undeployed the old plan and
redeployed the new and ran the application. We recieved an error that i
exp
Michael C. wrote:
Thank you for your replies, they are greatly appreciated. I would like to
step back for a moment and be sure i understand the big picture.
When our team first changed over from WSAD to MyEclipse and decided to use
Geronimo 1.0 as our local app server, we ran into this same em
>> entity beans with cmr can you still migrate them one by one or do you
>> have to migrate the entire tree of objects?
if I want to migrate one by one, I think I'll have to break up the CMR
relations anyway, thats right.
> I'm not understanding what you are saying here. Geronimo 1.2 (not
> qu
Thank you for your replies, they are greatly appreciated. I would like to
step back for a moment and be sure i understand the big picture.
When our team first changed over from WSAD to MyEclipse and decided to use
Geronimo 1.0 as our local app server, we ran into this same email problem.
I fou
On Jan 25, 2007, at 1:47 AM, Hans J. Prueller wrote:
David,
thank you for your thoughts. You provided good entry points for me.
I mentioned hibernate specifically because
we already are using hibernate and CMP in parallel within our
project (as CMP2.x sometimes does not fulfill all nee
It is possible there might be a bug in the address parser that's
incompatible with the Sun version. If possible, could you show me
exactly what's getting specified? Feel free to block out the
userid/node characters, but leave everything else intact (including
whitespace, if any).
Rick
Mic
The message about unable to relay for that address is sent back from the
SMTP server. I'm not sure what it didn't like, but it appears it
couldn't figure out where to relay the message.
The part I find interesting is the stack trace. You're using the Sun
javamail transport implementation, no
I tried your approach and that particular error went away but now i believe i
am back to the root cause of all this effort; our email logic is throwing an
error on this line in our application:
javax.mail.Transport.send(message);
Message=Could not send eMail to address [EMAIL PROTECTED] <;>
Thre
David,
thank you for your thoughts. You provided good entry points for me. I
mentioned hibernate specifically because
we already are using hibernate and CMP in parallel within our project (as
CMP2.x sometimes does not fulfill all needs).
targeting JPA instead of hibernate specifically is e
On Jan 24, 2007, at 10:15 PM, Hans J. Prueller wrote:
hi together,
I have been working with the JOnAS Java 2 EE application server for
about 5 years now, meanwhile
I have several projects, one of them is rather big already, it
contains about 60-70 EJB’s, two thirds
of them are CMP/CM
13 matches
Mail list logo
