[jboss-dev-forums] [Embedded JBoss Development] - Re: ShrinkWrap Export to File

jaikiran do-not-reply at jboss.com
Mon Oct 19 15:37:10 EDT 2009


"ALRubinger" wrote : 
  | Also, the TMPDPL (temporary name) project in JIRA handles this abstractly, so for instance Archives may be deployed directly:
  | 
  | ...
  | 

The usecases where i think this functionality of exporting to files is going to be useful, is when ShrinkWrap starts getting used as a tool to dynamically generate archives, replacing the current approach of the jars/archives being built statically through the ant build files (or other tools). So if a project was doing this:

1) Build static jars (Ant scripts) as a separate step
2) Run tests which expect the archives/artifacts to be available on the file system

With the use of ShrinkWrap, the #1 could be completely gone and #2 would assemble the archive dynamically. And if there was an API which could export this dynamically generated archive to the file system, then the rest of the tests could continue to work without having to change to work against ShrinkWrap "Archives". Well, the clients could themselves write a simple util (which really is nothing more than a few lines) which writes out to the filesystem once the Archive is assembled, but i guess almost all clients would at some point of time require such functionality :-) 

I guess i am thinking outside the lines of the Archive being used for deploying to some server. In the context of ShrinkWrap being used to create Archives for deploying to the server, the links that you pointed to, are better alternatives.    

"ALRubinger" wrote : 
  | Yep. My feeling at the time (and may still be) was "everything in its place", and flushing the contents of an InputStream to a File (or any other resource) is a generic IO function better suited elsewhere.

I see what you are saying. I haven't actually completely looked at the code/goals of ShrinkWrap, but isn't it already doing some of the IO related stuff? I might be wrong though :-) And yes, i do agree that it's a matter of finding the right place for this API. 



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

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



More information about the jboss-dev-forums mailing list