December 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBossCache] - Re: Serialization Compatibility Tests

by scott.stark＠jboss.org

The javax classes validated for jbossas are from the javaee namespace. Since we supply those we need to validate them. Any javax classes in the jdk are a function of jdk versions, and compatibility at that level is a jdk compatibility problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992863#3992863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992863

18 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by pavel.tsekov＠redhat.com

The problem is that I don't really understand why only those classes ("javax") from the java runtime are processed while the others are left out. Maybe in jboss some instances of classes from the "javax" package are serialized - but is this the case for JBossCache ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992862#3992862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992862

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-615 still present in Embedded-ALPHA9

by hennejg

Bill, thanks. I tried 2006-9-14 (the timestamp of the release on sf and inside the archive) but the line numbers for jbosssx (the starting point for me) just don't match with the ones from the code's debug information. In fact, I'm even confused about which repository is the correct one. The version I mentioned above is from CVS. SVN also has a JBossAuthorizationManager in /repos/jbossas/projects/security et al. However, those versions lack the updateCache method. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992861#3992861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992861

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by scott.stark＠jboss.org

Add type a class assumes a single instance of that type. This is simply a convience method for addAttachment(expectedType.getName(), T attachment, Class expectedType). If there are multiple instance of a type you would need different names. The ServiceMetaData example does not apply. Each ServiceMetaData instance is associated with a component deployment, a type of DeploymentUnit that has no children. DeploymentUnit component is structurally related to the owning deployment unit (a ServiceDeployment for a ServiceMetaData), and each service is a child component deployment unit with a single ServiceMetaData. I'll look to add the getParent today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992859#3992859 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992859

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Other IoC containers support

by scott.stark＠jboss.org

Its just a licensing issue. As long as the license allows it, its is fine. We need to be using a unique namespace to avoid conflicts with the base version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992845#3992845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992845

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

by anil.saldhana＠jboss.com

Deployment Unit: | Object addAttachment(String name, Object attachment); | <T> T addAttachment(String name, T attachment, Class<T> expectedType); | <T> T addAttachment(Class<T> type, T attachment); | Minor issue: the addition of attachments with reference to Class and the attachment itself is not consistent across the api (mainly the second and third add attachments) * I am assuming that a deployment can have multiple service beans. * Now if a deployer wants to remove an attachment in its undeploy method, it is better to have added the attachment with a name?? | unit.addAttachment("somename",bean, ServiceMetaData.class); | unit.removeAttachment("somename", ServiceMetaData.class); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992844#3992844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992844

18 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by ryan.campbell＠jboss.com

1. If these classes are included in any of the jars included in the JBossCache distribution, yes. 2. http://jira.jboss.com/jira/browse/JBAS-3772 is the issue I'm aware of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992843#3992843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992843

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: ClientContainer enc handling

by scott.stark＠jboss.org

What I'm wondering is whether we can collapse the ee5-1.2 client containers into the same one where injection is simply a noop for the legacy container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992830#3992830 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992830

18 years, 1 month

1
0
0 / 0

[Other JBoss Development Design] - Re: Updates to the logging framework for JBossAS 4.2.x

by scott.stark＠jboss.org

Yes, its just a renaming of the package. For tomcat/jbossweb, we need to remove the dependency either through obfuscation or replacing the api usage. For jbc/jgroups, separarte releases that are obfuscated along with the commons logging jars. jarjar can do this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992824#3992824 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992824

18 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by pavel.tsekov＠redhat.com

Ryan, I have vague idea of what had to be done. Instead of doing something and then waiting for people to complain I prefer to do the asking first. I hope you don't have problem with that. Now back to the topic... 1) The original tool creates a database of serialVersionUIDs for the classes found in the java "javax" package . Do we need this for JBossCache ? 2) Are there any known serialization issues between the different JBossCache versions ? If you know of such issues, please, let me know so I can blacklist the classes in question. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992816#3992816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992816

18 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2006