[jira] [Commented] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
[
https://issues.apache.org/jira/browse/ISIS-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365751#comment-14365751
]
Dan Haywood commented on ISIS-1097:
---
Here's a simple script we wrote to ping our test instance of our app (Estatio):
{code}
rm cookies.txt
pid=$$
#
# sign in
#
curl -e http://testserver/wicket/signin; -c cookies.txt -D /tmp/curl.$pid.1
--data id1_hf_0=username=ypassword=xrememberMeRow%3ArememberMe=on
http://testserver/wicket/signin?-1.IFormSubmitListener-signInPanel-signInForm
# Redirect after signin
curl -e http://ams-s-estatio01/wicket/signin -b cookies.txt -c cookies.txt
http://testserver/wicket/
# Home page
echo ##
echo #
echo # HOME PAGE
echo #
echo ##
curl -e http://testserver/wicket/signin -b cookies.txt -c cookies.txt
http://testserver/wicket/entity?2
# submit Fixed Assets All Properties
curl -e http://testserver/wicket/entity?2 -H Wicket-Ajax:true -H
Wicket-Ajax-BaseURL:entity?2 -H Wicket-FocusedElementId:id5 -H
X-Requested-With:XMLHttpRequest -b cookies.txt -c cookies.txt
http://testserver/wicket/entity?2-1.IBehaviorListener.0-theme-header-primaryMenuBar-menuItems-0-topMenu-subMenuItems-2-content-menuLink
# render results
echo ##
echo #
echo # Fixed Assets All Properties
echo #
echo ##
curl -e http://testserver/wicket/entity?2 -b cookies.txt
http://testserver/wicket/wicket/page?3
sleep 1
#
#
rm /tmp/curl.$pid.1
{code}
Suspicion that Isis may be leaving DB connections open under certain
circumstances, leading to instability
--
Key: ISIS-1097
URL: https://issues.apache.org/jira/browse/ISIS-1097
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Fix For: 1.9.0
Report from the field:
Users reporting that the app was slow. We've seen some active sessions in
Tomcat that didn't correspond to any user, but also 3 database connections on
PostgreSQL that were IN TRANSACTION for a long time.
Killing the Tomcat and database sessions the correct speed has been recovered
One monitoring option to consider (open source with commercial support) is
hyperic,
* http://sourceforge.net/projects/hyperic-hq/
*
https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1096) Derive the object type from the schema and table of @PersistenceCapable (but ensure backward compatibility is preserved).
[
https://issues.apache.org/jira/browse/ISIS-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365683#comment-14365683
]
ASF subversion and git services commented on ISIS-1096:
---
Commit f9d34ae74f2432a17b0ad647a8fcc797c6f79ad8 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f9d34ae ]
Merge branch 'ISIS-1096'
Derive the object type from the schema and table of @PersistenceCapable (but
ensure backward compatibility is preserved).
-
Key: ISIS-1096
URL: https://issues.apache.org/jira/browse/ISIS-1096
Project: Isis
Issue Type: New Feature
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
The algorithm should be:
1. @DomainObject(objectType = ...)
2. @ObjectType(...)
3. @PersistenceCapable(schema=..., table=...)
4. use the default fully qualified class name.
This ticket is all about introducing (3). The inferred objecttype should be:
schemaname.TableName, where schemaname is lowercased.
If schema is not present, then should ignore.
~~~
In addition, to support any legacy serialized data that uses the fully
qualified class name, the resolution of objects by object type should first
lookup the object type by its specified name, else fallback to looking up as
if FQN.
eg suppose have:
{code}
package com.mycompany.myapp
@DomainObject(objectType=CUS)
public class Customer { ... }
{code}
then the serialized form of this is CUS:1, but Isis should also resolve
this object if com.mycompany.myapp.Customer:1 is provided instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
[ https://issues.apache.org/jira/browse/ISIS-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365725#comment-14365725 ] Dan Haywood commented on ISIS-1097: --- I'm not convinced that Axon will sort this. Rather, I think that the current design does not allow for a stack of events nested one within the other, and that is probably where the issue is. Rather than currentInteraction.set(...) on a thread-local, it should be doing push() and pop(). These thread-locals can be found in PropertyDomainEventFacetAbstract, ActionDomainEventFacetAbstract, CollectionDomainEventFacetAbstract. Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability -- Key: ISIS-1097 URL: https://issues.apache.org/jira/browse/ISIS-1097 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.9.0 Report from the field: Users reporting that the app was slow. We've seen some active sessions in Tomcat that didn't correspond to any user, but also 3 database connections on PostgreSQL that were IN TRANSACTION for a long time. Killing the Tomcat and database sessions the correct speed has been recovered One monitoring option to consider (open source with commercial support) is hyperic, * http://sourceforge.net/projects/hyperic-hq/ * https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
[ https://issues.apache.org/jira/browse/ISIS-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365725#comment-14365725 ] Dan Haywood edited comment on ISIS-1097 at 3/17/15 6:35 PM: I'm not convinced that Axon will sort this. Rather, I think that the current design does not allow for a stack of events nested one within the other, and that is probably where the issue is. Rather than currentInteraction.set(...) on a thread-local, it should be doing push() and pop(). These thread-locals can be found in PropertyDomainEventFacetAbstract, ActionDomainEventFacetAbstract, CollectionDomainEventFacetAbstract. Have raised a ticket for this... https://issues.apache.org/jira/browse/ISIS-1045. was (Author: danhaywood): I'm not convinced that Axon will sort this. Rather, I think that the current design does not allow for a stack of events nested one within the other, and that is probably where the issue is. Rather than currentInteraction.set(...) on a thread-local, it should be doing push() and pop(). These thread-locals can be found in PropertyDomainEventFacetAbstract, ActionDomainEventFacetAbstract, CollectionDomainEventFacetAbstract. I think I raised a ticket for this... can't locate it just now (in the ISIS-10xx range). Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability -- Key: ISIS-1097 URL: https://issues.apache.org/jira/browse/ISIS-1097 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.9.0 Report from the field: Users reporting that the app was slow. We've seen some active sessions in Tomcat that didn't correspond to any user, but also 3 database connections on PostgreSQL that were IN TRANSACTION for a long time. Killing the Tomcat and database sessions the correct speed has been recovered One monitoring option to consider (open source with commercial support) is hyperic, * http://sourceforge.net/projects/hyperic-hq/ * https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1098) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)
[ https://issues.apache.org/jira/browse/ISIS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365715#comment-14365715 ] Dan Haywood commented on ISIS-1098: --- It might make sense to have an Extension annotation (cf JDO API) that allows arbitrary metadata to be specified. Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API) -- Key: ISIS-1098 URL: https://issues.apache.org/jira/browse/ISIS-1098 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: 1.10.0 see https://issues.apache.org/jira/browse/ISIS-1095 for background. arguably it should be @PropertyLayout and @ParameterLayout annotations that we extend, rather than @Property and @Parameter ... depends on how intrinsic to the domain this hint is. Opinions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365686#comment-14365686 ] Jörg Rade commented on ISIS-1085: - Party and PartyType didn*t work. I could not spot any differences in their implementations as compared to 'Application'. Should I attach sources? Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1096) Derive the object type from the schema and table of @PersistenceCapable (but ensure backward compatibility is preserved).
[
https://issues.apache.org/jira/browse/ISIS-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365682#comment-14365682
]
ASF subversion and git services commented on ISIS-1096:
---
Commit 930ccfe7d2f24c187bd65c6dd5db1dce11b51f2c in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=930ccfe ]
ISIS-1096: extend facet factory for @PersistenceCapable to also capture schema,
and notice this in DomainObjectFacetFactory and use for the objectType if not
otherwise specified.
In addition:
- extended ProgrammingModel / ProgrammingModelAbstract API so that
refinements to the programming model (ie additional facet factories such as
the JdoPersistenceCapableAnnotationFacetFactory) can be added to the beginning
rather than to the end, thus ensuring that the JdoPersistenceCapableFacet is
present by the time that DomainObjectFacetFactory processes the type.
Derive the object type from the schema and table of @PersistenceCapable (but
ensure backward compatibility is preserved).
-
Key: ISIS-1096
URL: https://issues.apache.org/jira/browse/ISIS-1096
Project: Isis
Issue Type: New Feature
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
The algorithm should be:
1. @DomainObject(objectType = ...)
2. @ObjectType(...)
3. @PersistenceCapable(schema=..., table=...)
4. use the default fully qualified class name.
This ticket is all about introducing (3). The inferred objecttype should be:
schemaname.TableName, where schemaname is lowercased.
If schema is not present, then should ignore.
~~~
In addition, to support any legacy serialized data that uses the fully
qualified class name, the resolution of objects by object type should first
lookup the object type by its specified name, else fallback to looking up as
if FQN.
eg suppose have:
{code}
package com.mycompany.myapp
@DomainObject(objectType=CUS)
public class Customer { ... }
{code}
then the serialized form of this is CUS:1, but Isis should also resolve
this object if com.mycompany.myapp.Customer:1 is provided instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1096) Derive the object type from the schema and table of @PersistenceCapable (but ensure backward compatibility is preserved).
[
https://issues.apache.org/jira/browse/ISIS-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365681#comment-14365681
]
ASF subversion and git services commented on ISIS-1096:
---
Commit b3b89d1c554f2e5e08e5ef82e6dfea7ccd6f9f7f in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b3b89d1 ]
ISIS-1096: fallback to using objectType as classname if not found
Also:
- updated simpleapp (SimpleObject) to use custom schema
Derive the object type from the schema and table of @PersistenceCapable (but
ensure backward compatibility is preserved).
-
Key: ISIS-1096
URL: https://issues.apache.org/jira/browse/ISIS-1096
Project: Isis
Issue Type: New Feature
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
The algorithm should be:
1. @DomainObject(objectType = ...)
2. @ObjectType(...)
3. @PersistenceCapable(schema=..., table=...)
4. use the default fully qualified class name.
This ticket is all about introducing (3). The inferred objecttype should be:
schemaname.TableName, where schemaname is lowercased.
If schema is not present, then should ignore.
~~~
In addition, to support any legacy serialized data that uses the fully
qualified class name, the resolution of objects by object type should first
lookup the object type by its specified name, else fallback to looking up as
if FQN.
eg suppose have:
{code}
package com.mycompany.myapp
@DomainObject(objectType=CUS)
public class Customer { ... }
{code}
then the serialized form of this is CUS:1, but Isis should also resolve
this object if com.mycompany.myapp.Customer:1 is provided instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ISIS-1096) Derive the object type from the schema and table of @PersistenceCapable (but ensure backward compatibility is preserved).
[
https://issues.apache.org/jira/browse/ISIS-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1096.
---
Resolution: Fixed
Derive the object type from the schema and table of @PersistenceCapable (but
ensure backward compatibility is preserved).
-
Key: ISIS-1096
URL: https://issues.apache.org/jira/browse/ISIS-1096
Project: Isis
Issue Type: New Feature
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
The algorithm should be:
1. @DomainObject(objectType = ...)
2. @ObjectType(...)
3. @PersistenceCapable(schema=..., table=...)
4. use the default fully qualified class name.
This ticket is all about introducing (3). The inferred objecttype should be:
schemaname.TableName, where schemaname is lowercased.
If schema is not present, then should ignore.
~~~
In addition, to support any legacy serialized data that uses the fully
qualified class name, the resolution of objects by object type should first
lookup the object type by its specified name, else fallback to looking up as
if FQN.
eg suppose have:
{code}
package com.mycompany.myapp
@DomainObject(objectType=CUS)
public class Customer { ... }
{code}
then the serialized form of this is CUS:1, but Isis should also resolve
this object if com.mycompany.myapp.Customer:1 is provided instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1095) Make it possible to show the datepicker in a birthdate mode
[ https://issues.apache.org/jira/browse/ISIS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365015#comment-14365015 ] ASF subversion and git services commented on ISIS-1095: --- Commit b04c965843e93fda1ec4fa5ec39e9ff26da81296 in isis's branch refs/heads/master from [~mgrigorov] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b04c965 ] ISIS-1095 Make it possible to show the datepicker in a birthdate mode Make it possible to show the datepicker in a birthdate mode - Key: ISIS-1095 URL: https://issues.apache.org/jira/browse/ISIS-1095 Project: Isis Issue Type: Improvement Components: Core: Viewer: Wicket Affects Versions: 1.9.0 Reporter: Martin Grigorov Assignee: Martin Grigorov Priority: Minor Fix For: 1.9.0 Add an additional constructor to org.apache.isis.viewer.wicket.ui.components.scalars.datepicker.TextFieldWithDatePicker that allows to use custom DateTimeConfig. The improvement won't be available for temporal properties in Isis because there is no facet for this. The improvement will be useful for applications using TextFieldWithDatePicker in custom components (e.g. for view models). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
Dan Haywood created ISIS-1097: - Summary: Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability Key: ISIS-1097 URL: https://issues.apache.org/jira/browse/ISIS-1097 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.9.0 Report from the field: Users reporting that the app was slow. We've seen some active sessions in Tomcat that didn't correspond to any user, but also 3 database connections on PostgreSQL that were IN TRANSACTION for a long time. Killing the Tomcat and database sessions the correct speed has been recovered One monitoring option to consider (open source with commercial support) is hyperic, * http://sourceforge.net/projects/hyperic-hq/ * https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
[ https://issues.apache.org/jira/browse/ISIS-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365060#comment-14365060 ] Dan Haywood commented on ISIS-1097: --- I was wondering if the IsisWicketRequestCycle stuff isn't completing the xactn in certain circumstances, eg if a DB exception (unique index violation, opt locking exception) is encountered. Then again, for this particular app where the problem was reported, it doesn't use the Wicket viewer, so perhaps that's an unrelated issue. ~~~ Have also had a similar report (but perhaps unrelated) for other system that does use the Wicket viewer. Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability -- Key: ISIS-1097 URL: https://issues.apache.org/jira/browse/ISIS-1097 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.9.0 Report from the field: Users reporting that the app was slow. We've seen some active sessions in Tomcat that didn't correspond to any user, but also 3 database connections on PostgreSQL that were IN TRANSACTION for a long time. Killing the Tomcat and database sessions the correct speed has been recovered One monitoring option to consider (open source with commercial support) is hyperic, * http://sourceforge.net/projects/hyperic-hq/ * https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1095) Make it possible to show the datepicker in a birthdate mode
[ https://issues.apache.org/jira/browse/ISIS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365026#comment-14365026 ] ASF subversion and git services commented on ISIS-1095: --- Commit cf42db12316d56e55d540cb464cabc516a4a5aa3 in isis's branch refs/heads/master from [~mgrigorov] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=cf42db1 ] ISIS-1095 Rename the constant so it doesn't clash with the enum Make it possible to show the datepicker in a birthdate mode - Key: ISIS-1095 URL: https://issues.apache.org/jira/browse/ISIS-1095 Project: Isis Issue Type: Improvement Components: Core: Viewer: Wicket Affects Versions: core-1.8.0 Reporter: Martin Grigorov Assignee: Martin Grigorov Priority: Minor Fix For: 1.9.0 Add an additional constructor to org.apache.isis.viewer.wicket.ui.components.scalars.datepicker.TextFieldWithDatePicker that allows to use custom DateTimeConfig. The improvement won't be available for temporal properties in Isis because there is no facet for this. The improvement will be useful for applications using TextFieldWithDatePicker in custom components (e.g. for view models). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365059#comment-14365059 ] Jörg Rade commented on ISIS-1085: - Hi Martin, they show the intrended cssClassFa icon - I'll attach some screenshots. Best regards Jörg Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1085: Attachment: ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1096) Derive the object type from the schema and table of @PersistenceCapable (but ensure backward compatibility is preserved).
Dan Haywood created ISIS-1096:
-
Summary: Derive the object type from the schema and table of
@PersistenceCapable (but ensure backward compatibility is preserved).
Key: ISIS-1096
URL: https://issues.apache.org/jira/browse/ISIS-1096
Project: Isis
Issue Type: New Feature
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
The algorithm should be:
1. @DomainObject(objectType = ...)
2. @ObjectType(...)
3. @PersistenceCapable(schema=..., table=...)
4. use the default fully qualified class name.
This ticket is all about introducing (3). The inferred objecttype should be:
schemaname.TableName, where schemaname is lowercased.
If schema is not present, then should ignore.
~~~
In addition, to support any legacy serialized data that uses the fully
qualified class name, the resolution of objects by object type should first
lookup the object type by its specified name, else fallback to looking up as if
FQN.
eg suppose have:
{code}
package com.mycompany.myapp
@DomainObject(objectType=CUS)
public class Customer { ... }
{code}
then the serialized form of this is CUS:1, but Isis should also resolve this
object if com.mycompany.myapp.Customer:1 is provided instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1095) Make it possible to show the datepicker in a birthdate mode
[ https://issues.apache.org/jira/browse/ISIS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grigorov updated ISIS-1095: -- Affects Version/s: (was: 1.9.0) core-1.8.0 Make it possible to show the datepicker in a birthdate mode - Key: ISIS-1095 URL: https://issues.apache.org/jira/browse/ISIS-1095 Project: Isis Issue Type: Improvement Components: Core: Viewer: Wicket Affects Versions: core-1.8.0 Reporter: Martin Grigorov Assignee: Martin Grigorov Priority: Minor Fix For: 1.9.0 Add an additional constructor to org.apache.isis.viewer.wicket.ui.components.scalars.datepicker.TextFieldWithDatePicker that allows to use custom DateTimeConfig. The improvement won't be available for temporal properties in Isis because there is no facet for this. The improvement will be useful for applications using TextFieldWithDatePicker in custom components (e.g. for view models). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365059#comment-14365059 ] Jörg Rade edited comment on ISIS-1085 at 3/17/15 12:51 PM: --- Hi Martin, they show the intended cssClassFa icon - I'll attach some screenshots. Best regards Jörg was (Author: joerg.rade): Hi Martin, they show the intrended cssClassFa icon - I'll attach some screenshots. Best regards Jörg Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1095) Make it possible to show the datepicker in a birthdate mode
[ https://issues.apache.org/jira/browse/ISIS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365018#comment-14365018 ] ASF subversion and git services commented on ISIS-1095: --- Commit efe69a277cf022833ae3c61614522b328d7cc426 in isis's branch refs/heads/master from [~mgrigorov] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=efe69a2 ] ISIS-1095 Rename StartView to ViewMode, to be in sync with the new name in the JS widget Make it possible to show the datepicker in a birthdate mode - Key: ISIS-1095 URL: https://issues.apache.org/jira/browse/ISIS-1095 Project: Isis Issue Type: Improvement Components: Core: Viewer: Wicket Affects Versions: core-1.8.0 Reporter: Martin Grigorov Assignee: Martin Grigorov Priority: Minor Fix For: 1.9.0 Add an additional constructor to org.apache.isis.viewer.wicket.ui.components.scalars.datepicker.TextFieldWithDatePicker that allows to use custom DateTimeConfig. The improvement won't be available for temporal properties in Isis because there is no facet for this. The improvement will be useful for applications using TextFieldWithDatePicker in custom components (e.g. for view models). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1098) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)
Dan Haywood created ISIS-1098: - Summary: Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API) Key: ISIS-1098 URL: https://issues.apache.org/jira/browse/ISIS-1098 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: 1.10.0 see https://issues.apache.org/jira/browse/ISIS-1095 for background. arguably it should be @PropertyLayout and @ParameterLayout annotations that we extend, rather than @Property and @Parameter ... depends on how intrinsic to the domain this hint is. Opinions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1098) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)
[ https://issues.apache.org/jira/browse/ISIS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365091#comment-14365091 ] Martin Grigorov edited comment on ISIS-1098 at 3/17/15 1:19 PM: I think the ***Layout annotations should be extended. Or even introduce a special annotation for temporal properties/parameters ?! Because the JS widget has many settings: http://eonasdan.github.io/bootstrap-datetimepicker/Options/. For ISIS-1095 I needed just: http://eonasdan.github.io/bootstrap-datetimepicker/Options/#viewmode You can see it in action at http://eonasdan.github.io/bootstrap-datetimepicker/#view-mode. With years viewMode the picker asks you first to select the year, then the month and finally the date. This is much easier for selecting a birthdate than trying to navigate with the default view (http://eonasdan.github.io/bootstrap-datetimepicker/#minimum-setup) was (Author: mgrigorov): I think the ***Layout annotations should be extended. Or even introduce a special annotation for temporal properties/parameters ?! Because the JS widget has many settings: http://eonasdan.github.io/bootstrap-datetimepicker/Options/. For ISIS-1095 I needed just: http://eonasdan.github.io/bootstrap-datetimepicker/Options/#viewmode You can see it in action at http://eonasdan.github.io/bootstrap-datetimepicker/#view-mode. With years viewMode the picker asks you first to select the year, then the month and finally the date. This is much easier to selecting a birthdate than trying to navigate with the default view (http://eonasdan.github.io/bootstrap-datetimepicker/#minimum-setup) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API) -- Key: ISIS-1098 URL: https://issues.apache.org/jira/browse/ISIS-1098 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: 1.10.0 see https://issues.apache.org/jira/browse/ISIS-1095 for background. arguably it should be @PropertyLayout and @ParameterLayout annotations that we extend, rather than @Property and @Parameter ... depends on how intrinsic to the domain this hint is. Opinions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1098) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)
[ https://issues.apache.org/jira/browse/ISIS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365091#comment-14365091 ] Martin Grigorov commented on ISIS-1098: --- I think the ***Layout annotations should be extended. Or even introduce a special annotation for temporal properties/parameters ?! Because the JS widget has many settings: http://eonasdan.github.io/bootstrap-datetimepicker/Options/. For ISIS-1095 I needed just: http://eonasdan.github.io/bootstrap-datetimepicker/Options/#viewmode You can see it in action at http://eonasdan.github.io/bootstrap-datetimepicker/#view-mode. With years viewMode the picker asks you first to select the year, then the month and finally the date. This is much easier to selecting a birthdate than trying to navigate with the default view (http://eonasdan.github.io/bootstrap-datetimepicker/#minimum-setup) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API) -- Key: ISIS-1098 URL: https://issues.apache.org/jira/browse/ISIS-1098 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: 1.10.0 see https://issues.apache.org/jira/browse/ISIS-1095 for background. arguably it should be @PropertyLayout and @ParameterLayout annotations that we extend, rather than @Property and @Parameter ... depends on how intrinsic to the domain this hint is. Opinions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1097) Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability
[ https://issues.apache.org/jira/browse/ISIS-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365103#comment-14365103 ] Oscar Bou commented on ISIS-1097: - In our case we've discovered that the long-time running queries we've detected are due to a infinite recursion action invocation. But that code is heavily dependant on the EventBusService. So we're suspecting about the queueing behavior we notified on the user list, and whose solution might be the one proposed at [1] (implementing one based on Axon), or create a new Guava's Event Bus Service descendant that instantiates a dispatcher that does not enqueue calls. [1] https://issues.apache.org/jira/browse/ISIS-1028 Suspicion that Isis may be leaving DB connections open under certain circumstances, leading to instability -- Key: ISIS-1097 URL: https://issues.apache.org/jira/browse/ISIS-1097 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.8.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.9.0 Report from the field: Users reporting that the app was slow. We've seen some active sessions in Tomcat that didn't correspond to any user, but also 3 database connections on PostgreSQL that were IN TRANSACTION for a long time. Killing the Tomcat and database sessions the correct speed has been recovered One monitoring option to consider (open source with commercial support) is hyperic, * http://sourceforge.net/projects/hyperic-hq/ * https://my.vmware.com/web/vmware/details?downloadGroup=VRHQ_584_OSSproductId=378 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
