October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-106) xsd:attribute ref not supported by SchemaBinding

by Anil Saldhana (JIRA)

xsd:attribute ref not supported by SchemaBinding ------------------------------------------------ Key: JBXB-106 URL: http://jira.jboss.com/jira/browse/JBXB-106 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.0.CR2 Reporter: Anil Saldhana Priority: Critical Refer to forum for additional details. -- 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

17 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-71) Making Http Request Parameters available to Login Modules via Callbacks

by Sriraman Gopalan (JIRA)

Making Http Request Parameters available to Login Modules via Callbacks ----------------------------------------------------------------------- Key: JBWEB-71 URL: http://jira.jboss.com/jira/browse/JBWEB-71 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Sriraman Gopalan Assigned To: Mladen Turk The details of the feature request are given in the forum under the following thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97420 -- 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

17 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4872) Invalid URI if the jboss.bind.address is IPv6

by Takayoshi Kimura (JIRA)

Invalid URI if the jboss.bind.address is IPv6 --------------------------------------------- Key: JBAS-4872 URL: http://jira.jboss.com/jira/browse/JBAS-4872 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.2.1.GA Reporter: Takayoshi Kimura Assigned To: Ron Sigal JBossRemoting uses jboss.bind.address in URI like the following: socket://${jboss.bind.address}:4446/?datatype=invocation However, if the jboss.bind.address is IPv6, it should be inside of square brackets. Invalid URI socket://::1:4446/?datatype=invocation Valid URI socket://[::1]:4446/?datatype=invocation To reproduce this issue: Run JBoss instance by the following commend on IPv6 enabled system. $ ./run.sh -c default -b ::1 Workaround: Edit JBossRemoting URL not to use jboss.bind.address. Note: IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6 parsing needs updated version of JBossRemoting. http://jira.jboss.com/jira/browse/JBREM-645 -- 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

17 years, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4669) Port ClusteredSingleSignOn testNoAuthSingleSignOn test to trunk

by Brian Stansberry (JIRA)

Port ClusteredSingleSignOn testNoAuthSingleSignOn test to trunk --------------------------------------------------------------- Key: JBAS-4669 URL: http://jira.jboss.com/jira/browse/JBAS-4669 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Port from Branch_4_2. -- 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

17 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4616) NamingContext lookupLink() does not acquire stub to server Naming service

by Brian Stansberry (JIRA)

NamingContext lookupLink() does not acquire stub to server Naming service ------------------------------------------------------------------------- Key: JBAS-4616 URL: http://jira.jboss.com/jira/browse/JBAS-4616 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 org.jnp.interfaces.NamingContext.lookupLink(Name) does not invoke the checkRef() method before invoking on the stub to the server-side Naming object. The checkRef() method is what actually contacts the JNDI server to download the stub.. Result of this is an NPE will be thrown if an earlier call hasn't downloaded the stub before lookupLink() is called. -- 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

17 years, 12 months

1
8
0 / 0

[JBoss JIRA] Created: (JBWEB-87) JasperException for JSP page using generics

by David Ward (JIRA)

JasperException for JSP page using generics ------------------------------------------- Key: JBWEB-87 URL: http://jira.jboss.com/jira/browse/JBWEB-87 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Customer submitted using AS 4.2.0.GA and Sun JDK 1.5.0_11. I verified using AS 4.2.0.GA and AS 4.2.1.GA and Sun JDK 1.6.0_02. Reporter: David Ward Assigned To: Mladen Turk I am submitting this as a JBoss Web bug; not sure if it should have been submitted as an AS bug instead... This test.jsp page does not compile in AS 4.2.0 or AS 4.2.1: <%@page contentType="text/html" import="java.util.*" %> <html><head><title>test</title></head><body> <% Vector<String> v = (Vector<String>)request.getSession().getAttribute("v"); out.println("v: " + v); %> </body></html> However, it does with a workaround (please see "Workaround Description" below). I believe that this is a bug since we require a 1.5 JVM for AS 4.2.x. Here is the error without using the workaround: 15:41:21,960 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 4 in the jsp file: /test.jsp The type Vector is not generic; it cannot be parameterized with arguments <String> 1: <%@page contentType="text/html" import="java.util.*" %> 2: <html><head><title>test</title></head><body> 3: <% 4: Vector<String> v = (Vector<String>)request.getSession().getAttribute("v"); 5: out.println("v: " + v); 6: %> 7: </body></html> An error occurred at line: 4 in the jsp file: /test.jsp Syntax error, parameterized types are only available if source level is 5.0 1: <%@page contentType="text/html" import="java.util.*" %> 2: <html><head><title>test</title></head><body> 3: <% 4: Vector<String> v = (Vector<String>)request.getSession().getAttribute("v"); 5: out.println("v: " + v); 6: %> 7: </body></html> An error occurred at line: 4 in the jsp file: /test.jsp The type Vector is not generic; it cannot be parameterized with arguments <String> 1: <%@page contentType="text/html" import="java.util.*" %> 2: <html><head><title>test</title></head><body> 3: <% 4: Vector<String> v = (Vector<String>)request.getSession().getAttribute("v"); 5: out.println("v: " + v); 6: %> 7: </body></html> An error occurred at line: 4 in the jsp file: /test.jsp Syntax error, parameterized types are only available if source level is 5.0 1: <%@page contentType="text/html" import="java.util.*" %> 2: <html><head><title>test</title></head><body> 3: <% 4: Vector<String> v = (Vector<String>)request.getSession().getAttribute("v"); 5: out.println("v: " + v); 6: %> 7: </body></html> Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:308) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

17 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-70) Add

by Amit Kasher (JIRA)

Add ---- Key: JBWEB-70 URL: http://jira.jboss.com/jira/browse/JBWEB-70 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Amit Kasher Assigned To: Mladen Turk -- 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

17 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-65) context.xml is ignored.

by Nicolas Leroux (JIRA)

context.xml is ignored. ----------------------- Key: JBWEB-65 URL: http://jira.jboss.com/jira/browse/JBWEB-65 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Standalone 4.0.4 RC1 Reporter: Nicolas Leroux Assigned To: Mladen Turk The context.xml file is ignored by jboss. It's thus impossible to setup the docRoot property. I followed the wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingContextDotXML without any success (The context.xml is in my META-INF). -- 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

17 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4282) Can't create a root context web app

by Stan Silvert (JIRA)

Can't create a root context web app ----------------------------------- Key: JBAS-4282 URL: http://jira.jboss.com/jira/browse/JBAS-4282 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Remy Maucherat I am unable to deploy a web app as root context using the instructions here: http://wiki.jboss.org/wiki/Wiki.jsp?page=SetupARootContextApp One thing that is unclear is if ROOT.war "must" be removed from /deploy. In 4.2, root context web apps do not require removal of ROOT.war. IMHO, this is how it should work. If you deploy a WAR as the root context, it should simply override whatever was there before. If ROOT.war is removed, 5.0 will allow a root context web app as long as it is deployed from an EAR and specified as such in application.xml. Otherwise, it will fail. If you choose to deploy a stand-alone WAR and specify it as root context using jboss-web.xml, it will always fail - regardless of whether or not you remove ROOT.war. I have committed a test for root deployment in both 4.2 and 5.0. The test passes in 4.2, but not in 5.0. You can run it with: build one-test -Dtest=org.jboss.test.web.test.RootContextUnitTestCase -- 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

17 years, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-494) Investigate marshalling format to simplify wireshark / ethereal plugin

by Bela Ban (JIRA)

Investigate marshalling format to simplify wireshark / ethereal plugin ----------------------------------------------------------------------- Key: JGRP-494 URL: http://jira.jboss.com/jira/browse/JGRP-494 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Currently, parsing JGroups network data via wireshark is difficult: - message lists don't have (a) total number of bytes and (b) bytes/message and - headers don't have (a) total bytes for all headers and (b) bytes / header Investigate whether we can change the marshalling format to accommodate the wireshark plugin. This has the nice side effect that the JGroups wire format becomes standardized, ie. each header has the same format. This allows us to display a header even if we don't know how to parse it. In this case, we'd simply display the name and number of bytes. Caveat: we want to avoid having to make messages bigger when marshalled. -- 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

17 years, 12 months

2
5
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 October 2007