Hi Craig!
but just wanted to note that the
integration between JSF and Commons Validator in Shale is usable even
if you don't buy in to the rest of the Shale architecture
Yes, I know - I already use it that way (or better, I started to use it ;-).
However, even if shale-core is small, if we go
I found this comment interesting:
"What about something less definite and more 'code word'? What about not
having the word 'web'? 'Arctic' or 'Telsa' or something completely
meaningless but catchier than 'Web .*$"
I think if a proper name is choosen along these lines, the result is
something bet
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by FrankZammetti:
http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents
---
On 6/25/05, Dean Pickersgill <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Phil Steitz [mailto:[EMAIL PROTECTED]
> > I like "WebLibs" the best.
> > Phil
>
> ... Nah. That's an anagram of 'Wibbles', and it might upset the company
> that makes those fashionable toys that are all
-Original Message-
From: Phil Steitz [mailto:[EMAIL PROTECTED]
Sent: 26 June 2005 02:16
To: Jakarta General List
Subject: Re: Name for commons-like area for web
Stephen Colebourne wrote:
> There doesn't seem to be a thread for this
>
> The current suggestions are:
>
> Commons Web
>
Stephen Colebourne wrote:
There doesn't seem to be a thread for this
The current suggestions are:
Commons Web
Jakarta Web Parts for Java (JWP4J)
Web App Commons
Web App Components
Web App Modules
Web Bricks
Web Commons
Web Components
Web Libs
Web Parts
Web Tools
Weblets
Of thes
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by TimObrien:
http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents
The comment on the change is:
Silly name ideas
---
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by TimObrien:
http://wiki.apache.org/jakarta/Migrating_to_Subversion
--
On 6/25/05, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> Hi!
> > Web Commons
> > Web Components
> For me it depends how fine grained those components are.
>
> Say, if there is a project which cummulates all filters for a servlet
> container I am for "web commons" as it might result in project s
Hi!
Web Commons
Web Components
For me it depends how fine grained those components are.
Say, if there is a project which cummulates all filters for a servlet
container I am for "web commons" as it might result in project sizes we
have in "commons".
If we manage (what I prefer) to have muc
I like "Components" the best ("Jakarta Web Components"). Apparently so does
Sun (e.g. SCWCD).
To me, "Parts" sounds like what I need when my car breaks down.
And "brick" reminds me of a funny insult that was going around the net for a
while:
http://forums.modemhelp.net/viewtopic.php?t=4161
> The most obvious would be CommonsWeb or WebCommons, as the general user
> community could link the concept to commons easily enough. However,
> there is a danger that it could be confusing precisely because of that.
As long as it is not under the
umbrella of the Jakarta Commons
project I would a
There doesn't seem to be a thread for this
The current suggestions are:
Commons Web
Jakarta Web Parts for Java (JWP4J)
Web App Commons
Web App Components
Web App Modules
Web Bricks
Web Commons
Web Components
Web Libs
Web Parts
Web Tools
Weblets
Of these, WebParts has issues with
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by StephenColebourne:
http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents
The comment on the change is:
Add Web Libs
---
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by StephenColebourne:
http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents
The comment on the change is:
Add Web Commons
Stephen Colebourne wrote:
robert burrell donkin wrote:
On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
9 or somewhere else should speak to J2EE or other external config
requirments, which should be fine, even encouraged in some cases
is 9 needed? are any configuration guidelines nee
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by StephenColebourne:
http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents
The comment on the change is:
Add a couple more suggestions on
robert burrell donkin wrote:
On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
9 or somewhere else should speak to J2EE or other external config
requirments, which should be fine, even encouraged in some cases
is 9 needed? are any configuration guidelines needed?
if they are then i agre
robert burrell donkin wrote:
this has proved impractical in the jakarta commons. i propose we drop
point 12.
"12. The subproject will also provide a single JAR of all stable package
releases. It may also provide a second JAR with a subset of only JDK 1.1
compatible releases. A gump of nightly
Rahul Akolkar wrote:
is boils down to the question: does this subproject need it's own
sandbox or will neophyte components start in the jakarta commons
sandbox?
+1 for sandbox (non-binding)
Its slightly hard to imagine anything otherwise, but maybe I'm just
used to seeing how commons and tagli
Howard Lewis Ship wrote:
> Tapestry is distributed as a combined binary/source distribution, and
> a seperate documentation distribution.
What is required to build this? Am I correct in assuming the process is
like Tapestry 3.0, with non ASF libs being fetched by an ant script? If
so, what real
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by StephenColebourne:
http://wiki.apache.org/jakarta/DraftCharterForWebComponentCommons
The comment on the change is:
Change CVS to SVN
---
The first beta release of Tapestry 4.0 is now available. Tapestry is a
component based web application framework that provides lots of
functionality with minimal Java coding, and creates an environment
that supports high levels of reuse. Tapestry 4.0 represents a
significant advance over Tapestry 3
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for
change notification.
The following page has been changed by JulesGosnell:
http://wiki.apache.org/jakarta/ApacheAtJavaOne2005
--
24 matches
Mail list logo
