[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Changing the way AbstractVFSDeployment serializes root

[alesj]

"scott.stark at jboss.org" wrote : I suppose that is true regardless of how serialization is done.
  | 
"alesj" wrote : 
  | I think this is the right way to do it anyway.
  | 
  | If you would like to have full structure already present, I don't think you would gain much, since you would then 'pay' huge on transport, instead of at re-creation.
Thinking about it a bit more + hitting Memory VirtualFile issue,
this looks like wrong approach. :-(

Why?
e.g. having Memory VirtualFile, we know how to serialize it - 
passing info from server to client, since we transfer bytes that make
up that Memory VirtualFile, where in the case of root+path approach,
that won't work - client JVM doesn't know anything about it.

Hence, I'll revert my changes:
 - https://jira.jboss.org/jira/browse/JBDEPLOY-48
 - https://jira.jboss.org/jira/browse/JBDEPLOY-72

Although I saw Dimitris increased memory for smoke-tests,
I think we should properly fix how tests access server side deployments.

I believe there's already a JIRA issue about that,
assigned to Shelly if my memory serves me correctly?

But I can go ahead and fix it,
just need to know what I should use - ProfileService or DeploymentManager?
Or do we even have full API to port previous access code?

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

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