[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286

2013-10-08 Thread Pieter Schoenmakers (JIRA)

[ 
https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789270#comment-13789270
 ] 

Pieter Schoenmakers commented on TAP5-64:
-

I'd expect this issue to be closed once tap5 has out-of-the-box portlet support.
(PS: I didn't check out the fine work on code or github.)

 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
Assignee: François Facon
 Attachments: tapestry_portlet_5.0.15.zip, 
 tapestry_portlet_5.0.18.zip, tapestry_portlet_5.1.0.5.zip


 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 was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286

2013-10-08 Thread Pieter Schoenmakers (JIRA)

[ 
https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789426#comment-13789426
 ] 

Pieter Schoenmakers commented on TAP5-64:
-

Separate jar is what I'd expect; you don't want to force portlet.jar upon 
everybody.
Out of the box, as in documented and provided on tapestry.apache.org just like 
all tap5 jars.
(I'm still maintaining a tap4-based portlet app and I would love to migrate to 
tap5.)

 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
Assignee: François Facon
 Attachments: tapestry_portlet_5.0.15.zip, 
 tapestry_portlet_5.0.18.zip, tapestry_portlet_5.1.0.5.zip


 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 was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286

2013-10-08 Thread Pieter Schoenmakers (JIRA)

[ 
https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789482#comment-13789482
 ] 

Pieter Schoenmakers commented on TAP5-64:
-

Inclusion on tapestry.apache.org is like a seal of approval.  It provides 
trust.  Provision from somewhere else lacks the seal.  It must earn the trust 
all by itself.

On the other hand, portlet support from tapestry.apache.org reflects good on 
tapestry itself.  If I were running tapestry, I'd want portlet support in 
there.  All other serious UI frameworks support portlets :-)

But, we're talking hypotheses here.  The attached jars would need to be brought 
up to par with the latest tap5 before being able to be considered for inclusion.

 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
Assignee: François Facon
 Attachments: tapestry_portlet_5.0.15.zip, 
 tapestry_portlet_5.0.18.zip, tapestry_portlet_5.1.0.5.zip


 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 was sent by Atlassian JIRA
(v6.1#6144)