February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1900) setContentType is now optional in JSR 286

by Thomas Heute (JIRA)

setContentType is now optional in JSR 286 ----------------------------------------- Key: JBPORTAL-1900 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1900 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Thomas Heute Assigned To: Julien Viet Fix For: Portlet-2.0 JSR-286 spec says: RenderResponse.setContentType is no longer required before calling getWriter or getOutputstream. Calling getWriter or getOutputstream without previously setting the content type results no longer in an IllegalStateException in V 2.0. Right now it still result in an IllegalStateException -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5126) Stax API is duplicated in lib/stax-api.jar and server/lib/jboss-javaee.jar

by Thomas Diesler (JIRA)

Stax API is duplicated in lib/stax-api.jar and server/lib/jboss-javaee.jar -------------------------------------------------------------------------- Key: JBAS-5126 URL: http://jira.jboss.com/jira/browse/JBAS-5126 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBXB-117) Map binding annotations

by Alexey Loubyansky (JIRA)

Map binding annotations ----------------------- Key: JBXB-117 URL: http://jira.jboss.com/jira/browse/JBXB-117 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR5 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-2.0.0.CR6 Currently maps are bound with @XmlJavaTypeAdapter. See org.jboss.test.xb.builder.object.element.javatypeadapter.test.JavaTypeAdapterUnitTestCase. There was an idea to add map-specific binding annotations. -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-854) Mechanism for interceptor-level communications

by David Lloyd (JIRA)

Mechanism for interceptor-level communications ---------------------------------------------- Key: JBREM-854 URL: http://jira.jboss.com/jira/browse/JBREM-854 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 Need a way for interceptors to "talk" across the wire, to implement interceptor operations and share state. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-643) ClassConfigurator.getInstance() not thread safe

by Michael Newcomb (JIRA)

ClassConfigurator.getInstance() not thread safe ----------------------------------------------- Key: JGRP-643 URL: http://jira.jboss.com/jira/browse/JGRP-643 Project: JGroups Issue Type: Bug Reporter: Michael Newcomb Assigned To: Bela Ban Creating 2 or more JChannels simultaneously could result in multiple ClassConfigurators being created and inited at once or a ClassConfigurator being used before it has been inited. Recommend synchronizing the getInstance() method. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Commented: (JBAS-5251) Move all JBoss AS documentation to docs.jboss.org

by Mark Newton (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-5251?page=comments#action_12400471 ] Mark Newton commented on JBAS-5251: ----------------------------------- Once all of the existing content on docs.jboss.org has been moved then we need to move over the 4.2.2 beta and 5.0.0 beta content from the JBoss Labs CMS. As this is still labelled as beta material it seems reasonable to not use redirects from the old locations. This keeps things simple and allows us to remove all of the files from JBoss Labs CMS. The amount of data that needs to be moved can be determined using the 'du -I \.svn -c -h' command from the relevant directory having performed a checkout from SVN: 5.0.0 beta - Installation Guide 1.2M Getting Started Guide 2.0M Configuration Guide 26M Clustering Guide 2.0M 4.2.2 beta - Installation Guide 2.1M Getting Started Guide 2.7M Configuration Guide 21M Clustering Guide 3.1M Total: 60.1MB > Move all JBoss AS documentation to docs.jboss.org > ------------------------------------------------- > > Key: JBAS-5251 > URL: http://jira.jboss.com/jira/browse/JBAS-5251 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Mark Newton > Assigned To: Mark Newton > > JBoss AS documentation should be centralised on docs.jboss.org. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-5251) Move all JBoss AS documentation to docs.jboss.org

by Mark Newton (JIRA)

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-548) TCP_NIO: include in cruise control (beside UDP, TCP and MUX)

by Bela Ban (JIRA)

TCP_NIO: include in cruise control (beside UDP, TCP and MUX) ------------------------------------------------------------ Key: JGRP-548 URL: http://jira.jboss.com/jira/browse/JGRP-548 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-688) Need to report root causes to end user as exception in code

by Dipak Kothari (JIRA)

Need to report root causes to end user as exception in code ----------------------------------------------------------- Key: JGRP-688 URL: http://jira.jboss.com/jira/browse/JGRP-688 Project: JGroups Issue Type: Task Affects Versions: 2.6.1 Environment: Windows/Linux Reporter: Dipak Kothari Assigned To: Bela Ban An example of what exception is received at the application level when an incorrect host has been specified in the protocol properties: org.jgroups.ChannelException: unable to setup the protocol stack at org.jgroups.JChannel.init(JChannel.java:1403) at org.jgroups.JChannel.<init>(JChannel.java:279) at org.jgroups.JChannelFactory.createChannel(JChannelFactory.java:308) at com.ubs.apm.control.service.nameservice.jgroup.JGroupNameService.init(JGroupNameService.java:82) at com.ubs.apm.control.service.nameservice.jgroup.JGroupTest.testPropertiesLoad(JGroupTest.java:17) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.lang.IllegalArgumentException: the following properties in TCPPING are not recognized: {num_initial_members=1, timeout=3000} at org.jgroups.stack.Configurator$ProtocolConfiguration.createLayer(Configurator.java:700) at org.jgroups.stack.Configurator$ProtocolConfiguration.access$000(Configurator.java:595) at org.jgroups.stack.Configurator.createProtocols(Configurator.java:375) at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:58) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:205) at org.jgroups.JChannel.init(JChannel.java:1400) ... 27 more either you have to look into the code or enable correct logging level to see real cause. What would be useful is to see the actual cause of exception at the application layer. -- 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, 5 months

2
2
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 February 2008