[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring
[ https://issues.apache.org/jira/browse/ATLAS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1198: --- Attachment: 0001-ATLAS-1198-Spring-Framework-v4-with-Spring-security-.patch > Move from Guice + Spring to only Spring > --- > > Key: ATLAS-1198 > URL: https://issues.apache.org/jira/browse/ATLAS-1198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1198-Spring-Framework-v4-with-Spring-security-.patch > > > Right now we're using both Guice and Spring and dependency injection which is > not a ideal combination. As Atlas evolves as a product we can leverage the > spring framework to avoid re-inventing the wheel like caching, transaction > management etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring
[ https://issues.apache.org/jira/browse/ATLAS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1198: --- Request participants: Ruchi Solani (was: ) > Move from Guice + Spring to only Spring > --- > > Key: ATLAS-1198 > URL: https://issues.apache.org/jira/browse/ATLAS-1198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > Right now we're using both Guice and Spring and dependency injection which is > not a ideal combination. As Atlas evolves as a product we can leverage the > spring framework to avoid re-inventing the wheel like caching, transaction > management etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring
[ https://issues.apache.org/jira/browse/ATLAS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1198: --- Affects Version/s: (was: 0.8-incubating) (was: 0.7-incubating) 0.9-incubating > Move from Guice + Spring to only Spring > --- > > Key: ATLAS-1198 > URL: https://issues.apache.org/jira/browse/ATLAS-1198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > > Right now we're using both Guice and Spring and dependency injection which is > not a ideal combination. As Atlas evolves as a product we can leverage the > spring framework to avoid re-inventing the wheel like caching, transaction > management etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring
[ https://issues.apache.org/jira/browse/ATLAS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated ATLAS-1198: --- Description: Right now we're using both Guice and Spring and dependency injection which is not a ideal combination. As Atlas evolves as a product we can leverage the spring framework to avoid re-inventing the wheel like caching, transaction management etc. (was: Right now we're using both Guice and Spring and dependency injection which is not a ideal combination. As Atlas evolves as a product we can leverage the spring framework to re-invent the wheel like caching, transaction management etc.) > Move from Guice + Spring to only Spring > --- > > Key: ATLAS-1198 > URL: https://issues.apache.org/jira/browse/ATLAS-1198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Apoorv Naik > > Right now we're using both Guice and Spring and dependency injection which is > not a ideal combination. As Atlas evolves as a product we can leverage the > spring framework to avoid re-inventing the wheel like caching, transaction > management etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
