You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Matt Welch <ma...@gmail.com> on 2005/09/23 00:33:45 UTC
TheServerSide.com moving away from Tapestry?
http://www.theserverside.com/news/thread.tss?thread_id=36654
In the above referenced thread there is a reference to the TSS having some
serious issues with the perfromance and UI of their site and that they will
soon be moving to an all new codebase. Wasn't it pretty recently that TSS
relaunched using Tapestry? Are they having problems with it? I'd be curious
to find out as I'm considering using Tapestry on a large scale product in
the not to distant future and wouldn't want to come up against the same
problems.
Re: TheServerSide.com moving away from Tapestry?
Posted by Geoff Longman <gl...@gmail.com>.
Howard blogs about the problem
http://howardlewisship.com/blog/2005/09/theserverside-software-problems.html
Geoff
On 9/22/05, Patrick Casey <pa...@adelphia.net> wrote:
>
>
> > -----Original Message-----
> > From: Tom Davies [mailto:tom@atlassian.com]
> > Sent: Thursday, September 22, 2005 6:46 PM
> > To: Tapestry users
> > Subject: Re: TheServerSide.com moving away from Tapestry?
> >
> > Matt Welch wrote:
> > > http://www.theserverside.com/news/thread.tss?thread_id=36654
> > >
> > > In the above referenced thread there is a reference to the TSS having
> > some
> > > serious issues with the perfromance and UI of their site
> >
> > To quote from the thread: "These are the two most severe problems TSS
> > has right now. Both are related to data, not UI (although we're aware of
> > some UI issues too)"
> >
> > So the UI is not the serious issue, the DB is.
>
> I dunno how their code looks, but sometimes bad UI design can murder
> your database layer even if the DB layer is, itself, nominally sound. A UI
> which, for example, evaluates every joined field in a list with a separate
> request from the UI e.g. "what is user#1's manager's name? ok, how about
> user #2's manager's name ... how about user #1045? ... etc".
>
> It's been my experience that trying to keep a theoretically sound
> separation of concerns between the two layers is usually a recipe for
> trouble. Letting the UI hint things to the DB layer about the use cases for
> data requests can go a long way towards ameliorating the problem though
> without necessarily driving a stake through your design.
>
> --- Pat
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: TheServerSide.com moving away from Tapestry?
Posted by Patrick Casey <pa...@adelphia.net>.
> -----Original Message-----
> From: Tom Davies [mailto:tom@atlassian.com]
> Sent: Thursday, September 22, 2005 6:46 PM
> To: Tapestry users
> Subject: Re: TheServerSide.com moving away from Tapestry?
>
> Matt Welch wrote:
> > http://www.theserverside.com/news/thread.tss?thread_id=36654
> >
> > In the above referenced thread there is a reference to the TSS having
> some
> > serious issues with the perfromance and UI of their site
>
> To quote from the thread: "These are the two most severe problems TSS
> has right now. Both are related to data, not UI (although we're aware of
> some UI issues too)"
>
> So the UI is not the serious issue, the DB is.
I dunno how their code looks, but sometimes bad UI design can murder
your database layer even if the DB layer is, itself, nominally sound. A UI
which, for example, evaluates every joined field in a list with a separate
request from the UI e.g. "what is user#1's manager's name? ok, how about
user #2's manager's name ... how about user #1045? ... etc".
It's been my experience that trying to keep a theoretically sound
separation of concerns between the two layers is usually a recipe for
trouble. Letting the UI hint things to the DB layer about the use cases for
data requests can go a long way towards ameliorating the problem though
without necessarily driving a stake through your design.
--- Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Tom Davies <to...@atlassian.com>.
Matt Welch wrote:
> http://www.theserverside.com/news/thread.tss?thread_id=36654
>
> In the above referenced thread there is a reference to the TSS having some
> serious issues with the perfromance and UI of their site
To quote from the thread: "These are the two most severe problems TSS
has right now. Both are related to data, not UI (although we're aware of
some UI issues too)"
So the UI is not the serious issue, the DB is.
> and that they will
> soon be moving to an all new codebase. Wasn't it pretty recently that TSS
> relaunched using Tapestry? Are they having problems with it? I'd be curious
> to find out as I'm considering using Tapestry on a large scale product in
> the not to distant future and wouldn't want to come up against the same
> problems.
>
And see http://www.theserverside.com/news/thread.tss?thread_id=36654#185521
Where Ottinger says "The conversion to Tapestry was well-known, but
honestly, never *finished* - so a lot of functionality was left on the
drawing board, simply because of time constraints."
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by John <mm...@web.de>.
Hello,
Do the Tapestry users use Cayenne at all?
Or they use something diffrent?
John.
----- Original Message -----
From: "Matt Welch" <ma...@gmail.com>
To: <ta...@jakarta.apache.org>
Sent: Friday, September 23, 2005 12:33 AM
Subject: TheServerSide.com moving away from Tapestry?
http://www.theserverside.com/news/thread.tss?thread_id=36654
In the above referenced thread there is a reference to the TSS having some
serious issues with the perfromance and UI of their site and that they will
soon be moving to an all new codebase. Wasn't it pretty recently that TSS
relaunched using Tapestry? Are they having problems with it? I'd be curious
to find out as I'm considering using Tapestry on a large scale product in
the not to distant future and wouldn't want to come up against the same
problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Konstantin Ignatyev <kg...@yahoo.com>.
http://www.theserverside.com/news/thread.tss?thread_id=36654#185568
That IMO says exactly (although indirectly) what does
not work and why TSS cannot tell directly what the
problem is.
--- Benjamin Tomasini <bt...@neteverything.com>
wrote:
> It *could* get really ugly. But from the tone of
> the discussions, it
> looks like the TSS folks are taking a very balanced
> and honest approach.
>
> There was one ad hominem post that just listed the
> "culprits" without
> any kind of logical support. Joseph seemed to take
> care of that well.
>
> The best way to answer any unfounded blame is to ask
> for meaningful data
> behind any presented analysis. If TSS keeps this
> up, I think the
> Tapestry community, and the Java community as a
> whole will be served
> well. I still have faith that the OSS community is
> a mertiocracy, and
> that over the long run, merit wins out over
> marketing and FUD.
>
> We'll see.
>
> I did try to post something like this on TSS, but I
> couldn't login. :)
>
> Ben
>
> Geoff Longman wrote:
>
> >I understand. It's just that nobody is standing up
> for Tapestry and
> >you are the only one with enough information to do
> that without
> >sounding like an idiot.
> >
> >I realize there's a fine line to tread to avoid
> things degenerating
> >into fingerpointing. But the way I see it, the
> longer TechTarget is
> >in trouble the more likely it is that they will
> start looking for
> >scapegoats. I'm sure the people in there are
> working hard to solve the
> >problems. But what if another 3 weeks go by without
> improvement? I
> >would expect at that point the insiders will go
> into "save my butt"
> >mode and shift blame to anything and everything
> they can to save thier
> >jobs.
> >
> >I could get really ugly.
> >
> >Geoff
> >
> >On 9/23/05, Howard Lewis Ship <hl...@gmail.com>
> wrote:
> >
> >
> >>These posts about TSS are troubling.
> >>
> >>The basic issue is that I signed on with The
> Middleware Company to do
> >>a number of phases of development of
> TheServerSide.com. The first
> >>phase was the basic translation of the site to a
> component object
> >>model, leaving all the functionality unchanged.
> >>
> >>At the same time this was occuring, a seperate
> team was converting the
> >>backend access from entity EJBs to Solarmetric
> Kodo.
> >>
> >>In the end, I had less than a week to integrate
> the two before going
> >>live. And yet, for the most part, the result was
> quite succesful.
> >>
> >>However, with the acquisition of The Middleware
> Company by Tech
> >>Target, my involvement with TSS came to an end;
> the later, more
> >>interesting phases, where we simplified the stack
> and built
> >>considerable UI improvements, has not come to
> pass. All I've seen is
> >>the introduction of more and more ads on the site.
> >>
> >>I can't talk to the root problem today; I don't
> know it ... I do know
> >>that Tapestry is doing exactly what its supposed
> to be doing, that the
> >>functionality problems (missing posts and such)
> are a problem at the
> >>application layer (the stateless session bean used
> to manage
> >>transactions) and the interaction between that
> layer, Kodo, Coherence,
> >>WebLogic and the database. In fact, given the
> simplicity of the
> >>database schema (just six or eight tables) I
> suspect the problem
> >>really is in the configuration and integration of
> these elements.
> >>
> >>Based on what I've read, and some high level
> discussions I had with
> >>them last winter, I believe TechTarget is building
> a single enterprise
> >>wide solution for all their many web sites.,
> migrating away from the
> >>Tcl-based Vignette solution used by the majority
> of their sites, as
> >>well as the Tapestry-based solution for TSS.com
> and TSS.net. All I
> >>know about the solution is that it will be based
> on JEE (assuming that
> >>hasn't changed since our discussions).
> >>
> >>
> >>
> >>On 9/22/05, Matt Welch <ma...@gmail.com>
> wrote:
> >>
> >>
>
>>>http://www.theserverside.com/news/thread.tss?thread_id=36654
> >>>
> >>>In the above referenced thread there is a
> reference to the TSS having some
> >>>serious issues with the perfromance and UI of
> their site and that they will
> >>>soon be moving to an all new codebase. Wasn't it
> pretty recently that TSS
> >>>relaunched using Tapestry? Are they having
> problems with it? I'd be curious
> >>>to find out as I'm considering using Tapestry on
> a large scale product in
> >>>the not to distant future and wouldn't want to
> come up against the same
> >>>problems.
> >>>
> >>>
> >>>
> >>>
> >>--
> >>Howard M. Lewis Ship
> >>Independent J2EE / Open-Source Java Consultant
> >>Creator, Jakarta Tapestry
> >>Creator, Jakarta HiveMind
> >>
> >>Professional Tapestry training, mentoring, support
> >>and project work. http://howardlewisship.com
> >>
>
>>---------------------------------------------------------------------
> >>To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >--
> >The Spindle guy. http://spindle.sf.net
> >Get help with Spindle:
>
>http://lists.sourceforge.net/mailman/listinfo/spindle-user
> >Announcement Feed:
>
>http://www.jroller.com/rss/glongman?catname=/Announcements
> >Feature Updates:
> http://spindle.sf.net/updates
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> >
> >
> >
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
>
Konstantin Ignatyev
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Benjamin Tomasini <bt...@neteverything.com>.
It *could* get really ugly. But from the tone of the discussions, it
looks like the TSS folks are taking a very balanced and honest approach.
There was one ad hominem post that just listed the "culprits" without
any kind of logical support. Joseph seemed to take care of that well.
The best way to answer any unfounded blame is to ask for meaningful data
behind any presented analysis. If TSS keeps this up, I think the
Tapestry community, and the Java community as a whole will be served
well. I still have faith that the OSS community is a mertiocracy, and
that over the long run, merit wins out over marketing and FUD.
We'll see.
I did try to post something like this on TSS, but I couldn't login. :)
Ben
Geoff Longman wrote:
>I understand. It's just that nobody is standing up for Tapestry and
>you are the only one with enough information to do that without
>sounding like an idiot.
>
>I realize there's a fine line to tread to avoid things degenerating
>into fingerpointing. But the way I see it, the longer TechTarget is
>in trouble the more likely it is that they will start looking for
>scapegoats. I'm sure the people in there are working hard to solve the
>problems. But what if another 3 weeks go by without improvement? I
>would expect at that point the insiders will go into "save my butt"
>mode and shift blame to anything and everything they can to save thier
>jobs.
>
>I could get really ugly.
>
>Geoff
>
>On 9/23/05, Howard Lewis Ship <hl...@gmail.com> wrote:
>
>
>>These posts about TSS are troubling.
>>
>>The basic issue is that I signed on with The Middleware Company to do
>>a number of phases of development of TheServerSide.com. The first
>>phase was the basic translation of the site to a component object
>>model, leaving all the functionality unchanged.
>>
>>At the same time this was occuring, a seperate team was converting the
>>backend access from entity EJBs to Solarmetric Kodo.
>>
>>In the end, I had less than a week to integrate the two before going
>>live. And yet, for the most part, the result was quite succesful.
>>
>>However, with the acquisition of The Middleware Company by Tech
>>Target, my involvement with TSS came to an end; the later, more
>>interesting phases, where we simplified the stack and built
>>considerable UI improvements, has not come to pass. All I've seen is
>>the introduction of more and more ads on the site.
>>
>>I can't talk to the root problem today; I don't know it ... I do know
>>that Tapestry is doing exactly what its supposed to be doing, that the
>>functionality problems (missing posts and such) are a problem at the
>>application layer (the stateless session bean used to manage
>>transactions) and the interaction between that layer, Kodo, Coherence,
>>WebLogic and the database. In fact, given the simplicity of the
>>database schema (just six or eight tables) I suspect the problem
>>really is in the configuration and integration of these elements.
>>
>>Based on what I've read, and some high level discussions I had with
>>them last winter, I believe TechTarget is building a single enterprise
>>wide solution for all their many web sites., migrating away from the
>>Tcl-based Vignette solution used by the majority of their sites, as
>>well as the Tapestry-based solution for TSS.com and TSS.net. All I
>>know about the solution is that it will be based on JEE (assuming that
>>hasn't changed since our discussions).
>>
>>
>>
>>On 9/22/05, Matt Welch <ma...@gmail.com> wrote:
>>
>>
>>>http://www.theserverside.com/news/thread.tss?thread_id=36654
>>>
>>>In the above referenced thread there is a reference to the TSS having some
>>>serious issues with the perfromance and UI of their site and that they will
>>>soon be moving to an all new codebase. Wasn't it pretty recently that TSS
>>>relaunched using Tapestry? Are they having problems with it? I'd be curious
>>>to find out as I'm considering using Tapestry on a large scale product in
>>>the not to distant future and wouldn't want to come up against the same
>>>problems.
>>>
>>>
>>>
>>>
>>--
>>Howard M. Lewis Ship
>>Independent J2EE / Open-Source Java Consultant
>>Creator, Jakarta Tapestry
>>Creator, Jakarta HiveMind
>>
>>Professional Tapestry training, mentoring, support
>>and project work. http://howardlewisship.com
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>>
>
>
>--
>The Spindle guy. http://spindle.sf.net
>Get help with Spindle:
>http://lists.sourceforge.net/mailman/listinfo/spindle-user
>Announcement Feed:
>http://www.jroller.com/rss/glongman?catname=/Announcements
>Feature Updates: http://spindle.sf.net/updates
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Geoff Longman <gl...@gmail.com>.
I understand. It's just that nobody is standing up for Tapestry and
you are the only one with enough information to do that without
sounding like an idiot.
I realize there's a fine line to tread to avoid things degenerating
into fingerpointing. But the way I see it, the longer TechTarget is
in trouble the more likely it is that they will start looking for
scapegoats. I'm sure the people in there are working hard to solve the
problems. But what if another 3 weeks go by without improvement? I
would expect at that point the insiders will go into "save my butt"
mode and shift blame to anything and everything they can to save thier
jobs.
I could get really ugly.
Geoff
On 9/23/05, Howard Lewis Ship <hl...@gmail.com> wrote:
> These posts about TSS are troubling.
>
> The basic issue is that I signed on with The Middleware Company to do
> a number of phases of development of TheServerSide.com. The first
> phase was the basic translation of the site to a component object
> model, leaving all the functionality unchanged.
>
> At the same time this was occuring, a seperate team was converting the
> backend access from entity EJBs to Solarmetric Kodo.
>
> In the end, I had less than a week to integrate the two before going
> live. And yet, for the most part, the result was quite succesful.
>
> However, with the acquisition of The Middleware Company by Tech
> Target, my involvement with TSS came to an end; the later, more
> interesting phases, where we simplified the stack and built
> considerable UI improvements, has not come to pass. All I've seen is
> the introduction of more and more ads on the site.
>
> I can't talk to the root problem today; I don't know it ... I do know
> that Tapestry is doing exactly what its supposed to be doing, that the
> functionality problems (missing posts and such) are a problem at the
> application layer (the stateless session bean used to manage
> transactions) and the interaction between that layer, Kodo, Coherence,
> WebLogic and the database. In fact, given the simplicity of the
> database schema (just six or eight tables) I suspect the problem
> really is in the configuration and integration of these elements.
>
> Based on what I've read, and some high level discussions I had with
> them last winter, I believe TechTarget is building a single enterprise
> wide solution for all their many web sites., migrating away from the
> Tcl-based Vignette solution used by the majority of their sites, as
> well as the Tapestry-based solution for TSS.com and TSS.net. All I
> know about the solution is that it will be based on JEE (assuming that
> hasn't changed since our discussions).
>
>
>
> On 9/22/05, Matt Welch <ma...@gmail.com> wrote:
> > http://www.theserverside.com/news/thread.tss?thread_id=36654
> >
> > In the above referenced thread there is a reference to the TSS having some
> > serious issues with the perfromance and UI of their site and that they will
> > soon be moving to an all new codebase. Wasn't it pretty recently that TSS
> > relaunched using Tapestry? Are they having problems with it? I'd be curious
> > to find out as I'm considering using Tapestry on a large scale product in
> > the not to distant future and wouldn't want to come up against the same
> > problems.
> >
> >
>
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Howard Lewis Ship <hl...@gmail.com>.
These posts about TSS are troubling.
The basic issue is that I signed on with The Middleware Company to do
a number of phases of development of TheServerSide.com. The first
phase was the basic translation of the site to a component object
model, leaving all the functionality unchanged.
At the same time this was occuring, a seperate team was converting the
backend access from entity EJBs to Solarmetric Kodo.
In the end, I had less than a week to integrate the two before going
live. And yet, for the most part, the result was quite succesful.
However, with the acquisition of The Middleware Company by Tech
Target, my involvement with TSS came to an end; the later, more
interesting phases, where we simplified the stack and built
considerable UI improvements, has not come to pass. All I've seen is
the introduction of more and more ads on the site.
I can't talk to the root problem today; I don't know it ... I do know
that Tapestry is doing exactly what its supposed to be doing, that the
functionality problems (missing posts and such) are a problem at the
application layer (the stateless session bean used to manage
transactions) and the interaction between that layer, Kodo, Coherence,
WebLogic and the database. In fact, given the simplicity of the
database schema (just six or eight tables) I suspect the problem
really is in the configuration and integration of these elements.
Based on what I've read, and some high level discussions I had with
them last winter, I believe TechTarget is building a single enterprise
wide solution for all their many web sites., migrating away from the
Tcl-based Vignette solution used by the majority of their sites, as
well as the Tapestry-based solution for TSS.com and TSS.net. All I
know about the solution is that it will be based on JEE (assuming that
hasn't changed since our discussions).
On 9/22/05, Matt Welch <ma...@gmail.com> wrote:
> http://www.theserverside.com/news/thread.tss?thread_id=36654
>
> In the above referenced thread there is a reference to the TSS having some
> serious issues with the perfromance and UI of their site and that they will
> soon be moving to an all new codebase. Wasn't it pretty recently that TSS
> relaunched using Tapestry? Are they having problems with it? I'd be curious
> to find out as I'm considering using Tapestry on a large scale product in
> the not to distant future and wouldn't want to come up against the same
> problems.
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: How dynamic components could be created?
Posted by Patrick Casey <pa...@adelphia.net>.
I built some dynamic search forms that introspect the object being
displayed and set up the appropriate list of search widgets based on a
combination of the object properties and some metadata so it can definitely
be done. However, I couldn't find a good way to do it without essentially
shoving Tapestry into a corner and taking control of the process myself.
So my search component spits out label and input fields via an
HTMLWriter and sets their IDs according to my (not Howard's) naming
convention. Then my form handler (for when the user clicks search) extracts
the values directly out of the session e.g.
Enumeration en = cycle.getRequestContext().getRequest()
.getParameterNames();
while (en.hasMoreElements()) {
String s = (String) en.nextElement();
if (s is one of my magic fields)
...
It works great, but, since I'm not using Tapestry to set up the
fields for me, I can't use the OOB validation or binding code.
--- Pat
> -----Original Message-----
> From: Pavel Rezny [mailto:pare@tmapy.cz]
> Sent: Tuesday, September 27, 2005 7:34 AM
> To: tapestry-user@jakarta.apache.org
> Subject: How dynamic components could be created?
>
> Hello,
> we are a small group of developers creating a multilayer system that
> will process databases and map applications. We decided to build
> user-interface layer using Tapestry, and business-logic layer using
> Spring. The specification of the project requests separating business
> logic layer from user interface layer.
>
> System architecture conforms, from our point of view, to MVC
> (Model-View-Controller) design pattern. Spring components and business
> logics create Model (data and metadata). Tapestry serves as interpreter
> for the Model, and it creates View. Model is thus transferred from
> business logic (Controller) to Tapestry components (View); it contains
> data and metadata in the form of XML document. Model interpretation
> provided by some components of Tapestry (eg. form or table) would enable
> us generate from received data and metadata dynamic outputs.
>
> Here we face difficulties. We tried to create dynamic Template and
> Specification using Delegate class (Template-Source-Delegate,
> Specification-Resolver-Delegate). But at this very moment neither page
> instance exists, nor exist parameters, that should be passed between
> pages in RequestCycle. We use PrepareForRender to retrieve our Model
> from business logic layer.
>
> Is there anybody to give us a piece of advice? Has Tapestry a solution
> how such dynamic components could be created? (those that use data
> passed by another layer) Can Delegate Template use parameters from
> RequestCycle? Or can Delegete be invoked after PrepareForRender has been
> processed?
>
> We look forward to hearing your advice.
>
> Thanks
>
> Jirka and Pavel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How dynamic components could be created?
Posted by Chris Nelson <cn...@yahoo.com>.
Hmm, sounds like you are doing something fairly
similar to what I'm doing with Trails. Check it out
at trails.dev.java.net. In Trails, I solve the
problem of needing to dynamically decide how to
render a property by using the Tapestry recommended
approach, Block components. I have Blocks for each
editor (string, date, number, etc) and choose which
Block to render by the type of the property (or other
metadata).
--Chris
--- Pavel Rezny <pa...@tmapy.cz> wrote:
> Hello,
> we are a small group of developers creating a
> multilayer system that
> will process databases and map applications. We
> decided to build
> user-interface layer using Tapestry, and
> business-logic layer using
> Spring. The specification of the project requests
> separating business
> logic layer from user interface layer.
>
> System architecture conforms, from our point of
> view, to MVC
> (Model-View-Controller) design pattern. Spring
> components and business
> logics create Model (data and metadata). Tapestry
> serves as interpreter
> for the Model, and it creates View. Model is thus
> transferred from
> business logic (Controller) to Tapestry components
> (View); it contains
> data and metadata in the form of XML document. Model
> interpretation
> provided by some components of Tapestry (eg. form or
> table) would enable
> us generate from received data and metadata dynamic
> outputs.
>
> Here we face difficulties. We tried to create
> dynamic Template and
> Specification using Delegate class
> (Template-Source-Delegate,
> Specification-Resolver-Delegate). But at this very
> moment neither page
> instance exists, nor exist parameters, that should
> be passed between
> pages in RequestCycle. We use PrepareForRender to
> retrieve our Model
> from business logic layer.
>
> Is there anybody to give us a piece of advice? Has
> Tapestry a solution
> how such dynamic components could be created? (those
> that use data
> passed by another layer) Can Delegate Template use
> parameters from
> RequestCycle? Or can Delegete be invoked after
> PrepareForRender has been
> processed?
>
> We look forward to hearing your advice.
>
> Thanks
>
> Jirka and Pavel
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
>
______________________________________________________
Yahoo! for Good
Donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
How dynamic components could be created?
Posted by Pavel Rezny <pa...@tmapy.cz>.
Hello,
we are a small group of developers creating a multilayer system that
will process databases and map applications. We decided to build
user-interface layer using Tapestry, and business-logic layer using
Spring. The specification of the project requests separating business
logic layer from user interface layer.
System architecture conforms, from our point of view, to MVC
(Model-View-Controller) design pattern. Spring components and business
logics create Model (data and metadata). Tapestry serves as interpreter
for the Model, and it creates View. Model is thus transferred from
business logic (Controller) to Tapestry components (View); it contains
data and metadata in the form of XML document. Model interpretation
provided by some components of Tapestry (eg. form or table) would enable
us generate from received data and metadata dynamic outputs.
Here we face difficulties. We tried to create dynamic Template and
Specification using Delegate class (Template-Source-Delegate,
Specification-Resolver-Delegate). But at this very moment neither page
instance exists, nor exist parameters, that should be passed between
pages in RequestCycle. We use PrepareForRender to retrieve our Model
from business logic layer.
Is there anybody to give us a piece of advice? Has Tapestry a solution
how such dynamic components could be created? (those that use data
passed by another layer) Can Delegate Template use parameters from
RequestCycle? Or can Delegete be invoked after PrepareForRender has been
processed?
We look forward to hearing your advice.
Thanks
Jirka and Pavel
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: TheServerSide.com moving away from Tapestry?
Posted by Konstantin Ignatyev <kg...@yahoo.com>.
>From TSS:
>>These are the two most severe problems TSS has right
now. Both are related to data, not UI (although we're
aware of some UI issues too),<<
My speculations:
I newer trusted JDO and it looks like they do have
problems on that layer plus possible DB design and the
way ORM handles that.
I love ORMs, but at times I complement them with
iBatis to achieve better performance and convenience.
--- Matt Welch <ma...@gmail.com> wrote:
>
http://www.theserverside.com/news/thread.tss?thread_id=36654
>
> In the above referenced thread there is a reference
> to the TSS having some
> serious issues with the perfromance and UI of their
> site and that they will
> soon be moving to an all new codebase. Wasn't it
> pretty recently that TSS
> relaunched using Tapestry? Are they having problems
> with it? I'd be curious
> to find out as I'm considering using Tapestry on a
> large scale product in
> the not to distant future and wouldn't want to come
> up against the same
> problems.
>
Konstantin Ignatyev
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org