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

[Design of Messaging on JBoss (Messaging/JBoss)] - how to prevent sending message to a queue ??

by subrata_jboss

i have a queue named /queue/MessageQueue i created one role as admin with read/write/create now i want other than admin no body can send a message to this queue. while using createConnection("user","password") , it is working as it is userid and password for admin. But my createConnection() is also able to send the message to the queue ! i am using jboss messaging 1.4.2 In destinations-service.xml i added <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=SubrataTest" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer jboss.messaging:service=PostOffice in login-config.xml i added <application-policy name = "messaging"> <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule" flag = "required" > <module-option name = "unauthenticatedIdentity">Subrata</module-option> <module-option name = "usersProperties">props/messaging-users.properties</module-option> <module-option name = "rolesProperties">props/messaging-roles.properties</module-option> </login-module> </application-policy> In messaging-roles.properties,messaging-users.properties i added password , role. Any help?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136247#4136247 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136247

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBDEPLOY-3 issues

by scott.stark＠jboss.org

No, the org.jboss.deployers.spi.deployer.managed.ManagedDeploymentCreator relies on DeploymentUnit or the unit ManagedObject set: | public interface ManagedDeploymentCreator | { | /** | * Build up the deployment management view. | * @param unit - the deployment unit to process | * @param md - the unit ManagedDeployment | */ | public ManagedDeployment build(DeploymentUnit unit, Map<String, ManagedObject> unitMOs, | ManagedDeployment parent); | } | If type is not part of DeploymentUnit, then a ManagementDeployment annotation would have to be added to use with the ManagedObjects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136237#4136237 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136237

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Notion of 'compatible-version'?

by scott.stark＠jboss.org

The http://maven.apache.org/release-notes.html show a number of issues related to version ranges as being fixed. The question is, what happens when you use them? | <dependency> | <groupid>org.jboss.x</groupid> | <artifactid>x-api</artifactid> |  | <version>[3.3.0,3.4.0)</version> | </dependency> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136235#4136235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136235

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBDEPLOY-3 issues

by alesj

"scott.stark(a)jboss.org" wrote : Implementations of org.jboss.profileservice.spi.DeploymentRepository.getDeploymentNamesForType are looking to the VFSDeployment.getType, not Deployer.getType. | Sure, but that's exactly what was asked to be removed. The Deployment(Unit|Context) shouldn't have the types. "scott.stark(a)jboss.org" wrote : There are some deployer beans.xml that are setting the type property, so they would need to be updated to remove Deployer.getType. | So, you're saying you wont be needing Deployer::getType? "scott.stark(a)jboss.org" wrote : | The org.jboss.managed.api.ManagedDeployment has a types notion, so support will have to be based on that. | Yup, but I thought this would use Deployer::getType to build the ManagedDeployment with the right types. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136234#4136234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136234

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBDEPLOY-3 issues

by scott.stark＠jboss.org

Implementations of org.jboss.profileservice.spi.DeploymentRepository.getDeploymentNamesForType are looking to the VFSDeployment.getType, not Deployer.getType. There are some deployer beans.xml that are setting the type property, so they would need to be updated to remove Deployer.getType. The org.jboss.managed.api.ManagedDeployment has a types notion, so support will have to be based on that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136233#4136233 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136233

18 years

1
0
0 / 0

[Design of JBoss Portal] - ServletContainer.register(ServletContainerContext context) m

by julien＠jboss.com

Can I assume that the method needs to be present on the interface because JBoss Portal in AS is using dynamic proxies for injection ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136228#4136228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136228

18 years

1
0
0 / 0

[Design of POJO Server] - Re: Generalizing dependency injection

by scott.stark＠jboss.org

An extension of org.jboss.beans.metadata.spi.factory.BeanFactory is needed: | public interface BeanFactory | { | /** | * Create bean. | * | * @return bean | * @throws Throwable for any error | */ | Object createBean() throws Throwable; | } | public interface PooledBeanFactory extends BeanFactory | { | destroy(Object instance) throws Throwable; | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136227#4136227 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136227

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBDEPLOY-3 issues

by alesj

"alesj" wrote : | OK, I'll go ahead and remove them from deployers. | I removed it from Deployment(Unit|Context), but I still left Deployer::getType, since I guess that is what Scott will still need to hook up with Managed* api. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136225#4136225 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136225

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM With Seam

by kukeltje

Fady, Locally I already have an ldap based identity management system (user, group, mail, role). Quite configurable. The jBPM core needs some changes tough I think where user/group/identity service should become interfaces in the core. This has some influence on the user/group hibernate configs so it is a little more work before I can demonstrate. But deriving from the portal would be even better. Maybe I have a quick look at this next week. I would not like to have to include the full portal, just for this. Maybe they (portal) or JBoss can split something off. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136215#4136215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136215

18 years

1
0
0 / 0

[Design of POJO Server] - Re: Generalizing dependency injection

by wolfc

I think we need to separate injection and component construction (/destruction). It seems we're forgetting again that a component class = 1 bean class + interceptor classes. So interceptor lifecycle is tied to the bean. While injection follows the same rules. At the end of the day I want to have something like: package org.jboss.ejb3.pool; | | /** | * Creates and destroys stateless objects. | * | * The object returned by create has dependencies injected. The PostConstruct | * callback, if defined, has been called. | * | * @author <a href="mailto:carlo.dewolf@jboss.com">Carlo de Wolf</a> | * @version $Revision: $ | */ | public interface StatelessObjectFactory<T> | { | /** | * Creates a new stateless object by calling it's empty constructor, | * do injection and calling post-construct. | * | * @return | */ | T create(); | | /** | * Perform any cleanup actions on the object, such as | * calling the pre-destroy callback. | * | * @param obj the object | */ | void destroy(T obj); | } http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/ejb3/trunk/po... Behind the scenes it delegates to 'bean factory' for construction which delegates to injection for each object which is part of the component. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136213#4136213 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136213

18 years

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 March 2008