[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: VFS3 - missing features and other issues

[david.lloyd@jboss.com]

"alesj" wrote : "david.lloyd at jboss.com" wrote : I think the quick/easy fix would be a mistake here.
  | I'm not looking for a quick&easy&dirty fix here.
  | I'm simply looking for an old API mapping to the new functionality.
  | 
  | How you glue those "assembled" or temp or what-ever-you-wanna-call-them resources,
  | I don't really care, all I need is the old API.
  | Which shouldn't be that difficult to support, or, 
  | if it is difficult, then there is something wrong with the new API.
  | 

The equivalent you want is probably "VFS.mountTemp()".

"alesj" wrote : 
  | The issue is if I don't have this old API present in VFS or some other top level project/artifact,
  | it means I have to re-write a lot of MC's tests, which is definitely something I don't wanna do or have time for.

Like Jason said - the first thing we're doing is porting over the VFS tests.  Once that's done we'll be looking at the greater integration question.  As we discussed in the meeting, if you don't want to do this work, you don't have to (Jason and I are the ones to whom the work was assigned) - but if you do, that's great as well.  In terms of the tests, if that's the only reason for the API, then just duplicate the API in the tests.  Tests are not a sufficient reason to keep an API around, no matter how inconvenient it is.

That said, if you want to use the mountTemp() API instead, that's even better.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246736#4246736

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246736