[jira] [Commented] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735452#comment-17735452 ] Lenny Primak commented on TAP5-2211: Hi, Thiago :) > Replace DatePicker with Bootstrap or JQueryUI

[jira] [Closed] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed TAP5-2211. -- Resolution: Abandoned > Replace DatePicker with Bootstrap or JQueryUI DatePicker >

[jira] [Closed] (TAP5-1634) Grid, inPlace Update and expired Sessions - Redirect to Login

[ https://issues.apache.org/jira/browse/TAP5-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed TAP5-1634. -- Resolution: Abandoned > Grid, inPlace Update and expired Sessions - Redirect to Login >

[jira] [Commented] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735352#comment-17735352 ] Lenny Primak commented on TAP5-2211: No longer using Tapestry > Replace DatePicker with Bootstrap or

[jira] [Commented] (TAP5-1634) Grid, inPlace Update and expired Sessions - Redirect to Login

[ https://issues.apache.org/jira/browse/TAP5-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735351#comment-17735351 ] Lenny Primak commented on TAP5-1634: No longer using Tapestry > Grid, inPlace Update and expired

[jira] [Commented] (TAP5-1661) Grid inPlace=true - Gracedul degradation with JavaScript disabled

[ https://issues.apache.org/jira/browse/TAP5-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185194#comment-15185194 ] Lenny Primak commented on TAP5-1661: I no longer use Tapestry, and cannot verify this issue Sorry >

[jira] [Commented] (TAP5-2170) constructAssetPath() requires use of internal service

[ https://issues.apache.org/jira/browse/TAP5-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082716#comment-14082716 ] Lenny Primak commented on TAP5-2170: Agreed. The above method works

[jira] [Commented] (TAP5-2170) constructAssetPath() requires use of internal service

[ https://issues.apache.org/jira/browse/TAP5-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082718#comment-14082718 ] Lenny Primak commented on TAP5-2170: Perhaps there should be some kind of migration

[jira] [Commented] (TAP5-1973) :443 added to URLs when using the Link.toAbsoluteURI(true)

[ https://issues.apache.org/jira/browse/TAP5-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083187#comment-14083187 ] Lenny Primak commented on TAP5-1973: As far as I know the bug still exists, as

[jira] [Commented] (TAP5-1973) :443 added to URLs when using the Link.toAbsoluteURI(true)

[ https://issues.apache.org/jira/browse/TAP5-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083199#comment-14083199 ] Lenny Primak commented on TAP5-1973: Also, take a look at my comment from 21/Oct/12

[jira] [Created] (TAP5-2321) Tapestry 5.3.7 does not run with Java 8

Lenny Primak created TAP5-2321: -- Summary: Tapestry 5.3.7 does not run with Java 8 Key: TAP5-2321 URL: https://issues.apache.org/jira/browse/TAP5-2321 Project: Tapestry 5 Issue Type: Bug

[jira] [Created] (TAP5-2320) Tapestry 5.3.7 does not run with Java 8

Lenny Primak created TAP5-2320: -- Summary: Tapestry 5.3.7 does not run with Java 8 Key: TAP5-2320 URL: https://issues.apache.org/jira/browse/TAP5-2320 Project: Tapestry 5 Issue Type: Bug

[jira] [Commented] (TAP5-2321) Tapestry 5.3.7 does not run with Java 8

[ https://issues.apache.org/jira/browse/TAP5-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13971760#comment-13971760 ] Lenny Primak commented on TAP5-2321: Related Ticket:

[jira] [Commented] (TAP5-2187) CSS relative URL rewriting isn't lenient enough

[ https://issues.apache.org/jira/browse/TAP5-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13945839#comment-13945839 ] Lenny Primak commented on TAP5-2187: My particular reason is a 3rd party JS/CSS library

[jira] [Commented] (TAP5-2214) Make tapestry5 java8 compatible

[ https://issues.apache.org/jira/browse/TAP5-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889022#comment-13889022 ] Lenny Primak commented on TAP5-2214: I would also like a T5.3.x release that's

[jira] [Commented] (TAP5-2196) RequireJs custom path contribution - via Stacks or JavaScriptSupport

[ https://issues.apache.org/jira/browse/TAP5-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811388#comment-13811388 ] Lenny Primak commented on TAP5-2196: Not sure I understand this approach completely,

[jira] [Commented] (TAP5-2158) Client-side validation of @Size is not working when only min or max is set

[ https://issues.apache.org/jira/browse/TAP5-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811414#comment-13811414 ] Lenny Primak commented on TAP5-2158: I believe that this issue is only fixed for

[jira] [Commented] (TAP5-2158) Client-side validation of @Size is not working when only min or max is set

[ https://issues.apache.org/jira/browse/TAP5-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811713#comment-13811713 ] Lenny Primak commented on TAP5-2158: Looks good Client-side validation of @Size is

[jira] [Commented] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810353#comment-13810353 ] Lenny Primak commented on TAP5-2208: But this forces the user to generate different

[jira] [Commented] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810400#comment-13810400 ] Lenny Primak commented on TAP5-2208: In any case this ticket is in the comments of

[jira] [Commented] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810407#comment-13810407 ] Lenny Primak commented on TAP5-2208: That's exactly the problem. New behavior is

[jira] [Commented] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810426#comment-13810426 ] Lenny Primak commented on TAP5-2208: If block parameters won't require different markup

[jira] [Commented] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810462#comment-13810462 ] Lenny Primak commented on TAP5-2208: Than, things can be handled even easier. We can

[jira] [Reopened] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak reopened TAP5-2208: Will change to improvement BeanEditForm doesn't generate form-group DIVs with block parameters

[jira] [Updated] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-2208: --- Issue Type: New Feature (was: Bug) BeanEditForm doesn't generate form-group DIVs with block

[jira] [Closed] (TAP5-2208) BeanEditForm doesn't generate form-group DIVs with block parameters

[ https://issues.apache.org/jira/browse/TAP5-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed TAP5-2208. -- Resolution: Won't Fix Risk of incompatibility too great BeanEditForm doesn't generate form-group DIVs

[jira] [Commented] (TAP5-2182) BeanEditor should be more flexible in the markup it generates (was BeanEditor doesn't look as good in T5.4 as in T5.3)

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811023#comment-13811023 ] Lenny Primak commented on TAP5-2182: The fix should be able to modify all

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809268#comment-13809268 ] Lenny Primak commented on TAP5-2211: I just found a good one:

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809425#comment-13809425 ] Lenny Primak commented on TAP5-2211: Barry, this is it! This date picker does what it

[jira] [Updated] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-2211: --- Summary: Replace DatePicker with Bootstrap or JQueryUI DatePicker (was: Replace DatePicker with

[jira] [Commented] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809450#comment-13809450 ] Lenny Primak commented on TAP5-2211: That would be wonderful, and will take pressure

[jira] [Created] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

Lenny Primak created TAP5-2211: -- Summary: Replace DatePicker with JQueryUI DatePicker Key: TAP5-2211 URL: https://issues.apache.org/jira/browse/TAP5-2211 Project: Tapestry 5 Issue Type:

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808252#comment-13808252 ] Lenny Primak commented on TAP5-2211: Examples of this being done already are here:

[jira] [Commented] (TAP5-2197) Overriding core css - bug?

[ https://issues.apache.org/jira/browse/TAP5-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808258#comment-13808258 ] Lenny Primak commented on TAP5-2197: I created a mixin to as a workaround for this

[jira] [Commented] (TAP5-2197) Overriding core css - bug?

[ https://issues.apache.org/jira/browse/TAP5-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808256#comment-13808256 ] Lenny Primak commented on TAP5-2197: Also, if you put your stylesheet in the layout

[jira] [Commented] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808262#comment-13808262 ] Lenny Primak commented on TAP5-2182: Related ticket:

[jira] [Comment Edited] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808262#comment-13808262 ] Lenny Primak edited comment on TAP5-2182 at 10/29/13 6:20 PM: --

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808366#comment-13808366 ] Lenny Primak commented on TAP5-2211: I see #1 being the best option. It's not ideal

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808476#comment-13808476 ] Lenny Primak commented on TAP5-2211: Quick google search revealed this:

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808531#comment-13808531 ] Lenny Primak commented on TAP5-2211: Barry, I don't think that the problem that you

[jira] [Comment Edited] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808531#comment-13808531 ] Lenny Primak edited comment on TAP5-2211 at 10/29/13 10:21 PM:

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808619#comment-13808619 ] Lenny Primak commented on TAP5-2211: I am not convinced that this is an unsolvable

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808633#comment-13808633 ] Lenny Primak commented on TAP5-2211: I think in any case, tying Tapestry to a legacy

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808725#comment-13808725 ] Lenny Primak commented on TAP5-2211: Barry, Thiago, all are valid points, but from the

[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker

[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808727#comment-13808727 ] Lenny Primak commented on TAP5-2211: As far as fixing old DateField, (which I could

[jira] [Commented] (TAP5-2080) Default BaseURLSource does not handle all scenarios

[ https://issues.apache.org/jira/browse/TAP5-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807148#comment-13807148 ] Lenny Primak commented on TAP5-2080: He didn't use proper words, but the issue is

[jira] [Commented] (TAP5-2196) RequireJs custom path contribution - via Stacks or JavaScriptSupport

[ https://issues.apache.org/jira/browse/TAP5-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795329#comment-13795329 ] Lenny Primak commented on TAP5-2196: Why do you need paths for AMD modules? Its nice to

[jira] [Commented] (TAP5-2196) RequireJs custom path contribution - via Stacks or JavaScriptSupport

[ https://issues.apache.org/jira/browse/TAP5-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795344#comment-13795344 ] Lenny Primak commented on TAP5-2196: Never mind... you probably have paths relative to

[jira] [Commented] (TAP5-2196) RequireJs custom path contribution - via Stacks or JavaScriptSupport

[ https://issues.apache.org/jira/browse/TAP5-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795689#comment-13795689 ] Lenny Primak commented on TAP5-2196: For AMD, if module paths are the same, and they

[jira] [Commented] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794698#comment-13794698 ] Lenny Primak commented on TAP5-2182: As pointed in this discussion:

[jira] [Updated] (TAP5-2170) constructAssetPath() requires use of internal service

[ https://issues.apache.org/jira/browse/TAP5-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-2170: --- Priority: Minor (was: Major) constructAssetPath() requires use of internal service

[jira] [Commented] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777172#comment-13777172 ] Lenny Primak commented on TAP5-2182: Bootstrap 3 has a class .form-inline to fix the

[jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough

Lenny Primak created TAP5-2187: -- Summary: CSS relative URL rewriting isn't lenient enough Key: TAP5-2187 URL: https://issues.apache.org/jira/browse/TAP5-2187 Project: Tapestry 5 Issue Type: Bug

[jira] [Commented] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

[ https://issues.apache.org/jira/browse/TAP5-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768556#comment-13768556 ] Lenny Primak commented on TAP5-2182: From User Experience point of view (I already did

[jira] [Created] (TAP5-2185) Problem with the asset checksums and relative paths based on them

Lenny Primak created TAP5-2185: -- Summary: Problem with the asset checksums and relative paths based on them Key: TAP5-2185 URL: https://issues.apache.org/jira/browse/TAP5-2185 Project: Tapestry 5

[jira] [Created] (TAP5-2182) BeanEditor doesn't look as good in T5.4 as in T5.3

Lenny Primak created TAP5-2182: -- Summary: BeanEditor doesn't look as good in T5.4 as in T5.3 Key: TAP5-2182 URL: https://issues.apache.org/jira/browse/TAP5-2182 Project: Tapestry 5 Issue Type:

[jira] [Commented] (TAP5-2158) Client-side validation of @Size is not working when only min or max is set

[ https://issues.apache.org/jira/browse/TAP5-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762044#comment-13762044 ] Lenny Primak commented on TAP5-2158: I would say this is a critical bug, not minor.

[jira] [Created] (TAP5-2175) Bean Validation fails when @Size(min) is not specified but max is specified

Lenny Primak created TAP5-2175: -- Summary: Bean Validation fails when @Size(min) is not specified but max is specified Key: TAP5-2175 URL: https://issues.apache.org/jira/browse/TAP5-2175 Project:

[jira] [Closed] (TAP5-1730) Ajax Zone is improperly reloaded when a mixin submits form via JavaScript

[ https://issues.apache.org/jira/browse/TAP5-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed TAP5-1730. -- Resolution: Fixed Fix Version/s: 5.4 Since form submission was rewritten in 5.4, there is no

[jira] [Created] (TAP5-2167) Ass location warnings are actually coded as errors

Lenny Primak created TAP5-2167: -- Summary: Ass location warnings are actually coded as errors Key: TAP5-2167 URL: https://issues.apache.org/jira/browse/TAP5-2167 Project: Tapestry 5 Issue Type:

[jira] [Created] (TAP5-2168) Asset Not Found messages are prompting to put assets into wrong location

Lenny Primak created TAP5-2168: -- Summary: Asset Not Found messages are prompting to put assets into wrong location Key: TAP5-2168 URL: https://issues.apache.org/jira/browse/TAP5-2168 Project: Tapestry 5

[jira] [Updated] (TAP5-2167) Asset location warnings are actually coded as errors

[ https://issues.apache.org/jira/browse/TAP5-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-2167: --- Summary: Asset location warnings are actually coded as errors (was: Ass location warnings are

[jira] [Created] (TAP5-2169) Core stack is not included by default

Lenny Primak created TAP5-2169: -- Summary: Core stack is not included by default Key: TAP5-2169 URL: https://issues.apache.org/jira/browse/TAP5-2169 Project: Tapestry 5 Issue Type: Bug

[jira] [Commented] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759822#comment-13759822 ] Lenny Primak commented on TAP5-1408: This ticket should be re-opened (T5.4-alpha) Users

[jira] [Commented] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself

[ https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725340#comment-13725340 ] Lenny Primak commented on TAP5-2070: I would love to get this fix incorporated. I

[jira] [Commented] (TAP5-1730) Ajax Zone is improperly reloaded when a mixin submits form via JavaScript

[ https://issues.apache.org/jira/browse/TAP5-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720450#comment-13720450 ] Lenny Primak commented on TAP5-1730: I will do this as part of port of FlowLogix to Tap

[jira] [Commented] (TAP5-2014) Zone highlight leaves behind an explicit background-color which overrides css background-color

[ https://issues.apache.org/jira/browse/TAP5-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707894#comment-13707894 ] Lenny Primak commented on TAP5-2014: The FlowLogix tapestry library will contain a fix

[jira] [Commented] (TAP5-1892) FormFragment validates non-displayed fragments (reopen)

[ https://issues.apache.org/jira/browse/TAP5-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606057#comment-13606057 ] Lenny Primak commented on TAP5-1892: Has there been any progress on this issue? I

[jira] [Updated] (TAP5-1779) Tapestry allows directory listing of assets via client browser

[ https://issues.apache.org/jira/browse/TAP5-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-1779: --- Description: You can access asset directory listing by going to Tapestry web site

[jira] [Commented] (TAP5-1779) Tapestry allows directory listing of assets via client browser

[ https://issues.apache.org/jira/browse/TAP5-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504856#comment-13504856 ] Lenny Primak commented on TAP5-1779: Updated the code to fix the problem with directory

[jira] [Commented] (TAP5-2027) EntityManagerObjectProvider always provides the initial EntityManger proxy created

[ https://issues.apache.org/jira/browse/TAP5-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498317#comment-13498317 ] Lenny Primak commented on TAP5-2027: I can reproduce the problem with your code. DAO

[jira] [Commented] (TAP5-2027) EntityManagerObjectProvider always provides the initial EntityManger proxy created

[ https://issues.apache.org/jira/browse/TAP5-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497167#comment-13497167 ] Lenny Primak commented on TAP5-2027: I just tested that second scenario, without DAOs,

[jira] [Commented] (TAP5-2027) EntityManagerObjectProvider always provides the initial EntityManger proxy created

[ https://issues.apache.org/jira/browse/TAP5-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496804#comment-13496804 ] Lenny Primak commented on TAP5-2027: I just took a quick look (but not tested) at your

[jira] [Commented] (TAP5-1973) :443 added to URLs when using the Link.toAbsoluteURI(true)

[ https://issues.apache.org/jira/browse/TAP5-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13481147#comment-13481147 ] Lenny Primak commented on TAP5-1973: I run my production Tapestry apps behind Apache

[jira] [Created] (TAP5-1661) Grid inPlace=true - Gracedul degradation with JavaScript disabled

Grid inPlace=true - Gracedul degradation with JavaScript disabled - Key: TAP5-1661 URL: https://issues.apache.org/jira/browse/TAP5-1661 Project: Tapestry 5 Issue Type:

[jira] [Commented] (TAP5-840) Support character references in tml files with HTML 5 Doctype

[ https://issues.apache.org/jira/browse/TAP5-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101946#comment-13101946 ] Lenny Primak commented on TAP5-840: --- The problem with using entity numbers instead of

[jira] [Created] (TAP5-1634) Grid, inPlace Update and expired Sessions - Redirect to Login

Grid, inPlace Update and expired Sessions - Redirect to Login - Key: TAP5-1634 URL: https://issues.apache.org/jira/browse/TAP5-1634 Project: Tapestry 5 Issue Type: Improvement

[jira] [Commented] (TAP5-1576) JPA Integration 5.3.0 with Primary Key Entity Classes Fails

[ https://issues.apache.org/jira/browse/TAP5-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066715#comment-13066715 ] Lenny Primak commented on TAP5-1576: The following patch solves the problem for me:

[jira] [Commented] (TAP5-1576) JPA Integration 5.3.0 with Primary Key Entity Classes Fails

[ https://issues.apache.org/jira/browse/TAP5-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066729#comment-13066729 ] Lenny Primak commented on TAP5-1576: Thank you - that works perfectly. JPA

[jira] [Commented] (TAP5-1576) JPA Integration 5.3.0 with Primary Key Entity Classes Fails

[ https://issues.apache.org/jira/browse/TAP5-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066146#comment-13066146 ] Lenny Primak commented on TAP5-1576: 1 ?xml version=1.0 encoding=UTF-8? 2