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

[Design the new POJO MicroContainer] - Re: New Lifecycle aspects is wrong

by alesj

"adrian(a)jboss.org" wrote : | Ales also made the same mistake, so I guess we need a big warning | message on BeanMetaData to stop people adding things to the model | that are not declartive (intended to be declared by the user)? :-) | Where? At the introduction of BeanMetaData being ValueMetaData? That's still a work in progress. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033092#4033092 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033092

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: New Lifecycle aspects is wrong

by adrian＠jboss.org

Don't get me wrong. Overall, I think what this is trying to achieve is correct and I like the idea of a builder. But it has been targetted too specifically at solving a problem in one particular context and this is coupled with a misunderstanding of what each part of the model is intended to do. The ideas need abstracting into a context neutral api (not just POJO) and implementations details removed from the spi. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033089#4033089 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033089

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - New Lifecycle aspects is wrong

by adrian＠jboss.org

This relates to this long discussion thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101253 I finally got chance to look at what has been done for this and it is wrong. 1) Type safety I quite like the idea of the BeanInfo.getDependencies() returning a builder rather than just names so it can be called back with additional context on what it needs to work on. But this needs to be type safe. e.g. This code shows the problem (the cast - which isn't even checked properly!) | // add custom dependencies (e.g. AOP layer). | List<Object> dependencies = info.getDependencies(md); | log.trace("Extra dependencies for " + context.getName() + " " + dependencies); | if (dependencies != null) | { | for (Object dependencyItem : dependencies) | { | ((DependencyBuilderListItem)dependencyItem).addDependency(context); | } | } | 2) BeanMetaData is not a place to store runtime information that is what the ControllerContext is for. You should not be modifying the BeanMetaData. This is information that the user/client is requesting. Any additional information runtime information should be stored in the ControllerContext, i.e. linked in via DependencyInfo/Item This is how the initial runtime/additional depedencies were coded and that rule must be maintained. Ales also made the same mistake, so I guess we need a big warning message on BeanMetaData to stop people adding things to the model that are not declartive (intended to be declared by the user)? :-) 3) Too much of this implementation detail is being leaked into spi. e.g. the KernelControllerContext interface | /** | * Get the lifecycle callbacks for a particular state. | * | * @param state the state callbacks refer to | * @return List<LifecycleCallbackMetaData> | */ | List<LifecycleCallbackMetaData> getLifecycleCallbacks(ControllerState state); | Besides what I said on the other thread that this is too POJO specifc, it is also an implementation detail that should not need to be exposed on the interface. This is also something else that I've tried to maintain in the Microcontainer api. If the processing is generic state that is going to be useful for all implementations of an interface then it belongs on thatinterface, Otherwise it should be a method specific to an implementation and the integration should use "private api". e.g. I wouldn't have a problem if this was on the Abstract[Kernel]ControllerContext. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033088#4033088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033088

17 years, 1 month

1
0
0 / 0

[Design of Security on JBoss] - Re: Problems while configuring server.policy file

by jahnviv

Oh, I am extremely sorry as I overlooked the previous post of not posting user problems. - Jahnvi View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033082#4033082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033082

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by wolfc

http://jira.jboss.com/jira/browse/EJBTHREE-932 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033075#4033075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033075

17 years, 1 month

1
0
0 / 0

[Design of Security on JBoss] - Problems while configuring server.policy file

by jahnviv

Hi, I want to grant permission to MBeans and MBeanServer of my web application i.e. these MBeans and MBeanServer are application specific, it has nothing to do with JBoss. I am assigning this permission in server.policy file. It already has default permission java.security.AllPermission. So it overrides the MBean specific permission given by me. Now I have removed AllPermission and give some minimum permission required from this link : http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfiguringAJavaSecurityManager Now it gives error regarding deploy folder. The stacktrace is given below: 15:21:10,350 ERROR [MainDeployer] could not create deployment: file:/C:/Java/jboss-4.0.2/server/all/deploy/jboss-aop.deployer/ org.jboss.deployment.DeploymentException: MBeanTrustPermission(register) not implied by protection domain of mbean class: org.jboss.aop.deployment.AspectManagerService, pd: ProtectionDomain (file:/C:/Java/jboss-4.0.2/server/all/tmp/deploy/tmp25826jboss-aspect-library.jar <no certificates>) org.jboss.mx.loading.UnifiedClassLoader3@1546dbc{ url=file:/C:/Java/jboss-4.0.2/server/all/deploy/jboss-aop.deployer/ ,addedOrder=3} <no principals> java.security.Permissions@c4d04d ( (java.net.SocketPermission localhost:1024- listen,resolve) (java.net.SocketPermission * connect,resolve) (java.net.SocketPermission * connect,resolve) (java.net.SocketPermission localhost:1024- listen,resolve) (javax.security.auth.AuthPermission createLoginContext.*) (unresolved javax.management.MBeanServerPermission findMBeanServer null) (unresolved javax.management.MBeanServerPermission findMBeanServer null) (unresolved javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) (unresolved javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) (java.lang.RuntimePermission accessClassInPackage.*) (java.lang.RuntimePermission queuePrintJob) (java.lang.RuntimePermission org.jboss.security.SecurityAssociation.getSubject) (java.lang.RuntimePermission stopThread) (java.util.PropertyPermission java.version read) (java.util.PropertyPermission java.vm.name read) (java.util.PropertyPermission java.vm.vendor read) (java.util.PropertyPermission os.name read) (java.util.PropertyPermission java.vendor.url read) (java.util.PropertyPermission java.vm.specification.vendor read) (java.util.PropertyPermission os.version read) (java.util.PropertyPermission java.specification.vendor read) (java.util.PropertyPermission java.class.version read) (java.util.PropertyPermission java.specification.name read) (java.util.PropertyPermission file.separator read) (java.util.PropertyPermission os.arch read) (java.util.PropertyPermission java.vm.version read) (java.util.PropertyPermission java.vendor read) (java.util.PropertyPermission java.specification.version read) (java.util.PropertyPermission java.vm.specification.version read) (java.util.PropertyPermission java.vm.specification.name read) (java.util.PropertyPermission * read) (java.util.PropertyPermission path.separator read) (java.util.PropertyPermission line.separator read) (java.io.FilePermission C:/Java/jboss-4.0.2/server/all/- read,write,delete) (java.io.FilePermission C:/Java/jboss-4.0.2/- read,write,delete) (java.io.FilePermission C:\j2sdk1.4.2_08\jre/- read,write,delete) (java.io.FilePermission C:/Java/jboss-4.0.2/server/all/- read,write,delete) (java.io.FilePermission C:/Java/jboss-4.0.2/- read,write,delete) (java.io.FilePermission C:\j2sdk1.4.2_08\jre/- read,write,delete) (java.io.FilePermission C:\Java\jboss-4.0.2\server\all\tmp\deploy\tmp25826jboss-aspect-library.jar read) (java.io.FilePermission C:\Java\jboss-4.0.2\server\all\deploy\jboss-aop.deployer read) ) ; - nested throwable: (java.lang.SecurityException: MBeanTrustPermission(register) not implied by protection domain of mbean class: org.jboss.aop.deployment.AspectManagerService, pd: ProtectionDomain (file:/C:/Java/jboss-4.0.2/server/all/tmp/deploy/tmp25826jboss-aspect-library.jar <no certificates>) org.jboss.mx.loading.UnifiedClassLoader3@1546dbc{ url=file:/C:/Java/jboss-4.0.2/server/all/deploy/jboss-aop.deployer/ ,addedOrder=3} <no principals> java.security.Permissions@c4d04d ( (java.net.SocketPermission localhost:1024- listen,resolve) (java.net.SocketPermission * connect,resolve) (java.net.SocketPermission * connect,resolve) (java.net.SocketPermission localhost:1024- listen,resolve) (javax.security.auth.AuthPermission createLoginContext.*) (unresolved javax.management.MBeanServerPermission findMBeanServer null) (unresolved javax.management.MBeanServerPermission findMBeanServer null) (unresolved javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) (unresolved javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) (java.lang.RuntimePermission accessClassInPackage.*) (java.lang.RuntimePermission queuePrintJob) (java.lang.RuntimePermission org.jboss.security.SecurityAssociation.getSubject) (java.lang.RuntimePermission stopThread) (java.util.PropertyPermission java.version read) ..... Any clues?? Thanks. Jahnvi View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033074#4033074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033074

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: No ClassLoaders found for: org.jboss.soa.esb.listeners.c

by ldimaggi＠redhat.com

Also - is there some way to either move this post to the user forum - or just delete it and I'll repost it there - thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032993#4032993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032993

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: No ClassLoaders found for: org.jboss.soa.esb.listeners.c

by kurt.stam＠jboss.com

You need to first run 'ant dist' from the product directory. Also note that there is a newer release out (4.2MR1). Good luck! --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032992#4032992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032992

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: No ClassLoaders found for: org.jboss.soa.esb.listeners.c

by ldimaggi＠redhat.com

Hey Kurt, Sorry to be in the wrong forum! yes - I'm building from source. There is no dist target in build.xml - these are the jars that are generated: jaxr-api-1.0-SNAPSHOT.jar jbossts-common.jar scout-1.0-SNAPSHOT.jar Am I working with the right bits? I downloaded: jbossesb-4.0GA-src.zip Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032991#4032991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032991

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: No ClassLoaders found for: org.jboss.soa.esb.listeners.c

by kurt.stam＠jboss.com

Hi Len, Are you building from source? If so can you run the 'ant dist' task before trying to deploy it? If that does not work can you list the jbossesb-*.jars in the jbossesb.sar/lib directory? Also these kind of questions kinda go in the user forum, not the design forum. thx, --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032990#4032990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032990

17 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007