"emuckenhuber" wrote :
| Hmm inmemory deployment - so that you don't need to create a physical jar?
| Wouldn't that then be just another Profile implementation which actually creates
the deployments?
|
Yes, that is what I'm trying out. Right now I'm looking to see if I can just use
the existing ProfileMetaData with an vfsmemory://xxx url. I need a new ProfileFactory to
handle this, and support for multiple ProfileFactorys.
"emuckenhuber" wrote :
| I guess @Profile would be similar to the sub-profile in xml then - where you
basically
| just choose a required profile for the unit test?
|
Yes, I'll probably change that to @ProfileRef to avoid name clashes with the Profile
interface. The @Profiles are showing up as the subprofiles in the ProfileMetaData.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207448#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...