Hi,
for extending tapestrys internal service classes it's often required to
copy a lot of code because almost everything is private. Why not
changing it to protected to allow others to extend those classes?
Because it makes keeping backward-compatibility way harder and that's
very important
Hi Thiago,
first of all, I must admit that I'm not really familiar with JCache and
I'm not sure what it is that you have implemented. I assume it's an
implementation of JSR-107 based upon tapestry-ioc.
If that is the case, I'd like to know how much of the actual caching
functionality depends
Hi,
I can access the type of a bound parameter using
ComponentResources.getBoundType(parameterName). But for ListString it
returns (of course) List.class. Is there a way to access the generic
parameters of the bound type somehow? I need this for correct
(automatic) type coercion in some
On Mon, 12 May 2014 06:07:41 -0300, Jochen Kemnade
jochen.kemn...@eddyson.de wrote:
Hi Thiago,
Hi, Jochen! By the way, your first weeks as a Tapestry committer have been
awesome! Thank you very much for that! ;)
first of all, I must admit that I'm not really familiar with JCache and
On Mon, 12 May 2014 05:54:31 -0300, Michael Wyraz
michael.wy...@evermind.de wrote:
Hi,
Hi!
Protected methods are normally not part of the official stable api. So
there's no difference for maintaining backward compatibility. I don't
see any drawback here
There's a huge difference. If
Hi,
on 2013-01-14, in an effort to close some outdated JIRA issues, Uli
added the label bulk-close-candidate to every issue that has been last
updated more than 1.5 years ago, has no assignee, affects an old version
of Tapestry that is not actively developed anymore, and is therefore
prone to be
On Mon, 12 May 2014 12:27:09 -0300, Michael Wyraz
michael.wy...@evermind.de wrote:
Hi,
Hi!
configuration.add(ImportUIStack, importUIStack);
We run Tapestry 5.4-beta3. The problem is that randomly after
application start JavaScriptSupport is not set on environment. If this
Hello,
Yvon Perreault has commented on
http://tapestry.apache.org/loading-the-project-into-eclipse.html.
You can find the comment here:
http://tapestry.apache.org/loading-the-project-into-eclipse.html#comment_2499
Please note that if the comment contains a hyperlink, it must be
+1
GATAATGCTATTTCTTTAACGAA
On May 12, 2014, at 3:22 PM, Howard Lewis Ship hls...@gmail.com wrote:
Well, obviously, we haven't managed the issue list very well, and it got a
bit out of control.
I'm in favor of closing them; they've had over a year to sit and gather
attention.
We
Hi Thiago,
Am 12.05.2014 14:53, schrieb Thiago H de Paula Figueiredo:
Hi, Jochen! By the way, your first weeks as a Tapestry committer have
been awesome! Thank you very much for that! ;)
Thank you! :-) I had a great time working on some of the remaining JIRA
bug type issues for 5.4. I'll
Hi,
we have a layout package that adds some extra css/js to all pages. It is
implemented as contributeMarkupRenderer:
public void
contributeMarkupRenderer(OrderedConfigurationMarkupRendererFilter
configuration, final Environment environment)
{
+1
On 2014-05-12 19:51, Jochen Kemnade wrote:
Hi,
on 2013-01-14, in an effort to close some outdated JIRA issues, Uli added the
label
bulk-close-candidate to every issue that has been last updated more than 1.5
years ago, has no
assignee, affects an old version of Tapestry that is not
12 matches
Mail list logo
