November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-467) Serialize container proxies out of vm

by Kabir Khan (JIRA)

Serialize container proxies out of vm ------------------------------------- Key: JBAOP-467 URL: http://jira.jboss.com/jira/browse/JBAOP-467 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR1 -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-799) Add a separate timeout parameter for callback clients, part 2

by Ron Sigal (JIRA)

Add a separate timeout parameter for callback clients, part 2 ------------------------------------------------------------- Key: JBREM-799 URL: http://jira.jboss.com/jira/browse/JBREM-799 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) This issue is a continuation of JBREM-765 "Add a separate timeout parameter for callback clients". The changes have been applied to branches remoting_2_2_0_GA and remoting_2_x, but unit tests exist only for transports socket and bisocket. A unit test should be written for the RMI transport as well. However, no additional changes will be made to Remoting 2.2.2.GA, so this issue is introduced for 2.4.0. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-851) In LeasePinger and TimerUtil replace Timer if it has shut down

by Ron Sigal (JIRA)

In LeasePinger and TimerUtil replace Timer if it has shut down -------------------------------------------------------------- Key: JBREM-851 URL: http://jira.jboss.com/jira/browse/JBREM-851 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When all of the TimerTasks running in a java.util.TimerTask have shut down, the TImer will also shut down, at which point it will accept no more TimerTasks. There are places in Remoting where there should be a test which will create a new Timer the attempt to schedule a TimerTask results in an exception. Two places the problem exists: 1. org.jboss.remoting.LeasePinger, and 2. org.jboss.remoting.util.TimerUtil. A similar problem is described in JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer" Reported by James on Remoting forum. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-804) Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator

by Ron Sigal (JIRA)

Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator ------------------------------------------------------------------------------------------- Key: JBREM-804 URL: http://jira.jboss.com/jira/browse/JBREM-804 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.GA Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, the value for the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.NO_THROW_ON_ERROR in org.jboss.remoting.transport.http.HTTPClientInvoker is configurable only by way of the invocation metadata map passed to org.jboss.remoting.Client.invoke(). However, for EJB3 invocations, the Client is created by the EJB3 proxy (org.jboss.aspects.remoting.InvokeRemoteInterceptor, in particular) and is not accessible by application code. If HTTPClientInvoker checked the InvokerLocator for this parameter, then it could be configured declaratively in the EJB3 jboss-service.xml file. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4943) jboss-ds_1_5.dtd is wrong

by Michael Lipp (JIRA)

jboss-ds_1_5.dtd is wrong ------------------------- Key: JBAS-4943 URL: http://jira.jboss.com/jira/browse/JBAS-4943 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, JCA service Affects Versions: JBossAS-4.0.5.GA Environment: Any Reporter: Michael Lipp Assigned To: Norman Richards The jboss-ds_1_5.dtd (as distributed in docs/dtd/) is wrong or not up-to-date (and there is no newer version and no out-of-date mark). As has been pointed out by Adrian Brock in JBAS-4942, it is possible to specify a loader-repository like this: <connection-factories>  <loader-repository>jboss.test:loader=JavaClassIsolation</loader-repository> <tx-connection-factory>  <rar-name>some.ear#some.rar</rar-name> <etc/> </tx-connection-factory> </connection-factories> ... although this is not compliant with the DTD! Keeping the DTD up-to-date would avoid unnecessary bug reports and/or forum questions because looking at the DTD is the first step in finding out how to configure required behavior. -- 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

16 years, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-4842) TECH REVIEW: Server Configuration Guide - TRACKER

by samson kittoli (JIRA)

TECH REVIEW: Server Configuration Guide - TRACKER -------------------------------------------------- Key: JBAS-4842 URL: http://jira.jboss.com/jira/browse/JBAS-4842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Server Configuration Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli -- 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

16 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4819) TECH REVIEW: Installation Guide - TRACKER

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - TRACKER ----------------------------------------- Key: JBAS-4819 URL: http://jira.jboss.com/jira/browse/JBAS-4819 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Tracker for Chapter Edits of the Installation Guide -- 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

16 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAOP-290) Make src/build.xml work

by Kabir Khan (JIRA)

Make src/build.xml work ----------------------- Key: JBAOP-290 URL: http://jira.jboss.com/jira/browse/JBAOP-290 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 Should be part of the dist and it should be possible to build the full aop/aspects releases and run some of the tests -- 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

16 years, 11 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAOP-453) maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath

by Anders Andersen (JIRA)

maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath ---------------------------------------------------------------------------------- Key: JBAOP-453 URL: http://jira.jboss.com/jira/browse/JBAOP-453 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Environment: maven 2 Reporter: Anders Andersen In order to use the plugin I have to add the following dependencies to the client artifact dependency list. <dependency> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jbossaop-plugin</artifactId> <version>1.0-SNAPSHOT</version> </dependency> <dependency> <groupId>jboss</groupId> <artifactId>jboss-aop</artifactId> <version>2.0.0.alpha2</version> </dependency> <dependency> <groupId>jboss</groupId> <artifactId>jboss-common</artifactId> <version>4.0.2</version> </dependency> <dependency> <groupId>concurrent</groupId> <artifactId>concurrent</artifactId> <version>1.3.4</version> </dependency> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact. See lists below. I think the statement cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())}); is wrong. I tried to include only project.getPluginArtifacts(), but it gave me a NPE So I am not 100% sure what the code solution should be but it is not good to having maven artifacts in the resulting dependency list of the client-artifact list: (resulting depenency list) The ** marked should not be there **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar -- 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

16 years, 11 months

5
22
0 / 0

[JBoss JIRA] Created: (JBAS-3815) Deployment Level Principal-Role Mapping passed to authorization layer

by Anil Saldhana (JIRA)

Deployment Level Principal-Role Mapping passed to authorization layer --------------------------------------------------------------------- Key: JBAS-3815 URL: http://jira.jboss.com/jira/browse/JBAS-3815 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Since the JBoss 4.0.x days, the deployment level rolename to principal set mapping is available in the meta data, but there was no usage of this in the authorization layer. There is a need for this information to be passed to the authorization manager/mapping layer. Affects the ejb3, ejb21 and web layers [jboss.xml,jboss-web.xml and jboss-app.xml] -- 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

16 years, 11 months

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007