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

[Design of Security on JBoss] - Re: CachePolicy in JaasSecurityManagerService

by anil.saldhana＠jboss.com

I know about what you said. I am thinking whether there was any other reason why the objectfactory approach was chosen, like some customer wanting to do "java:/jaas/securitydomain/cache-policy" to get to the cache policy instance or such. I think the simpler approach is just to inject the FQN of the cache policy implementation into the jaassecmgr mbean service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093695#4093695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093695

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: The default local interface (vs. EJBTHREE-785)

by ALRubinger

"wolfc" wrote : Or even better: | * If bean class implements a single interface, that interface is assumed to be a business interface of the bean. This business interface will be a local interface unless the interface is designated as a remote business interface by use of the Remote annotation on the bean class or interface or by means of the deployment descriptor. I think this is the correct case. "wolfc" wrote : | The failing scenario is: | | | @Stateless class MyBean extends SuperBean implements SomeInterface {} | | | | interface SomeInterface {} | | | | class SuperBean implements RemoteInterface {} | | | | @Remote interface RemoteInterface {} | | | If I follow the letter than SomeInterface will become the only business interface (local). | Disagree with the last statement; unclear here whether the spec dictates that "SomeInterface" must be the *only* local business interface: "EJB3 4.6.6" wrote : | If bean class implements a single interface, that interface is assumed to be the (local) business interface of the bean. So the question becomes: can we intrepret "the" as "a"? If so, in the case above I'd have "SomeInterface" be exposed as local business, as well as "RemoteInterface" as remote business. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093693#4093693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093693

18 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: CachePolicy in JaasSecurityManagerService

by scott.stark＠jboss.org

Its just a factory that happens to use a jndi lookup as an implicit factory api based on the javax.naming.spi.ObjectFactory. In reality, its equivalent to: | public interface AuthenticationManagerFactory | { | public AuthenticationManager newInstance(String domainName); | } | // Getting hold of this is the problem the jndi lookup solves | AuthenticationManagerFactory factory = ...; | AuthenticationManager am = factory.newInstance("jaas-domain"); | Instead, use of a naming convention for the security domain (java:/jaas prefix) implicitly locates the AuthenticationManager factory: | InitialContextFactory factory = new InitialContextFactory(); | AuthenticationManager am = (AuthenticationManager) factory.lookup("java:/jaas/jaas-domain"); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093686#4093686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093686

18 years, 6 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: DeploymentInfo/Template MCF

by scott.stark＠jboss.org

Its needs to be done in applyTemplates. The initial creation to create the template properties is just a way to leverage the existing annotations and AbstractManagedObjectFactory. In reality that ManagedObject and group are unused. The AbstractTemplateInfoFactory.createInfo(...) call could just as easily take the ManagedConnectionFactoryDeploymentGroup.class and scan for the ManagedPropertys that should be part of the template. It gets away from the issue of knowing what ds type and name are at that point. One thing we have gotten confused about is that the ManagedPropertys are used in two different ways, as detached by value objects used by admin clients (similar to detached ejb3 entities), and as server side objects that are really proxies for properties on the underlying metadata. Step 1 and the DeploymentTemplateInfo represents the client side case, applyTemplates represents the server side case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093682#4093682 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093682

18 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - CachePolicy in JaasSecurityManagerService

by anil.saldhana＠jboss.com

Scott, do you remember the reason behind the CachePolicy injection into security managers happening into SecurityManagers via JNDI (java:/timedCachePolicy)? Why not just a property taking a FQN of the cache policy implementation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093653#4093653 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093653

18 years, 6 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: DeploymentInfo/Template MCF

by weston.price＠jboss.com

Ok, thanks it's a bit clearer but I am still hung up on the first two portions in what layer should creating the ManagedConnectionFactoryDeploymentGroup and it's associated ManagedConnectionFactoryDeploymentMetaData reside? From your example, I am assuming that the admin client is passing enough contextual information to make this happen, but I am not quite clear on *where* it should happen. In other words, by the time applyTemplates is invoked quite a bit has already been done. It's more of a workflow issue that I am not getting at this point. The primary example provided in the few existing test cases simply call applyTemplates which obviously is not going to work directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093652#4093652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093652

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Transaction behavior of clustered SFSB caching

by bstansberry＠jboss.com

I'll have to see if I can get the concept to work with JBC as the backing caching system. SimplePassivatingCache will not work with JBC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093622#4093622 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093622

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Injection at invocation time, not instantiation time

by bdecoste

The problem is only for @Service beans because we instantiate at deploy time - I still like the idea of being flexible. We support injection at instantiation but give the flexibility to inject at invocation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093613#4093613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093613

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Injection at invocation time, not instantiation time

by wolfc

JSR 250 disallows for injection after construction. (See also EJBTHREE-1055.) So either we don't allow it, or it's a JBoss specific feature. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093610#4093610 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093610

18 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Injection at invocation time, not instantiation time

by bdecoste

There seems to be an echo in here. The more I think about it, the more I like the idea of doing injection based on an interceptor. The interceptor could be bound to constructors or to methods, so config would control when injection occurs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093604#4093604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093604

18 years, 6 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 October 2007