[forge-dev] POH5 runtime generation

[Lincoln Baxter, III]

Thomas, I believe you have a specific requirement that you need to access
MVEL classes directly. My recommendation would either to be use Velocity
(or another templating library) or avoid direct access to MVEL classes from
Seam Render templates for now. (Notice that you can use MVEL directly if
not coming from a Seam Render classloaded object.)

This is only a problem because of the way Weld does classloading - and the
fact that Seam Render is a CDI enabled project. Other libraries will work
fine.

~Lincoln

On Tue, Feb 28, 2012 at 6:08 PM, Thomas Frühbeck <fruehbeck at aon.at> wrote:

> I'm not absolutely sure, but it seems your are going to end up at the
> same point where I am now.
> See   http://lists.jboss.org/pipermail/forge-dev/201I'm pretty sure this
> works?2-February/001572.html<http://lists.jboss.org/pipermail/forge-dev/2012-February/001572.html>
>
> I took the code from the faces scaffold and wanted to extend it in a
> separate plugin.
> What I see is that the tests work fine but at runtime different
> classloader restrictions apply.
>
> I think Lincoln is right
> Am 27.02.2012 17:01, schrieb Lincoln Baxter, III:
> > Actually I think that perhaps the best solution is actuallly just to
> > expose MVEL as a dependency to plugins that request it. This would be
> > the simplest solution IMO, and would only request code-changes in the
> > Forge plugin installer:
>
> Perhaps it makes sense to get this fixed before "repairing" a working
> plugin?
>
> Thomas
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120228/9b00447b/attachment.html