You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by James Hays <ja...@mac.com> on 2003/09/17 18:47:17 UTC
WebObjects and Tapestry
I hope this is ok to post here, but I'm curious.
Bryan Lewis responded to a message earlier that I posted and mentioned
that he had used webobjects. I'm curious how many others have used
webObjects and how they feel tapestry compares, both pro's and con's.
Bryan, and others, could you enlighten us a bit if you have time?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: WebObjects and Tapestry
Posted by James Orchard-Hays <ja...@dang.com>.
Drew, thanks for that post! Wow!
Jamie
On Friday, September 19, 2003, at 01:37 PM, Drew Davidson wrote:
> Jamie Orchard-Hays wrote:
>
>> On the political side of things...
>>
>> I was at WWDC this June and was planning on attending a bunch of WO
>> sessions. The first one I went to was so depressing that I didn't
>> attend any
>> others. Why was it depressing? There was no energy coming from the
>> speakers,
>> everything seemed to be in "maintenance mode," there were no
>> interesting or
>> exciting future plans mentioned. The whole vibe was, "this thing's
>> dying on
>> the vine." The atmosphere in almost every other session was the
>> opposite:
>> excitement, bright future, loads of energy, lots to talk about.
>>
>> WO may be around for a while yet, but I don't think you'll see any
>> exciting
>> enhancements to it. Fortunately Tapestry is here, and is in many ways
>> better
>> anyway.
>>
> Your experience is similar to mine.
>
> I went to WWDC 2001 full of excitement about WO, since at that time
> they were just getting the pure Java 5.0 version out the door. I had
> talked with them previously about how they were going to transition
> from ObjC to Java and was concerned about the API.
>
> Their main focus was to make it API compatible with ObjC - something I
> thought was ridiculous. From their point of view, I guess that their
> customers were clamoring for this because it would make transitioning
> their applications from ObjC to Java easier; most of the WO work we
> did at Running Start (where I worked with Erik Hatcher) during 2000
> involved using the ObjC-Java bridge and the Java API to WO that was
> provided. So there was an existing Java API for WO.
>
> However, this decision had long-term consequences to users. The API
> as presented by the ObjC-Java bridge was an Objective-C API - no two
> ways about it. It was not Java-like in the least. The API used
> internal collections (NSArray, NSDictionary, etc.) instead of the
> soon-to-be-standard Java Collections in java.util. The method names
> were ObjC-like and not JavaBeans patterns where that made sense. ObjC
> concepts like categories and inherited class methods that Java does
> not support were rough translations and sometimes the disconnect was
> obvious.
>
> Short term this is a benefit as developers can more easily port their
> code.
> Long term, however, this means that you must live in the Apple WO
> world instead of the bigger Java world. Adaptors must be written when
> interaction is required between APIs and standard tools for doing
> JavaBeans stuff just won't fit without making custom BeanInfo objects
> for the necessary objects.
>
> The WO API itself was written very long ago (it started back at NeXT
> back in 1994, for crying out loud!) and it was written with the
> perspective that you build a WO *application* that acts as an
> application server. It does not take into account the notion of
> Application Servers and therefore solves the entire Application Server
> role from soup to nuts. At the time it was written this was sensible.
>
> But the world has moved on. Servlets are now the standard way to
> deploy Java web applications. Apple has made efforts to integrate WO
> with the Servlets, and even integrate with JSP, but IMNSHO they have
> not really made it feasible to develop and deploy this way. The API
> is just too elderly and they needed to have ripped a new page off the
> notebook, taken the concepts and started over. The concepts are still
> very valid. Nothing else (up until Tapestry) had attempted to really
> componentize the web, and that is very much to NeXT's (then Apple's)
> credit. When Howard started over with the basic assumptions of
> Application Server, Servlets, etc. and applied the excellent concepts
> from WO he created Tapestry. Tapestry is, to my mind, what WO 5.0
> should have been. The failure was due to Apple's doing what the
> customer *wanted* and not what they *needed*. I'm sure that Apple's
> rationale for doing what they did was to support their customer base
> and not lose those customers. But look at their market now - they are
> niche. But the 3 WO customers left probably had a very easy time
> porting their 4.5 applications to 5.0.
>
> BTW I mentioned the collections problem at WWDC (in one of the
> sessions, in front of everyone) and was brushed off by Ernie Prabakhar
> (the manager in charge of WO at the time) by him claiming that their
> collections were not functionaly compatible (mainly due to null
> handling); I told him that I had integrated the two without conflict
> with some facades that wrapped the NS stuff to Java Collection stuff.
> It worked, but was wasteful because of all of the adaptors hanging
> around and the constant awareness you had to have at integration
> points. They really had no interest in solving this problem, and it
> was clear they just wanted me to shut up and go away because I was
> expressing concern and critique instead of praise and adulation.
>
> You, Jamie, are correct in your assesment that WO has stopped
> evolving. It has become a niche solution wherein you have to buy into
> the entire Apple web development package, rather than being able to
> use the tools you want and exclude those you don't. The only company
> that can get away with this kind of behaviour and still keep market
> share is Microsoft.
>
> - Drew
>
> --
> +---------------------------------+
> < Drew Davidson | OGNL Technology >
> < Professional Open Source >
> +---------------------------------+
> | Email: drew@ognl.org /
> | Web: http://www.ognl.org /
> | Vox: (520) 531-1966 <
> | Fax: (520) 531-1965 \
> | Mobile: (520) 405-2967 \
> +---------------------------------+
>
>
>
> ---------------------------------------------------------------------
> 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: WebObjects and Tapestry
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Don't expect to post a message the rich and colorful and not get quoted in my blog!
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: WebObjects and Tapestry
Posted by Drew Davidson <dr...@ognl.org>.
Jamie Orchard-Hays wrote:
>On the political side of things...
>
>I was at WWDC this June and was planning on attending a bunch of WO
>sessions. The first one I went to was so depressing that I didn't attend any
>others. Why was it depressing? There was no energy coming from the speakers,
>everything seemed to be in "maintenance mode," there were no interesting or
>exciting future plans mentioned. The whole vibe was, "this thing's dying on
>the vine." The atmosphere in almost every other session was the opposite:
>excitement, bright future, loads of energy, lots to talk about.
>
>WO may be around for a while yet, but I don't think you'll see any exciting
>enhancements to it. Fortunately Tapestry is here, and is in many ways better
>anyway.
>
>
Your experience is similar to mine.
I went to WWDC 2001 full of excitement about WO, since at that time they
were just getting the pure Java 5.0 version out the door. I had talked
with them previously about how they were going to transition from ObjC
to Java and was concerned about the API.
Their main focus was to make it API compatible with ObjC - something I
thought was ridiculous. From their point of view, I guess that their
customers were clamoring for this because it would make transitioning
their applications from ObjC to Java easier; most of the WO work we did
at Running Start (where I worked with Erik Hatcher) during 2000 involved
using the ObjC-Java bridge and the Java API to WO that was provided. So
there was an existing Java API for WO.
However, this decision had long-term consequences to users. The API as
presented by the ObjC-Java bridge was an Objective-C API - no two ways
about it. It was not Java-like in the least. The API used internal
collections (NSArray, NSDictionary, etc.) instead of the
soon-to-be-standard Java Collections in java.util. The method names
were ObjC-like and not JavaBeans patterns where that made sense. ObjC
concepts like categories and inherited class methods that Java does not
support were rough translations and sometimes the disconnect was obvious.
Short term this is a benefit as developers can more easily port their
code.
Long term, however, this means that you must live in the Apple WO world
instead of the bigger Java world. Adaptors must be written when
interaction is required between APIs and standard tools for doing
JavaBeans stuff just won't fit without making custom BeanInfo objects
for the necessary objects.
The WO API itself was written very long ago (it started back at NeXT
back in 1994, for crying out loud!) and it was written with the
perspective that you build a WO *application* that acts as an
application server. It does not take into account the notion of
Application Servers and therefore solves the entire Application Server
role from soup to nuts. At the time it was written this was sensible.
But the world has moved on. Servlets are now the standard way to deploy
Java web applications. Apple has made efforts to integrate WO with the
Servlets, and even integrate with JSP, but IMNSHO they have not really
made it feasible to develop and deploy this way. The API is just too
elderly and they needed to have ripped a new page off the notebook,
taken the concepts and started over. The concepts are still very
valid. Nothing else (up until Tapestry) had attempted to really
componentize the web, and that is very much to NeXT's (then Apple's)
credit. When Howard started over with the basic assumptions of
Application Server, Servlets, etc. and applied the excellent concepts
from WO he created Tapestry. Tapestry is, to my mind, what WO 5.0
should have been. The failure was due to Apple's doing what the
customer *wanted* and not what they *needed*. I'm sure that Apple's
rationale for doing what they did was to support their customer base and
not lose those customers. But look at their market now - they are
niche. But the 3 WO customers left probably had a very easy time
porting their 4.5 applications to 5.0.
BTW I mentioned the collections problem at WWDC (in one of the sessions,
in front of everyone) and was brushed off by Ernie Prabakhar (the
manager in charge of WO at the time) by him claiming that their
collections were not functionaly compatible (mainly due to null
handling); I told him that I had integrated the two without conflict
with some facades that wrapped the NS stuff to Java Collection stuff.
It worked, but was wasteful because of all of the adaptors hanging
around and the constant awareness you had to have at integration
points. They really had no interest in solving this problem, and it was
clear they just wanted me to shut up and go away because I was
expressing concern and critique instead of praise and adulation.
You, Jamie, are correct in your assesment that WO has stopped evolving.
It has become a niche solution wherein you have to buy into the entire
Apple web development package, rather than being able to use the tools
you want and exclude those you don't. The only company that can get
away with this kind of behaviour and still keep market share is Microsoft.
- Drew
--
+---------------------------------+
< Drew Davidson | OGNL Technology >
< Professional Open Source >
+---------------------------------+
| Email: drew@ognl.org /
| Web: http://www.ognl.org /
| Vox: (520) 531-1966 <
| Fax: (520) 531-1965 \
| Mobile: (520) 405-2967 \
+---------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: pdfs as private assets?
Posted by Eric Schneider <er...@centralparksoftware.com>.
Thanks. That was easy.
e.
----- Original Message -----
From: "Howard M. Lewis Ship" <hl...@comcast.net>
To: "'Tapestry users'" <ta...@jakarta.apache.org>
Sent: Wednesday, September 17, 2003 5:30 PM
Subject: RE: pdfs as private assets?
> You can use the Any component, i.e.
>
> <a jwcid="@Any" href="ognl:assets.mypdf"> the secret doc </a>
>
> Informal parameters whose type is IAsset are converted into URLs when
rendered as attributes.
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/tapestry
> http://jakarta.apache.org/commons/sandbox/hivemind/
> http://javatapestry.blogspot.com
>
> > -----Original Message-----
> > From: Eric Schneider [mailto:eric@centralparksoftware.com]
> > Sent: Wednesday, September 17, 2003 5:12 PM
> > To: Tapestry users
> > Subject: pdfs as private assets?
> >
> >
> > Hi,
> >
> > Just wondering if you can reference pdf files as private
> > assets? For security reasons, I prefer not to put these
> > files outside of the /WEB-INF folder.
> >
> > Is there a way to reference private assets with a tapestry
> > hyperlink/action?
> >
> > Thanks,
> > Eric
> >
> >
> > ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: pdfs as private assets?
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
You can use the Any component, i.e.
<a jwcid="@Any" href="ognl:assets.mypdf"> the secret doc </a>
Informal parameters whose type is IAsset are converted into URLs when rendered as attributes.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Eric Schneider [mailto:eric@centralparksoftware.com]
> Sent: Wednesday, September 17, 2003 5:12 PM
> To: Tapestry users
> Subject: pdfs as private assets?
>
>
> Hi,
>
> Just wondering if you can reference pdf files as private
> assets? For security reasons, I prefer not to put these
> files outside of the /WEB-INF folder.
>
> Is there a way to reference private assets with a tapestry
> hyperlink/action?
>
> Thanks,
> Eric
>
>
> ---------------------------------------------------------------------
> 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
pdfs as private assets?
Posted by Eric Schneider <er...@centralparksoftware.com>.
Hi,
Just wondering if you can reference pdf files as private assets? For
security reasons, I prefer not to put these files outside of the /WEB-INF
folder.
Is there a way to reference private assets with a tapestry hyperlink/action?
Thanks,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: WebObjects and Tapestry
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
In some ways its more work, but the stuff I'm doing with bytecode enhancement (using Javassist) is
pretty far beyond what you could do with Objective-C categories.
Anyone going to ApacheCon? We'll see if I can put a little energy into Tapestry. Of course, how
much can you cover in 60 minutes (including Q&A)?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Jamie Orchard-Hays [mailto:jamie@dang.com]
> Sent: Wednesday, September 17, 2003 3:36 PM
> To: Tapestry users
> Subject: Re: WebObjects and Tapestry
>
>
> On the political side of things...
>
> I was at WWDC this June and was planning on attending a bunch
> of WO sessions. The first one I went to was so depressing
> that I didn't attend any others. Why was it depressing? There
> was no energy coming from the speakers, everything seemed to
> be in "maintenance mode," there were no interesting or
> exciting future plans mentioned. The whole vibe was, "this
> thing's dying on the vine." The atmosphere in almost every
> other session was the opposite: excitement, bright future,
> loads of energy, lots to talk about.
>
> WO may be around for a while yet, but I don't think you'll
> see any exciting enhancements to it. Fortunately Tapestry is
> here, and is in many ways better anyway.
>
> Jamie
>
>
> ----- Original Message -----
> From: "Bryan Lewis" <br...@maine.rr.com>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Wednesday, September 17, 2003 2:37 PM
> Subject: Re: WebObjects and Tapestry
>
>
> > Search the mailing list for "webobjects". (Gmane is pretty good at
> one-word
> > searches. :-) You should get a list of about 24 postings.
> >
> > To summarize my view (after 3.5 years of webobjects
> experience and 0.5
> years of
> > tapestry), Tapestry is what I had hoped WebObjects would
> be. Similar
> > architecture and concepts (easy component reuse, little or
> no code in
> > the view... I'm still reserving judgment on the "ognl:property"
> > shorthand in
> the
> > html!), but Tapestry has better separation of concerns
> (perhaps partly
> because
> > it didn't attempt to provide persistence), and seems to be better
> implemented
> > in lots of little ways (error reporting, for example).
> >
> > Disclaimer: I'm still on the old webobjects 4.51 using Objective-C
> > and
> I've
> > forgotten what a working debugger is, so feel free to ignore me.
> > Perhaps
> the
> > newer versions are better, especially if you can leave behind the
> compatibility
> > baggage of the old frameworks. For all I know. it might be possible
> nowadays
> > to use Ant and Eclipse with WO.
> >
> > Second disclaimer: Here's hoping not to touch off any
> arguments with
> > the occasional webobjects fan slumming this list. :-) I
> didn't say WO
> > was
> bad --
> > I'm still using it productively every day -- just not as good. Some
> people
> > prefer an all-in-one proprietary product that includes presentation
> > and persistence, and that preference would easily be enough
> to justify
> > the
> small
> > cost of WO. (I mean, the one-time price of most software is almost
> irrelevant,
> > right?) If you want to argue about things that are _bad_, we could
> > take
> up
> > windows or interpreted scripting languages. :-) (Notice
> how tactfully
> > I avoided mentioning other open-source products with
> six-letter names
> beginning
> > and ending with s.)
> >
> > P.S. Proposed entry for the Tapestry Museum:
> > When I first looked at Tapestry I could tell it was somehow
> related to
> > WO
> but I
> > wasn't quite sure how... Howard never mentioned it in the
> docs. After
> some
> > creative googling I discovered this bit of history, indicating that
> > Tap
> and WO
> > are something like step-cousins:
> > http://www.stepwise.com/Articles/Technical/JavaCats.html
> > where Howard said, "I'm an OpenStep/Objective-C developer making the
> transition
> > to Java." That was 5.5 years ago!
> >
> >
> >
> > ----- Original Message -----
> > From: "James Hays" <ja...@mac.com>
> > To: "Tapestry users" <ta...@jakarta.apache.org>
> > Sent: Wednesday, September 17, 2003 12:47 PM
> > Subject: WebObjects and Tapestry
> >
> >
> > > I hope this is ok to post here, but I'm curious.
> > > Bryan Lewis responded to a message earlier that I posted and
> > > mentioned that he had used webobjects. I'm curious how
> many others
> > > have used webObjects and how they feel tapestry compares,
> both pro's
> > > and con's.
> > >
> > > Bryan, and others, could you enlighten us a bit if you have time?
> > >
> > >
> > >
> --------------------------------------------------------------------
> > > -
> > > 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
> >
> >
>
>
> ---------------------------------------------------------------------
> 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: WebObjects and Tapestry
Posted by Jamie Orchard-Hays <ja...@dang.com>.
On the political side of things...
I was at WWDC this June and was planning on attending a bunch of WO
sessions. The first one I went to was so depressing that I didn't attend any
others. Why was it depressing? There was no energy coming from the speakers,
everything seemed to be in "maintenance mode," there were no interesting or
exciting future plans mentioned. The whole vibe was, "this thing's dying on
the vine." The atmosphere in almost every other session was the opposite:
excitement, bright future, loads of energy, lots to talk about.
WO may be around for a while yet, but I don't think you'll see any exciting
enhancements to it. Fortunately Tapestry is here, and is in many ways better
anyway.
Jamie
----- Original Message -----
From: "Bryan Lewis" <br...@maine.rr.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, September 17, 2003 2:37 PM
Subject: Re: WebObjects and Tapestry
> Search the mailing list for "webobjects". (Gmane is pretty good at
one-word
> searches. :-) You should get a list of about 24 postings.
>
> To summarize my view (after 3.5 years of webobjects experience and 0.5
years of
> tapestry), Tapestry is what I had hoped WebObjects would be. Similar
> architecture and concepts (easy component reuse, little or no code in the
> view... I'm still reserving judgment on the "ognl:property" shorthand in
the
> html!), but Tapestry has better separation of concerns (perhaps partly
because
> it didn't attempt to provide persistence), and seems to be better
implemented
> in lots of little ways (error reporting, for example).
>
> Disclaimer: I'm still on the old webobjects 4.51 using Objective-C and
I've
> forgotten what a working debugger is, so feel free to ignore me. Perhaps
the
> newer versions are better, especially if you can leave behind the
compatibility
> baggage of the old frameworks. For all I know. it might be possible
nowadays
> to use Ant and Eclipse with WO.
>
> Second disclaimer: Here's hoping not to touch off any arguments with the
> occasional webobjects fan slumming this list. :-) I didn't say WO was
bad --
> I'm still using it productively every day -- just not as good. Some
people
> prefer an all-in-one proprietary product that includes presentation and
> persistence, and that preference would easily be enough to justify the
small
> cost of WO. (I mean, the one-time price of most software is almost
irrelevant,
> right?) If you want to argue about things that are _bad_, we could take
up
> windows or interpreted scripting languages. :-) (Notice how tactfully I
> avoided mentioning other open-source products with six-letter names
beginning
> and ending with s.)
>
> P.S. Proposed entry for the Tapestry Museum:
> When I first looked at Tapestry I could tell it was somehow related to WO
but I
> wasn't quite sure how... Howard never mentioned it in the docs. After
some
> creative googling I discovered this bit of history, indicating that Tap
and WO
> are something like step-cousins:
> http://www.stepwise.com/Articles/Technical/JavaCats.html
> where Howard said, "I'm an OpenStep/Objective-C developer making the
transition
> to Java." That was 5.5 years ago!
>
>
>
> ----- Original Message -----
> From: "James Hays" <ja...@mac.com>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Wednesday, September 17, 2003 12:47 PM
> Subject: WebObjects and Tapestry
>
>
> > I hope this is ok to post here, but I'm curious.
> > Bryan Lewis responded to a message earlier that I posted and mentioned
> > that he had used webobjects. I'm curious how many others have used
> > webObjects and how they feel tapestry compares, both pro's and con's.
> >
> > Bryan, and others, could you enlighten us a bit if you have time?
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: WebObjects and Tapestry
Posted by Bryan Lewis <br...@maine.rr.com>.
Search the mailing list for "webobjects". (Gmane is pretty good at one-word
searches. :-) You should get a list of about 24 postings.
To summarize my view (after 3.5 years of webobjects experience and 0.5 years of
tapestry), Tapestry is what I had hoped WebObjects would be. Similar
architecture and concepts (easy component reuse, little or no code in the
view... I'm still reserving judgment on the "ognl:property" shorthand in the
html!), but Tapestry has better separation of concerns (perhaps partly because
it didn't attempt to provide persistence), and seems to be better implemented
in lots of little ways (error reporting, for example).
Disclaimer: I'm still on the old webobjects 4.51 using Objective-C and I've
forgotten what a working debugger is, so feel free to ignore me. Perhaps the
newer versions are better, especially if you can leave behind the compatibility
baggage of the old frameworks. For all I know. it might be possible nowadays
to use Ant and Eclipse with WO.
Second disclaimer: Here's hoping not to touch off any arguments with the
occasional webobjects fan slumming this list. :-) I didn't say WO was bad --
I'm still using it productively every day -- just not as good. Some people
prefer an all-in-one proprietary product that includes presentation and
persistence, and that preference would easily be enough to justify the small
cost of WO. (I mean, the one-time price of most software is almost irrelevant,
right?) If you want to argue about things that are _bad_, we could take up
windows or interpreted scripting languages. :-) (Notice how tactfully I
avoided mentioning other open-source products with six-letter names beginning
and ending with s.)
P.S. Proposed entry for the Tapestry Museum:
When I first looked at Tapestry I could tell it was somehow related to WO but I
wasn't quite sure how... Howard never mentioned it in the docs. After some
creative googling I discovered this bit of history, indicating that Tap and WO
are something like step-cousins:
http://www.stepwise.com/Articles/Technical/JavaCats.html
where Howard said, "I'm an OpenStep/Objective-C developer making the transition
to Java." That was 5.5 years ago!
----- Original Message -----
From: "James Hays" <ja...@mac.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, September 17, 2003 12:47 PM
Subject: WebObjects and Tapestry
> I hope this is ok to post here, but I'm curious.
> Bryan Lewis responded to a message earlier that I posted and mentioned
> that he had used webobjects. I'm curious how many others have used
> webObjects and how they feel tapestry compares, both pro's and con's.
>
> Bryan, and others, could you enlighten us a bit if you have time?
>
>
> ---------------------------------------------------------------------
> 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: WebObjects and Tapestry
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I used WebObjects briefly and never really did anything substantial
with it, so I'll only make a comment on what I do know and let others
fill in more.
Tapestry's HTML templates are purer - in that the dynamic "tags" are
really HTML elements, whereas in WebObjects there was only the
<WEBOBJECT> tag. So Tapestry is even more designer friendly.
Erik
On Wednesday, September 17, 2003, at 12:47 PM, James Hays wrote:
> I hope this is ok to post here, but I'm curious.
> Bryan Lewis responded to a message earlier that I posted and mentioned
> that he had used webobjects. I'm curious how many others have used
> webObjects and how they feel tapestry compares, both pro's and con's.
>
> Bryan, and others, could you enlighten us a bit if you have time?
>
>
> ---------------------------------------------------------------------
> 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