-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
oh, now - raked isn't at all what I was going for... although it does
have a certain ring to it. :-)
I've got a push going on this week but will be opening it up this
weekend. To be clear - I _will_ be putting up the current as well as the
'unicorn' l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Bell wrote:
> Like I said I have only had a quick look at it so some of my impressions my
> be off base. I can see cases where this would be the greatest thing since
> sliced bread, and others where it would be a nightmare to work with.
Soun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is a link on the home page to Tassel - under Related Projects
Peter Svensson wrote:
> Actually, one does not exclude the other. Tassel has a large number of
> components already. My only gripe with tassel is that there is not direct
> link to it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JavaOne ending was my main hold off on doing anything further on this
subject, but as attendees start migrating back, I'll comment a bit here:
(and if you can't take tongue and cheek, delete and move on)
Steve Motola wrote:
> javaone tapering off, wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to apologize for any "lack of helpfulness" you may have
experienced. The addresses on the site are, as you correctly pointed
out, incorrect due to the recent promotion of Tapestry to TLP status.
This transition is in progress, but I will e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As he stated, it was his opinion ("a must IMHO") - something to which he
is most definitely entitled. Is it an Apache requirement? No. Further
examples not required.
Warner Onstine wrote:
> Just one look at Tomcat really shows that this isn't a *must*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although there seemed to be consensus on this, I was giving a little
more time on the dev list before formalizing this as there needs to be
not only logo submissions, but also criteria logos must adhere to in
order for consideration. If everyone can tu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are reasons why I'll never see that methodology in some places,
but let's stick to where it can work: Despite issues anyone may have
with Maven, why not use ibiblio for it? Instead of YAPTG (yet another
place to go)?
I'm still in favor of gettin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The "dependencies will be downloaded" from a "central repository" is
Maven 101. The problem I ran into was "this is your build machine. it
has NO connectivity outside this room". Corner case? Oh, yeah... but it
shows where the "Maven 101" logic falls s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
*zing!*
Another ref to EWDT!
thinkin' 'bout keeping track of how popular this book is by number of
references to it in responses to questions. (you know - make sure Kent's
able to retire off the proceeds ;-) )
[not dissing the response - he does hav
.
> Somehow I couldn't see that...
>
> On 5/17/06, Rui Pacheco <[EMAIL PROTECTED]> wrote:
>>
>> I am using Java 6 on the desktop and 5 on the deployment machine.
>> And tapestry-annotations-4.0.1 is on my classpath. Its included on the
>> build path of my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(and have the tapestry-annotations jar on your classpath?)
James Carman wrote:
> Are you using JDK5?
>
> -Original Message-
> From: Rui Pacheco [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 17, 2006 10:24 AM
> To: Tapestry users
> Subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And now, the required:
Is it done yet? Do you have a demo? ;-)
James Carman wrote:
> I would probably do it as a generalized HiveMind library first which
> includes an AcegiInterceptor implementation of some sort. Then, I'd write a
> tapestry-spe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
GO JAMES :-D
James Carman wrote:
> Well, I did it for the Sprint transaction stuff. I'm sure I can do it for
> the Acegi stuff. :-)
>
>
> -Original Message-
> From: Hugo Palma [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 16, 2006
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is where I stick with ACEGI being unobtrusive. Not discounting any
other method of doing it at all, but I found that with ACEGI I add a
hook into "login/logout" pages and there's no other intrusion into my
Tapestry applications outside the configu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl Pelletier wrote:
> Hi everyone, I'm currently building a web site and looking for
> documentations on how-to or best practice of implementing Role security
> in Tapestry 4.0.
>
> It`s a Simple CRUD application and we need to give some security to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, this is not a proper approach to this issue for two very
significant reasons (and having recently seen one of the biggest "legal"
teams at work, you very seldom get a second chance to tell them to "do
their job" :-)]:
1. PracticalBrowserSni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is where definitions of "currently" come in to play :-)
The 3.x series also references it in the inspector.
Andreas Andreou wrote:
> For those wondering, it's currently used by contrib:Palette
>
> Sergei Dubov wrote:
>> Politely tell your legal
hould
> have a .application file. It should be appropriate to spit out a warning if
> it can't find the file.
>
>
> -Original Message-
> From: Brian K. Wallace [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 12, 2006 9:25 AM
> To: Tapestry users
> Subject: R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When Tapestry can't find the application specification, it currently
outputs a DEBUG message indicating as much ("Could not find an
application specification for application servlet ").
Given the ramifications (in a lot of situations) of not finding th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wanted to verify before I gave out bad info: In Tapestry-3.0.3-bin.zip,
it's under web\doc.
HTH
Brian
Mark Stang wrote:
> Silly question, where in the distribution?
>
>
> -Original Message-----
> From: Brian K. Wallace [mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Stang wrote:
> Could we get a tag in the Subject for "Tapestry"?
>
> All of my filters are looking for it and now that it is gone, my in-box is
> starting to look like a Tapestry Meeting Room.
>
> thanks,
>
> Mark
>
All traffic for the list n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 3.0.3 documentation is not 'lost', it's still part of the 3.0.3
distribution. SOP is for the latest release of the docs to be on the
site, which - for the 3.X branch - is 3.0.4.
Mark Stang wrote:
> Boys and girls, am I to interpret the "loss" of t
>
> On 5/10/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
>>
> Well, when it started out being just 3.0 - thinking the 3 thread would
> die when 4 came out it made a bit of sense... then 3.0.1 just kept it
> going. So all I did was change the last 3 to a 4. One of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, when it started out being just 3.0 - thinking the 3 thread would
die when 4 came out it made a bit of sense... then 3.0.1 just kept it
going. So all I did was change the last 3 to a 4. One of those "it's
always been like that" things - except "al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Stang wrote:
> They were here...
>
> http://jakarta.apache.org/tapestry/3.0.3/doc/ComponentReference/index.html
>
They were, until 3.0.4 came out (actually a little longer as I didn't
have permission to remove them at the time). What's online is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And if I'm going to reply like that, I should stress what should be
stressed: 1.4.1 works ONLY for Eclipse 3.2 - not previous versions.
1.3.0 is still the latest for Eclipse 3.1.
Brian K. Wallace wrote:
> I'm not Geoff... but JettyLaun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not Geoff... but JettyLauncher 1.4.1 is out which supports Eclipse
3.2. If there are any issues with it working, let me know.
Brian
Gentry, Michael (Contractor) wrote:
> Geoff:
>
> Will there be an update of JettyLauncher for Eclipse 3.2 sometim
s are made part of an official release.
Brian
Mark wrote:
> Is this online only, or is the downloadable documentation archive
> updated as well?
>
> Thanks,
>
> MARK
>
> Brian K. Wallace wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All -
I've just uploaded the latest documentation to the site. If you run in
to any issues, please let me know.
Otherwise - enjoy the updated documentation.
Brian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEXBLuaCoPKRo
30 matches
Mail list logo
