I just noticed that a 3.0 (presumably final) release is available. What are
the differences between this and the RC1 release candidate?
Also, I'm beginning to look at using Annotations with Tapestry and Javassist.
My plan for Tapestry 5.0 is to read annotations at class load time and modify
The docs for 3.0 still state that try ... finally is not supported. Is this true? I
would very much like to use Javassist for a particular application, but being able to
use a finally clause is critical.
View the original post :
As an example, what would be nice if Javassist would write the code-markup text to a
temporary file and add line number information for its code that pointed to that file,
so that a debugger (such as Eclipse) could step through the source.
Currently, when users step into a method dynamically
Oh ... and both Tapestry and HiveMind don't modify existing sources, they always
create new classes entirely (often as enhanced subclasses of existing, user-provided
classes). I can see that trying to do what I suggest for full-bore AOP would be a
great challenge, but for new classes created
Tapestry doesn't care about file extensions.
By convention, page-specifications are .page and
component-specifications are .jwc.
Earlier versions of tapestry didn't differentiate
between page-specification and component-specification,
pages and components alike used .jwc.
--
[EMAIL
I don't have enough information to proceed from here.
Are you doing anything tricky on this page, such as
Block/RenderBlock?
It sounds like something, somewhere, is holding a
reference to a component or page not within the current
page. Nothing in Tapestry does that. Are you passing a
It would be easy enough to make it simply log an error
instead of throwing an exception.
--
[EMAIL PROTECTED]
http://tapestry.sf.net
Phil Surette wrote:
(snip)
wouldn't care)? It's a nice feature to be able to be able to
automatically detect cruft when you're in cleanup mode, but when
I just removed Mr. Morales from the list because of all
the bounced messages. Hopefully he can resubscribe once
he resolves his mail issues.
--
[EMAIL PROTECTED]
http://tapestry.sf.net
-- Forwarded Message: -
From:[EMAIL PROTECTED]
To:
Yeah, what I do in this case is define an interface and
supply per-JVM implementations of the interface.
I instantiate them (from class name) starting with the
JDK 1.4 version and, if that fails, back to the 1.3,
1.2, etc. version.
The trick is to compile each class with the correct
