You mean "commons attributes"
(http://jakarta.apache.org/commons/attributes/)?
:)
I don't think that development time should be spent on such "backports".
I think that if one have to use a pre5 jre then use the xml specifications
instead of annotations.
Of course it's my personal opinion...
Br,
Norbi
----- Original Message -----
From: "Joel Trunick" <[EMAIL PROTECTED]>
To: "Tapestry users" <[email protected]>
Sent: Tuesday, July 12, 2005 10:54 PM
Subject: RE: 3.0 -> 4.0 porting issues
This might not go over well with the community, but there is a way to
get annotations in 1.4:
http://backport175.codehaus.org/
It would need to be supported by Tapestry itself and needs another .jar
file, but if enough folks (or Howard) thought it necessary, there it is.
It's like a "commons" for annotations.
Joel
-----Original Message-----
From: Scott F. Walter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 3:44 PM
To: Tapestry users
Subject: Re: 3.0 -> 4.0 porting issues
Eric Schneider wrote:
Thanks Scott,
I'm kinda new to this hivemind stuff. It looks like you are
injecting these objects with annotations. Which is jdk 1.5 thing,
no? There must be an xml config way of accomplishing the same thing
right?
Thanks,
e.
On Jul 12, 2005, at 4:00 PM, Scott F. Walter wrote:
Eric Schneider wrote:
Hi,
Just updated the tapestry (and related) .jar files in one of our
libraries. Here are the things I noticed that aren't listed on
the upgrade page on the jakarta site.
deprecated:
IEngine.getScriptSource();
FormEventType
RequestContext
Body.get(requestCycle);
RequestCycle.getRequestContext()
gone completely:
IScriptSource.getScript(scriptLocation);
Location.getResourceLocation();
AbstractTextField
ApplicationRuntimeException
IEngineServiceView
ResponseOutputStream
RequestContext.getRequestURI()
Unfortunately, this looks a little more involved than I originally
thought. Also, the upgrade page mentioned something about the
following 4.x releases requiring the JDK 1.5 because of some
commons dependency. Is this so? If it is I won't bother
upgrading from 3.0.3.
Thanks,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
In terms of the deprecation with the request objects. You can:
1. Inject an HttpServletRequest with:
@InjectObject("service:tapestry.globals.HttpServletRequest";)
public abstract Object getHttpRequest();
2. Inject a WebRequest
@InjectObject("infrastructure:request")
public abstract Object getWebRequest()
The page is http://jakarta.apache.org/tapestry/tapestry/hivedocs/
index.html is very valuable. It contains a list of what can be
injected.
scott.
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: [EMAIL PROTECTED]
E: [EMAIL PROTECTED]
Visit scottwalter.com <http://scottwalter.com> --Point. Click.
Explore!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
yes you can do the xml config way with <inject> have a look at:
http://jakarta.apache.org/tapestry/UsersGuide/spec.html#spec.inject
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: [EMAIL PROTECTED]
E: [EMAIL PROTECTED]
Visit scottwalter.com <http://scottwalter.com> --Point. Click.
Explore!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
