[forge-dev] JBoss modules doesn't load CORBA (lol)

[George Gastaldi]

Fixed. Try it with 2.2.1-SNAPSHOT.

Thanks for reporting this! Hope your CORBA code works now in your Forge 
addons! :)

On 17-03-2014 13:34, Ivan St. Ivanov wrote:
> God knows, it's thousands lines of code, owned by other teams :)
>
> I created this JIRA:
> https://issues.jboss.org/browse/FORGE-1675
>
>
>
> On Mon, Mar 17, 2014 at 6:32 PM, George Gastaldi <ggastald at redhat.com 
> <mailto:ggastald at redhat.com>> wrote:
>
>     Lincoln is working in an extension to manage these different
>     paths. For the meantime, we'll add the required packages as a
>     ModuleSpec in Furnace.
>     Do you have any other package besides javax.rmi.CORBA that is also
>     used?
>
>
>     On 17-03-2014 13:29, Ivan St. Ivanov wrote:
>>     We had the same issue with Forge 1 (without Furnace). Do you
>>     think how we can re-configure that in Furnace?
>>
>>
>>     On Mon, Mar 17, 2014 at 6:26 PM, George Gastaldi
>>     <ggastald at redhat.com <mailto:ggastald at redhat.com>> wrote:
>>
>>         Only if you want to We have the
>>         test.org.jboss.forge.furnace.classpath.XPathLookupTest that
>>         is quite similar ;)
>>
>>
>>         On 17-03-2014 13:25, Ivan St. Ivanov wrote:
>>>         Thanks! I hope I don't have to write a test case for it? ;)
>>>
>>>
>>>         On Mon, Mar 17, 2014 at 6:22 PM, George Gastaldi
>>>         <ggastald at redhat.com <mailto:ggastald at redhat.com>> wrote:
>>>
>>>             This is easy to fix. Please open a JIRA and we'll make
>>>             that work for you :)
>>>
>>>             Thanks!
>>>
>>>             On 17-03-2014 13:15, Ivan St. Ivanov wrote:
>>>>             Hi folks,
>>>>
>>>>             This is more a JBoss Modules question, but I decided to
>>>>             start here first ;)
>>>>
>>>>             A colleague of mine is writing a Forge 1 plugin that
>>>>             uses SAP's APIs to deploy ear files to the NetWeaver
>>>>             server. And he gets a weird ClassNotFoundException for
>>>>             the class javax.rmi.CORBA.Tie. It is used by our APIs
>>>>             for performing remote connections.
>>>>
>>>>             We rewrote his plugin to Forge 2 addon and we got the
>>>>             same exception again. Here is the JBoss Modules
>>>>             specific part of the exception trace, although I don't
>>>>             think it is quite useful:
>>>>
>>>>             Caused by: java.lang.ClassNotFoundException:
>>>>             javax.rmi.CORBA.Tie from [Module
>>>>             "com.sap.nw.deploy.forge.nwdeploy:1.0.0-SNAPSHOT_d5a54a79-5d83-4f31-bc98-1d6384c4df1c"
>>>>             from AddonModuleLoader]
>>>>             at
>>>>             org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
>>>>             at
>>>>             org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
>>>>             at
>>>>             org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
>>>>             at
>>>>             org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
>>>>             at
>>>>             org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
>>>>             ... 83 more
>>>>
>>>>
>>>>             I de-compiled the SAP code that blows up and at the row
>>>>             where the exception is thrown, I see the following:
>>>>
>>>>             this.out = new MarshalOutputStream(new
>>>>             ByteArrayOutput(this.offset));
>>>>
>>>>             The MarshalOutputStream class is from SAP APIs as well
>>>>             and it has in its imports javax.rmi.CORBA.Tie.
>>>>
>>>>             Can you think of a reason why JBoss Modules would have
>>>>             a problem loading a class that is part of the standard JDK?
>>>>
>>>>             Thanks,
>>>>             Ivan
>>>>
>>>>
>>>>             _______________________________________________
>>>>             forge-dev mailing list
>>>>             forge-dev at lists.jboss.org  <mailto:forge-dev at lists.jboss.org>
>>>>             https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>>
>>>             _______________________________________________
>>>             forge-dev mailing list
>>>             forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>>>             https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         forge-dev mailing list
>>>         forge-dev at lists.jboss.org  <mailto:forge-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>>         _______________________________________________
>>         forge-dev mailing list
>>         forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>>
>>
>>     _______________________________________________
>>     forge-dev mailing list
>>     forge-dev at lists.jboss.org  <mailto:forge-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>     _______________________________________________
>     forge-dev mailing list
>     forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140317/1b30d79c/attachment.html