You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Mark Stang <ms...@pingidentity.com> on 2007/01/29 16:57:38 UTC
FW: Tapestry 3.0.4..not on mirrors
All,
We were looking to upgrade from 3.03. to 3.04 and it appears that 3.04 isn't on the mirrors.
Thoughts?
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Dave Smith
Sent: Mon 1/29/2007 6:48 AM
To: Mark Stang
Subject: Tapestry 3.0.4..not on mirrors
I was going to upgrade to 3.0.4 this morning, but it's not on any of the
Apache mirrors. Care to inquire on the list as to what's going on?
Thx.
D.
Re: Tapestry 3.x DEAD
Posted by Jeff Poetker <je...@gmail.com>.
To anybody whom it may concern...
The threading problem referred to in this thread, can be worked
around by overriding the AbstractEngine's protected
createComponentClassEnhancer method to return a synchronized version
of the enhancer. This makes 3.0.4 work like earlier versions of
Tapestry as far as we can tell.
Of course, you shouldn't *have* to do this.
Below is some code:
In your custom engine:
protected IComponentClassEnhancer createComponentClassEnhancer
(RequestContext context)
{
boolean disableValidation =
"true".equals(
this._propertySource.getPropertyValue(
"org.apache.tapestry.enhance.disable-abstract-
method-validation"));
return new SynchronizedComponentClassEnhancer
(this._resolver, disableValidation);
}
And a new class:
public class SynchronizedComponentClassEnhancer extends
DefaultComponentClassEnhancer {
public SynchronizedComponentClassEnhancer(IResourceResolver
resolver, boolean disableValidation) {
super(resolver, disableValidation);
}
/**
* Returns the Class, in a synchronized manner.
*
* @see
org.apache.tapestry.enhance.DefaultComponentClassEnhancer#getEnhancedCla
ss(org.apache.tapestry.spec.IComponentSpecification, java.lang.String)
*/
public synchronized Class getEnhancedClass
(IComponentSpecification specification, String className)
{
Class result = getCachedClass(specification);
if (result == null) {
result = constructComponentClass(specification, className);
storeCachedClass(specification, result);
}
return result;
}
/**
* Returns a Synchronized implemenation of IEnhancedClassFactory
*
* @see
org.apache.tapestry.enhance.DefaultComponentClassEnhancer#createEnhanced
ClassFactory()
*/
protected IEnhancedClassFactory createEnhancedClassFactory()
{
return new SynchronizedEnhancedClassFactory
(getResourceResolver());
}
}
On Jan 31, 2007, at 2:37 PM, Mark Stang wrote:
> Howard,
> It appears that development on 3.x has stalled to a complete stop.
> The web-site lists the latest 3.x release as 3.0.4. According to
> the "news" it says 3.0.4 has hundreds of bug fixes. What it
> doesn't show is that 3.0.4 has a threading issue. The issue was
> identified over two months ago. The 3.0.4 is not on any of the
> mirrors, I guess because of the bug.
>
> All-in-all, it appears that not only is 3.x dead but there is a
> "bad" version sitting out there mis-leading potential users.
> Unless someone is going to pick up 3.x, the web site should be
> reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and
> all JIRA issues reflecting the fixes that were done should be re-
> listed as outstanding. Those "fixes" which happened in 3.0.4 are
> still a problem for anyone using 3.0.3 but JIRA says they were fixed.
>
> The web site might as well show that 3.x is dead and tell everyone
> that it will no longer be maintained.
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Mark Stang
> Sent: Tue 1/30/2007 11:33 PM
> To: Tapestry users; Tapestry users
> Subject: RE: FW: Tapestry 3.0.4..not on mirrors
>
> Nick,
> Thanks for pointing that out, I finally found the e-mail trail. I
> decided that I couldn't take a chance on 3.0.4 and reverted back to
> 3.0.3. I guess we are done with 3.x and will wait for 5.x or the
> next great GUI Framework. Tapestry has been fun and very interesting.
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Nick Westgate [mailto:nick@key-planning.co.jp]
> Sent: Tue 1/30/2007 8:10 PM
> To: Tapestry users
> Subject: Re: FW: Tapestry 3.0.4..not on mirrors
>
> Hi Mark.
>
> I'm referring to this thread:
> "3.0.4 and repetitive method name/signature problem (class
> enhancement)"
> http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
>
> Take it to the dev list when you've read that.
> (I'm not a dev, so as to who is managing 3 now ...)
>
> Cheers,
> Nick.
>
>
> Mark Stang wrote:
>> Nick,
>> I did a quick look and only saw references to 4.x. If 3.0.4 is
>> not the current release, then why does the Tapestry Web site have
>> it listed as such?
>>
>> http://tapestry.apache.org/tapestry3/
>>
>> Who is managing this?
>>
>> thanks,
>>
>> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Tapestry 3.x DEAD
Posted by Mark Stang <ms...@pingidentity.com>.
Jesse,
In other words, 3.0.4 has a fairly significant bug and nobody is maintaining it. So, at the very least someone should update the Tapestry 3 website with a WARNING that 3.0.4 has a threading bug. Of course, 3.0.3 has a bunch of bugs that were fixed in 3.0.4 so someone should annotate the website with a WARNING that 3.0.3 has many bugs.
Which sounds like to me, that 3.X is DEAD and no longer being maintained.
So, let's have a wake, toss back a few and tell everyone to move onto 4.x which is the only version being maintained at this time.
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wed 1/31/2007 2:13 PM
To: Tapestry users
Subject: Re: Tapestry 3.x DEAD
I don't remember the details surrounding the 3.0.4 release but don't
think mirrors having / not having them have anything to do with anyone
thinking it was fully / not fully released.
Really "released" just means the core downloads && website are done. I
don't think the 3.0.4 website was updated because the forrest
documentation runtime wasn't playing very well, but the actual jars
were.
After looking at the thread I do recognize that section of code and
can say with confidence that it ~has~ been fully fixed in >= 4.1.1
versions.
Opening the old project up / using the ant definitions is a real PITA,
but if you felt strongly enough about it I suppose you could always
make a patch and file it in JIRA.
The ultimate fix was achieved in the DisableCachingFilter (for 4.x at
least), instead of the ComponentClass enhancer. The synchronized
blocks can probably be taken out. (or replaced with more thread
efficient backport-util counterparts - unless you are using more
recent jres in production where it looks like the old synchronized
speed issues have potentially been fixed)
On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> Jesse,
> I don't think the dynamic url stuff is the issue. Actually, there are two issues. The first issue is the threading bug. The next issue is that 3.0.4 was never fully released, as I understand it, due to the threading bug. Which is why it isn't on the mirrors. It is supposed to be "released", but it looks like it got half way there and then died.
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Wed 1/31/2007 1:27 PM
> To: Tapestry users
> Cc: hlship@gmail.com
> Subject: Re: Tapestry 3.x DEAD
>
> I don't know what's wrong with the dynamic url stuff (I did test it
> before updating the main site), but you can always get it from:
>
> http://www.apache.org/dist/tapestry/
>
> On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> > Howard,
> > It appears that development on 3.x has stalled to a complete stop. The web-site lists the latest 3.x release as 3.0.4. According to the "news" it says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a threading issue. The issue was identified over two months ago. The 3.0.4 is not on any of the mirrors, I guess because of the bug.
> >
> > All-in-all, it appears that not only is 3.x dead but there is a "bad" version sitting out there mis-leading potential users. Unless someone is going to pick up 3.x, the web site should be reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and all JIRA issues reflecting the fixes that were done should be re-listed as outstanding. Those "fixes" which happened in 3.0.4 are still a problem for anyone using 3.0.3 but JIRA says they were fixed.
> >
> > The web site might as well show that 3.x is dead and tell everyone that it will no longer be maintained.
> >
> > Mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
> > -----Original Message-----
> > From: Mark Stang
> > Sent: Tue 1/30/2007 11:33 PM
> > To: Tapestry users; Tapestry users
> > Subject: RE: FW: Tapestry 3.0.4..not on mirrors
> >
> > Nick,
> > Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
> >
> > regards,
> >
> > Mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
> > -----Original Message-----
> > From: Nick Westgate [mailto:nick@key-planning.co.jp]
> > Sent: Tue 1/30/2007 8:10 PM
> > To: Tapestry users
> > Subject: Re: FW: Tapestry 3.0.4..not on mirrors
> >
> > Hi Mark.
> >
> > I'm referring to this thread:
> > "3.0.4 and repetitive method name/signature problem (class enhancement)"
> > http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
> >
> > Take it to the dev list when you've read that.
> > (I'm not a dev, so as to who is managing 3 now ...)
> >
> > Cheers,
> > Nick.
> >
> >
> > Mark Stang wrote:
> > > Nick,
> > > I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
> > >
> > > http://tapestry.apache.org/tapestry3/
> > >
> > > Who is managing this?
> > >
> > > thanks,
> > >
> > > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry 3.x DEAD
Posted by Jesse Kuhnert <jk...@gmail.com>.
I don't remember the details surrounding the 3.0.4 release but don't
think mirrors having / not having them have anything to do with anyone
thinking it was fully / not fully released.
Really "released" just means the core downloads && website are done. I
don't think the 3.0.4 website was updated because the forrest
documentation runtime wasn't playing very well, but the actual jars
were.
After looking at the thread I do recognize that section of code and
can say with confidence that it ~has~ been fully fixed in >= 4.1.1
versions.
Opening the old project up / using the ant definitions is a real PITA,
but if you felt strongly enough about it I suppose you could always
make a patch and file it in JIRA.
The ultimate fix was achieved in the DisableCachingFilter (for 4.x at
least), instead of the ComponentClass enhancer. The synchronized
blocks can probably be taken out. (or replaced with more thread
efficient backport-util counterparts - unless you are using more
recent jres in production where it looks like the old synchronized
speed issues have potentially been fixed)
On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> Jesse,
> I don't think the dynamic url stuff is the issue. Actually, there are two issues. The first issue is the threading bug. The next issue is that 3.0.4 was never fully released, as I understand it, due to the threading bug. Which is why it isn't on the mirrors. It is supposed to be "released", but it looks like it got half way there and then died.
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Wed 1/31/2007 1:27 PM
> To: Tapestry users
> Cc: hlship@gmail.com
> Subject: Re: Tapestry 3.x DEAD
>
> I don't know what's wrong with the dynamic url stuff (I did test it
> before updating the main site), but you can always get it from:
>
> http://www.apache.org/dist/tapestry/
>
> On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> > Howard,
> > It appears that development on 3.x has stalled to a complete stop. The web-site lists the latest 3.x release as 3.0.4. According to the "news" it says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a threading issue. The issue was identified over two months ago. The 3.0.4 is not on any of the mirrors, I guess because of the bug.
> >
> > All-in-all, it appears that not only is 3.x dead but there is a "bad" version sitting out there mis-leading potential users. Unless someone is going to pick up 3.x, the web site should be reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and all JIRA issues reflecting the fixes that were done should be re-listed as outstanding. Those "fixes" which happened in 3.0.4 are still a problem for anyone using 3.0.3 but JIRA says they were fixed.
> >
> > The web site might as well show that 3.x is dead and tell everyone that it will no longer be maintained.
> >
> > Mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
> > -----Original Message-----
> > From: Mark Stang
> > Sent: Tue 1/30/2007 11:33 PM
> > To: Tapestry users; Tapestry users
> > Subject: RE: FW: Tapestry 3.0.4..not on mirrors
> >
> > Nick,
> > Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
> >
> > regards,
> >
> > Mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
> > -----Original Message-----
> > From: Nick Westgate [mailto:nick@key-planning.co.jp]
> > Sent: Tue 1/30/2007 8:10 PM
> > To: Tapestry users
> > Subject: Re: FW: Tapestry 3.0.4..not on mirrors
> >
> > Hi Mark.
> >
> > I'm referring to this thread:
> > "3.0.4 and repetitive method name/signature problem (class enhancement)"
> > http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
> >
> > Take it to the dev list when you've read that.
> > (I'm not a dev, so as to who is managing 3 now ...)
> >
> > Cheers,
> > Nick.
> >
> >
> > Mark Stang wrote:
> > > Nick,
> > > I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
> > >
> > > http://tapestry.apache.org/tapestry3/
> > >
> > > Who is managing this?
> > >
> > > thanks,
> > >
> > > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Tapestry 3.x DEAD
Posted by Mark Stang <ms...@pingidentity.com>.
Jesse,
I don't think the dynamic url stuff is the issue. Actually, there are two issues. The first issue is the threading bug. The next issue is that 3.0.4 was never fully released, as I understand it, due to the threading bug. Which is why it isn't on the mirrors. It is supposed to be "released", but it looks like it got half way there and then died.
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wed 1/31/2007 1:27 PM
To: Tapestry users
Cc: hlship@gmail.com
Subject: Re: Tapestry 3.x DEAD
I don't know what's wrong with the dynamic url stuff (I did test it
before updating the main site), but you can always get it from:
http://www.apache.org/dist/tapestry/
On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> Howard,
> It appears that development on 3.x has stalled to a complete stop. The web-site lists the latest 3.x release as 3.0.4. According to the "news" it says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a threading issue. The issue was identified over two months ago. The 3.0.4 is not on any of the mirrors, I guess because of the bug.
>
> All-in-all, it appears that not only is 3.x dead but there is a "bad" version sitting out there mis-leading potential users. Unless someone is going to pick up 3.x, the web site should be reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and all JIRA issues reflecting the fixes that were done should be re-listed as outstanding. Those "fixes" which happened in 3.0.4 are still a problem for anyone using 3.0.3 but JIRA says they were fixed.
>
> The web site might as well show that 3.x is dead and tell everyone that it will no longer be maintained.
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Mark Stang
> Sent: Tue 1/30/2007 11:33 PM
> To: Tapestry users; Tapestry users
> Subject: RE: FW: Tapestry 3.0.4..not on mirrors
>
> Nick,
> Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Nick Westgate [mailto:nick@key-planning.co.jp]
> Sent: Tue 1/30/2007 8:10 PM
> To: Tapestry users
> Subject: Re: FW: Tapestry 3.0.4..not on mirrors
>
> Hi Mark.
>
> I'm referring to this thread:
> "3.0.4 and repetitive method name/signature problem (class enhancement)"
> http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
>
> Take it to the dev list when you've read that.
> (I'm not a dev, so as to who is managing 3 now ...)
>
> Cheers,
> Nick.
>
>
> Mark Stang wrote:
> > Nick,
> > I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
> >
> > http://tapestry.apache.org/tapestry3/
> >
> > Who is managing this?
> >
> > thanks,
> >
> > Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry 3.x DEAD
Posted by Jesse Kuhnert <jk...@gmail.com>.
I don't know what's wrong with the dynamic url stuff (I did test it
before updating the main site), but you can always get it from:
http://www.apache.org/dist/tapestry/
On 1/31/07, Mark Stang <ms...@pingidentity.com> wrote:
> Howard,
> It appears that development on 3.x has stalled to a complete stop. The web-site lists the latest 3.x release as 3.0.4. According to the "news" it says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a threading issue. The issue was identified over two months ago. The 3.0.4 is not on any of the mirrors, I guess because of the bug.
>
> All-in-all, it appears that not only is 3.x dead but there is a "bad" version sitting out there mis-leading potential users. Unless someone is going to pick up 3.x, the web site should be reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and all JIRA issues reflecting the fixes that were done should be re-listed as outstanding. Those "fixes" which happened in 3.0.4 are still a problem for anyone using 3.0.3 but JIRA says they were fixed.
>
> The web site might as well show that 3.x is dead and tell everyone that it will no longer be maintained.
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Mark Stang
> Sent: Tue 1/30/2007 11:33 PM
> To: Tapestry users; Tapestry users
> Subject: RE: FW: Tapestry 3.0.4..not on mirrors
>
> Nick,
> Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Nick Westgate [mailto:nick@key-planning.co.jp]
> Sent: Tue 1/30/2007 8:10 PM
> To: Tapestry users
> Subject: Re: FW: Tapestry 3.0.4..not on mirrors
>
> Hi Mark.
>
> I'm referring to this thread:
> "3.0.4 and repetitive method name/signature problem (class enhancement)"
> http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
>
> Take it to the dev list when you've read that.
> (I'm not a dev, so as to who is managing 3 now ...)
>
> Cheers,
> Nick.
>
>
> Mark Stang wrote:
> > Nick,
> > I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
> >
> > http://tapestry.apache.org/tapestry3/
> >
> > Who is managing this?
> >
> > thanks,
> >
> > Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Tapestry 3.x DEAD
Posted by Mark Stang <ms...@pingidentity.com>.
Howard,
It appears that development on 3.x has stalled to a complete stop. The web-site lists the latest 3.x release as 3.0.4. According to the "news" it says 3.0.4 has hundreds of bug fixes. What it doesn't show is that 3.0.4 has a threading issue. The issue was identified over two months ago. The 3.0.4 is not on any of the mirrors, I guess because of the bug.
All-in-all, it appears that not only is 3.x dead but there is a "bad" version sitting out there mis-leading potential users. Unless someone is going to pick up 3.x, the web site should be reverted back to 3.0.3. Then 3.0.4 and 3.0.5 should be deleted and all JIRA issues reflecting the fixes that were done should be re-listed as outstanding. Those "fixes" which happened in 3.0.4 are still a problem for anyone using 3.0.3 but JIRA says they were fixed.
The web site might as well show that 3.x is dead and tell everyone that it will no longer be maintained.
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Mark Stang
Sent: Tue 1/30/2007 11:33 PM
To: Tapestry users; Tapestry users
Subject: RE: FW: Tapestry 3.0.4..not on mirrors
Nick,
Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Nick Westgate [mailto:nick@key-planning.co.jp]
Sent: Tue 1/30/2007 8:10 PM
To: Tapestry users
Subject: Re: FW: Tapestry 3.0.4..not on mirrors
Hi Mark.
I'm referring to this thread:
"3.0.4 and repetitive method name/signature problem (class enhancement)"
http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
Take it to the dev list when you've read that.
(I'm not a dev, so as to who is managing 3 now ...)
Cheers,
Nick.
Mark Stang wrote:
> Nick,
> I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
>
> http://tapestry.apache.org/tapestry3/
>
> Who is managing this?
>
> thanks,
>
> Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: FW: Tapestry 3.0.4..not on mirrors
Posted by Mark Stang <ms...@pingidentity.com>.
Nick,
Thanks for pointing that out, I finally found the e-mail trail. I decided that I couldn't take a chance on 3.0.4 and reverted back to 3.0.3. I guess we are done with 3.x and will wait for 5.x or the next great GUI Framework. Tapestry has been fun and very interesting.
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Nick Westgate [mailto:nick@key-planning.co.jp]
Sent: Tue 1/30/2007 8:10 PM
To: Tapestry users
Subject: Re: FW: Tapestry 3.0.4..not on mirrors
Hi Mark.
I'm referring to this thread:
"3.0.4 and repetitive method name/signature problem (class enhancement)"
http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
Take it to the dev list when you've read that.
(I'm not a dev, so as to who is managing 3 now ...)
Cheers,
Nick.
Mark Stang wrote:
> Nick,
> I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
>
> http://tapestry.apache.org/tapestry3/
>
> Who is managing this?
>
> thanks,
>
> Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Component timeouts and an NPE
Posted by Bryan Lewis <br...@maine.rr.com>.
The easy solution is, don't use private variables like that. Declare
them as persistent page properties. Do your development with caching
disabled so that the problem appears right away, rather than after a
ten-minute garbage-collection period.
Mark Stang wrote:
> Hi,
> I am seeing Tapestry 3 components with values which is good, say a ArrayList:
>
> private ArrayList<ConnectionItem> displayList;
>
> If I don't touch the component for 10 minutes or maybe a little longer, then the "displayList" is null. I assume that this is due to Tapestry putting it back in the pool. However, I then get a NPE. Any idea where I can set the timeout? Or if I can find a way to disable it. What I have to do is put a null check around access to the variable and then re-create the list if it is null.
>
> thanks,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Component timeouts and an NPE
Posted by Mark Stang <ms...@pingidentity.com>.
Hi,
I am seeing Tapestry 3 components with values which is good, say a ArrayList:
private ArrayList<ConnectionItem> displayList;
If I don't touch the component for 10 minutes or maybe a little longer, then the "displayList" is null. I assume that this is due to Tapestry putting it back in the pool. However, I then get a NPE. Any idea where I can set the timeout? Or if I can find a way to disable it. What I have to do is put a null check around access to the variable and then re-create the list if it is null.
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
How to add a .js scripts to a 3.x Shell Component
Posted by Mark Stang <ms...@pingidentity.com>.
Hi,
I have some .js scripts that I am specifying external to the Shell component. Is there a way to add them to the Shell component?
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
Re: OpenLazlo and Tapestry
Posted by Konstantin Ignatyev <kg...@yahoo.com>.
I have attended Flex presentation by Christophe
Coenraets
(http://coenraets.org/blog/2007/01/flex-data-management-services-tutorial/)
and was quite impressed (even I hate Flash ads).
I am convinced that rich flash applications are the
next big thing (web 3.0).
I wish it was JVM and Java Web Start, but because of
non modularity of JRE and inconvenience of installing
I believe that FVM (Flash VM) will be the king on
clients...
--- Jan Vissers <Ja...@cumquat.nl> wrote:
> When I'm think about Flex, movies is the last thing
> on my mind lately. I'm
> intrigued by the potential of Flex apps and/or Flex
> hybrid apps. I don't
> think Tapestry will be particularly well equipped to
> create complete Flex
> apps (but do correct me if I'm wrong). It would be
> really nice though if
> we could easily create hybrid applications using
> Flex components tied to
> our 'regular' HTML/CSS/JavaScript components using
> Flex's Ajax Bridge
> technology.
>
>
> > Anything is possible, of course. The idea of
> creating Flash (i.e.,
> > Flex or Laszlo) movies on the fly is intriguing.
> At one extreme, you
> > could get Tapestry to directly create and spool
> out the bytestream of
> > the movie, on another you could use Tapestry to
> generate the XML
> > descriptor from which the bytestream is generated.
> There's lots of
> > options.
> >
> > It's just a matter of developer bandwidth ...
> something sorely missing
> > from my life right now. Viva T5!
> >
> > On 1/31/07, munich@fantasymail.de
> <mu...@fantasymail.de> wrote:
> >> Have you heard of OpenLaszlo yet?
> >>
> >>
>
http://www.openlaszlo.org/demos#Laszlo%20Components%20in%20OL4
> >>
> >> is this "compatible" with Tapestry (maybe
> Tapestry 5?) or a theoretical
> >> possible to also integrate such technologies into
> Tapestry?
> >>
> >> Maybe pages and components could be rendered into
> their Flash
> >> counterparts
> >> without the Tapestry programmer having to worry
> about the details?
> >>
> >>
>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail:
> users-help@tapestry.apache.org
> >>
> >>
> >
> >
> > --
> > Howard M. Lewis Ship
> > TWD Consulting, Inc.
> > Independent J2EE / Open-Source Java Consultant
> > Creator and PMC Chair, Apache Tapestry
> > Creator, Apache HiveMind
> >
> > Professional Tapestry training, mentoring, support
> > and project work. http://howardlewisship.com
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail:
> users-help@tapestry.apache.org
> >
> >
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail:
> users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: OpenLazlo and Tapestry
Posted by Jan Vissers <Ja...@cumquat.nl>.
When I'm think about Flex, movies is the last thing on my mind lately. I'm
intrigued by the potential of Flex apps and/or Flex hybrid apps. I don't
think Tapestry will be particularly well equipped to create complete Flex
apps (but do correct me if I'm wrong). It would be really nice though if
we could easily create hybrid applications using Flex components tied to
our 'regular' HTML/CSS/JavaScript components using Flex's Ajax Bridge
technology.
> Anything is possible, of course. The idea of creating Flash (i.e.,
> Flex or Laszlo) movies on the fly is intriguing. At one extreme, you
> could get Tapestry to directly create and spool out the bytestream of
> the movie, on another you could use Tapestry to generate the XML
> descriptor from which the bytestream is generated. There's lots of
> options.
>
> It's just a matter of developer bandwidth ... something sorely missing
> from my life right now. Viva T5!
>
> On 1/31/07, munich@fantasymail.de <mu...@fantasymail.de> wrote:
>> Have you heard of OpenLaszlo yet?
>>
>> http://www.openlaszlo.org/demos#Laszlo%20Components%20in%20OL4
>>
>> is this "compatible" with Tapestry (maybe Tapestry 5?) or a theoretical
>> possible to also integrate such technologies into Tapestry?
>>
>> Maybe pages and components could be rendered into their Flash
>> counterparts
>> without the Tapestry programmer having to worry about the details?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: OpenLazlo and Tapestry
Posted by Howard Lewis Ship <hl...@gmail.com>.
Anything is possible, of course. The idea of creating Flash (i.e.,
Flex or Laszlo) movies on the fly is intriguing. At one extreme, you
could get Tapestry to directly create and spool out the bytestream of
the movie, on another you could use Tapestry to generate the XML
descriptor from which the bytestream is generated. There's lots of
options.
It's just a matter of developer bandwidth ... something sorely missing
from my life right now. Viva T5!
On 1/31/07, munich@fantasymail.de <mu...@fantasymail.de> wrote:
> Have you heard of OpenLaszlo yet?
>
> http://www.openlaszlo.org/demos#Laszlo%20Components%20in%20OL4
>
> is this "compatible" with Tapestry (maybe Tapestry 5?) or a theoretical
> possible to also integrate such technologies into Tapestry?
>
> Maybe pages and components could be rendered into their Flash counterparts
> without the Tapestry programmer having to worry about the details?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
OpenLazlo and Tapestry
Posted by mu...@fantasymail.de.
Have you heard of OpenLaszlo yet?
http://www.openlaszlo.org/demos#Laszlo%20Components%20in%20OL4
is this "compatible" with Tapestry (maybe Tapestry 5?) or a theoretical
possible to also integrate such technologies into Tapestry?
Maybe pages and components could be rendered into their Flash counterparts
without the Tapestry programmer having to worry about the details?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: FW: Tapestry 3.0.4..not on mirrors
Posted by Nick Westgate <ni...@key-planning.co.jp>.
Hi Mark.
I'm referring to this thread:
"3.0.4 and repetitive method name/signature problem (class enhancement)"
http://thread.gmane.org/gmane.comp.java.tapestry.user/43121
Take it to the dev list when you've read that.
(I'm not a dev, so as to who is managing 3 now ...)
Cheers,
Nick.
Mark Stang wrote:
> Nick,
> I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
>
> http://tapestry.apache.org/tapestry3/
>
> Who is managing this?
>
> thanks,
>
> Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: FW: Tapestry 3.0.4..not on mirrors
Posted by Mark Stang <ms...@pingidentity.com>.
Nick,
I did a quick look and only saw references to 4.x. If 3.0.4 is not the current release, then why does the Tapestry Web site have it listed as such?
http://tapestry.apache.org/tapestry3/
Who is managing this?
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Nick Westgate [mailto:nick@key-planning.co.jp]
Sent: Mon 1/29/2007 11:56 PM
To: Tapestry users
Subject: Re: FW: Tapestry 3.0.4..not on mirrors
Hi Mark.
If you aren't aware of the threading bug in 3.04 then
please search the dev list for the last 3.04 thread.
Cheers,
Nick.
Mark Stang wrote:
> All,
> We were looking to upgrade from 3.03. to 3.04 and it appears that 3.04 isn't on the mirrors.
>
> Thoughts?
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Dave Smith
> Sent: Mon 1/29/2007 6:48 AM
> To: Mark Stang
> Subject: Tapestry 3.0.4..not on mirrors
>
> I was going to upgrade to 3.0.4 this morning, but it's not on any of the
> Apache mirrors. Care to inquire on the list as to what's going on?
>
> Thx.
>
> D.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: FW: Tapestry 3.0.4..not on mirrors
Posted by Nick Westgate <ni...@key-planning.co.jp>.
Hi Mark.
If you aren't aware of the threading bug in 3.04 then
please search the dev list for the last 3.04 thread.
Cheers,
Nick.
Mark Stang wrote:
> All,
> We were looking to upgrade from 3.03. to 3.04 and it appears that 3.04 isn't on the mirrors.
>
> Thoughts?
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Dave Smith
> Sent: Mon 1/29/2007 6:48 AM
> To: Mark Stang
> Subject: Tapestry 3.0.4..not on mirrors
>
> I was going to upgrade to 3.0.4 this morning, but it's not on any of the
> Apache mirrors. Care to inquire on the list as to what's going on?
>
> Thx.
>
> D.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org