March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7801) Delete asynch tests in aspects module

by Brian Stansberry (JIRA)

Delete asynch tests in aspects module ------------------------------------- Key: JBAS-7801 URL: https://jira.jboss.org/jira/browse/JBAS-7801 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Aspects Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M3 The classes in https://svn.jboss.org/repos/jbossas/trunk/aspects/src/test/java/org/jboss... don't compile because the classes being tested don't exist. If they do still exist in some project somewhere, whoever maintains them should find these tests on some old AS branch and port them to that project. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7788) <check-valid-connection-sql> done after a failure maybe?

by deanhiller (JIRA)

<check-valid-connection-sql> done after a failure maybe? -------------------------------------------------------- Key: JBAS-7788 URL: https://jira.jboss.org/jira/browse/JBAS-7788 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3, Hibernate service Affects Versions: JBossAS-5.1.0.GA Reporter: deanhiller Assignee: Carlo de Wolf Priority: Critical related directly to this bug in seam https://jira.jboss.org/jira/browse/JBSEAM-4528 I would prefer the <check-valid-connection-sql> be run AFTER any exceptions from the jdbc api rather than before it. This would fix half the bug in the ticket referred to above(at least with postgres' case).... ie. 1. go get a wrapper connection(not from pool) 2. when you make a real jdbc call, go get the real connection from the pool 3. if that jdbc call fails with an exception, run the check-valid-connection-sql 4. If check-valid-connection-sql fails, go get another connection from pool(or create one) and if fails, move to next 5. once all connections are exhausted, throw exception back to framework or whoever called the jdbc call. NOTE: This gives the performance benefit on sunny day we are never running the check valid connection sql. It also solves half of the ticket above which tends to break postgres/jboss/seam combination from working. I have to have check valid connection sql or my seam app never recovers from a db outage but having that also causes all normal seam pages that don't need the database to spin the browser into infinite redirect(ie. if I hit login page it comes up in jboss/seam IF AND ONLY IF I don't have check-valid-connection-sql set). thanks, Dean -- 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

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1995) Invoking SessionContext.getCallerPrincipal inside @Init method of SFSB should return correct principal

by Marcus Moyses (JIRA)

Invoking SessionContext.getCallerPrincipal inside @Init method of SFSB should return correct principal ------------------------------------------------------------------------------------------------------ Key: EJBTHREE-1995 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1995 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Reporter: Marcus Moyses In EAP 4.x, this scenario throws "IllegalStateException: No valid security context for the caller identity" and in EAP 5 it throws "llegalStateException: getCallerPrincipal not allowed during injection (EJB3 4.4.1 & 4.5.2)" -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBVFS-149) VirtualFileURLConnection does not override getContentType()

by Alessio Soldano (JIRA)

VirtualFileURLConnection does not override getContentType() ----------------------------------------------------------- Key: JBVFS-149 URL: https://jira.jboss.org/jira/browse/JBVFS-149 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR3 Reporter: Alessio Soldano While overriding URLConnection:getContentType() seems at first not required, this is currently causing regressions in JBossWS SwA testsuite. When the user provides a DataHandler as a parameter for an attachment, JBossWS needs to get the content-type from it. DataHandler (javax.activation) delegates to its datasource, which in in the example below is a URLDataSource. The URLDataSource simply opens a connection from the url and calls getContentType on it. Since VirtualFileURLConnection does not override getContentType(), it uses the impl in java.net.URLConnection, which simply returns null. Before the changes for VFS3, this was using the Sun's impl sun.net.www.URLConnection which redefines the getContentType() and leverages the convenient method guessContentTypeFromName(..) from java.net.URLConnection. Example: InitialContext iniCtx = getInitialContext(); Service service = (Service)iniCtx.lookup("java:comp/env/service/AttachmentService"); Attachment port = (Attachment)service.getPort(Attachment.class); URL url = new File("jaxrpc/samples/swa/attach.gif").toURL(); String value = port.send("Some text message", new DataHandler(url)); -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBVFS-150) Introduce Mount interface to grant the caller access to the mount source

by John Bailey (JIRA)

Introduce Mount interface to grant the caller access to the mount source ------------------------------------------------------------------------ Key: JBVFS-150 URL: https://jira.jboss.org/jira/browse/JBVFS-150 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR3 Reporter: John Bailey Assignee: John Bailey Fix For: 3.0.0.CR4 Introduce new Mount interface to allow the caller to VFS.mount* to get access to the mount source. This should be the copy of the file for archives files. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7800) Upgrade wsdl4j to 1.6.2

by Alessio Soldano (JIRA)

Upgrade wsdl4j to 1.6.2 ----------------------- Key: JBAS-7800 URL: https://jira.jboss.org/jira/browse/JBAS-7800 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: JBossAS-6.0.0.M3 Now that the VFS3 causes org.jboss.vfs.protocol.FileURLConnection to be used, the wsdl4j's StringUtils throws IllegalArgumentException when calling getContent() on the file url connection and not getting back an InputStream. This issue in 1.6.1 has already been fixed in 1.6.2. Release notes for 1.6.2: http://sourceforge.net/project/shownotes.php?release_id=461975 -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-104) Remove javadoc warnings from jboss-classpool project

by Flavia Rainone (JIRA)

Remove javadoc warnings from jboss-classpool project ---------------------------------------------------- Key: JBREFLECT-104 URL: https://jira.jboss.org/jira/browse/JBREFLECT-104 Project: JBoss Reflection Issue Type: Sub-task Components: Class Pool Affects Versions: JBossReflection.2.2.0-Alpha3 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Alpha4 There should be no broken javadoc comments in the jboss-classpool project -- 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

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-7799) DeploymentManager fails to specify a context when unable to determine the module type

by Carlo de Wolf (JIRA)

DeploymentManager fails to specify a context when unable to determine the module type ------------------------------------------------------------------------------------- Key: JBAS-7799 URL: https://jira.jboss.org/jira/browse/JBAS-7799 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Minor Fix For: JBossAS-6.0.0.M3 java.lang.RuntimeException: cannot obtain module type at org.jboss.deployment.spi.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:533) -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7794) Integrate Remoting into AS

by David Lloyd (JIRA)

Integrate Remoting into AS -------------------------- Key: JBAS-7794 URL: https://jira.jboss.org/jira/browse/JBAS-7794 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 Name it jboss-remoting-3.jar so that it doesn't conflict with R2 during the migration -- 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

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7795) Integrate Remoting Metadata

by David Lloyd (JIRA)

Integrate Remoting Metadata --------------------------- Key: JBAS-7795 URL: https://jira.jboss.org/jira/browse/JBAS-7795 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 jboss-remoting.xml descriptor tags and deployer. -- 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

14 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010