[JBoss JIRA] (FORGE-779) Class parameters are not correctly loaded for the consuming addon's classloader
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-779?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-779:
----------------------------------
Fix Version/s: 2.0.0.Alpha5
(was: 2.0.0.Alpha4)
> Class parameters are not correctly loaded for the consuming addon's classloader
> -------------------------------------------------------------------------------
>
> Key: FORGE-779
> URL: https://issues.jboss.org/browse/FORGE-779
> Project: Forge
> Issue Type: Bug
> Reporter: George Gastaldi
> Assignee: Lincoln Baxter III
> Priority: Critical
> Fix For: 2.0.0.Alpha5
>
>
> Having the following scenario:
> Eclipse plugin -> calls ConverterFactory -> passes Resource.class as a parameter
> {code:java}
> ConverterFactory.getConverter(File.class, Resource.class)
> {code}
> in ResourceConverterGenerator (resources addon):
> {code:java}
> @Override
> public boolean handles(Class<?> source, Class<?> target)
> {
> return Resource.class.isAssignableFrom(target);
> }
> {code}
> Returns false, because the classloader that loaded the Resource class is the Eclipse classloader, not the Resource addon classloader AND Resource.class is not visible in the convert addon.
--
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
12 years, 10 months
[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-770:
----------------------------------
Fix Version/s: 2.0.0.Alpha5
(was: 2.0.0.Alpha4)
> 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
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Alpha5
>
>
> 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
12 years, 10 months