Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Subject: Re: Failure on sending email using Flow.
From: Jason Johnston <jason.johnston@Intrado.com>
To: dev@cocoon.apache.org
In-Reply-To: <35568.199.117.205.101.1150925081.squirrel@mail.lojjic.net>
References: <20060613233740.GA8638@uncanny.net>
	 <448F53F1.9010307@lojjic.net> <20060621210622.GB21603@uncanny.net>
	 <35568.199.117.205.101.1150925081.squirrel@mail.lojjic.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 21 Jun 2006 15:26:03 -0600
Message-Id: <1150925164.26559.61.camel@jjohnston>
Mime-Version: 1.0

Sorry folks, sent to the wrong list. :(


On Wed, 2006-06-21 at 15:24 -0600, Jason Johnston wrote:
> > Thanks Jason the geronimo-spec jars were the problems. More below.
> >
> > * Jason Johnston <cocoon@lojjic.net> wrote on [2006-06-13 17:11]:
> >> Edward Elhauge wrote:
> >> >Hi, I have a problem that is stumping me. I've created a class
> >> >to send canned email messages; it uses the Sun mail.jar,
> >> >Debian Linux, Cocoon 2.1.8, and the Jetty AppServer.
> >> >
> >> >I can use this class in a stand alone mode and get mail sent out (this
> >> >is true whether I'm running as myself or as the cocoon user).
> >> >
> >> >When I try to use the same class within Flow I get nothing at all.
> >> >There isn't even an error in the log. The status is always "SENT"
> >> >so it doesn't seem like an exception is every thrown.
> >>
> >> When you run your Java test class, I assume it is run outside the Cocoon
> >> environment, correct?  My first guess would be a classpath issue.
> >>
> >> Make sure that the Sun mail.jar and activation.jar are in Cocoon's
> >> WEB-INF/lib, and that the geronimo-spec-* version of both are *not*
> >> there, as they will conflict.
> >
> > Yes I did have the Sun jars, but I had to get rid of the geronimo-spec
> > ones also. The mail doesn't go through if you use the geronimo-spec jars
> > alone. I guess geronimo-spec is not totally compliant with the Sun Spec,
> > or is plain broken?
> >
> > To be able to rebuild and reinstall the release you need to exclude
> > the mail block, otherwise the geronimo-spec jars come back. To bad there
> > isn't an easy way to provide equivalent jars to fulfill dependencies.
> 
> 
> Good to know that was the issue.
> 
> FYI, the Cocoon trunk code has been converted to use Maven for its build
> process and dependency resolution; one advantage of this is that Maven is
> able to download the Sun JARs directly from an official location at build
> time.  The Cocoon distribution no longer has to include the geronimo JARs
> simply to satisfy compile-time dependencies (they could not redistribute
> the Sun JARs due to license restrictions.)  So in future versions this
> will "just work".
> 
> 
>