Re: Failover Service

My original patch does use WebBeanConfigurationLister, but that requires 2 attributes to be set on a sessionContext, one is WebBeanConfigurationLister itself which will receive HttpSessionActivationListener callbacks, the problem is that it could not hold any session specific data for serialization

actualResourceReference in ResourceBean should be a local variable in createInstance method?

Does anyone know why we use the normal field variable to store the actual resource reference in ResourceBean? Considering 2 threads try to create resource bean instance at same time, there is a chance that 2 threads access the same actual reference in ResourceBean.createInstance() method. thanks i

Re: actualResourceReference in ResourceBean should be a local variable in createInstance method?

variable of the method instead of a variable of ResourceBean. On Wed, Oct 27, 2010 at 10:34 AM, Gurkan Erdogdu wrote: > ResourceBeans are dependent, so every reference gets new bean instance. > > > Could you give some example? > > > > - Original Message >

Re: svn commit: r1057407 - in /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans: component/BuildInOwbBean.java proxy/JavassistProxyFactory.java

Thanks David, I did not notice the recent changes around static variables. Your fix should be ok since we only have 4 build-in beans. On Mon, Jan 10, 2011 at 9:58 PM, David Jencks wrote: > This didn't compile, which I fixed in rev 1057448. However there's a > design problem in that the proxy ch

[jira] Created: (OWB-241) Conversation scoped bean instance gets destroyed for every ELResolver.getValue

Issue Type: Bug Components: Core Affects Versions: 1.0.0 Environment: windows Reporter: YING WANG Assignee: Gurkan Erdogdu Fix For: 1.0.0 1. I am testing @disposes for conversation scoped bean and found my disposes method get invoked

[jira] Created: (OWB-244) OWB injects a new object for @disposes injection point for dependent scope

Issue Type: Bug Components: Context and Scopes Affects Versions: 1.0.0 Environment: windows Reporter: YING WANG Assignee: Gurkan Erdogdu Fix For: 1.0.0 1. I am testing @disposes for dependent scope for the following bean. However, the

[jira] Commented: (OWB-244) OWB injects a new object for @disposes injection point for dependent scope

[ https://issues.apache.org/jira/browse/OWB-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806623#action_12806623 ] YING WANG commented on OWB-244: --- Sorry for the delay. I tested the recent r901845, the sym

[jira] Updated: (OWB-244) OWB injects a new object for @disposes injection point for dependent scope

[ https://issues.apache.org/jira/browse/OWB-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-244: -- Attachment: dispose2.jar test code for dependent and request scope @disposes > OWB injects a new object

[jira] Created: (OWB-273) Given class is not annotated with @Alternative Exception when try to enable alternative producer/producer field beans

://issues.apache.org/jira/browse/OWB-273 Project: OpenWebBeans Issue Type: Bug Components: Injection and Lookup Affects Versions: M3 Reporter: YING WANG Assignee: Gurkan Erdogdu Priority: Minor I have an alternative producer

[jira] Commented: (OWB-273) Given class is not annotated with @Alternative Exception when try to enable alternative producer/producer field beans

[ https://issues.apache.org/jira/browse/OWB-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831508#action_12831508 ] YING WANG commented on OWB-273: --- hmm. I am thinking, if a class itself is annotated

[jira] Updated: (OWB-273) Given class is not annotated with @Alternative Exception when try to enable alternative producer/producer field beans

[ https://issues.apache.org/jira/browse/OWB-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-273: -- Attachment: alternative2.jar test cases around alternative/producer/disposes. > Given class is not annota

[jira] Commented: (OWB-273) Given class is not annotated with @Alternative Exception when try to enable alternative producer/producer field beans

[ https://issues.apache.org/jira/browse/OWB-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832062#action_12832062 ] YING WANG commented on OWB-273: --- Thanks a lot, Gurkan. So the only way to enable an alterna

[jira] Created: (OWB-279) Indirect specialization (4.3.1) throws InconsistentSpecializationException

Issue Type: Bug Components: Injection and Lookup Affects Versions: M3 Reporter: YING WANG Assignee: Gurkan Erdogdu I have a list of specializes/extends beans (Car <- CarToyota <- CarToyotaCamry <- CarToyotaCamryHybird). However the te

[jira] Updated: (OWB-279) Indirect specialization (4.3.1) throws InconsistentSpecializationException

[ https://issues.apache.org/jira/browse/OWB-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-279: -- Attachment: specialize2.jar Still not working even with my patch, bean size is 0 for some reason. debugging

[jira] Updated: (OWB-279) Indirect specialization (4.3.1) throws InconsistentSpecializationException

[ https://issues.apache.org/jira/browse/OWB-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-279: -- Attachment: owb299-patch.jar Please help review the patch. I modified configureSpecializations a little bit to

[jira] Updated: (OWB-279) Indirect specialization (4.3.1) throws InconsistentSpecializationException

[ https://issues.apache.org/jira/browse/OWB-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-279: -- Attachment: owb279.svn.patch svn patch against the latest r910649. > Indirect specialization (4.3.1) thr

[jira] Created: (OWB-284) OWB could not find default bean if alternative specialized bean is not enabled.

Issue Type: Bug Components: Injection and Lookup Affects Versions: M3 Reporter: YING WANG Assignee: Gurkan Erdogdu I have 2 managed beans: @QualifierSpecialized Bus @Alternative @Specializes public class SchoolBus extends Bus owb works fine when

[jira] Updated: (OWB-284) OWB could not find default bean if alternative specialized bean is not enabled.

[ https://issues.apache.org/jira/browse/OWB-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-284: -- Attachment: owb284testcase.jar test case for 284. > OWB could not find default bean if alternative speciali

[jira] Commented: (OWB-284) OWB could not find default bean if alternative specialized bean is not enabled.

[ https://issues.apache.org/jira/browse/OWB-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834492#action_12834492 ] YING WANG commented on OWB-284: --- Gurkan, I will try to combine both, might take me some tim

[jira] Updated: (OWB-284) OWB could not find default bean if alternative specialized bean is not enabled.

[ https://issues.apache.org/jira/browse/OWB-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-284: -- Attachment: owb284.patch please review the patch(r911238) for 284, 279. Thanks. > OWB could not find defa

[jira] Created: (OWB-289) Owb return 2 beans for Indirect specialized producer beans

: Injection and Lookup Affects Versions: M3 Reporter: YING WANG Assignee: Gurkan Erdogdu Priority: Minor The problem might be similar to 279 managed bean bug. I have "@QualifierSpecialized IPen" bean being generated by 3 producers: DefaultP

[jira] Updated: (OWB-289) Owb return 2 beans for Indirect specialized producer beans

[ https://issues.apache.org/jira/browse/OWB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-289: -- Attachment: owb289.test.jar owb289.patch I think the bug might be mis-closed. Please review the

[jira] Reopened: (OWB-289) Owb return 2 beans for Indirect specialized producer beans

[ https://issues.apache.org/jira/browse/OWB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reopened OWB-289: --- Reopen it, so the patch could be integrated. > Owb return 2 beans for Indirect specialized producer be

[jira] Created: (OWB-308) minor clean up on specialization code path

Affects Versions: M3 Reporter: YING WANG Assignee: Gurkan Erdogdu Priority: Minor Ran some tests on recent driver and found a few Exceptions fired due to multiple invocation of bean.setBeanName( ) when configure specialization. Changes in this patch include: 1

[jira] Updated: (OWB-308) minor clean up on specialization code path

[ https://issues.apache.org/jira/browse/OWB-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-308: -- Attachment: 308.patch upload patch. > minor clean up on specialization code p

[jira] Commented: (OWB-289) Owb return 2 beans for Indirect specialized producer beans

[ https://issues.apache.org/jira/browse/OWB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839821#action_12839821 ] YING WANG commented on OWB-289: --- Thanks Mark, are the 2 methods shares the same

[jira] Commented: (OWB-289) Owb return 2 beans for Indirect specialized producer beans

[ https://issues.apache.org/jira/browse/OWB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839861#action_12839861 ] YING WANG commented on OWB-289: --- I would presume the exact being-extended method in the s

[jira] Created: (OWB-321) Conversation beans could not be populated to non-faces request by a JSF redirect navigation rule

Project: OpenWebBeans Issue Type: Bug Components: Injection and Lookup Affects Versions: M4 Reporter: YING WANG Assignee: Gurkan Erdogdu I have the following JSF redirect navigation rule, which redirect a JSF page to a jsp page

[jira] Commented: (OWB-321) Conversation beans could not be populated to non-faces request by a JSF redirect navigation rule

[ https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843741#action_12843741 ] YING WANG commented on OWB-321: --- Thanks Sven for the info, I tested again, the reirect

[jira] Updated: (OWB-321) Conversation beans could not be populated to non-faces request by a JSF redirect navigation rule

[ https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-321: -- Attachment: owb321.patch Could someone help review my change? Thanks in advance. > Conversation beans could

[jira] Commented: (OWB-321) Conversation beans could not be populated to non-faces request by a JSF redirect navigation rule

[ https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844204#action_12844204 ] YING WANG commented on OWB-321: --- Thanks a lot Gurkan for clarifying. I must be tooo focu

[jira] Commented: (OWB-321) Conversation beans could not be populated to non-faces request by a JSF redirect navigation rule

[ https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844217#action_12844217 ] YING WANG commented on OWB-321: --- Ok, sounds good. I will keep this open. > Conversatio

[jira] Created: (OWB-334) cid is missing when using redirect for a jsf 2.0 application

Components: Java EE Integration Affects Versions: M4 Reporter: YING WANG Assignee: YING WANG Priority: Minor I have converted conversation-sample to a jsf 2 .0 application by changing jsf version to 2.0 and disabling FaceletViewHandler. When I click "To Li

[jira] Resolved: (OWB-334) cid is missing when using redirect for a jsf 2.0 application

[ https://issues.apache.org/jira/browse/OWB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG resolved OWB-334. --- Resolution: Fixed Fix Version/s: 1.0.0 > cid is missing when using redirect for a jsf 2.0 applicat

[jira] Closed: (OWB-334) cid is missing when using redirect for a jsf 2.0 application

[ https://issues.apache.org/jira/browse/OWB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-334. - > cid is missing when using redirect for a jsf 2.0 applicat

[jira] Assigned: (OWB-310) Drop dom4j and use jre builtin xml parsers for processing beans.xml

[ https://issues.apache.org/jira/browse/OWB-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reassigned OWB-310: - Assignee: YING WANG (was: Gurkan Erdogdu) Assign to Ying. > Drop dom4j and use jre builtin xml pars

[jira] Resolved: (OWB-310) Drop dom4j and use jre builtin xml parsers for processing beans.xml

[ https://issues.apache.org/jira/browse/OWB-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG resolved OWB-310. --- Resolution: Fixed > Drop dom4j and use jre builtin xml parsers for processing beans.

[jira] Assigned: (OWB-312) Add dopriv's to allow OWB to function with java 2 security enabled

[ https://issues.apache.org/jira/browse/OWB-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reassigned OWB-312: - Assignee: YING WANG (was: Gurkan Erdogdu) > Add dopriv's to allow OWB to function with java 2

[jira] Commented: (OWB-312) Add dopriv's to allow OWB to function with java 2 security enabled

[ https://issues.apache.org/jira/browse/OWB-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858614#action_12858614 ] YING WANG commented on OWB-312: --- To avoid this annoying "Access denied" Excepti

[jira] Commented: (OWB-363) Intermittent bug with ApplicationScope disposers not being called

[ https://issues.apache.org/jira/browse/OWB-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861834#action_12861834 ] YING WANG commented on OWB-363: --- Gurkan, Joe, I took a look on the latest change. It could

[jira] Created: (OWB-366) ContextNotActiveException fired from AppScope/NormalScopedBeanInterceptorHandler when a proxied object finalized

://issues.apache.org/jira/browse/OWB-366 Project: OpenWebBeans Issue Type: Bug Components: Interceptor and Decorators Affects Versions: M4 Reporter: YING WANG Assignee: YING WANG Priority: Minor Whenever a proxied object recycled by JVM

[jira] Closed: (OWB-366) ContextNotActiveException fired from AppScope/NormalScopedBeanInterceptorHandler when a proxied object finalized

[ https://issues.apache.org/jira/browse/OWB-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-366. - Fix Version/s: 1.0.0 Resolution: Fixed > ContextNotActiveException fired from > Ap

[jira] Created: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

/OWB-369 Project: OpenWebBeans Issue Type: Bug Affects Versions: M4 Reporter: YING WANG Assignee: YING WANG Fix For: 1.0.0 To reproduce, Application A, which does not support conversation, installed and tested without any issue. then

[jira] Updated: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

[ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-369: -- Attachment: ContextFactory.patch Thanks Gurkan, Joe. With Gurkan's recent changes, my second app still

[jira] Created: (OWB-370) Intransient Conversation context get rdestroyed randomly by destroyWithRespectToTimout

: OpenWebBeans Issue Type: Bug Components: Context and Scopes Affects Versions: M4 Reporter: YING WANG Assignee: YING WANG Priority: Minor Fix For: 1.0.0 Before we put conversation context into ConversationManager's hashma

[jira] Closed: (OWB-370) Intransient Conversation context get rdestroyed randomly by destroyWithRespectToTimout

[ https://issues.apache.org/jira/browse/OWB-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-370. - Resolution: Fixed > Intransient Conversation context get rdestroyed randomly by > destroyWithRespectTo

[jira] Reopened: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

[ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reopened OWB-369: --- Assignee: YING WANG (was: Gurkan Erdogdu) Still randomly see different conversationManagers invoked for same

[jira] Closed: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

[ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-369. - Resolution: Fixed > Static ContextsService in ContextFactory causes wrong webContextService used > for mu

[jira] Created: (OWB-394) Any idea why our BeforeBeanDiscovery.addInterceptorBinding() has different signature?

: OpenWebBeans Issue Type: TCK Challenge Components: TCK Affects Versions: 1.0.0-GA Reporter: YING WANG Assignee: Gurkan Erdogdu Fix For: 1.0.0-GA It seems we have a different signature for BeforeBeanDiscovery.addInterceptorBinding method

[jira] Created: (OWB-399) Proxy objects could not be correctly deserialized by using javassist 3.11. we need to update to 3.12

-399 Project: OpenWebBeans Issue Type: Improvement Components: Core Affects Versions: 1.0.0-CR1 Reporter: YING WANG Assignee: Gurkan Erdogdu Fix For: 1.0.0-CR2 While I am investigating owb failover / passivation support , I

[jira] Commented: (OWB-399) Proxy objects could not be correctly deserialized by using javassist 3.11. we need to update to 3.12

[ https://issues.apache.org/jira/browse/OWB-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880197#action_12880197 ] YING WANG commented on OWB-399: --- Thanks a lot , Mark. > Proxy objects could not be co

[jira] Assigned: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reassigned OWB-385: - Assignee: YING WANG (was: Gurkan Erdogdu) > implement passivation of managed beans

[jira] Commented: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893030#action_12893030 ] YING WANG commented on OWB-385: --- My plan is to first add basic failover/passivation support

[jira] Commented: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893188#action_12893188 ] YING WANG commented on OWB-385: --- 6.6.1 and 6.6.3 define the beans and scopes, including ses

[jira] Commented: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893213#action_12893213 ] YING WANG commented on OWB-385: --- The main target is to, at application level to config(en

[jira] Updated: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-385: -- Attachment: owb-385-1.patch Hi Guys, please review the changes under this bug. Basic failover /passivation

[jira] Updated: (OWB-385) implement passivation of managed beans in ServletContextListener

[ https://issues.apache.org/jira/browse/OWB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-385: -- Attachment: owb-385-2.patch Sorry, fogot checkstyle. the second patch fixed CS issues and 2 minor bugs in the

[jira] Created: (OWB-435) What is the expected result for following 2 decorators?

: Interceptor and Decorators Reporter: YING WANG Assignee: Gurkan Erdogdu Priority: Minor While I am testing 2 decorators decorate the same getName() method of UserBean, I found the result is: 1. "UserDecorator1(UserDecorator2(MYNAME)) " <

[jira] Commented: (OWB-435) What is the expected result for following 2 decorators?

[ https://issues.apache.org/jira/browse/OWB-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897944#action_12897944 ] YING WANG commented on OWB-435: --- I know we did not break the spec ;) But If I am a user

[jira] Commented: (OWB-435) What is the expected result for following 2 decorators?

[ https://issues.apache.org/jira/browse/OWB-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898037#action_12898037 ] YING WANG commented on OWB-435: --- Two more questions, 1. My UserBean is a session scope

[jira] Created: (OWB-448) More changes for decorator and interceptor passivation support

Components: Interceptor and Decorators Affects Versions: 1.0.0-alpha-2 Reporter: YING WANG Assignee: YING WANG Priority: Minor Fix For: 1.0.0-alpha-3 add some serialization/deserialization code for interceptor, decorator, and @EJB and

[jira] Created: (OWB-452) set active flag to false then context is destroyed

Scopes Affects Versions: 1.0.0-alpha-2 Reporter: YING WANG Assignee: Gurkan Erdogdu Priority: Minor Fix For: 1.0.0-alpha-3 We should clear AbstractContext.active flag when a context is destroyed. So it will not affect the next request/session run

[jira] Closed: (OWB-452) set active flag to false then context is destroyed

[ https://issues.apache.org/jira/browse/OWB-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-452. - Resolution: Fixed > set active flag to false then context is destro

[jira] Closed: (OWB-448) More changes for decorator and interceptor passivation support

[ https://issues.apache.org/jira/browse/OWB-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-448. - Resolution: Fixed There is a limitation that abstract decorator passivation still not works. It is because that we

[jira] Created: (OWB-508) Dependent scope proxies are needed to wrap the build-in beans returned from the services if they are not serializable yet

: https://issues.apache.org/jira/browse/OWB-508 Project: OpenWebBeans Issue Type: Improvement Affects Versions: 1.0.0 Reporter: YING WANG Assignee: YING WANG Priority: Minor Fix For: 1.1.0 the 4 build-in beans in section 3.6

[jira] Commented: (OWB-514) Leak in ELContextStore

[ https://issues.apache.org/jira/browse/OWB-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978849#action_12978849 ] YING WANG commented on OWB-514: --- Hi Gurkan, I have some troube to lo

[jira] Created: (OWB-522) Missing updateTimeout in one of begin methods for conversation

Components: Core Affects Versions: 1.0.0 Reporter: YING WANG Assignee: YING WANG Priority: Minor Fix For: 1.0.1 This could cause conversion being mis-deleted by timer thread. -- This message is automatically generated by JIRA. - For more

[jira] Resolved: (OWB-508) Dependent scope proxies are needed to wrap the build-in beans returned from the services if they are not serializable yet

[ https://issues.apache.org/jira/browse/OWB-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG resolved OWB-508. --- Resolution: Fixed > Dependent scope proxies are needed to wrap the build-in beans returned from > the se

[jira] Closed: (OWB-522) Missing updateTimeout in one of begin methods for conversation

[ https://issues.apache.org/jira/browse/OWB-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG closed OWB-522. - > Missing updateTimeout in one of begin methods for conversat

[jira] Resolved: (OWB-522) Missing updateTimeout in one of begin methods for conversation

[ https://issues.apache.org/jira/browse/OWB-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG resolved OWB-522. --- Resolution: Fixed Fix Version/s: 1.1.0 > Missing updateTimeout in one of begin methods for conversat