[jira] Commented: (OFBIZ-4041) Materialized views
[ https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12969414#action_12969414 ] Marc Morin commented on OFBIZ-4041: --- Good point Scott. We have removed the bulk operations in our implementation for specifically that reason... We've noticed that even though these are bulk operations, they don't appear to be from an API point of view. There isn't much to help guide the developer that using these API's will circumvent all ECA activity We had thought about only doing the bulk operation iff there are no ECAs defined for the entity and operation defined. Otherwise, leave it as bulk. But that too would appear to be dangerous since there are unknown side affects of not running the ECA. Not sure what the best/good compromise is for the bulk vs normal operation is. Just seems incorrect to bypass the ECA. Not that disabling the eca via the entityengine.xml also causes the materialized views to not always maintaining it's results. Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin Attachments: OFBIZ-4041.patch We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4041) Materialized views
[ https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12969573#action_12969573 ] Marc Morin commented on OFBIZ-4041: --- Adam, are you commenting on the materialized view problem vs the bulk operations? Either way, both use the same logic of cascading possible operations to dependent model items (either in the cache) or materlalized views. If you look at the patch, the materialized views use the EXACT same ModelConversion information that the cache uses to propage, but instead of clearing values, it clears and rebuilds. Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin Attachments: OFBIZ-4041.patch We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4041) Materialized views
[ https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-4041: -- Attachment: OFBIZ-4041.patch Patch for implementation of Materialized views. This implementation used a visitor pattern, on the ModelEntity (and related classes) so they are part of the patch. Also, since entities are created by code, as opposed to by reading XML files, a number of getters and setters were added to the model objects. A new class, ModelMaterializedEntity is created when a view is read having materialized=true property. It creates an ECA for all the dependent entities used by the view. There is NO checking on the usefulness or expense of the materialized views. It should also only be used on views where the pkey of the underlying entity is exposed as a field in the view, since this makes the ECA more efficient. CheckDb will rebuild all materialized views since there is no way currently in OFBIZ to detect that the view's definition has changed. In our implementation, we record an MD5 of the view as a comment on the table thereby detecting if we need to rebuild. That wasn't included at this time. No ECA to prevent store/remove on the backing entity. Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin Attachments: OFBIZ-4041.patch We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4041) Materialized views
Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4041) Materialized views
[ https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966673#action_12966673 ] Marc Morin commented on OFBIZ-4041: --- Not yet, I would need to pull it out of our OFbiz source tree... which is about a year old and co-mingled with a lot of other framework goodies... I am prepared to do the work though if the community wants the feature. Marc Morin Emforium Group Inc. ALL-IN Software 519-772-6824 ext 201 mmo...@emforium.com - Original Message - Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3774) Add The Visitor Pattern To Screen Widget Model Classes
[ https://issues.apache.org/jira/browse/OFBIZ-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868470#action_12868470 ] Marc Morin commented on OFBIZ-3774: --- We did a similar visitor pattern to the entire presentment (Screen, Form, Menu) space and the controller. This path, mainly separation of concern, is very powerful, and allows easy extension to the system. The typical implementation path that has been taken, is to develop a series of abstract visitors that have a few base behaviors, navigation of the components, and throwing exceptions for each component. This enables a specific visitors to extend the base navigation class, to get full model navigation and add any specific behavior with a surprisingly small amount of code. We've done Presentment visitors for walking, validation (examining location/name references looking for dangling screen/from/controller references, etc.. used in junit test cases - fail build if broken links), security auto-notation (propagates service security declarations, to screens model objects, and will automatically remove buttons, links to areas in the application that the user doesn't have rights to access.) We have a partial dump (pretty-print) for the PresentmentModel as well. Externalizing the creation of the model objects, is crucial to getting the full power of this type of change. The model objects should have nothing but their attributes with their getter/setter methods (and the accept). Add The Visitor Pattern To Screen Widget Model Classes -- Key: OFBIZ-3774 URL: https://issues.apache.org/jira/browse/OFBIZ-3774 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Adrian Crum Priority: Minor Attachments: OFBIZ-3774.patch From time to time there has been interest expressed in introducing the visitor pattern to the screen widget model classes. This issue is intended to provide a forum on the subject and a means to vote on it. Details are in the comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3540) Multi-Tenant Support (Login Based)
[ https://issues.apache.org/jira/browse/OFBIZ-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842745#action_12842745 ] Marc Morin commented on OFBIZ-3540: --- From the experience of our multi-tenant implementation, we've noticed - multi-tenant was easy to add for the base case, as this patch indicates, the delegator pretty much abstracted much of it away. - we more formally, expanded the entity-engine.xml definition to define ftl templates for the tenant databases configuration. When looking up a tenant's db configuration, we set the hostname, username, password, tenantId, etc in a context that is applied to generate the tenant's specific configuration. This allows for changing the sequenced-id-prefix for each tenant, allowing easier merging of data between tenants. We chose to use entirely different delegatorNames, such as 1, 10001, etc directly from the SequenceValueItem. - The EntityCache is per delegator, and not per unique datasource, we haven't changed this, but it essentially, prevents sharing the same datasource amongst tenants - Selecting the delegator/tenant is needed in different areas of the application, via different techniques. via explicity selection, as the login demo application here, but we've also need to associate the hostname of the HTTP request, to enable multiple entire instances, both authenticated and not, to be distinguishable. - The dispatcher will create a seperate job manager for each tenant. This is fine for a small number of tenants, but with a larger number, a single JobPoller/Manager is required. We've added these enhancements and additional tenantId field on the JobSandbox. We interpret, null in tenantId, here to mean, replicate this job to run all all tenant instances. Think of all the cleanup jobs, etc... - Singleton JobManager also handles scheduling of jobs for tenants that haven't been loaded... The current mechanism will not load the tenant, until someone logs in that instance. - The life cycle, create, upgrade, decommission of the tenants is a non trivial amount of work. We've spent a large amount of effort here, to keep the support cost down for 1000's of tenants in a system. Creating a new tenant from a blank template, applying upgrade sql files, etc... - Since our service is a subscription, we modeled the tenant instance as a Product in our master instance. We use the Subscription product behavior to help control the expiration, etc.. of the tenant. Many of these changes are in our forked version of the code. We can try to extract components that people feel would be beneficial if there is interest. Multi-Tenant Support (Login Based) -- Key: OFBIZ-3540 URL: https://issues.apache.org/jira/browse/OFBIZ-3540 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: David E. Jones Assignee: David E. Jones Priority: Minor Fix For: SVN trunk Attachments: MultiTenant20100305.patch, MultiTenant20100305.patch, MultiTenant20100305.patch Support multiple tenants in a single instance of OFBiz. Each tenant will have its own databases (one for each entity group). Database settings will override the settings on the delegator with parameters from an entity record so that new tenants can be added on the fly without restarting the server (new tenants will still need to have data loaded in their databases just like any other). If valid Tenant ID is specified when user logs in then webapp context will be setup with tools for that tenant as a variation of the base delegator (including delegator, dispatcher, security, authz, visit, server hit, etc handled for it). Demo data includes a couple of sample tenants. After loading demo data (ant run-install) try logging in to webtools or any other admin app with the Tenant ID of DEMO1. NOTE: this patch also addresses some stability issues with the LoginWorker, ControlServlet, Visit, and ServerHit functionality that was exposed while developing this. For example, after a logout functionality that runs in the ControlServlet may fail because things that were in the session before are not there any more. In this patch there is code to rebuild the request and session after logout (necessary for changing tenants, helpful for these other issues). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2974) JobManager.reloadCrashedJobs fails to reload crashed jobs
[ https://issues.apache.org/jira/browse/OFBIZ-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798650#action_12798650 ] Marc Morin commented on OFBIZ-2974: --- Has anyone else run into this? Seems like this is a core problem in the framework. JobManager.reloadCrashedJobs fails to reload crashed jobs - Key: OFBIZ-2974 URL: https://issues.apache.org/jira/browse/OFBIZ-2974 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Scott Gray Priority: Critical The JobManager.reloadCrashedJobs() method fails to reload most crashed jobs each time it is run, this occurs for two reasons: 1. The method only supports reloading jobs that have a related RecurrenceInfo, if it has no recurrence information or if it uses the newer temporal expressions then the job is passed over and not reloaded 2. If the job does have a related RecurrenceInfo then the method checks to see if the next recurrence from now is less than the runTime of the crashed job, this is almost never the case so once again the job isn't reloaded. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3157) application - accounting
[ https://issues.apache.org/jira/browse/OFBIZ-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791957#action_12791957 ] Marc Morin commented on OFBIZ-3157: --- jacques, I have been overwhelmed with other work will eventually get to it, not sure when though :-( Marc Morin Emforium Group Inc. ALL-IN Software™ 519-772-6824 ext 201 mmo...@emforium.com application - accounting Key: OFBIZ-3157 URL: https://issues.apache.org/jira/browse/OFBIZ-3157 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: OFBIZ-3157.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3157) application - accounting
[ https://issues.apache.org/jira/browse/OFBIZ-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780190#action_12780190 ] Marc Morin commented on OFBIZ-3157: --- I've tried the application/content a couple of times. There appears to be bugs in there, where what is put into the maps/lists isn't what is extracted. I'll file a jira to fix the bug first, before the code cleanup. Marc Morin Emforium Group Inc. ALL-IN Software™ 519-772-6824 ext 201 mmo...@emforium.com application - accounting Key: OFBIZ-3157 URL: https://issues.apache.org/jira/browse/OFBIZ-3157 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Assignee: Jacques Le Roux Fix For: SVN trunk Attachments: OFBIZ-3157.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3107) framework - entity
[ https://issues.apache.org/jira/browse/OFBIZ-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3107: -- Attachment: OFBIZ-3107-take2.patch redone to adjust for changes since last created framework - entity -- Key: OFBIZ-3107 URL: https://issues.apache.org/jira/browse/OFBIZ-3107 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3107-take2.patch, OFBIZ-3107.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3105) framework - common
[ https://issues.apache.org/jira/browse/OFBIZ-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778090#action_12778090 ] Marc Morin commented on OFBIZ-3105: --- there are no warnings in this area framework - common -- Key: OFBIZ-3105 URL: https://issues.apache.org/jira/browse/OFBIZ-3105 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-3110) framework - exampleext
[ https://issues.apache.org/jira/browse/OFBIZ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin closed OFBIZ-3110. - Resolution: Invalid There were no warnings in this area framework - exampleext -- Key: OFBIZ-3110 URL: https://issues.apache.org/jira/browse/OFBIZ-3110 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-3113) framework - images
[ https://issues.apache.org/jira/browse/OFBIZ-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin closed OFBIZ-3113. - Resolution: Invalid no warnings in this area framework - images -- Key: OFBIZ-3113 URL: https://issues.apache.org/jira/browse/OFBIZ-3113 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3157) application - accounting
application - accounting Key: OFBIZ-3157 URL: https://issues.apache.org/jira/browse/OFBIZ-3157 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3157) application - accounting
[ https://issues.apache.org/jira/browse/OFBIZ-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3157: -- Attachment: OFBIZ-3157.patch patch for generic's warnings for accounting application application - accounting Key: OFBIZ-3157 URL: https://issues.apache.org/jira/browse/OFBIZ-3157 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3157.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3120) framework - webapp
[ https://issues.apache.org/jira/browse/OFBIZ-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3120: -- Attachment: OFBIZ-3120.patch framework - webapp -- Key: OFBIZ-3120 URL: https://issues.apache.org/jira/browse/OFBIZ-3120 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3120.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3107) framework - entity
[ https://issues.apache.org/jira/browse/OFBIZ-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3107: -- Attachment: OFBIZ-3107.patch entity patch. This was a more difficult one because of the partially parameterized generics in the condition evaluation. framework - entity -- Key: OFBIZ-3107 URL: https://issues.apache.org/jira/browse/OFBIZ-3107 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3107.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3121) framework - webslinger
[ https://issues.apache.org/jira/browse/OFBIZ-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3121: -- Attachment: OFBIZ-3121.patch framework - webslinger -- Key: OFBIZ-3121 URL: https://issues.apache.org/jira/browse/OFBIZ-3121 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3121.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3100) Resolve java warnings exposed in Eclipse
[ https://issues.apache.org/jira/browse/OFBIZ-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12773335#action_12773335 ] Marc Morin commented on OFBIZ-3100: --- Once we apply the patch for framework/entity. Likely a number of warnings using EntityCondition.makeCondition() will go away... or we'll likely need to do a second pass. Once we get the framework area patched, I will be happy to proceed into the other areas. Resolve java warnings exposed in Eclipse Key: OFBIZ-3100 URL: https://issues.apache.org/jira/browse/OFBIZ-3100 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Bob Morley There are over 9000 warnings reported when you do a build in Eclipse. Let's clean them up! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3117) framework - service
[ https://issues.apache.org/jira/browse/OFBIZ-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3117: -- Attachment: OFBIZ-3117.patch framework - service --- Key: OFBIZ-3117 URL: https://issues.apache.org/jira/browse/OFBIZ-3117 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3117.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3118) framework - start
[ https://issues.apache.org/jira/browse/OFBIZ-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3118: -- Attachment: OFBIZ-3118.patch framework - start - Key: OFBIZ-3118 URL: https://issues.apache.org/jira/browse/OFBIZ-3118 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3118.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3119) framework - testtools
[ https://issues.apache.org/jira/browse/OFBIZ-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3119: -- Attachment: OFBIZ-3119.patch framework - testtools - Key: OFBIZ-3119 URL: https://issues.apache.org/jira/browse/OFBIZ-3119 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3119.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3100) Resolve java warnings exposed in Eclipse
[ https://issues.apache.org/jira/browse/OFBIZ-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771477#action_12771477 ] Marc Morin commented on OFBIZ-3100: --- I just formatted using the built in Eclipse feature, haven't set it up any differently. This likely points to needing to have a common Eclipse code style error/warning profile as well. Resolve java warnings exposed in Eclipse Key: OFBIZ-3100 URL: https://issues.apache.org/jira/browse/OFBIZ-3100 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Bob Morley There are over 9000 warnings reported when you do a build in Eclipse. Let's clean them up! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3102) framework - base
[
https://issues.apache.org/jira/browse/OFBIZ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771529#action_12771529
]
Marc Morin commented on OFBIZ-3102:
---
Generally, we should strive to have no @SuppressWarnings(unchecked) in the
code at all. Ideally, only in 1 or two spots in UtilGenerics where you just
can't get around Java generics issues like the following:
ListMyClass mymethod(ListInput list) {
return (ListMyClass) list;
}
The compiler cannot check the generic type at compile time and will not check
at run-time. It will generate a compiler warning. To now have it show up, you
can @SuppressWarnings(unchecked) on the method.
For the normal case in the code, we want to encourage the proper use of
generics. An example, which is the bulk of the type of code we're modifying is
a hold over of pre-Java 1.5 (I think that's when Generics were introduced).
Map myMethod(Map values) {
Map newMap = new FastMap(values);
newMap.put(this, that);
return newMap;
}
This will result in warnings related to the generics. You can make them go
away with a big old @SuppressWarnings(unchecked) on the method, but that
isn't as desirable as
MapString, String myMethod(MapString, String values) {
MapString, String newMap = new FastMapString, String)(values);
newMap.put(this, that);
return newMap;
}
framework - base
Key: OFBIZ-3102
URL: https://issues.apache.org/jira/browse/OFBIZ-3102
Project: OFBiz
Issue Type: Sub-task
Components: framework
Affects Versions: SVN trunk
Reporter: Bob Morley
Attachments: OFBIZ-3102 base warning.patch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3102) framework - base
[ https://issues.apache.org/jira/browse/OFBIZ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771530#action_12771530 ] Marc Morin commented on OFBIZ-3102: --- Agree that the choice of the generic placeholder (X, E, T, ) should be closest to what the user of the class/function would expect. In java.util, you see a lot of E, since Collections, Lists, etc work on elements. E being a good choice for that. I was sloppy and just picked X, which I have historically used for I don't know what this is placeholder. I'll improve the choice going forward on a case by case basis. framework - base Key: OFBIZ-3102 URL: https://issues.apache.org/jira/browse/OFBIZ-3102 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3102 base warning.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3102) framework - base
[ https://issues.apache.org/jira/browse/OFBIZ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771212#action_12771212 ] Marc Morin commented on OFBIZ-3102: --- I'll tackle this an put the patch up framework - base Key: OFBIZ-3102 URL: https://issues.apache.org/jira/browse/OFBIZ-3102 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3102) framework - base
[ https://issues.apache.org/jira/browse/OFBIZ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3102: -- Attachment: OFBIZ-3102 base warning.patch Patch to remove warnings in framework/base framework - base Key: OFBIZ-3102 URL: https://issues.apache.org/jira/browse/OFBIZ-3102 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3102 base warning.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3101) framework - appserver
[ https://issues.apache.org/jira/browse/OFBIZ-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3101: -- Attachment: OFBIZ-3101.patch patches to removed warnings framework - appserver - Key: OFBIZ-3101 URL: https://issues.apache.org/jira/browse/OFBIZ-3101 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3101.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3103) framework - bi
[ https://issues.apache.org/jira/browse/OFBIZ-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3103: -- Attachment: OFBIZ-3103.patch framework - bi -- Key: OFBIZ-3103 URL: https://issues.apache.org/jira/browse/OFBIZ-3103 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3103.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3104) framework - catalina
[ https://issues.apache.org/jira/browse/OFBIZ-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3104: -- Attachment: OFBIZ-3104.patch framework - catalina Key: OFBIZ-3104 URL: https://issues.apache.org/jira/browse/OFBIZ-3104 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3104.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3110) framework - entityext
framework - entityext - Key: OFBIZ-3110 URL: https://issues.apache.org/jira/browse/OFBIZ-3110 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3110) framework - exampleext
[ https://issues.apache.org/jira/browse/OFBIZ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3110: -- Summary: framework - exampleext (was: framework - entityext) framework - exampleext -- Key: OFBIZ-3110 URL: https://issues.apache.org/jira/browse/OFBIZ-3110 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3109) framwork - example
framwork - example -- Key: OFBIZ-3109 URL: https://issues.apache.org/jira/browse/OFBIZ-3109 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3111) framework - geronimo
[ https://issues.apache.org/jira/browse/OFBIZ-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3111: -- Summary: framework - geronimo (was: geronimo) framework - geronimo Key: OFBIZ-3111 URL: https://issues.apache.org/jira/browse/OFBIZ-3111 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3113) framework - images
framework - images -- Key: OFBIZ-3113 URL: https://issues.apache.org/jira/browse/OFBIZ-3113 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3114) framework - jetty
framework - jetty - Key: OFBIZ-3114 URL: https://issues.apache.org/jira/browse/OFBIZ-3114 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3111) geronimo
geronimo Key: OFBIZ-3111 URL: https://issues.apache.org/jira/browse/OFBIZ-3111 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3118) framework - start
framework - start - Key: OFBIZ-3118 URL: https://issues.apache.org/jira/browse/OFBIZ-3118 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3116) framework - security
framework - security Key: OFBIZ-3116 URL: https://issues.apache.org/jira/browse/OFBIZ-3116 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3115) framework - minilang
framework - minilang Key: OFBIZ-3115 URL: https://issues.apache.org/jira/browse/OFBIZ-3115 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3117) framework - service
framework - service --- Key: OFBIZ-3117 URL: https://issues.apache.org/jira/browse/OFBIZ-3117 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3120) framework - webapp
framework - webapp -- Key: OFBIZ-3120 URL: https://issues.apache.org/jira/browse/OFBIZ-3120 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3119) framework - testtools
framework - testtools - Key: OFBIZ-3119 URL: https://issues.apache.org/jira/browse/OFBIZ-3119 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3123) framework -widget
framework -widget - Key: OFBIZ-3123 URL: https://issues.apache.org/jira/browse/OFBIZ-3123 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3122) framework - webtools
framework - webtools Key: OFBIZ-3122 URL: https://issues.apache.org/jira/browse/OFBIZ-3122 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3123) framework -widget
[ https://issues.apache.org/jira/browse/OFBIZ-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3123: -- Attachment: OFBIZ-3123.patch framework -widget - Key: OFBIZ-3123 URL: https://issues.apache.org/jira/browse/OFBIZ-3123 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3123.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3106) framework - datafile
[ https://issues.apache.org/jira/browse/OFBIZ-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3106: -- Attachment: OFBIZ-3106.patch framework - datafile Key: OFBIZ-3106 URL: https://issues.apache.org/jira/browse/OFBIZ-3106 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3106.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3109) framework - exampleext
[ https://issues.apache.org/jira/browse/OFBIZ-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3109: -- Summary: framework - exampleext (was: framwork - example) framework - exampleext -- Key: OFBIZ-3109 URL: https://issues.apache.org/jira/browse/OFBIZ-3109 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3108) framework - entityext
[ https://issues.apache.org/jira/browse/OFBIZ-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3108: -- Attachment: OFBIZ-3108.patch framework - entityext - Key: OFBIZ-3108 URL: https://issues.apache.org/jira/browse/OFBIZ-3108 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Bob Morley Attachments: OFBIZ-3108.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3109) framework - example
[ https://issues.apache.org/jira/browse/OFBIZ-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3109: -- Summary: framework - example (was: framework - exampleext) framework - example --- Key: OFBIZ-3109 URL: https://issues.apache.org/jira/browse/OFBIZ-3109 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3109) framework - example
[ https://issues.apache.org/jira/browse/OFBIZ-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3109: -- Attachment: OFBIZ-3109.patch framework - example --- Key: OFBIZ-3109 URL: https://issues.apache.org/jira/browse/OFBIZ-3109 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3109.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3111) framework - geronimo
[ https://issues.apache.org/jira/browse/OFBIZ-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3111: -- Attachment: OFBIZ-3111.patch framework - geronimo Key: OFBIZ-3111 URL: https://issues.apache.org/jira/browse/OFBIZ-3111 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3111.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3114) framework - jetty
[ https://issues.apache.org/jira/browse/OFBIZ-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Morin updated OFBIZ-3114: -- Attachment: OFBIZ-3114.patch framework - jetty - Key: OFBIZ-3114 URL: https://issues.apache.org/jira/browse/OFBIZ-3114 Project: OFBiz Issue Type: Sub-task Reporter: Marc Morin Attachments: OFBIZ-3114.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2766) Multi-tenant support
Multi-tenant support Key: OFBIZ-2766 URL: https://issues.apache.org/jira/browse/OFBIZ-2766 Project: OFBiz Issue Type: New Feature Components: framework Reporter: Marc Morin Ability to run multiple instances of an ofbiz deployment within the same VM to enable increased resource utilization. There are a number of cases, depending upon how independent the tenants are from one another. In our particular case, we need to deploy a large number of tenants, all running the same application suite built on top of ofbiz. This means that they share all .properties, .xml, .ftl files and their only private data is maintained by private databases. Requirements are separate database for each tenant, but possible some shared entities. (want to maintain ability to have tenants have direct jdbc/odbc access to their database). UserLogin space is seperate for each tenant. Tenant selection is via hostname and/or url and maintained in session. An application needs to be developed to manage the life cycle of the tenants. We have an implementation of this type of deployment. It would take some work to extract it from our application in order to develop a generic feature set. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
