[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789143#comment-13789143 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hi, guys! Shouldn't this issue be closed due to the tapestry5-portlet linked above? I haven't used portlets myself, so I'm not the best one to check it. If nobody says no in a couple weeks, I'll close this issue. 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-1624) Add support for overriding default TypeCoercer's coercions
[ https://issues.apache.org/jira/browse/TAP5-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789221#comment-13789221 ] Thiago H. de Paula Figueiredo commented on TAP5-1624: - Denis, is this still an issue? TAP5-1446 is already fixed. Do you still see a need for TypeCoercer coercion overrides? Add support for overriding default TypeCoercer's coercions -- Key: TAP5-1624 URL: https://issues.apache.org/jira/browse/TAP5-1624 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Reporter: Denis Stepanov Right now it is imposible to implement TAP5-1446 without changes in Tapestry. It will probably require to add new service TypeCoercerOverride, TyprCoercerImpl will use it to override all tuples with equal sourceType and targetType. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-1624) Add support for overriding default TypeCoercer's coercions
[ https://issues.apache.org/jira/browse/TAP5-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789223#comment-13789223 ] Denis Stepanov commented on TAP5-1624: -- I don't need it anymore, there are some votes so maybe someone needs it. Add support for overriding default TypeCoercer's coercions -- Key: TAP5-1624 URL: https://issues.apache.org/jira/browse/TAP5-1624 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Reporter: Denis Stepanov Right now it is imposible to implement TAP5-1446 without changes in Tapestry. It will probably require to add new service TypeCoercerOverride, TyprCoercerImpl will use it to override all tuples with equal sourceType and targetType. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
[ 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
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789367#comment-13789367 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hello, Pieter! What do you mean by out-of-the-box portlet support? As in tapestry-core itself? I'm sorry, that's not going to happen. Not everybody which uses Tapestry uses portlets, so it doesn't make much sense to put support for it in core. The Tapestry philosophy is to have the basic functionality in tapestry-core and more specific stuff in other JARs, such as tapestry-upload and tapestry-hibernate. If it's about a separate JAR under the Apache Tapestry project, tapestry5-portlet is mostly written by Tapestry committers themselves. In addition, we avoid having too much stuff under the Tapestry project itself because we're all volutaries and we'd need to support that code. I agree with you that tapestry5-porlet should have its JAR in Maven Central Repository. Cheers! 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
[ 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] [Updated] (TAP5-1971) HibernateGridDataSource should include some workaround or protection agains wrong Projections.rowCount() result
[ https://issues.apache.org/jira/browse/TAP5-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago H. de Paula Figueiredo updated TAP5-1971: Priority: Minor (was: Critical) Changing this from critical to minor because the cause of the problem isn't Tapestry, it's Hibernate, and it has an easy workaround. HibernateGridDataSource should include some workaround or protection agains wrong Projections.rowCount() result --- Key: TAP5-1971 URL: https://issues.apache.org/jira/browse/TAP5-1971 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-hibernate Affects Versions: 5.3.3 Reporter: Andrei Arapov Priority: Minor In some cases Hibernate's criteria construction like criteria.setProjection(Projections.rowCount()) returns wrong number of rows. More specifically, for example, if you have some JPA restrictions in you entity annotations (e.g. @ManyToOne @JoinColumn(name = USER_ID, nullable = false) this one! @NonVisual public UserImpl user; ) then such restrictions (for USER_ID is not null) will not be taken in account while building row-count query. Vice-versa hibernate will use such restrictions in query for getting LIST of entities. This behaivour fails, when in entity table appear (e.g. some old) rows with NULL in USER_ID (e.g.) columns. This is known, but not solved problem for Hibernate, see: https://hibernate.onjira.com/browse/HHH-3238 https://hibernate.onjira.com/browse/HHH-2787 https://hibernate.onjira.com/browse/HHH-3206 https://hibernate.onjira.com/browse/HHH-5719 https://hibernate.onjira.com/browse/HHH-4829 https://hibernate.onjira.com/browse/HHH-7438 There by we go into error in HibernateGridDataSource.getRowValue(int index) method: it throws IndexOutOfBoundsException due to row count number is bigger than actual number of selected rows. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789439#comment-13789439 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hello, Pieter! If tapestry5-portlet is working and if it had its JARs in the Maven Central Respository, would you be satisfied? As I said in the message above, we cannot have too much stuff under the Tapestry project itself because otherwise we wouldn't have the time to support all that. Cheers! 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] [Updated] (TAP5-2176) SymbolBeanFactoryPostProcessor breaks property placeholder in spring when using default values
[ https://issues.apache.org/jira/browse/TAP5-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago H. de Paula Figueiredo updated TAP5-2176: Priority: Minor (was: Major) Priority changed to Minor because it has an easy workaround. SymbolBeanFactoryPostProcessor breaks property placeholder in spring when using default values -- Key: TAP5-2176 URL: https://issues.apache.org/jira/browse/TAP5-2176 Project: Tapestry 5 Issue Type: Bug Reporter: Joris Vanleene Priority: Minor When a property used in a spring config xml has a default value tapestry will set this as the value of the property, then the spring property placeholder will run but he will not replace the property with the correct value from a properties file because it is already set by tapestry with the default value! Tapestry Spring Module SymbolBeanFactoryPostProcessor should only touch properties that start with 'tapestry.' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
[ 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)
[jira] [Commented] (TAP5-1920) Create old URL rewriter compatibility package for 5.3.4
[ https://issues.apache.org/jira/browse/TAP5-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789502#comment-13789502 ] Thiago H. de Paula Figueiredo commented on TAP5-1920: - Implemented in https://github.com/thiagohp/tapestry-url-rewriter. dependency groupIdbr.com.arsmachina/groupId artifactIdtapestry-url-rewriter/artifactId version1.0.1/version /dependency Create old URL rewriter compatibility package for 5.3.4 --- Key: TAP5-1920 URL: https://issues.apache.org/jira/browse/TAP5-1920 Project: Tapestry 5 Issue Type: Improvement Affects Versions: 5.3.4 Reporter: Thiago H. de Paula Figueiredo Assignee: Thiago H. de Paula Figueiredo Priority: Minor Fix For: 5.3.1, 5.4, 5.2.0 Create a separate, optional package so that applications that use the old Tapestry 5.1.0.5 URL rewriter API can be upgraded to T5.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (TAP5-1920) Create old URL rewriter compatibility package for 5.3.4
[ https://issues.apache.org/jira/browse/TAP5-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago H. de Paula Figueiredo resolved TAP5-1920. - Resolution: Implemented Fix Version/s: 5.3.1 5.2.0 5.4 Create old URL rewriter compatibility package for 5.3.4 --- Key: TAP5-1920 URL: https://issues.apache.org/jira/browse/TAP5-1920 Project: Tapestry 5 Issue Type: Improvement Affects Versions: 5.3.4 Reporter: Thiago H. de Paula Figueiredo Assignee: Thiago H. de Paula Figueiredo Priority: Minor Fix For: 5.4, 5.2.0, 5.3.1 Create a separate, optional package so that applications that use the old Tapestry 5.1.0.5 URL rewriter API can be upgraded to T5.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TAP5-2029) Copy annotations from service implementation to proxy (was JPA annotations expose implementation details in service interfaces)
[
https://issues.apache.org/jira/browse/TAP5-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago H. de Paula Figueiredo updated TAP5-2029:
Summary: Copy annotations from service implementation to proxy (was JPA
annotations expose implementation details in service interfaces) (was: JPA
annotations expose implementation details in service interfaces)
Copy annotations from service implementation to proxy (was JPA annotations
expose implementation details in service interfaces)
---
Key: TAP5-2029
URL: https://issues.apache.org/jira/browse/TAP5-2029
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Affects Versions: 5.3.6
Reporter: John Coleman
Assignee: Thiago H. de Paula Figueiredo
Priority: Minor
The commit after and persistence context annotations are required on the
service interface definition thereby exposing internal implementation details
(see below example from docs). Details of implementation should be hidden at
the interface level, both these annotations break the rule.
Perhaps this code could appear in the Impl classes, or be provided in
configuration somehow?
public interface UserDAO {
@CommitAfter
@PersistenceContext(unitName = DemoUnit)
void add(User user);
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789511#comment-13789511 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- What if the Tapestry documentation itself had a Recommended third-party modules section? For example, tapestry-security, the integration with Apache Shiro, isn't part of the Tapestry project itself but it's written by a committer of both Tapestry and Shiro and it's widely trusted. Latest released Tapestry version is 5.3.6 and tapestry5-portlet says it supports them. 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
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789553#comment-13789553 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- In addition, Tapestry *does* support portlets, but by using a thirdy-party module. 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
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789616#comment-13789616 ] François Facon commented on TAP5-64: I'm still working on this jira. this module is already in production and working correctly for 5.2.6, 5.3.7, 5.4.AlphaXX. the build process and testing integration with Pluto works well with Maven. The gradle build is ok but I have not managed to use Tomee Pluto and Arquilian in a gradle build. Any technical feedback is welcome 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)
