[Microcontainer] - directly injecting a bean in a property
by bryan.kearney
Following the docs here:
http://www.jboss.org/file-access/default/members/jbossmc/freezone/docs/2....
I attempted to replace this xml:
| <bean name="Muppet" class="org.apache.qpid.agent.Muppet" />
|
| <bean name="Kermit" class="org.apache.qpid.agent.ManagedObject">
| <property name="name">Muppet</property>
| <property name="managed">
| <inject bean="Muppet" />
| </property>
| <property name="adapter">
| <inject bean="POJOAdapter" />
| </property>
| </bean>
|
with this:
| <bean name="Kermit" class="org.apache.qpid.agent.ManagedObject">
| <property name="name">Muppet</property>
| <property name="managed">
| <bean name="Muppet" class="org.apache.qpid.agent.Muppet" />
| </property>
| <property name="adapter">
| <inject bean="POJOAdapter" />
| </property>
| </bean>
|
But I get the following excption:
| Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'bean'. One of '{"urn:jboss:bean-deployer:2.0":value, "urn:jboss:bean-deployer:2.0":inject, "urn:jboss:bean-deployer:2.0":value-factory, "urn:jboss:bean-deployer:2.0":collection, "urn:jboss:bean-deployer:2.0":list, "urn:jboss:bean-deployer:2.0":set, "urn:jboss:bean-deployer:2.0":array, "urn:jboss:bean-deployer:2.0":map, "urn:jboss:bean-deployer:2.0":null, "urn:jboss:bean-deployer:2.0":this, WC[##other:"urn:jboss:bean-deployer:2.0"], "urn:jboss:bean-deployer:2.0":annotation}' is expected.
|
I scanned JIRA but did not see a bug. Is the documentation correct?
-- bk
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220780#4220780
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220780
17 years
[JBoss jBPM] - Re: Exception-Handler an Transitions
by bradsdavis
Ronald, maybe I am wrong, but it is talking about your Action within the <exception-handler> moving the exception to an arbitrary node. But before that, it states:
anonymous wrote :
| In the case of jBPM, control flow cannot be changed by the jBPM exception handling mechanism.
|
I guess its saying that in Java, you can have nested exceptions, and the thread execution will move to whatever point the exception is caught. In other words, JBPM does not move its token automatically to like a global exception handler... it just executes a script or action within a given exception handler. It is the responsibility of the action within the exception handler to actually move the process to another node.
anonymous wrote :
| No, it is clear (to me ;-))
|
What are you saying no about? Clearing it up?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220777#4220777
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220777
17 years