<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11-12-12 5:34 PM, Lincoln Baxter, III wrote:
<blockquote
cite="mid:CAEp_U4EXnG5Q+TwOFiRR6-m8tEUXou_-r3hNWmc+mEVo-RV-Zw@mail.gmail.com"
type="cite">Darn, for some reason this got saved as a draft and
never sent... sorry.<br>
<br>
</blockquote>
NP, you just saved me a ping :)<br>
<blockquote
cite="mid:CAEp_U4EXnG5Q+TwOFiRR6-m8tEUXou_-r3hNWmc+mEVo-RV-Zw@mail.gmail.com"
type="cite">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>
</blockquote>
Ok, thanks for the update. I can see it in the snapshot build. I or
Ryan will try this tomorrow.<br>
<blockquote
cite="mid:CAEp_U4EXnG5Q+TwOFiRR6-m8tEUXou_-r3hNWmc+mEVo-RV-Zw@mail.gmail.com"
type="cite">This appears to be a bug in weld.<br>
</blockquote>
<blockquote
cite="mid:CAEp_U4EXnG5Q+TwOFiRR6-m8tEUXou_-r3hNWmc+mEVo-RV-Zw@mail.gmail.com"
type="cite">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>
</blockquote>
In what sense is this not the right solution? As a standalone plugin
developer, I don't think that I should be *expected* to package a
version of seam-render inside my plugin. It would be much easier for
plugin writers if they could rely on accessing certain modules (in
the same sense as plugins which are packaged with forge can use
them).<br>
<br>
Of course, I should be *allowed* to use my own version of
seam-render, which is a different thing, but one particular problem
right now is that seam-render itself depends on Solder and other
libraries. That wouldn't be a problem in itself, but IIRC one of the
issues of packaging Solder was that extension loading became
completely messed up - I would need to try that again to remember
what exactly was the cause, but classloader issues were definitely
involved. In the long run, this needs to be be solved as well, I
agree.<br>
<blockquote
cite="mid:CAEp_U4EXnG5Q+TwOFiRR6-m8tEUXou_-r3hNWmc+mEVo-RV-Zw@mail.gmail.com"
type="cite">
<br>
Pete, Ales, Josef - any tips on how to get this to work?<br>
<br>
<a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
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 moz-do-not-send="true" href="http://ocpsoft.com"
target="_blank">http://ocpsoft.com</a><br>
<a moz-do-not-send="true" href="http://scrumshark.com"
target="_blank">http://scrumshark.com</a><br>
"Keep it Simple"<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
forge-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>