"alesj" wrote : "epbernard" wrote : EJB-326 is now fixed on HEM side.
| I don't know if this relates, but Hibernate Core/Ann/EM should make it pluggable to scan for resources w/o URLClassLoader awareness:
| - http://www.jboss.org/index.html?module=bb&op=viewtopic&t=127103&postdays=...
| Since, like stated in the post above, the new classloader is not URLCL.
I think it has been discussed previously in this thread. There are 2 problems:
- the spec ask for a URL, so URL it has to be to plug any JPA imnplementation
- writing an resource scan and context discovery is certainly possible but will require me a lot of work. Before we do that, I need a) time b) a proof that it will speed up things significantly
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120429#4120429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120429
"adrian(a)jboss.org" wrote : It current throws an IOE if you
| do findChild(), getChildren(), visit(), etc. on a leaf.
| We should probably keep for that for findChild (backwards compatibilty - null is not an
| expected return value) but return null, Collections.emptyList() or do a no-op visit
| in the other methods.
I've added a getChild to VFS and VirtualFile.
The current code has some duplicates.
I'll remove the findChild from spi parts, just leaving the findChild on the api.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120347#4120347
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120347
We need all 3 properties: partition, service name, singleton.
The singleton quite likely has no idea what it's "service name" is, which is what the HASingletonSupport that's controlling it uses to register it w/ DRM.
Without the service name the policy can't invoke most methods on the DRM if it needs to. It's the param that gets passed to a lot of DRM methods.
Re: docs, yes they are needed. When doing the 4.2 stuff I'd found JBAS-4919 so I made the docs a low priority until it was fixed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120260#4120260
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120260