[JBoss Messaging] - Spring JNDI lookup using proxyInterface fails
by nkhadakk
I am attempting to use Spring(2.0.6) JMSTemplate with JBoss Messaging (1.3). Spring JNDI lookups can defer actual 'connection' to the first time the object is to be used...For this to be possible we need to supply a 'proxyInterface' like so :
<bean id="URIQueue"
| class="org.springframework.jndi.JndiObjectFactoryBean">
| <property name="jndiTemplate">
| <ref bean="jndiTemplate"/>
| </property>
| <property name="jndiName">
| <value>/queue/UniversalResourceProcessingQueue</value>
| </property>
| <property name="lookupOnStartup">
| <value>false</value>
| </property>
| <property name="proxyInterface">
| <value>javax.jms.Queue</value>
| </property>
| <property name="cache">
| <value>true</value>
| </property>
| </bean>
This causes the following exception to be thrown from jboss code.
Caused by: javax.jms.InvalidDestinationException: Not a JBossDestination:JBossQueue[UniversalResourceProcessingQueue]
at org.jboss.jms.client.JBossSession.createProducer(JBossSession.java:206)
at org.springframework.jms.core.JmsTemplate.doCreateProducer(JmsTemplate.java:846)
at org.springframework.jms.core.JmsTemplate.createProducer(JmsTemplate.java:827)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:505)
This error occurs due to using 'javax.jms.Queue' as the interface causing the Proxy created to implement Queue and hence failing the instanceOf JBossDestination test in JBossSession.
If we had a JBossDestination interface available we could use this interface to create a proxy.
Does the messaging team have any plan of refactoring this particular code to use an Interface based implementation ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072118#4072118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072118
18Â years, 9Â months
[JBoss Seam] - entity's lifecycle and jBPM
by vladimir.kovalyuk
The question is "Can Seam+jBPM help with implementing entity's lifecycle?"
Let's consider Document as an example of entity that has lifecycle. The states are as follows: Draft, Pending Verification, Pending Approval, Archived.
>From my perspective lifecycle is a graph with states and actions (transitions).
Instance of entity is always in some state, beginning from start-state and ending with end-state. Any action promotes the instance to the next state.
It seems that jBPM provides us with all means we need to implement lifecycle.
(I saw definition where lifecycle was a reduced graph where states were on the line. jBPM can handle this case as well)
My current understanding is as follows:
1. Entity has field lifecycleId, it is essentially the id of process instance.
2. Entity should keep current lifecycle state (for instance as a name of node).
3. Action should signal the process and eventually entity's lifecycle state should be changed.
>From the UI perspective we're on the page where entity details are shown.
There are lifecycle state and possible actions (as outgoing transitions from the state). When user clicks the link with an action the process instance is loaded and signal is sent.
How could Seam handle such a scenario?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072114#4072114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072114
18Â years, 9Â months