May 2008 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Classloading and versioning

by adrian＠jboss.org

This configuration is invalid (but the part that checks it is the outstanding issue in JBCL). acme1 exports ales version 1 and scott version 1 acme2 exports ales version 2 and scott version 3 foo wants to import ales version 1 from acme1 and scott version 3 from acme2 Tthis will lead to incompatibilities between the versions in the linked classloaders. foo, acme1 and acme2 are in the same "classloading space" so they must agree on a common instance of the classes in the exported ales package. It should be failing at deployment time with an "conflicting package resolution" error for the ales package. If foo wants to use scott version 3 (provided by acme2) then it must also use ales version 2 to be consistent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150300#4150300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150300

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO only waiting for completions on add

by timfox

A few points though on your last commit. 1) Several files were missing copyright headers and class headers showing authorship. All files must have both of these before committing! I shouldn't have to keep saying this.. ;) 2) Lots of cosmetic changes to files, code style, indentation, putting private public, static methods in their own sections of the file. Adding final to attributes and parameters. Making inner classes static. Making inner classes private. Making members private. Various other minor coding issues like the above. 3) Remoting timeout has changed from seconds to milliseconds? I agree we should change from s to ms, but has this been changed everywhere? 4) TypedProperties - the encodeSize() method traverses the entire map every time it is called. I don't like this for performance reasons. Instead the size should be maintained internally. 5) Min files was changed to 2, and file size changed from 10MB to 100 MB. 10MB was originally chosen since it seems a reasonable size to fit on a single cylinder of a disk. This allows the entire file to be accessed without moving the head. When I changed it back to 10MB and 10 files, none of the jms tests run any more reporting they can't initialise AIO (or something like that). Apart from that, looking good! :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150299#4150299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150299

17 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Classloading and versioning

by adrian＠jboss.org

This configuration is invalid (but the part that checks it is the outstanding issue in JBCL). acme1 exports scott version 1 and ales version 1 acme2 wants to import ales version from acme1 but it also wants to scott version 3 Tthis will lead to incompatibilities between the versions of scott in the linked classloaders. acme1 and acme2 are in the same "classloading space" so they must agree on a common instance of the classes in the scott package. It should be failing at deployment time with an "conflicting package resolution" error for the scott package. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150294#4150294 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150294

17 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: GA releases of mc projects?

by adrian＠jboss.org

Why would any of the above require a change to the existing api? Sure we might want to allow an alternate implementation of the parsing of the class annotations using javassist in the MDR so AOP can use thi s mechanism but that is an implemetation detail. I don't see why bean validation would require any api change. If you mean adding bean validation as a new api to the reflect project, the addition of new optional api is NOT an api change. But bean validation is not really reflection so I'd prefer additional validation api or integration to be in its own project. i.e. it is something that sits above the reflection layer. Allowing non-public method invocations is just an internal change to do access checks similar to what I did for non-public fields, i.e. no api change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150291#4150291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150291

17 years, 11 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Sharing session attribute between servelt and portlet

by chris.laprun＠jboss.com

Sharing session data indeed only works for portlets and servlets bundled in the same web application (war file). I think the problem here is that the name of the param is namespaced for the portlet so if you set a param called "foo" in the portlet session, you cannot access it using just "foo" in the servlet. Please look at the servlet specification for the namespace format. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150289#4150289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150289

17 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: 4.3 CR1 is available for download

by Kevin.Conner＠jboss.com

Hiya Jarkko. It looks like there is a jar file missing from the trailblazer distribution, let me check up on it and get back to you. Thanks for helping out. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150271#4150271 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150271

17 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: organization of the enterprise module

by tom.baeyens＠jboss.com

i forgot one item in the list I believe the coding of the timer entity bean has been done. I don't know to what extend the timer entity work is finished: * QA-ed * Configurtation in the enteprise ear deployment package * Documentation * Migration View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150265#4150265 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150265

17 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: organization of the enterprise module

by tom.baeyens＠jboss.com

"alex.guizar(a)jboss.com" wrote : There are two entity-based implementations of the scheduler service, one in org.jbpm.scheduler.ejbtimer and the other in org.jbpm.ejb. The descriptor points to the former; the latter is probably the remains of an earlier refactoring. | Up to the last release 3.2.2 the ejb timer service uses an SLSB: one bean on which all the timers are registered. This can become a scalability issue. That's why we (Me and then Fady) implemented the timer entity bean: one bean per timer. "alex.guizar(a)jboss.com" wrote : | The EjbSchedulerService class, introduced in earlier 3.2.x versions, invokes the entity bean, whereas the new EntitySchedulerService class invokes the timer session bean. | I believe the coding of the timer entity bean has been done. I don't know to what extend the timer entity work is finished: * QA-ed * Configurtation in the enteprise ear deployment package * Documentation Alejandro can you verify which of these are done ? "alex.guizar(a)jboss.com" wrote : | The command service interface, home interface and session bean are placed in the org.jbpm.ejb package, whereas the timer entity artifacts are located in org.jbpm.scheduler.ejbtimer. | Any reason for this odd arrangement? If not, I want to rearrange as follows. | Remove the timer entity in org.jbpm.ejb. Move the timer entity in org.jbpm.scheduler.ejbtimer to org.jbpm.ejb. | For backwards compatibility, have EjbSchedulerService invoke the timer session bean. Have EntitySchedulerService invoke the timer entity bean, which better matches its name. The only thing you can take into account is the architectural picture. The services are used inside of the JbpmContext-block. The timer entity bean is only an implementation detail of the EntitySchedulerService. If you take that into account, you can rearrange as you want (as long as it works :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150263#4150263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150263

17 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Virtual File semantics exist in TomcatDeployment

by anil.saldhana＠jboss.com

We have Virtual File semantics still existing in TomcatDeployment. There has been a new introduction of a concept of "UnifiedVirtualFile" from the webservices component just to make a serviceref to WS. At least the web services introduction seems wrong to me assuming that the tomcat usage of VFS semantics is a work in progress. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150255#4150255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150255

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO only waiting for completions on add

by timfox

Great :) I'll take a look. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150242#4150242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150242

17 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2008