November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6176) appclient doesn't declare a dependency on persistence unit

by Carlo de Wolf (JIRA)

appclient doesn't declare a dependency on persistence unit ---------------------------------------------------------- Key: JBAS-6176 URL: https://jira.jboss.org/jira/browse/JBAS-6176 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AppClient Affects Versions: JBossAS-5.0.0.CR2 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: JBossAS-5.0.0.GA 15:50:19,461 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=ejb3_appclient_annotation.ear,jar=ejb3_appclient_annotation_client.jar,name=ejb3_appclient_annotation_client,service=EJB3 15:50:19,462 INFO [JBossASKernel] with dependencies: 15:50:19,463 INFO [JBossASKernel] and demands: 15:50:19,464 INFO [JBossASKernel] and supplies: 15:50:19,465 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=ejb3_appclient_annotation.ear,jar=ejb3_appclient_annotation_client.jar,name=ejb3_appclient_annotation_client,service=EJB3) to KernelDeployment of: ejb3_appclient_annotation_client.jar 15:50:19,834 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=ejb3_appclient_annotation.ear,jar=ejb3_appclient_annotation_client.jar,name=ejb3_appclient_annotation_client,service=EJB3 state=Create java.lang.NullPointerException at org.jboss.ejb3.clientmodule.RemotePuEncInjector.inject(RemotePuEncInjector.java:62) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5927) Upgrade jboss-integration spis to 5.0.0.GA

by Dimitris Andreadis (JIRA)

Upgrade jboss-integration spis to 5.0.0.GA ------------------------------------------ Key: JBAS-5927 URL: https://jira.jboss.org/jira/browse/JBAS-5927 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assignee: Paul Gier Fix For: JBossAS-5.0.0.GA Produce the final release of the integration spis for AS5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1575) Upgrade to MC 2.0.0.CR5

by Carlo de Wolf (JIRA)

Upgrade to MC 2.0.0.CR5 ----------------------- Key: EJBTHREE-1575 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1575 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.0-Beta7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-382) VFSClassLoaderPolicy should support the security manager debug system property

by Anil Saldhana (JIRA)

VFSClassLoaderPolicy should support the security manager debug system property ------------------------------------------------------------------------------ Key: JBMICROCONT-382 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-382 Project: JBoss Microcontainer Issue Type: Sub-task Reporter: Anil Saldhana Assignee: Adrian Brock - access print all checkPermission results - jar print jar verification information - policy print policy information - scl print permissions assigned by the SecureClassLoader The access option has the following sub-options: - stack include stack trace - domain dump all domains in context - failure dump the stack and domain that did not have permission before throwing the exception For example, to print all checkPermission results and trace all domains in context, set java.security.debug to access,stack. To trace access failures, set it to access,failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2230) Internationalization problem with WSRP GUI

by Chris Laprun (JIRA)

Internationalization problem with WSRP GUI ------------------------------------------ Key: JBPORTAL-2230 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2230 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.7 Final, 2.7.0 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.0 Final, 2.6.8 Final BeanContext.createErrorMessage is not always properly called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBVFS-76) Add VFSUtils enable/disable options for VFS

by Ales Justin (JIRA)

Add VFSUtils enable/disable options for VFS ------------------------------------------- Key: JBVFS-76 URL: https://jira.jboss.org/jira/browse/JBVFS-76 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR5 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.GA We should be able to set options for VFS, same way we do it for VirtualFile - see VFSUtils. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6187) Break out profileservice spi from jboss-system.jar

by Scott M Stark (JIRA)

Break out profileservice spi from jboss-system.jar -------------------------------------------------- Key: JBAS-6187 URL: https://jira.jboss.org/jira/browse/JBAS-6187 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.0.0.CR2 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA The system module should have the profile service spi jars separated out so that admin clients can only depend on this jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6000) Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri()

by Stefan Ocke (JIRA)

Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri() -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-6000 URL: https://jira.jboss.org/jira/browse/JBAS-6000 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA Reporter: Stefan Ocke Assignee: Ales Justin To perform a JSR-88 deployment to a remotely installed server, the org.jboss.deployment.remoting.StreamingTarget seems to be the right target to use, since it perfomrs the file upload of the artificat to be deployed. However, StreamingTarget cannot really be used, since it is immpossible to construct a deployURI that is understood by both, StreamingTarget and org.jboss.deployment.spi.factories.DeploymentFactoryImpl.handleUri(): - DeploymentFactoryImpl.handleUri() understands the follwoing URIs: -- "http://org.jboss.deployment/jsr88" (only exact matches are allowed) -- URIs shaving scheme "jnp" - DeploymentManager impl only constructs a StreamingTarget, when the URI has a parameter "targetType=remote". This is in contradiction, wtih the excact matchin of "http://org.jboss.deployment/jsr88", sicne it just does not allow any parameters. So, to get a StreaminTarget, on has to use "jnp:" as scheme in the URI. - But: StreamingTarget cannot handle URIs starting with "jnp", but just schemes like "socket" or "http", where an according TransportClientFactory exists in jboss-remoting module. So in summary, handling of the deployURI seems to be quite inconsistent and works only for the local case and only if URI is "http://org.jboss.deployment/jsr88" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6152) URLComparator PrefixDeploymentSorter doesn't work for instance all in jboss 4.2.3GA only with instance "all"

by Benoit Reverbel (JIRA)

URLComparator PrefixDeploymentSorter doesn't work for instance all in jboss 4.2.3GA only with instance "all" ------------------------------------------------------------------------------------------------------------ Key: JBAS-6152 URL: https://jira.jboss.org/jira/browse/JBAS-6152 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-4.2.3.GA Environment: Windows XP Pro/Linux Red Hat Reporter: Benoit Reverbel Assignee: Ales Justin I used so far the PrefixDeploymentSorter to select in which order my archives would be deployed. It worked fine in JBoss AS 4.2.0GA. Now I am upgrading to JBoss AS 4.2.3GA and it seems not to work anymore (only for instance "all"). When I use instance "default", the deployer follows number prefixes of my archives: 1) 010-myear.ear 2) 020-myjar.jar 3) 030-mywar.war When using instance "all", it seems to use the default DeploymentSorter by deploying first service.xml, then my jars, after that my wars and at the end ears. 1) 020-myjar.jar 2) 030-mywar.war 3) 010-myear.ear As I need to use JBoss 4.2.3GA in cluster mode, it is mandatory for me to start from "all" instance. Is there any workaround or any special configuration to do ? Best Regards, Benoit Reverbel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBVFS-74) VFSCache::getFile should return null if no matching cache entry exists

by Ales Justin (JIRA)

VFSCache::getFile should return null if no matching cache entry exists ---------------------------------------------------------------------- Key: JBVFS-74 URL: https://jira.jboss.org/jira/browse/JBVFS-74 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR5 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.GA Change VFSCache::getFile to return null if no matching cache entry exists. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008