You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jan Vissers (JIRA)" <de...@tapestry.apache.org> on 2008/02/21 03:23:43 UTC
[jira] Created: (TAPESTRY-2183) Support Java Portlet Specification
V2 - JSR-286
Support Java Portlet Specification V2 - JSR-286
-----------------------------------------------
Key: TAPESTRY-2183
URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
Project: Tapestry
Issue Type: New Feature
Components: Portlet
Affects Versions: 5.0
Reporter: Jan Vissers
Fix For: 5.0
Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAP5-64) Support Java Portlet Specification V2 -
JSR-286
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-64:
-------------------------------------
Issue Type: New Feature (was: Bug)
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAP5-64
> URL: https://issues.apache.org/jira/browse/TAP5-64
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Jan Vissers
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by "Jan Vissers (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577613#action_12577613 ]
Jan Vissers commented on TAPESTRY-2183:
---------------------------------------
FYI: final spec approved - http://jcp.org/en/jsr/detail?id=286
JSR-301 will specify how JSF can be bridged for JSR-286.
Work is well underway for Wicket 1.4 to allow JSR-286 portlet development.
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAPESTRY-2183
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> Project: Tapestry
> Issue Type: New Feature
> Components: Portlet
> Affects Versions: 5.0
> Reporter: Jan Vissers
> Fix For: 5.1
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by "Jan Vissers (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577764#action_12577764 ]
Jan Vissers commented on TAPESTRY-2183:
---------------------------------------
OMG Jesse - you are doing the Tapestry community a bad favor reacting the way you do.
Just to make myself perfectly clear. I don't want to go to Wicket and/or JSF, because I love working in Tapestry. I'm personally responsible for the adoption of Tapestry at my company (from version 3.0). I just want to point out that Tapestry 5 will even be more appealing to use, when we can use it to create our portlets.
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAPESTRY-2183
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> Project: Tapestry
> Issue Type: New Feature
> Components: Portlet
> Affects Versions: 5.0
> Reporter: Jan Vissers
> Fix For: 5.1
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577706#action_12577706 ]
Jesse Kuhnert commented on TAPESTRY-2183:
-----------------------------------------
Why don't you just go use wicket then Jan? I don't think anyone here really cares what you use.
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAPESTRY-2183
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> Project: Tapestry
> Issue Type: New Feature
> Components: Portlet
> Affects Versions: 5.0
> Reporter: Jan Vissers
> Fix For: 5.1
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by Kevin Menard <km...@servprise.com>.
Fair enough. It could just be the way people read it, too. I agree, saying
we should add feature X because framework Y has it doesn't really add
anything of value and can be annoying. If a legitimate case is made as to
how feature X could improve Tapestry and framework Y is used as an example
of how others implement it, I'm not overly bothered by that *shrug*. In
fact, I may be more inclined to add a feature that's been shown to be
successful in the wild than just another wishlist item. Having said that,
you certainly have much more experience here than me, so I'm not trying to
say anything to diminish the value of your opinion.
--
Kevin
On 3/12/08 3:41 PM, "Jesse Kuhnert" <jk...@gmail.com> wrote:
> I think you've misunderstood my beef.
>
> You could just as easily replace the word "wicket" with "elves" and I
> would be no less annoyed by the implication that this feature - which
> is a very large feature that no current Tapestry developer is likely
> to use anytime soon - is more important because of the fact that elves
> are working on it.
>
> Combine this annoyance with repeating the exact same reasoning in blog
> comments / user forums / developer lists and jira issues makes it all
> the more annoying.
>
> On Wed, Mar 12, 2008 at 1:06 PM, Kevin Menard <km...@servprise.com> wrote:
>> Well, I clearly have a different POV, but I don't necessarily think
>> comparing Tapestry to something else is all that bad. Every framework has
>> something that it does better than others. People see it and naturally want
>> it their framework of choice. So long as what they want isn't fundamentally
>> at odds with how the framework is structured, I don't see that being a
>> particularly big problem.
>>
>> For example, I went to Django land for a little while after T4 and before T5
>> just to try something new. Django has some interesting ideas that I would
>> love to see implemented in Tapestry. On the whole, however, I don't think
>> Django even comes close to what Tapestry can provide. I definitely don't
>> want to see Tapestry become Django, but there's no reason not to make a good
>> framework better by using someone else's ideas.
>>
>> FWIW, I haven't really gotten drawn into the Wicket / Tapestry debate and
>> don't know much about it, other than that for whatever reason, one exists.
>> So, I could very well be looking at the issue naively.
>>
>> --
>> Kevin
>>
>> <snipped>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet Specification V2 - JSR-286
Posted by Jesse Kuhnert <jk...@gmail.com>.
I think you've misunderstood my beef.
You could just as easily replace the word "wicket" with "elves" and I
would be no less annoyed by the implication that this feature - which
is a very large feature that no current Tapestry developer is likely
to use anytime soon - is more important because of the fact that elves
are working on it.
Combine this annoyance with repeating the exact same reasoning in blog
comments / user forums / developer lists and jira issues makes it all
the more annoying.
On Wed, Mar 12, 2008 at 1:06 PM, Kevin Menard <km...@servprise.com> wrote:
> Well, I clearly have a different POV, but I don't necessarily think
> comparing Tapestry to something else is all that bad. Every framework has
> something that it does better than others. People see it and naturally want
> it their framework of choice. So long as what they want isn't fundamentally
> at odds with how the framework is structured, I don't see that being a
> particularly big problem.
>
> For example, I went to Django land for a little while after T4 and before T5
> just to try something new. Django has some interesting ideas that I would
> love to see implemented in Tapestry. On the whole, however, I don't think
> Django even comes close to what Tapestry can provide. I definitely don't
> want to see Tapestry become Django, but there's no reason not to make a good
> framework better by using someone else's ideas.
>
> FWIW, I haven't really gotten drawn into the Wicket / Tapestry debate and
> don't know much about it, other than that for whatever reason, one exists.
> So, I could very well be looking at the issue naively.
>
> --
> Kevin
>
> <snipped>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by Kevin Menard <km...@servprise.com>.
Well, I clearly have a different POV, but I don't necessarily think
comparing Tapestry to something else is all that bad. Every framework has
something that it does better than others. People see it and naturally want
it their framework of choice. So long as what they want isn't fundamentally
at odds with how the framework is structured, I don't see that being a
particularly big problem.
For example, I went to Django land for a little while after T4 and before T5
just to try something new. Django has some interesting ideas that I would
love to see implemented in Tapestry. On the whole, however, I don't think
Django even comes close to what Tapestry can provide. I definitely don't
want to see Tapestry become Django, but there's no reason not to make a good
framework better by using someone else's ideas.
FWIW, I haven't really gotten drawn into the Wicket / Tapestry debate and
don't know much about it, other than that for whatever reason, one exists.
So, I could very well be looking at the issue naively.
--
Kevin
On 3/12/08 11:24 AM, "Jesse Kuhnert" <jk...@gmail.com> wrote:
> I wouldn't really care if it were mentioning wicket once, but I think
> I can recall at least 7 or 8 (possibly more) of the same exact
> requests attempting to use "framework X has or will have it" as the
> reason why it should be done. After a while it starts to feel like
> being bullied.
>
> I guess I'm alone in that feeling though, so sorry to all for my
> comments. (not that I'm sorry for making them, but don't want to
> make everyone else feel uncomfortable)
>
> On Wed, Mar 12, 2008 at 10:30 AM, Davor Hrg <hr...@gmail.com> wrote:
>> I agree with kevin on this,
>> also Jesse is too aggressive when someone mentions wicket.
>>
>> Mentioning wicket is not a very good way to push an
>> issue, but the response was definitely way too aggressive.
>>
>> ... somewhere in the apache docs is said that beng a comitter:
>> (it's not a quote, I remember it something like this...)
>> being a comiter is not about solving only the issues you are passionate
>> about,
>> but concentrating on the issues the community is most interested in..
>>
>> Davor Hrg
>>
>>
>>
>> On Wed, Mar 12, 2008 at 2:49 PM, Kevin Menard <km...@servprise.com> wrote:
>>> Perhaps I'm missing something, but I don't see anything particularly
>>> inflammatory here. Maybe the priority level could be lowered. Maybe Jan
>>> could attach a patch. But, JIRA is the appropriate channel for new feature
>>> requests. If they're not in the design goals of the framework, they could
>>> be closed with reason.
>>>
>>> I'd just urge everyone to relax a little bit and air grievances on the list
>>> rather than in JIRA, which is the inappropriate medium. Please note that
>>> this is not an endorsement either way on the issue at hand.
>>>
>>> --
>>> Kevin
>>>
>>>
>>>
>>> On 3/12/08 8:50 AM, "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> wrote:
>>>
>>>>
>>>> [
>>>> https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira
>>>> .pl
>>>> ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#actio
>>>> n_1
>>>> 2577834 ]
>>>>
>>>> Jesse Kuhnert commented on TAPESTRY-2183:
>>>> -----------------------------------------
>>>>
>>>> I just don't think you understand how open source works Jan.
>>>>
>>>> If it was really that important then you should:
>>>>
>>>> a) Make a go of portlet support yourself.
>>>> b) Have your company pay Howard to do it.
>>>>
>>>> The source is right there, so anyone can in theory jump right in and do
>>>> it.
>>>> That's how it works.
>>>>
>>>>> Support Java Portlet Specification V2 - JSR-286
>>>>> -----------------------------------------------
>>>>>
>>>>> Key: TAPESTRY-2183
>>>>> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
>>>>> Project: Tapestry
>>>>> Issue Type: New Feature
>>>>> Components: Portlet
>>>>> Affects Versions: 5.0
>>>>> Reporter: Jan Vissers
>>>>> Fix For: 5.1
>>>>>
>>>>>
>>>>> Specification will be finished early 2008. We need a framework that allows
>>>>> us
>>>>> to write JSR-286 portlets, would be nice if we could stick with T5 for
>>>>> this.
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet Specification V2 - JSR-286
Posted by Jesse Kuhnert <jk...@gmail.com>.
I wouldn't really care if it were mentioning wicket once, but I think
I can recall at least 7 or 8 (possibly more) of the same exact
requests attempting to use "framework X has or will have it" as the
reason why it should be done. After a while it starts to feel like
being bullied.
I guess I'm alone in that feeling though, so sorry to all for my
comments. (not that I'm sorry for making them, but don't want to
make everyone else feel uncomfortable)
On Wed, Mar 12, 2008 at 10:30 AM, Davor Hrg <hr...@gmail.com> wrote:
> I agree with kevin on this,
> also Jesse is too aggressive when someone mentions wicket.
>
> Mentioning wicket is not a very good way to push an
> issue, but the response was definitely way too aggressive.
>
> ... somewhere in the apache docs is said that beng a comitter:
> (it's not a quote, I remember it something like this...)
> being a comiter is not about solving only the issues you are passionate about,
> but concentrating on the issues the community is most interested in..
>
> Davor Hrg
>
>
>
> On Wed, Mar 12, 2008 at 2:49 PM, Kevin Menard <km...@servprise.com> wrote:
> > Perhaps I'm missing something, but I don't see anything particularly
> > inflammatory here. Maybe the priority level could be lowered. Maybe Jan
> > could attach a patch. But, JIRA is the appropriate channel for new feature
> > requests. If they're not in the design goals of the framework, they could
> > be closed with reason.
> >
> > I'd just urge everyone to relax a little bit and air grievances on the list
> > rather than in JIRA, which is the inappropriate medium. Please note that
> > this is not an endorsement either way on the issue at hand.
> >
> > --
> > Kevin
> >
> >
> >
> > On 3/12/08 8:50 AM, "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> wrote:
> >
> > >
> > > [
> > > https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.pl
> > > ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#action_1
> > > 2577834 ]
> > >
> > > Jesse Kuhnert commented on TAPESTRY-2183:
> > > -----------------------------------------
> > >
> > > I just don't think you understand how open source works Jan.
> > >
> > > If it was really that important then you should:
> > >
> > > a) Make a go of portlet support yourself.
> > > b) Have your company pay Howard to do it.
> > >
> > > The source is right there, so anyone can in theory jump right in and do it.
> > > That's how it works.
> > >
> > >> Support Java Portlet Specification V2 - JSR-286
> > >> -----------------------------------------------
> > >>
> > >> Key: TAPESTRY-2183
> > >> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> > >> Project: Tapestry
> > >> Issue Type: New Feature
> > >> Components: Portlet
> > >> Affects Versions: 5.0
> > >> Reporter: Jan Vissers
> > >> Fix For: 5.1
> > >>
> > >>
> > >> Specification will be finished early 2008. We need a framework that allows us
> > >> to write JSR-286 portlets, would be nice if we could stick with T5 for this.
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet Specification V2 - JSR-286
Posted by Davor Hrg <hr...@gmail.com>.
I agree with kevin on this,
also Jesse is too aggressive when someone mentions wicket.
Mentioning wicket is not a very good way to push an
issue, but the response was definitely way too aggressive.
... somewhere in the apache docs is said that beng a comitter:
(it's not a quote, I remember it something like this...)
being a comiter is not about solving only the issues you are passionate about,
but concentrating on the issues the community is most interested in..
Davor Hrg
On Wed, Mar 12, 2008 at 2:49 PM, Kevin Menard <km...@servprise.com> wrote:
> Perhaps I'm missing something, but I don't see anything particularly
> inflammatory here. Maybe the priority level could be lowered. Maybe Jan
> could attach a patch. But, JIRA is the appropriate channel for new feature
> requests. If they're not in the design goals of the framework, they could
> be closed with reason.
>
> I'd just urge everyone to relax a little bit and air grievances on the list
> rather than in JIRA, which is the inappropriate medium. Please note that
> this is not an endorsement either way on the issue at hand.
>
> --
> Kevin
>
>
>
> On 3/12/08 8:50 AM, "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> wrote:
>
> >
> > [
> > https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.pl
> > ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#action_1
> > 2577834 ]
> >
> > Jesse Kuhnert commented on TAPESTRY-2183:
> > -----------------------------------------
> >
> > I just don't think you understand how open source works Jan.
> >
> > If it was really that important then you should:
> >
> > a) Make a go of portlet support yourself.
> > b) Have your company pay Howard to do it.
> >
> > The source is right there, so anyone can in theory jump right in and do it.
> > That's how it works.
> >
> >> Support Java Portlet Specification V2 - JSR-286
> >> -----------------------------------------------
> >>
> >> Key: TAPESTRY-2183
> >> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> >> Project: Tapestry
> >> Issue Type: New Feature
> >> Components: Portlet
> >> Affects Versions: 5.0
> >> Reporter: Jan Vissers
> >> Fix For: 5.1
> >>
> >>
> >> Specification will be finished early 2008. We need a framework that allows us
> >> to write JSR-286 portlets, would be nice if we could stick with T5 for this.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by Kevin Menard <km...@servprise.com>.
Perhaps I'm missing something, but I don't see anything particularly
inflammatory here. Maybe the priority level could be lowered. Maybe Jan
could attach a patch. But, JIRA is the appropriate channel for new feature
requests. If they're not in the design goals of the framework, they could
be closed with reason.
I'd just urge everyone to relax a little bit and air grievances on the list
rather than in JIRA, which is the inappropriate medium. Please note that
this is not an endorsement either way on the issue at hand.
--
Kevin
On 3/12/08 8:50 AM, "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.pl
> ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#action_1
> 2577834 ]
>
> Jesse Kuhnert commented on TAPESTRY-2183:
> -----------------------------------------
>
> I just don't think you understand how open source works Jan.
>
> If it was really that important then you should:
>
> a) Make a go of portlet support yourself.
> b) Have your company pay Howard to do it.
>
> The source is right there, so anyone can in theory jump right in and do it.
> That's how it works.
>
>> Support Java Portlet Specification V2 - JSR-286
>> -----------------------------------------------
>>
>> Key: TAPESTRY-2183
>> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
>> Project: Tapestry
>> Issue Type: New Feature
>> Components: Portlet
>> Affects Versions: 5.0
>> Reporter: Jan Vissers
>> Fix For: 5.1
>>
>>
>> Specification will be finished early 2008. We need a framework that allows us
>> to write JSR-286 portlets, would be nice if we could stick with T5 for this.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2183) Support Java Portlet
Specification V2 - JSR-286
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#action_12577834 ]
Jesse Kuhnert commented on TAPESTRY-2183:
-----------------------------------------
I just don't think you understand how open source works Jan.
If it was really that important then you should:
a) Make a go of portlet support yourself.
b) Have your company pay Howard to do it.
The source is right there, so anyone can in theory jump right in and do it. That's how it works.
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAPESTRY-2183
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> Project: Tapestry
> Issue Type: New Feature
> Components: Portlet
> Affects Versions: 5.0
> Reporter: Jan Vissers
> Fix For: 5.1
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2183) Support Java Portlet Specification
V2 - JSR-286
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2183:
-------------------------------------------
Fix Version/s: (was: 5.0)
5.1
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAPESTRY-2183
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183
> Project: Tapestry
> Issue Type: New Feature
> Components: Portlet
> Affects Versions: 5.0
> Reporter: Jan Vissers
> Fix For: 5.1
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org