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

2010-06-17 Thread Mark Struberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/OWB-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg updated OWB-399:
--

Fix Version/s: 1.0.0-CR1
   (was: 1.0.0-CR2)
   Issue Type: Bug  (was: Improvement)
 Assignee: Mark Struberg  (was: Gurkan Erdogdu)
Affects Version/s: M4
   (was: 1.0.0-CR1)
 Priority: Blocker  (was: Major)

Hi ying!

That's exactly the reason why I fixed javassist ;) Itmt my patch got applied 
and Andrew Dinn and David Allen also fixed a lot other parts. I'm currently 
working on getting this new version of javassist to maven.central so we can use 
it for releasing CR1.

> Proxy objects could not be correctly deserialized by using javassist 3.11. we 
> need to update to 3.12
> 
>
> Key: OWB-399
> URL: https://issues.apache.org/jira/browse/OWB-399
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Core
>Affects Versions: M4
>Reporter: YING WANG
>Assignee: Mark Struberg
>Priority: Blocker
> Fix For: 1.0.0-CR1
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> While I am investigating owb failover / passivation support , I encountered 
> an issue that de-serialized proxy object could not delegate calls to bean 
> instance object methods. The handler field held by the proxy object ( such as 
> NormalScopeBeanInterceptorHandler we used for normal scope ) is replaced with 
> javassist default handler. 
> Sandbox tests show hat if I upgrade to javassist 3.12 and use 
> ProxyObjectInputStream/ProxyObjectOutputStream, the handler in de-serialized 
> proxy object get restored correctly.
> But 3.12 is not in jboss repository yet, anyone know if there is a way  to 
> push them update their javasssist repository? or create our own snapshot 
> repository temporarily? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (OWB-398) DelegateHandler cached too agressively

2010-06-17 Thread Eric Covener (JIRA)

 [ 
https://issues.apache.org/jira/browse/OWB-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Covener resolved OWB-398.
--

Fix Version/s: 1.0.0-CR1
   Resolution: Fixed

http://svn.apache.org/viewvc?rev=955801&view=rev (tagged with wrong JIRA id)

> DelegateHandler cached too agressively
> --
>
> Key: OWB-398
> URL: https://issues.apache.org/jira/browse/OWB-398
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Interceptor and Decorators
>Affects Versions: M4
>Reporter: Eric Covener
>Assignee: Eric Covener
> Fix For: 1.0.0-CR1
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> The InterceptorHandler and OpenWebbeansEJBinterceptor keep the interceptor 
> that hooks the decorator stack in the cached interceptor stack.
> This can lead to an incorrect delegate handler being used, and in the case of 
> an decorated EJB can cause the wrong EJB InvocationContext to be used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



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

2010-06-17 Thread YING WANG (JIRA)
Proxy objects could not be correctly deserialized by using javassist 3.11. we 
need to update to 3.12


 Key: OWB-399
 URL: https://issues.apache.org/jira/browse/OWB-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 encountered an 
issue that de-serialized proxy object could not delegate calls to bean instance 
object methods. The handler field held by the proxy object ( such as 
NormalScopeBeanInterceptorHandler we used for normal scope ) is replaced with 
javassist default handler. 

Sandbox tests show hat if I upgrade to javassist 3.12 and use 
ProxyObjectInputStream/ProxyObjectOutputStream, the handler in de-serialized 
proxy object get restored correctly.

But 3.12 is not in jboss repository yet, anyone know if there is a way  to push 
them update their javasssist repository? or create our own snapshot repository 
temporarily? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (OWB-398) DelegateHandler cached too agressively

2010-06-17 Thread Eric Covener (JIRA)
DelegateHandler cached too agressively
--

 Key: OWB-398
 URL: https://issues.apache.org/jira/browse/OWB-398
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Interceptor and Decorators
Affects Versions: M4
Reporter: Eric Covener
Assignee: Eric Covener


The InterceptorHandler and OpenWebbeansEJBinterceptor keep the interceptor that 
hooks the decorator stack in the cached interceptor stack.

This can lead to an incorrect delegate handler being used, and in the case of 
an decorated EJB can cause the wrong EJB InvocationContext to be used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] release openwebbeans build-tools-1.0.0

2010-06-17 Thread Joseph Bergmark
+1

On Thu, Jun 17, 2010 at 12:55 PM, Eric Covener  wrote:

> On Wed, Jun 16, 2010 at 1:25 PM, Mark Struberg  wrote:
> > Source release:
> >
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-057/org/apache/openwebbeans/build-tools/checkstyle-rules/1.0.0/checkstyle-rules-1.0.0-source-release.zip
>
> +1 for release
>
> --
> Eric Covener
> cove...@gmail.com
>


Re: [VOTE] release openwebbeans build-tools-1.0.0

2010-06-17 Thread Eric Covener
On Wed, Jun 16, 2010 at 1:25 PM, Mark Struberg  wrote:
> Source release:
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-057/org/apache/openwebbeans/build-tools/checkstyle-rules/1.0.0/checkstyle-rules-1.0.0-source-release.zip

+1 for release

-- 
Eric Covener
cove...@gmail.com