"bob.mcwhirter" wrote : | At this point, my web.xml is super-easy, and my code just programmatically assembles it. | Does this mean you're assembling WMD or web.xml? I guess WMD should do it. "bob.mcwhirter" wrote : | I also an building a ClassLoadingMetaData (well, a VFSClassLoaderFactory...), and have setOutput( ClassLoaderingMetaData.class ). I'm figuring (?) that's how I setup my effective classpath for the deployed web-app, and it's there I can jack in my paths to jruby.jar and friends. That sound about right? | Yup. It's the CL deployers that pick this up. Or you can hack something up, like I do it in my Seam-int. e.g. adding custom jar if deployment is Seam app "bob.mcwhirter" wrote : | For the scope of attachments... got a pointer for the differences? | Not really. :-) Basic point is that some attachments are available to client, some are just server side info, e.g. temp info passing around. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176185#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...