July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-71) homeJndiName is not merged properly for JBossSessionBeanMetaData

by Emanuel Muckenhuber (JIRA)

homeJndiName is not merged properly for JBossSessionBeanMetaData ---------------------------------------------------------------- Key: JBMETA-71 URL: http://jira.jboss.com/jira/browse/JBMETA-71 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Emanuel Muckenhuber Assigned To: Emanuel Muckenhuber Fix For: 1.0.0.Beta28 -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4933) Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1)

by Dimitris Andreadis (JIRA)

Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1) --------------------------------------------- Key: JBAS-4933 URL: http://jira.jboss.com/jira/browse/JBAS-4933 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XML services Affects Versions: JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.3.GA Needed for fixing JBXB-115 (and anything else that pops up). -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5727) Upgrade javassist to 3.8.0.GA

by Kabir Khan (JIRA)

Upgrade javassist to 3.8.0.GA ----------------------------- Key: JBAS-5727 URL: http://jira.jboss.com/jira/browse/JBAS-5727 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5684) servlets are not properly loaded when load-at-startup is 0

by Matt Wringe (JIRA)

servlets are not properly loaded when load-at-startup is 0 ---------------------------------------------------------- Key: JBAS-5684 URL: http://jira.jboss.com/jira/browse/JBAS-5684 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta4 Environment: JBossAS 5.0.0.Beta4 and the current svn head Java 1.5 Linux Reporter: Matt Wringe Assigned To: Remy Maucherat JBoss web does not properly load servlets when load-at-startup is set to 0. For example the following in the web.xml file will not load the servlet at deployment (setting load-on-startup to something higher than 0 will result in it being properly loaded). <servlet> <servlet-name>TestServlet0</servlet-name> <servlet-class>test.TestServlet0</servlet-class> <load-on-startup>0</load-on-startup> </servlet> According to the 2.5 servlet spec, this should be the case "If the value is a positive integer or 0, the container must load and initialize the servlet as the application is deployed" (http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd) -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Updated: (JBAS-1549) utility JARs incorrectly deployed

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1549?page=all ] Dimitris Andreadis updated JBAS-1549: ------------------------------------- Fix Version/s: (was: JBossAS-3.2.8.SP2) Unschedule 3.2.8.SP2 tasks, since we are not going to produce another release from that branch. > utility JARs incorrectly deployed > --------------------------------- > > Key: JBAS-1549 > URL: http://jira.jboss.com/jira/browse/JBAS-1549 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Affects Versions: JBossAS-3.2.7 Final > Environment: Windows XP SP2 > Sun JDK 1.3.1_15 > Reporter: Erik Post > > Utility JARs in EARs are not correctly added to the classpath of Web modules (and possibly EJB modules) when these utility JARs contain a META-INF\ejb-jar.xml file, and when EARs are deployed using isolated class loaders. > Consider the following situation: > Code: > test.ear > META-INF\ > application.xml > web1.war > META-INF\ > MANIFEST.MF > web.xml > ejb1.jar > META-INF\ > ejb-jar.xml > > The application.xml only defines the web module: > Code: > <application> > <display-name>TestEAR</display-name> > <module> > <web> > <web-uri>web.war</web-uri> > <context-root>/web</context-root> > </web> > </module> > </application> > > Ejb1.jar is not listed as an EJB module. The web1.war MANIFEST.MF lists ejb1.jar. The web module contains a servlet that references a class in ejb1.jar. Ejb1.jar is thus used as an utility Jar. > The EAR is isolated in its own classloader space via the following configuration in conf\jboss-service.xml: > Code: >  > <mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer"> >  > <attribute name="Isolated">true</attribute> >  > <attribute name="CallByValue">true</attribute> > </mbean> > > When the servlet is executed, a NoClassDefFoundError occurs for the references class that is in ejb1.jar. For comparison, the above setup works on WebSphere 5.0. > Debugging and stepping through JBoss shows that the MainDeployer does not add ejb1.jar to the web module's classpath, because ejb1.jar is considered as an EJB module (ie an EJBDeployer is returned for the module). Only modules that are accepted by the JARDeployer are added to the classpath. > Adding ejb1.jar as a java module in the application deployment descriptor does not solve the problem, because the jar file is then deployed as an EJB module. Removing ejb-jar.xml from ejb1.jar does work, but that is not really an option in out project, as the Jar file is not under our control. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1493) IsCallerInRole with anonymous caller/run-as does not see run-as role

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1493?page=all ] Dimitris Andreadis updated JBAS-1493: ------------------------------------- Fix Version/s: (was: JBossAS-3.2.8.SP2) Unschedule 3.2.8.SP2 tasks, since we are not going to produce another release from that branch. > IsCallerInRole with anonymous caller/run-as does not see run-as role > -------------------------------------------------------------------- > > Key: JBAS-1493 > URL: http://jira.jboss.com/jira/browse/JBAS-1493 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-3.2.7 Final > Environment: EJBSpecUnitTestCase.testMDBDeepRunAs > Reporter: Scott M Stark > Assigned To: Scott M Stark > > And MDB using a run-as role along a call path: > DeepRunAsMDB -> Level1MDBCallerBean.callEcho() -> > Level2CallerBean.invokeEcho() -> Level3CalleeBean.echo() > properly uses the run-as role for access to the ejbs, but we have a weaker notion in 3.2 vs 4.0 of how the run-as should show up in the isCallerInRole context call, and this test validates that the run-as role is seen by isCallerInRole. The 3.2 implementation needs to be updated to support this 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2441) Duplicate target '_jars-util' in test-jars.xml of jboss-3.2

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2441?page=all ] Dimitris Andreadis updated JBAS-2441: ------------------------------------- Fix Version/s: (was: JBossAS-3.2.8.SP2) Unschedule 3.2.8.SP2 tasks, since we are not going to produce another release from that branch. > Duplicate target '_jars-util' in test-jars.xml of jboss-3.2 > ----------------------------------------------------------- > > Key: JBAS-2441 > URL: http://jira.jboss.com/jira/browse/JBAS-2441 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Rajesh Rajasekaran > > Duplicate target '_jars-util' in jboss-3.2\testsuite\imports\test-jars.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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3836) Conditional setting of -server may not be supported on sun jdk1.3

by Dimitris Andreadis (JIRA)

Conditional setting of -server may not be supported on sun jdk1.3 ----------------------------------------------------------------- Key: JBAS-3836 URL: http://jira.jboss.com/jira/browse/JBAS-3836 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-3.2.8.SP2 The change in JBAS-3458 conditionally sets -server. Although sun jdk1.3 seems to support -server, it fails with: Unrecognized option: -server (although the forum post refers erroneously to 4.0.5, the error appears in the 3.2 branch, too). -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3154) Cleanup the remoting module in 3.2.x

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3154?page=all ] Dimitris Andreadis updated JBAS-3154: ------------------------------------- Fix Version/s: (was: JBossAS-3.2.8.SP2) Unschedule 3.2.8.SP2 tasks, since we are not going to produce another release from that branch. > Cleanup the remoting module in 3.2.x > ------------------------------------ > > Key: JBAS-3154 > URL: http://jira.jboss.com/jira/browse/JBAS-3154 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Remoting > Affects Versions: JBossAS-3.2.8.SP1 > Reporter: Dimitris Andreadis > Assigned To: Tom Elrod > > Having removed the sources with proprietary licenses and files depending on them (all of them are tests), we need to further cleanup the remoting module in 3.2.x. As far I can tell, this is obsolete. There is only a remoting.sar installed in docs\example\remoting, who's META-INF descriptor needs renaming to jboss-service.xml to deploy properly (it does deploy with this change). > The files removed where: > src/main/test/classloading/InvokerTestCase.java > src/main/test/ComplexReturn.java > InvokerClientTest.java InvokerServerTest.java > InvokerTestCase.java OnewayInvokerServerTest.java > OnewayInvokerTestCase.java > src/main/test/classloading/server/InvokerServerNoClientTest.java > InvokerServerNoSecurityTest.java > InvokerServerNoServerTest.java > InvokerServerSecureTest.java > src/main/test/detection/DetectorUtil.java > src/main/org/jboss/remoting/transport/test/TransportTest.java > src/main/org/jboss/remoting/transport/mock/MockServerInvocationHandler.java MockTest.java > src/main/test/performance/TestServerInvocationHandler.java -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5503) JUnitReport OutOfMemoryError failed many testsuite on hudson

by Jeff Zhang (JIRA)

JUnitReport OutOfMemoryError failed many testsuite on hudson ------------------------------------------------------------ Key: JBAS-5503 URL: http://jira.jboss.com/jira/browse/JBAS-5503 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: Backlog Environment: Linux, Windows Reporter: Jeff Zhang Priority: Minor Fix For: JBossAS-5.0.0.CR1 We can see JunitReport Task throw OutOfMemeoryError on hudson testsuite tests both on JDK5 and JDK6. Manually increase -Xmx in ANT_OPTS can resolve this problem -- 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, 6 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008