January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4078) DeploymentManager.getAvailableModules() returns null

by Libor Kotouc (JIRA)

DeploymentManager.getAvailableModules() returns null ---------------------------------------------------- Key: JBAS-4078 URL: http://jira.jboss.com/jira/browse/JBAS-4078 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08 Reporter: Libor Kotouc Assigned To: Dimitris Andreadis Priority: Critical This issue blocks an integration of JBoss AS 5 into NetBeans IDE. Steps to reproduce the behavior: 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server) 2. start JBoss server (./run.sh) 3. run the following code from a J2SE application (I added JBoss jars to the classpath): public class Main { public static void main(String[] args) { try { javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl(); javax.enterprise.deploy.spi.DeploymentManager dm; dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null); javax.enterprise.deploy.spi.Target[] targets = dm.getTargets(); javax.enterprise.deploy.spi.TargetModuleID[] modules; modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets); System.out.println(targets.length + " " + targets[0]); System.out.println(modules); } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) { } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) { } } } The output of System.out.println statements is: 1 org.jboss.deployment.spi.JMXTarget@161d36b null I expect the module representing the web application, but null is returned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-641) Explore data center failover for clusters at the JGroups level

by Jimmy Wilson (JIRA)

Explore data center failover for clusters at the JGroups level -------------------------------------------------------------- Key: JGRP-641 URL: http://jira.jboss.com/jira/browse/JGRP-641 Project: JGroups Issue Type: Task Affects Versions: 2.x Reporter: Jimmy Wilson Assigned To: Bela Ban Priority: Minor Explore the possibility of using a JGroups protocol (or other mechanism) to provide data center fail over. Possible use cases: * Primary/Backup * Loadbalancing w/ sticky sessions * Rolling updates * Shared data Wiki generated from this discussion (was JBossCache-specific): http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres The forum discussion has been associated with this JIRA as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-56) SecurityContextAssociation missing in client path

by Thomas Diesler (JIRA)

SecurityContextAssociation missing in client path ------------------------------------------------- Key: SECURITY-56 URL: http://jira.jboss.com/jira/browse/SECURITY-56 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Anil Saldhana bin/twiddle.sh doe not work in AS5.0 because of missing security classes. A scan on client jars shows that SecurityContextAssociation is not part of any client jar [tdiesler@jbws jboss-5.0.0.Beta3]$ bin/twiddle.sh -s jnp://jbws2:1099 get jboss.system:type=Server Started Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/security/plugins/SecurityContextAssociation at org.jboss.proxy.SecurityActions$1.getPrincipal(SecurityActions.java:57) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:58) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy0.getAttributes(Unknown Source) at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168) at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3703) Update JRMPInvoker to not cast exported object to RemoteStub

by Scott M Stark (JIRA)

Update JRMPInvoker to not cast exported object to RemoteStub ------------------------------------------------------------ Key: JBAS-3703 URL: http://jira.jboss.com/jira/browse/JBAS-3703 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1 Reporter: Scott M Stark Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 If one runs with the jdk5 java.rmi.server.ignoreStubClasses dynamic stub override to force the server to generate stubs for exported objects, the JRMPInvoker fails to start with the following exception: [starksm@succubus bin]$ run.sh -D-Djava.rmi.server.ignoreStubClasses=true ========================================================================= ... 11:55:52,477 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp java.lang.ClassCastException: $Proxy13 at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:437) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:359) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:136) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274) The reason is that the code creating the remote object is explictly casting the export result to a RemoteStub: protected void exportCI() throws Exception { this.invokerStub = (RemoteStub) UnicastRemoteObject.exportObject (this, rmiPort, clientSocketFactory, serverSocketFactory); } even though the public contract for this stub only requires a Serializable instance. The type of the invokerStub should just be relaxed to Serializable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-421) Classpath is incorrect when running javadoc reports

by Paul Gier (JIRA)

Classpath is incorrect when running javadoc reports --------------------------------------------------- Key: JBBUILD-421 URL: http://jira.jboss.com/jira/browse/JBBUILD-421 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 JBoss Cache build has an issue with the javadoc plugin. The javadocs work fine when run from the main build, but fail with errors when generating the site. It appears that the testng jar is required for the javadoc generation, but this jar is not getting included in the classpath when run from the reports section. The issue could be related to this one: http://jira.codehaus.org/browse/MJAVADOC-140 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-442) Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files

by pether (JIRA)

Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files --------------------------------------------------------------------------------- Key: JBBUILD-442 URL: http://jira.jboss.com/jira/browse/JBBUILD-442 Project: JBoss Build System Issue Type: Feature Request Components: Maven Affects Versions: Maven Build - Maint 2008 Reporter: pether Priority: Minor Fix For: Maven Build - Maint 2008 Two different cases that should work for developers to choose from 1. Using eclipse project references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true 2. Using maven repository jar references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true In some ways an audit of http://jira.jboss.org/jira/browse/JBBUILD-258 and resolve any issues with dependencies. Current issues with jboss/trunk The projects below have compile errors, mostly incorrect project dependencies jboss-as-deployment jboss-as-console jboss-as-iiop jboss-as-varia -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-909) Injection of Simple Environment Entries Using Resource Annotation without name

by Roland R?z (JIRA)

Injection of Simple Environment Entries Using Resource Annotation without name ------------------------------------------------------------------------------ Key: EJBTHREE-909 URL: http://jira.jboss.com/jira/browse/EJBTHREE-909 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Roland R?z The name of the @Resource annotations should default to the property or method name. The following simple environment injections are not working as expected: @Resource String stringValue; Long longValue = Long.valueOf(1); @Resource void setLongValue(Long longValue) { this.longValue = longValue; } Workaround: @Resource(name = "stringValue") String stringValue = "hi"; Long longValue = Long.valueOf(1); @Resource(name = "longValue") public void setIntValue(Long longValue) { this.longValue = longValue; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-4363) OSGi Bundle Repository support

by Scott M Stark (JIRA)

OSGi Bundle Repository support ------------------------------ Key: JBAS-4363 URL: http://jira.jboss.com/jira/browse/JBAS-4363 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The OSGi Bundle Repository support requirements need to be considered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-3778) AttributePersistenceService does not allow absolute path for data-directory value

by Darran Lofthouse (JIRA)

AttributePersistenceService does not allow absolute path for data-directory value --------------------------------------------------------------------------------- Key: JBAS-3778 URL: http://jira.jboss.com/jira/browse/JBAS-3778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.0.6.CR1 AttributePersistenceService does not allow absolute path for data-directory value, any value specified even with a leading '/' is created within the folder of the configuration being executed. Also the default configuration in the jboss-service.xml should take into account the setting for jboss.server.data.dir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-3630) JMSTransportSupport is not portable across different JMS providers.

by Darran Lofthouse (JIRA)

JMSTransportSupport is not portable across different JMS providers. ------------------------------------------------------------------- Key: JBAS-3630 URL: http://jira.jboss.com/jira/browse/JBAS-3630 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Thomas Diesler Fix For: JBossAS-4.0.6.CR1 JMSTransportSupport is not portable across different JMS providers, the queue name is retrieved using the following code: - String fromName = null; Destination destination = message.getJMSDestination(); if (destination instanceof Queue) fromName = "queue/" + ((Queue)destination).getQueueName(); if (destination instanceof Topic) fromName = "topic/" + ((Topic)destination).getTopicName(); For JBossMQ this is fine and it results in a name that matches the JNDI name of the queue, for WebSphereMQ this returns the name of the queue as configured on WebSphere not the JNDI name the queue is bound to in JBoss. The Javadoc for Queue describes the getQueueName as not being suitable for portable clients: - http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Queue.html A more portable solution could be to lookup a variable in the ENC that contains the name of the web service, this could either be provided by the user deploying the MDB or the web service deployer could bind a value to the ENC of the message driven bean as the web service is deployed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008