July 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Portal] - Java 5 migration strategy

by julien＠jboss.com

Now it is time to migrate to Java 5 platform (hurray!!). HOWEVER, it must be done with *care*, I propose: 0/ take our time to do it, we are not in a hurry 1/ module by module (start with common module, etc...), probably new situations will arise and so new test case must be done. Also in some situations generics needs to be introduced carefully (like in the org.jboss.portal.common.value package or TypedMap). 2/ natural leads of module are responsible for the migration, otherwise I'll assign someone to do the migration depending on how complex the module is. 3/ review the changes and fix the problems. any suggestion is welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060803#4060803 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060803

18 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Soap messages logging

by vshorreo

Hi everyone. First of all, I apologize if this is not the correct place to put this topic. Then, let's go to the question. I have developed a service exposing an EJB as a web service, and it works, but I would want to log the content of the received SOAP requests. I am using log4j.xml with the org.jboss.ws.server.ServiceEndpoint category and it works fine in JBoss 4.0.4 in Windows, but when I try the same in another JBoss (4.2.0) in Solaris, the values of the parameters are replaced for '--------' in the log file. Does anyone know what happens? Is there a better way to get SOAP messages logged? Thanks in advance. Regards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060796#4060796 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060796

18 years, 9 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - AOP ClassLoader/Scoping needs thoroughly revising

by adrian＠jboss.org

There is a fundamentally bad assumption going on with AOP usage of classloading and scoping. The problem is exemplified by this code in ScopedClassLoaderDomain (but it is a more general issue that I will explain as I go on): | private LoaderRepository getAspectRepository(Object aspect) | { | ClassLoader cl = aspect.getClass().getClassLoader(); | ClassLoader parent = cl; | while (parent != null) | { | if (parent instanceof RepositoryClassLoader) | { | return ((RepositoryClassLoader)parent).getLoaderRepository(); | } | parent = parent.getParent(); | } | return null; | } | The above code is like using Class.forName() instead of the context classloader. It assumes co-location (either aspect and code or aspect and config or config and code) which just isn't true in all cases. When I say co-location I'm really talking about what AOP calls Domains although the way this currently implemented, it is closely related to classloading. In fact, the way AOP tries to guess what is going on and create domains itself based on "hardwired rules" is clearly wrong. The only reason it works is because of the "big ball mud" classloading model currently used by JBoss or the standalone classpath specified on the command line. It is also exemplified by the conflicting (overloaded) usage of Domains: 1) As a scoped configuration repository for the user 2) As a way to scope classloading where a class is deployed multiple times in different deployments 3) Like (1) but done by us, e.g. the ejb3 confurgation domain Before I explain what I would like to see, let me explain some of the use cases which are either not supported or at least difficult to do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060789#4060789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060789

18 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: @CacheListener impl must be public?

by manik.surtani＠jboss.com

It needs to be public because the callback is done via reflection. Good point re: the exception message, will do this for CR4/GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060759#4060759 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060759

18 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Unified metadata

by wolfc

I've committed an initial import for the unified metadata project (jbossas/projects/metadata/trunk). This doesn't show how it's going to be, just all metadata classes thrown together. For the part of WS I've imported the integration classes, because I can't find a mavenized ws-spi. Also I've removed some stuff that is dependent on Kernel, because the new metadata shouldn't have such a dependency and I just wanted it to compile. How shall we proceed from here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060714#4060714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060714

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Webservice - SOAP - JAXB Introductions

by tfennelly

Just posted a bog on the JAXB Annotation Introductions work we've done recently. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060708#4060708 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060708

18 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: @CacheListener impl must be public?

by bstansberry＠jboss.com

I see now the exception message did mention the need to be publicly accessible. But the message was too verbose and the relevant bit wasn't in my log viewer window when I was trying to figure out why this failed. If separated the public accessibility check into a separate if statement; if it fails the exception message will only discuss that problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060621#4060621 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060621

18 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Adding attributes (even nodes) to jPDL without DB changes

by kukeltje

Hi, I implemented a nice extension in jBPM which makes it possible to add custom attributes to jBPL by using a custom namespace | <variable myPrefix:myAttribute="myVal"> | becomes possible then, which can be used in the api by VariableAccess.getExtension(task, prefix, attribute). This does not require db changes since it is retrieved from the processdefinition xml file Maybe the method should move, but the idea is generic. It would even be possible to add jbpm/jpdl attributes without (initially) requiring db changes. E.g. the attribute 'evaluate="always|once(default)" on a swimlane could be implemented in a real method but retrieving the value from the processdefinition. This would limit using these attributes when designing a process with the api, but for adding functionality in between releases it would be ideal. Any comments? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060617#4060617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060617

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Portal build (Repost)

by julien＠jboss.com

Not yet discussed, what should we do ? - migrate to maven - keep the current build for a while and improve it - take a good existing ANT build and use it The constraints are : - no downtime of the project - migration should be transparent What I would like to have: - should have a notion of profile that would apply to various project artifacts like thirdparty libraries, properties - we would like to split the project into several subprojects with different life cycles and at apply the "Don't Repeat Yourself" principle (DRY) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060611#4060611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060611

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal build

by julien＠jboss.com

The current status is: - we use buildmagic - it works - everybody knows how to use it View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060613#4060613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060613

18 years, 9 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 July 2007