June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-216) integration with the eclipse bpel designer

by Alejandro Guizar (JIRA)

integration with the eclipse bpel designer ------------------------------------------ Key: BPEL-216 URL: http://jira.jboss.com/jira/browse/BPEL-216 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 Enable one-step deployment of a bpel process + interface wsdl definitions. -- 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

18 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4068) Port JBAS-4067 fix to trunk

by Brian Stansberry (JIRA)

Port JBAS-4067 fix to trunk --------------------------- Key: JBAS-4068 URL: http://jira.jboss.com/jira/browse/JBAS-4068 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 -- 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

18 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3527) Tomcat 6 fixes needed for JSF

by Stan Silvert (JIRA)

Tomcat 6 fixes needed for JSF ----------------------------- Key: JBAS-3527 URL: http://jira.jboss.com/jira/browse/JBAS-3527 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta Reporter: Stan Silvert Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.GA This JIRA task is for tracking the Tomcat 6 bugs that need to be fixed for JSF in JBoss AS 5.0.0 http://issues.apache.org/bugzilla/show_bug.cgi?id=39803 http://issues.apache.org/bugzilla/show_bug.cgi?id=39805 http://issues.apache.org/bugzilla/show_bug.cgi?id=40279 We have a workaround for this one, but it would be nice if it were fixed: http://issues.apache.org/bugzilla/show_bug.cgi?id=39804 -- 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

18 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException

by Anil Saldhana (JIRA)

Redeploy of Tomcat5 Service chokes with RuntimeException -------------------------------------------------------- Key: JBAS-3517 URL: http://jira.jboss.com/jira/browse/JBAS-3517 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens. You will notice the following Runtime Exception and the tomcat service fails to deploy. ============================================================================================== 13:33:30,421 INFO [Catalina] Initialization processed in 562 ms 13:33:30,421 INFO [StandardService] Starting service jboss.web 13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1 7 13:33:30,453 INFO [StandardHost] XML validation disabled 13:33:30,468 INFO [Catalina] Server startup in 47 ms 13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185) at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) =================================================================================== Use the following api of PolicyContext in Tomcat5 service http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h... -- 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

18 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4198) Align EJB3 Security with JEE 1.4 Behavior

by Anil Saldhana (JIRA)

Align EJB3 Security with JEE 1.4 Behavior ----------------------------------------- Key: JBAS-4198 URL: http://jira.jboss.com/jira/browse/JBAS-4198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Anil Saldhana Assigned To: Bill Burke Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.1.CR1 EJB3 security layer needs to be aligned with the ejb2 security layer. There is a need to sync up metadata and maybe pull a common abstract layer out such that there is alignment. -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-896) Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor

by Carlo de Wolf (JIRA)

Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor --------------------------------------------------------------------------------------------- Key: EJBTHREE-896 URL: http://jira.jboss.com/jira/browse/EJBTHREE-896 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: interceptor2 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical -- 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

18 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1082) Optimise nodes for single elements

by Manik Surtani (JIRA)

Optimise nodes for single elements ---------------------------------- Key: JBCACHE-1082 URL: http://jira.jboss.com/jira/browse/JBCACHE-1082 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR3, 2.0.0.GA Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should: 1) Create a reference to 2 Objects for key and value, as well as a Map. 2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair 3) Otherwise just hold the key/value pair as direct object refs. Would affect UnversionedNode and WorkspaceNodeImpl. -- 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

18 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1009) Support preload functionality as part of region activation

by Brian Stansberry (JIRA)

Support preload functionality as part of region activation ---------------------------------------------------------- Key: JBCACHE-1009 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Manik Surtani Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region. If one of the defined preload regions names a subregion of the region being activated, preload the subregion. -- 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

18 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4220) Hot deployment of jars does not always work

by Scott M Stark (JIRA)

Hot deployment of jars does not always work ------------------------------------------- Key: JBAS-4220 URL: http://jira.jboss.com/jira/browse/JBAS-4220 Project: JBoss Application Server Issue Type: Bug 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 Due to JBMICROCONT-160, redeployment of an existing jar may not work. -- 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

18 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly

by David Kilzer (JIRA)

org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly -------------------------------------------------------------------------------------------------------- Key: JBAS-3775 URL: http://jira.jboss.com/jira/browse/JBAS-3775 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.2 Final Environment: Microsoft Windows XP [Version 5.1.2600] java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) Xerces-J 2.6.2 Reporter: David Kilzer Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run outside of JBoss. The particular code run under JBoss was started through a Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the culprit (file path changed to protect the innocent): java.io.FileNotFoundException: \c$\path\to\file.xml at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89) at java.net.URL.openStream(URL.java:1007) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172) [...] Here is some sample code that should reproduce the issue. Note the path used to create the java.io.File object. File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"): DocumentBuilderFactory factory = new org.apache.xerces.jaxp.DocumentBuilderFactoryImpl(); factory.setNamespaceAware(false); factory.setValidating(false); DocumentBuilder builder = factory.newDocumentBuilder(); Document document = builder.parse(xmlFile); // exception thrown under JBossAS The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.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

18 years, 1 month

3
3
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 June 2007