Darn, for some reason this got saved as a draft and never sent... sorry.<br><br>There is already a seam-render module in Forge, and the duplicated classloader resources is something that Weld should be able to understand because classes from different classloaders are different classes. <br>
<br>This appears to be a bug in weld.<br>
<br>What happens when you add a module dependency on: "org.jboss.seam.render" ? If it works, I can fix this as a workaround in forge for now, but it's not the right solution in the long run, and we'll have to get weld fixed up. I'm working on creating a custom WeldBootstrap application that adds each plugin as a deployablearchive, but that's going to take some time unless I can get help from the weld guys.<br>
<br>Pete, Ales, Josef - any tips on how to get this to work?<br><br><a href="https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/forge/shell/ModularWeld.java">https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/forge/shell/ModularWeld.java</a><br>
<br>~Lincoln<br><br><div class="gmail_quote">On Tue, Nov 29, 2011 at 10:50 PM, Marius Bogoevici <span dir="ltr"><<a href="mailto:mariusb@redhat.com" target="_blank">mariusb@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
The problem can be made to go away by adding a dependency on<br>
'org.jboss.forge' in the plugin module (since this is where seam-render.<br>
That would be, however, a wrong thing to do, since it breaks modularity<br>
big time. On the other hand, adding seam-render to the module itself<br>
causes other types of class loader errors (due to the duplication).<br>
<br>
IMO the right way to deal with this would be to split out a separate<br>
'seam-render' (or otherwise aptly named) module, that plugins can depend<br>
on (after all, it is conceivable that template-based code generation is<br>
a wider used pattern, and third party plugins will want to get access to<br>
Forge's template-based generation facilities - perhaps just at the API<br>
level).<br>
<br>
Thoughts?<br>
<div><div><br>
On 11-11-28 10:54 AM, Ryan Bradley wrote:<br>
> Hi all,<br>
><br>
> I am trying to use seam-render in my plugin, for classes such as<br>
> TemplateCompiler. However, when I include it in the project and try to<br>
> build the plugin in Forge, I get a strange ResourceLoadingException<br>
> which suggests that the class is not being found. Can anyone shed some<br>
> light on this problem?<br>
><br>
> Thanks,<br>
> Ryan<br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br><a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
"Keep it Simple"<br>