[JBoss JIRA] Created: (SECURITY-549) Security Factory NPE when there is no configuration
by Anil Saldhana (JIRA)
Security Factory NPE when there is no configuration
---------------------------------------------------
Key: SECURITY-549
URL: https://issues.jboss.org/browse/SECURITY-549
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: PicketBox_v4_0_alpha2
Reporter: Anil Saldhana
Assignee: Anil Saldhana
A call :
String securityDomain = "other";
AuthenticationManager authM = SecurityFactory.getAuthenticationManager(securityDomain);
will lead to:
Caused by: java.lang.RuntimeException: Unable to init SecurityFactory:
at org.picketbox.factories.SecurityFactory.<clinit>(SecurityFactory.java:66)
... 7 more
Caused by: java.lang.NullPointerException
at org.picketbox.factories.SecurityFactory.<clinit>(SecurityFactory.java:57)
We need to replace the NPE with a meaningful message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-2231) Interceptor with generics, applied on a bean, isn't invoked
by jaikiran pai (JIRA)
Interceptor with generics, applied on a bean, isn't invoked
-----------------------------------------------------------
Key: EJBTHREE-2231
URL: https://issues.jboss.org/browse/EJBTHREE-2231
Project: EJB 3.0
Issue Type: Bug
Affects Versions: depchain-1.0.0-alpha-43
Reporter: jaikiran pai
A user has reported that a interceptor which involves generics and subclassing, as follows:
public abstract class AbstractServiceInitializer<T> {
@PostConstruct
public void init(InvocationContext ctx) {
Object o = ctx.getTarget();
try {
T service = (T) o;
init(service);
} catch (ClassCastException e) {
log.warn("Class {} is not supported... doing nothing", o.getClass().getName());
return;
}
}
public abstract void init(T service);
}
public class MyEjbImplInitializer extends AbstractServiceInitializer<MyEjbImpl>{
@Override
public void init(MyEjbImpl service) {
// specific init stuff
}
}
doesn't get invoked when the interceptor is applied to a EJB.
Please see the referenced forum thread for details.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBAS-8690) ServerDeploymentRepository not available on deployment activation
by Thomas Diesler (JIRA)
ServerDeploymentRepository not available on deployment activation
-----------------------------------------------------------------
Key: JBAS-8690
URL: https://jira.jboss.org/browse/JBAS-8690
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Reporter: Thomas Diesler
Assignee: Ales Justin
Fix For: 7.0.0.Alpha2
After the recent update to the deployment chain I see that
ServerDeploymentStartStopHandler.activate(...)
is called before the ServerDeploymentRepository service comes up.
This results in a ServiceNotFoundException in ServerDeploymentStartStopHandler.getDeploymentRepository(...) which is then swallowed and does not show up on the console and neither in the logs.
As a result, deployments do silently not activate.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Resolved: (JBAS-8668) All OSGi bundle install code paths must go through deployer chain
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBAS-8668?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved JBAS-8668.
----------------------------------
Assignee: Thomas Diesler (was: Jason Greene)
Resolution: Done
Done
> All OSGi bundle install code paths must go through deployer chain
> -----------------------------------------------------------------
>
> Key: JBAS-8668
> URL: https://issues.jboss.org/browse/JBAS-8668
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: OSGi integration
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 7.0.0.Alpha2
>
>
> There are multiple code paths paths that install a bundle
> Aries JMX install --> BundleContext.install()
> DeploymentChain --> DeployerService.deploy(Deployment)
> Bundle Hotdeploy --> DeployerService.deploy(Deployment)
> OSGi Console --> DeployerService.deploy(Deployment)
> BundleContext.install() -> BundleManager.install(Deployment)
> DeployerService.deploy(Deployment) --> BundleManager.install(Deployment)
> In AS7 all bundle install paths must go through the DeploymentChain
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months