[JBoss Messaging] - Re: JBoss Messaging 1.2 and JBoss AS 4.2.2
by ikarius
Very good question, complicated aswer:
I've already used JBM 1.4.0 with success, my problem is that i've got 2 version of JBoss that must share JMS communication:
- "client" JBoss AS 4.0.4 GA, with consumers MDB beans connected to a remote JMS provider ..
- ... remote JMS provider installed on a 4.2.2GA JBoss AS.
JBM 1.4.0 works flawlessly with AS 4.2.2 on both sides, but i think it is not intended to work with JBoss AS 4.0.x version, am i right ?
To make it simple:
- 4.0.4 AS version on "MDB side" is mandatory for warranty and compatibility purposes (ILOG/JRules must run on a 4.0.4 GA to enable support :( )
- a 4.2.x (and later 5.x) must be present on the other side to run the remote JMS provider (EJB3 dev coming)
What version of JBM must i use to achieve that ? JBM v1.2 seemed a good concurent, but now i doubt it ...
I was wondering if there is any compatibility matrix for JBoss AS and JBM versions ?
And thank you for your response.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103168#4103168
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103168
18 years, 7 months
[JBoss Seam] - Extinding Seam Built-in components and the "plugin architect
by Daoud
Hello;
First, Congrats for the the new release! Great Job Folks!
Well, am in the early stage of a new project, having identified some requirements, I do believe Seam will fit in there like magic. Other requirements are integration with an ESB, at the moment am lil bit familiar with openesb and servermix, I'll have a look at JBossESB, other requirement is some BI stuff in the application.
I think it would be great if i furnish those functionalities as Seam Built-in components to my team. That would be a great commodity to free them from infrastructure coding and focus on business value of the application in the same Seam spirit.
Here are the questions:
1- Is extending Seam Built-in component the *better* way to go?
2- What qualifies a component to become a -Built-In or available by default- (think of the static instance() method) one?
3- Is @Install annotation relevant to my thoughts?
4- Is there any guide/docs/examples to extending Seam (that would profit Seam if users start contributing components)
Finally Gavin in his InfoQ interview talked about some plugin architecture developed for the Seam wiki. Can anyone write some docs about this architecture and how to implement it in a Seam Application?
Best Regards
Daoud AbdelMonem Faleh
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103167#4103167
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103167
18 years, 7 months
[JBoss Seam] - ManagedPersistenceContext in Manning JPA book
by asookazian
The last chapter on Seam in the JPA with Hibernate book was very informative. I stumbled upon the section on triggering a LazyInitializationException when trying to root-cause analyze a colleague's LazyInitializationException problem.
So it turns out that you can fix this problem by extending the persistence context as follows in your SFSB:
@PersistenceContext(type=EXTENDED)
| private EntityManager em;
When I search for keyword "ManagedPersistenceContext" in all of the Seam example apps in the CR2 distro, I got no hits. Does that mean it's not necessary to use the Seam managed context and the TransactionalSeamPhaseListener to solve LazyInitializationException's?
When do you need to integrate the Seam-managed persistence context as explained in pages 814-815 of the book? I guess I'm not understanding exactly the added value of using the Seam-managed persistence context versus javax.persistence.PersistenceContext.
I see more methods in the API for the Seam-managed persistence context class...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103161#4103161
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103161
18 years, 7 months