January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (EJBTHREE-488) Services annotated with @Service are not deployed from SARs

by Adam Warski (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-488?page=comments#action_12351679 ] Adam Warski commented on EJBTHREE-488: -------------------------------------- I also see this in RC9. > Services annotated with @Service are not deployed from SARs > ----------------------------------------------------------- > > Key: EJBTHREE-488 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-488 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC5 - PFD > Environment: JBoss 4.0.4RC1 > Reporter: Jeff Schnitzer > > If I create a service with the @Service annotation and package it in a SAR, it doesn't get deployed. If I package it in a JAR, it gets deployed. > Seems like this should work in a SAR. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3158) Need a way to detect collisions between JSF RI and JSF MyFaces

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3158?page=all ] Stan Silvert closed JBAS-3158. ------------------------------ Resolution: Done > Need a way to detect collisions between JSF RI and JSF MyFaces > -------------------------------------------------------------- > > Key: JBAS-3158 > URL: http://jira.jboss.com/jira/browse/JBAS-3158 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JavaServerFaces > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > Developers who choose to bundle the Sun JSF Reference Implementation with their WAR will get strange errors like ERROR [javax.faces.webapp.UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml. > This is because of collisions between classes provided in both implementations which are required to have the same javax.faces package name. We should be able to detect if the RI is present and tell the user to either remove the RI, remove MyFaces, or scope the deployment. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3158) Need a way to detect collisions between JSF RI and JSF MyFaces

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3158?page=all ] Stan Silvert updated JBAS-3158: ------------------------------- Component/s: JavaServerFaces > Need a way to detect collisions between JSF RI and JSF MyFaces > -------------------------------------------------------------- > > Key: JBAS-3158 > URL: http://jira.jboss.com/jira/browse/JBAS-3158 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JavaServerFaces > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > Developers who choose to bundle the Sun JSF Reference Implementation with their WAR will get strange errors like ERROR [javax.faces.webapp.UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml. > This is because of collisions between classes provided in both implementations which are required to have the same javax.faces package name. We should be able to detect if the RI is present and tell the user to either remove the RI, remove MyFaces, or scope the deployment. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3158) Need a way to detect collisions between JSF RI and JSF MyFaces

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3158?page=all ] Stan Silvert updated JBAS-3158: ------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 Added a warning message in 4.2 if MyFaces classes can be loaded. > Need a way to detect collisions between JSF RI and JSF MyFaces > -------------------------------------------------------------- > > Key: JBAS-3158 > URL: http://jira.jboss.com/jira/browse/JBAS-3158 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JavaServerFaces > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > Developers who choose to bundle the Sun JSF Reference Implementation with their WAR will get strange errors like ERROR [javax.faces.webapp.UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml. > This is because of collisions between classes provided in both implementations which are required to have the same javax.faces package name. We should be able to detect if the RI is present and tell the user to either remove the RI, remove MyFaces, or scope the deployment. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2470) Test multiple partitions and subsequent merges using Gossip Router

by Jerry Gauthier (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2470?page=comments#action_12351668 ] Jerry Gauthier commented on JBAS-2470: -------------------------------------- See JBAS-2560. Modified DRMTestCase.testIsMasterReplica() as specified to provide a test of multiple partitions with a subsequent merge using a GossipRouter. This change was successfully implemented in 4.2.0.CR1; the cluster merged properly when the router was restarted. This change was also implemented in 5.0.1.Beta2; the cluster failed to merge properly when the router was restarted. This is currently under investigation. > Test multiple partitions and subsequent merges using Gossip Router > ------------------------------------------------------------------ > > Key: JBAS-2470 > URL: http://jira.jboss.com/jira/browse/JBAS-2470 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Jerry Gauthier > Fix For: JBossAS-5.0.1.CR1 > > > Create tests of the merge handling of HAPartition and related classes by using a GossipRouter in the JGroups config. A split in the partition can be simulated by killing the GR, merge > can be triggered by restarting it. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2560) Replace the MockHAPartition unit test with one that uses a JGroups GossipRouter

by Jerry Gauthier (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2560?page=all ] Jerry Gauthier closed JBAS-2560. -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 JBossAS-4.2.0.CR1 (was: JBossAS-5.0.1.CR1) Resolution: Done Modified DRMTestCase.testIsMasterReplica() so that it uses a GossipRouter to simulate a cluster failure and subsequent merge. Implemented this change in 4.2.0.CR1 and 5.0.0.Beta2. > Replace the MockHAPartition unit test with one that uses a JGroups GossipRouter > ------------------------------------------------------------------------------- > > Key: JBAS-2560 > URL: http://jira.jboss.com/jira/browse/JBAS-2560 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering, Test Suite > Reporter: Brian Stansberry > Assigned To: Jerry Gauthier > Priority: Minor > Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-778) Clear testcases

by Clebert Suconic (JIRA)

Clear testcases --------------- Key: JBMESSAGING-778 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-778 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Priority: Critical Fix For: 1.2.0.Beta2 On this task I shall clear: org.jboss.test.messaging.jms 1030 tests, 14 errors, 1 failure org.jboss.test.messaging.jms.message 555 3 errors 2 failures (except org.jboss.test.messaging.jms.XATest.testConvertFromLocalTx as this is http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004783#4004783) -- 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

19 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAS-4019) failing org.jboss.test.security.test.SRPUnitTestCase - unlimited crypto support needed

by Dimitris Andreadis (JIRA)

failing org.jboss.test.security.test.SRPUnitTestCase - unlimited crypto support needed -------------------------------------------------------------------------------------- Key: JBAS-4019 URL: http://jira.jboss.com/jira/browse/JBAS-4019 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Ryan Campbell Priority: Critical Fix For: JBossAS-4.2.0.CR1 This is a recurring testsuite failure, whevever we update JDKs, in this case Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. The JDKs must be configured for unlimited crypto support as see in the linked case. To avoid this problem in the future, configuring crypto support should be part of the process of installing a new JDK. -- 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

19 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-4020) is system property for jgroups/jboss mcast_port missing?

by David (JIRA)

is system property for jgroups/jboss mcast_port missing? -------------------------------------------------------- Key: JBAS-4020 URL: http://jira.jboss.com/jira/browse/JBAS-4020 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.5.GA Environment: windows/linux, java 1.5.0_09, jboss 4.0.5GA, ejb3, clustered Reporter: David Assigned To: Brian Stansberry Priority: Minor The inclusion of system properties in cluster configuration is a very nice feature. It is my understanding that to make a unique cluster(when using UDP), one must specify all three of "mcast_addr", "mcast_port", and "jboss.partition.name:DefaultPartition". If this is the case, then would it make sense to include "mcast_port" system property and a related run.sh argument ? I've changed my cluster-service.xml to include this, and it does work(also nice that it works for this attribute as well) <UDP mcast_addr="${jboss.partition.udpGroup:228.1.2.3}" mcast_port="${jboss.partition.mcastPort:45566}" ip_ttl="${jgroups.mcast.ip_ttl:8}" ip_mcast="${jboss.cluster.mcast.enabled:true}" mcast_recv_buf_size="2000000" mcast_send_buf_size="640000" ucast_recv_buf_size="2000000" ucast_send_buf_size="640000" loopback="${jboss.cluster.use.loopback:false}"/> run.sh -c all -u224.1.1.39 -Djboss.partition.mcastPort=45577 This is probably only an issue if running more than one node on a machine -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-2395) Allow for easy configuration of mutlicast port like multicast address

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2395?page=all ] Brian Stansberry updated JBAS-2395: ----------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) Moving to 4.2.1.CR1 as that is when JBAS-3940 will be done. > Allow for easy configuration of mutlicast port like multicast address > --------------------------------------------------------------------- > > Key: JBAS-2395 > URL: http://jira.jboss.com/jira/browse/JBAS-2395 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 Final > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > This bug report suggests http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4701650 > suggests that the new "-u" option isn't going to work on all platforms so we should look at using the port instead. > See the forums discussion for more info. -- 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

19 years, 3 months

1
0
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 January 2007