long conversations in rich client applications - orchestra

I was looking through some projects and came upon orchestra from apache as part of teh myfaces project. It provides a generic mechanism for conversations. It is geared towards web applications but the framework appears to be quite general, depending on spring scopes, and potentially can be used in rich client applications. I'll investigate and post back here to this blog.

I can report back that it all works for rich client applications. Even though it uses spring scopes (where one could just use annotations or conversation names), the framework works. For rich clients, you need a different configuration approach than listed in the myfaces documentation that composes the umbrella project of which orchestra is a subproject.

You need to do this once somewhere:


FrameworkAdapter.setCurrentInstance((FrameworkAdapter)getBean("orchestraFramework"));

Here, I have a method in the same class that has getBean() obtain a bean from the toplevel application context. In that toplevel context I have the following bean definitions:

<bean id="conversationLogger" class="org.apache.myfaces.orchestra.conversation.basic.LogConversationMessager"/>
<bean id="orchestraFramework" class="org.apache.myfaces.orchestra.frameworkAdapter.local.LocalFrameworkAdapter"
 p:conversationMessager-ref="conversationLogger" />

and I also include the following in my imported orchestra scopes xml configuration

<import resource="classpath*:/META-INF/spring-orchestra-init.xml" />
<bean
 class="org.springframework.beans.factory.config.CustomScopeConfigurer">  
<property name="scopes">
  <map>
<entry key="conversation.manual"><bean class="org.apache.myfaces.orchestra.conversation.spring.SpringConversationScope"></bean>

<bean class="org.apache.myfaces.orchestra.conversation.spring.SpringConversationScope"><property name="advices">


<entry key="conversation.anotherScopeRelatedToAView">
<bean class="org.apache.myfaces.orchestra.conversation.spring.SpringConversationScope"><property name="advices"><list></list></property> </entry>

<entry key="conversation.misc">
<bean class="org.apache.myfaces.orchestra.conversation.spring.SpringConversationScope">
     </bean></entry></entry></entry>
</map>
</property>

<bean id="persistentContextConversationInterceptor"
class="org.apache.myfaces.orchestra.conversation.spring.PersistenceContextConversationInterceptor">
 
</bean>


<bean id="persistentContextFactory"
 class="org.apache.myfaces.orchestra.hibernate.HibernatePersistenceContextFactory">
 <property name="entityManagerFactory" ref="defaultSessionFactory"></property></property>

That's about it. Now when you use an object whose bean definition has the scope defined as one of the scopes above, your object will have the same session object available on the thread for any method call in that class. Note that you need to watch your transaction boundaries so that the thread bound session has the correct transactional behavior you desire.

I know the formatting is completely messed up on the above configuration files. Hopefully, you can figure it out from what is posted here.

Comments

Post a Comment

Popular posts from this blog

quick note on scala.js, react hooks, monix, auth

quick note on scala.js, react hooks, monix, auth Reactjs hooks finally came out of preview in a recent version of React. scalajs-reaction has had support for hooks since they were in preview. React hooks seem like the hot new thing but for me the question is, do hooks help improve your code by improving maintainability, time to market, TCO, etc.? Let’s take a look using authentication as an example and employ monix , a reactive observable framework that also builds on cats . We will assume we are building a SPA. Does it improve your code and make your application & development experience better? Auth Auth processing can be complex. Many react auth examples you find in blogs like to show how to use “react-routing” and “auth” as a switch that determines which routes are protected or unprotected. Protected routes show application specific data. Unprotected routes show login content . Based on storing a “User” object in the browser session/local storage, th...
Read more

zio environment and modules pattern: zio, scala.js, react, query management

zio environment and modules pattern: zio, scala.js, react, query management This blog covers a zio-based fetch design for scala.js, react web applications. It heavily uses the zio “environment” feature to help motivate a point of view on the modules pattern in effect systems. At the end, I summarize some thoughts on ergonomics and complexity. This blog assumes a basic knowledge of zio and react. scala.js is just like scala so you mostly already know scala.js. This blog is a follow-on to previous blogs: https://appddeevvmeanderings.blogspot.com/2019/10/scalajs-react-fetcher-hook_48.html and https://appddeevvmeanderings.blogspot.com/2019/11/scalajs-and-react-suspense.html . I have been keeping an eye on and culling ideas from typscript/javascript fetching libraries that address query management concerns. The formulation below incorporates some of those concerns but does not try to comprehensively duplicate well established javascript libraries. I only care about ...
Read more

attributes with react and typescript.md

If you use typescript with react you may wonder what the right signature is for your “properties” interface. Obviously, your component will have few to many specific properties that reflect your domain. However, you may wish to also provide for the ability to add other attributes, such as those valid for a div property. In other words, you want to extend your props interface with that of the properties from a div element. How do you do that? There are really two issues: How do you extend your props interfaces How do you filter the props once you receive them to just those that apply. Extend Your Prop Interface or Use Sum Types It’s not uncommon to see interface Props { className ? : string yourProp ? : number } with the idea of using it in class MyComponent extends React.Component<Props, any> somewhere. If your component will have an outer div, you may also pass in a react element so that its configurable. But let’s say your outer element is a div and you wan...
Read more