[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-770:
-------------------------------------
Fix Version/s: 2.0.0.Alpha2
(was: 2.0.0.Alpha1)
> Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version
> -------------------------------------------------------------------------------------------
>
> Key: FORGE-770
> URL: https://issues.jboss.org/browse/FORGE-770
> Project: Forge
> Issue Type: Story
> Components: Container
> Affects Versions: 2.0.0.Alpha1
> Reporter: Lincoln Baxter III
> Fix For: 2.0.0.Alpha2
>
>
> Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.)
> {code}
> (A) -> (B, v1)
> -> Service 1
> (B, v2)
> -> Service 1v2
> -> Service 2v1
> {code}
> A should receive only the instance of Service 1 from (B, v1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (FORGE-688) Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-688?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-688:
-------------------------------------
Fix Version/s: 2.0.0.Alpha2
(was: 2.0.0.Alpha1)
> Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet
> -----------------------------------------------------------------------
>
> Key: FORGE-688
> URL: https://issues.jboss.org/browse/FORGE-688
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 1.1.0.Final
> Reporter: George Gastaldi
> Priority: Minor
> Fix For: 2.0.0.Alpha2
>
>
> It would be nice if we have a JavaEE6Facet, which installs the jboss bom.
> Even though the BaseJavaEEFacet abstract class already does that, this behavior would not be possible if a custom Facet is created extending a specific subclass of BaseFacet and requiring the JavaEE6.
> The more elegant solution would be to add:
> {code:java}
> @RequiresFacet(JavaEE6Facet.class)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (FORGE-801) Support for Transactional Resources
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-801?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-801:
-------------------------------------
Fix Version/s: 2.0.0.Alpha2
(was: 2.0.0.Alpha1)
> Support for Transactional Resources
> ------------------------------------
>
> Key: FORGE-801
> URL: https://issues.jboss.org/browse/FORGE-801
> Project: Forge
> Issue Type: Feature Request
> Components: Resources API
> Affects Versions: 1.2.1.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.0.Alpha2
>
> Attachments: IMG_20130225_215814.jpg, UserGuide_TXFileInJava_v1.0.pdf
>
>
> FileResources should be transactional, that is, allow modification of resources for displaying purposes and allow commit or rollback of changes.
> The implementation could copy the modified file to a temporary folder and when commit is invoked, copy back the contents to the original folder.
> It may be necessary to provide a pointer back to the original file (Properties file next to changed file maybe?).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months