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

[Design of POJO Server] - Re: ProfileService todos for deployer changes

by adrian＠jboss.org

I don't get the use AOP (DeployerAspects) for this? This api should be (and already is) part of the main deployers api. If it is wrong, then it needs changing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066240#4066240 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066240

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: ProfileService todos for deployer changes

by scott.stark＠jboss.org

The direction I'm currently heading is to generalize the profile service DeployerAspects to build the ManagedDeployment/ManagedComponent tree from the deployment metadata. The metadata handlers would come from the deployers who handle the associated component metadata. A component handler is something like: | public interface ManagedDeploymentCreator<T> | { | public buildComponents(ManagedDeployment ctx, Set<? extends T> metaData); | } | And the *-service.xml component handler would be: | public class ServiceMetaDataManagedDeploymentCreator | implements ManagedDeploymentCreator<ServiceMetaData> | { | | public void buildComponents(ManagedDeployment ctx, Set<? extends ServiceMetaData> metaData) | { | ... | } | | } | The DeployerAspects builds up the ManagedDeployment/ManagedComponent graph by calling out to the ManagedDeploymentCreators: | public class DeployerAspects | { | /** The metadata type to ManagedComponent handlers */ | private Map<Class, ManagedDeploymentCreator> mdCreators; | ... | ManagedDeployment md = ...; | for(Class mdType : mdCreators.keySet()) | { | Set metadata = unit.getAllMetaData(mdType); | if( metadata == null || metadata.size() == 0 ) | continue; | ManagedDeploymentCreator creator = mdCreators.get(mdType); | creator.buildComponents(md, metadata); | } | There can be interaction between multiple ManagedDeploymentCreators. For example, with jca, the factories(the managed components) and properties are determined by the ManagedConnectionFactoryDeploymentGroup metadata, but there are runtime ops and stats that have to come from the ServiceMetaData of the mbeans that the jca layer currently uses as the runtime objects implementing the factories. Those mbeans should not be showing up as some manageable sar, while jms destinations currently are deployed as just a collection of mbeans. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066236#4066236 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066236

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Beta3 roadmap items

by scott.stark＠jboss.org

"bgeorges" wrote : | Could you point me to the right individual. | | Thanks for your help. That is me for now as I'm working on moving the profile service managed object creation into a more general layer driven by the deployment metadata and all of these issues are usecases that affect that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066226#4066226 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066226

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Deployers api for client side

by adrian＠jboss.org

I've added "core" and "client" JBOSS_DIST/client so there is at least the new DeploymentException in there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066223#4066223 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066223

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Deployers api for client side

by adrian＠jboss.org

We probably need to add an assembly for the client side deployers api. The new deployers have been missing from the client jars since I first did them. This assembly would include "core", "client", and the client side of "vfs" plus the metatype and managed object jars. It would also require their dependencies like the vfs project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066222#4066222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066222

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Service mbean annotations

by alesj

"adrian(a)jboss.org" wrote : You need to fix the ServiceAnnotationMetaData such that it passes in the | classloader (it should use the classloader of the MBean). | I've added the ClassLoader parameter, but I'm unable (*) to find any concrete usage (apart from testcase) of ServiceAnnotationMetaData.getAnnotationInstance() to pass in MBean's classloader. * - IDEA's support for Eclipse's .classpath or .project sucks ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066188#4066188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066188

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Property lookup interceptors

by alesj

"adrian(a)jboss.org" wrote : Actually, I'm wondering whether this feature shouldn't just be a part of the | | | <inject/> | | | xml. | I thought of that too. But we already stuffed 'inject' with all sorts of things - bean property, contextual injection, fromContext. The concept is the same, but lets keep it separate, not to confuse people with too many configurations - specially if we want to have shorthand single parameter value-factory. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066172#4066172 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066172

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Property lookup interceptors

by adrian＠jboss.org

Actually, I'm wondering whether this feature shouldn't just be a part of the | <inject/> | | | xml. | | | | We already support retrieving a property from another bean | | (the default value may also be useful for that!) | | So this is just a different case where you invoke a method with parameters | | instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066169#4066169 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066169

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Property lookup interceptors

by alesj

"adrian(a)jboss.org" wrote : | But I don't think the value factory needs to know the default value, | it just returns "null" when it doesn't have the property. | | | <property name="x"> | | <value-factory bean="LDAPLookup" method="getValue" default="mydefault"> | | <parameter>foo.bar.prop</parameter> | | </value-factory> | | </property> | | | Value factory can take as many parameters as it wants, and return whatever you implement. What I meant was that LDAPLookup is something like this: | public class LDAPLookup { | | public String getValue(String key, String default) | { | String value = LDAP.lookup(key); | return value != null ? value : default; | } | | } | So your version would just be: | public class LDAPLookup { | | public String getValue(String key) | { | return getValue(key, null); | } | | public String getValue(String key, String default) | { | String value = LDAP.lookup(key); | return value != null ? value : default; | } | | } | "adrian(a)jboss.org" wrote : | We should probably still have the shorthand mechanism for simple one | parameter methods. | | | | <property name="x"> | | <value-factory bean="LDAPLookup" method="getValue" parameter="foo.bar.prop" default="mydefault"/> | | </property> | | | That sounds reasonable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066168#4066168 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066168

18 years, 8 months

1
0
0 / 0

[Design of JBoss Reporting] - Re: About jasperreport-portal from download section

by WeAzLe

Hi guys, I am curious to know if anybody ever successfully used the jasperreport portal. I get all my reports listed in the portal but on executiion. I do not get a result back. Uploading files and creating directories works also fine. Does anybody have more experience or is there any documentation available else then in the docs directory? KR, WeAzLe View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066167#4066167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066167

18 years, 8 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