Well, I think that the "one download" concept should be retired and we can do
better than that old fashioned rigid approach. IMO it should work like this: a
tiny project that defines configuration and dependencies has to be
created and uploaded to the central repository;
when somebody will want to use the project then all the dependencies
will be downloaded from the repository;
then if that someone will want to add to more components to the
project it would be simple matter of adding one line to the dependencies
section of the Ant's build.xml or Maven's POM file (it works today) or
choosing new dependency in an IDE (available in Eclipse with Maven plugin).
That is why I have created the CJAR project, I want it to become THE
repository for Java community so we all can easily assemble our applications in
the way we want. There are some ideas on how to allow people to upload
libraries and components, please have a glance and send your thoughts.
Common repositories serve well in other communities and I think we should get
one too.
Konstantin Ignatyev
----- Original Message ----
From: Peter Svensson <[EMAIL PROTECTED]>
To: Tapestry users <users@tapestry.apache.org>
Sent: Wednesday, May 17, 2006 12:03:07 AM
Subject: Re: Tapestry to generate mails ?
You know what I would like to see; An array of well-wanted services
integrated into Tapestry from day one.
Generic download of anything, sure, it's there. Send-an-email; well, of
course we have it. Et.c.
Maybe Someone could make something like those eclipse guys did with
EasyEclipse distributions, just bundle the best of breed into one download.
Hmm.. OK, yes, I know. The old argument which is a version of " I don't
wan't to be tied into the strict confines of a hig-level lanuage! You can do
all you want with assembler! And macros too!"
My point is this; You don't have to eat the peas even if they're on your
plate.
For veggies (newbies) however, it would help a lot not to have to track
stuff down, or break a neck getting a service to work the first time (then,
neck finally healed, getting Kents bok and copying it right off, maybe
understanding it in part a month later), rather than just using an in-system
readily available one.
<ducks>
Cheers,
PS
On 5/17/06, Michael Lake <[EMAIL PROTECTED]> wrote:
>
> I'm *very* interested in seeing such a service. I want to keep in line
> with using all of tapestry's i8n and be able to send multi-part mime
> messages which have html and plain text.
>
> Please do put something up on the wiki and let us all know.
>
> goody goody.
>
> -mike
>
>
> Henri Dupre wrote:
>
> > I don't agree on this... Also I don't see really differences between
> > "static" email and interactive HTML. In the emails we generate, there is
> > lots of dynamic content although there is no form handling, we use the
> > same
> > components plus many other tapestry features. Velocity is fine, but
> > not when
> > you start to have complex emails. What makes tapestry great for this
> task
> > are the templates. In addition, I rather not add another technology to
> > our
> > project, Velocity is simple, but just *more* to learn and manage for our
> > other developers.
> >
> > And I'll give you a very usefull usage of sending html pages: for
> > exceptions, we send the tapestry error page by email (in tapestry 3)
> > while
> > we give to the client a friendly error page. Logging is fine but it
> > doesn't
> > give you all the detailed info of an error.
> >
> > I've been working on an EmailService for T4, you can inject it in any
> > page
> > and the interface is quite simple. It takes a list of properties (for
> > email
> > headers, from/to/subject), a page (String or object) and eventually an
> > object map if you want to call the external interface of your page.
> > It is working 90% now and it is relying on a fresh request cycle, so
> > it will
> > be possible to thread the whole thing. Getting a fresh request
> > cycle requires quite a bit of hacking, I may need to write a specific
> > engine
> > object. I can post the code on the wiki once I'm done if anyone is
> > interested.
> >
> >
> >
> >
> >
> >
> >
> > On 5/3/06, James Carman <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Tapestry is for creating interactive HTML, not a static HTML-formatted
> >> email
> >> (IMHO). I think you're trying to use an elephant gun to hunt squirrel
> >> here.
> >> Velocity is perfect for generating email text. You can still use your
> >> architecture, you just put some helper beans in the VelocityContext.
> >>
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> >> Sent: Wednesday, May 03, 2006 6:17 PM
> >> To: Tapestry users; [EMAIL PROTECTED]
> >> Subject: Re: Tapestry to generate mails ?
> >>
> >> I had this related link over at my delicious (
> >> http://del.icio.us/andyhot/tapestry ).
> >> It's entitled 'Sending Tapestry-generated email with Spring' and it's
> >> at:
> >> http://www.behindthesite.com/blog/C1931765677/E2094832857/index.html
> >>
> >>
> >>
> >> >From Stephane Decleire <[EMAIL PROTECTED]>:
> >>
> >> > Hi,
> >> >
> >> > I would like to know if anybody use Tapestry to generate its email ?
> >> > Indeed, generate mails based on templates is very similar to generate
> >> > HTML pages ...
> >> > As an exemple, i would like to implement the famous "I've forgot my
> >> > password" by sending the user an email based on a template where the
> >> > password should be inserted.
> >> > I would be very interested in a Tapestry approach to do this in
> >> order to
> >> > reuse all of my existent architecture (Tapestry/Spring/Hibernate).
> >> >
> >> > Thanks in advance.
> >> >
> >> > --
> >> > Stιphane Decleire
> >> >
> >> > 05 56 57 99 20
> >> > 06 63 78 69 06
> >> >
> >> >
> >>
> >>
> >> --
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Thanks,
> >
> > Henri.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
