"[EMAIL PROTECTED]" wrote :
| What about some kind of mechanism to allow users to combine descriptors
into a single file?
You can already do this.
It's called 'urn:jboss:bean-deployer:2.0'. ;-)
|
|
| ...
|
|
|
|
|
|
|
|
Cool, I didn't know that...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190217#4190217
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190217
___
jboss-user mailing list
jbo
So what's the programmatic equivalent of doing this? Say I've got a
BeanMetaDataFactory... can I return other MetaData types as well from that
somehow, using BeanMetaDataBuilder?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191414#4191414
Reply to the pos
Like what?
KernelDeployment only cares about BMDF.
What this BMDF actually is or what it does it's up to you.
At the end all BMDs from those BMDFs are installed into Controller.
BMDB only deals with BMD,
actually the current impl deals with AbstractBMD.
The idea is to have your custom MD, which
"alesj" wrote : The idea is to have your custom MD, which implements BMDF,
| where its getBeans method uses BMDB extensively.
|
The idea behind BMDB is to hide impl details of how BMD is to be
created/assembled.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
So you're saying that only custom MD that implements BMDF can be included in a
jboss-beans.xml deployment like you describe above?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191423#4191423
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=
Hmmm ... actually I'm not really sure what JBossXB will do
if some wildcard deployment's element maps to MD which doesn't implement BMDF.
I would expect it to throw a useful exception. :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191428#4191428
Reply to
"alesj" wrote : Hmmm ... actually I'm not really sure what JBossXB will do
| if some wildcard deployment's element maps to MD which doesn't implement
BMDF.
| I would expect it to throw a useful exception. :-)
I did a quick check, this is the result:
| java.lang.ClassCastException:
org.jbo
"alesj" wrote :
| JBossXB doesn't consider generics info --> see JBossXB's
CollectionPropertyHandler
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146116
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191435#4191435
Reply to the post :
http://w
OK, so the rule is that SchemaResolverDeployers must, must, MUST produce
metadata that implements BMDF. Affirmed once again. :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191448#4191448
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
"[EMAIL PROTECTED]" wrote : OK, so the rule is that SchemaResolverDeployers
must, must, MUST produce metadata that implements BMDF.
No. ;-)
The MD that maps to deployment's element must, must, MUST produce metadata
that implements BMDF.
e.g.
|
| // <-- HERE
| ...
|
|
11 matches
Mail list logo
