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,
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
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, thatÂ’s right.
I'm not understanding what you are saying here. Geronimo 1.2 (not
quite
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
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
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?
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
