October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-577) Handle sequence numbers properly for state transfer...

by Tim Fox (JIRA)

Handle sequence numbers properly for state transfer... ------------------------------------------------------ Key: JBMESSAGING-577 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-577 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Alpha1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 Need to handle sequence numbers properly for state transfer as described in the jgroups wiki about 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-591) MessageConsumerTest::testTimeoutReceiveOnClose can randomly fail

by Clebert Suconic (JIRA)

MessageConsumerTest::testTimeoutReceiveOnClose can randomly fail ---------------------------------------------------------------- Key: JBMESSAGING-591 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-591 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Alpha1, 1.0.1.CR5 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.0.1.GA, 1.2.0.Alpha2 If any GC happens during close and assertion happens, or any delay on creating the thread happens the test will fail. We need to find a testcase that is not so fragile. Probably using two distinct threads and notification. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1063) Special characters like " ' " (Apostrophe) not encoded in URLs for pages.

by Sandeep Pujar (JIRA)

Special characters like " ' " (Apostrophe) not encoded in URLs for pages. --------------------------------------------------------------------------- Key: JBPORTAL-1063 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1063 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Environment: JBoss AS 4.0.2 Reporter: Sandeep Pujar Assigned To: Julien Viet Priority: Minor Repro steps: 1. Login as admin, create a page with name - "tester's page". 2. A page link would appear on the nav bar as "tester's page". 3. Click on the link and it would not take you to the newly created page. The link points to <portal path>/tester it skips "'s page" part. This is because the path part of the URL is not encoded. The special character " ' " would appear as it is, hence would conflict with apostrophe in HTML tag href. The bug seems to be in the file: org.jboss.portal.core.model.portal.PortalObjectURLFactory method getBaseURL. Fix: Instead of replacing only the spaces in the objectref, URL encode the paths. Eg. If object refs is "portal.default.tester's page" Url encode every part of the path (portal , default, tester's page) seperately and then concatenate to build the URL. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-726) no injection of @Resource TimerService within Entity EJB

by James (JIRA)

no injection of @Resource TimerService within Entity EJB -------------------------------------------------------- Key: EJBTHREE-726 URL: http://jira.jboss.com/jira/browse/EJBTHREE-726 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss AS 4.0.4GA (via web installer), EJB 3.0 RC9, JDK 1.5.0_6, Windows XP Pro 2002 w/SP2 Reporter: James I'm working with 4.0.4GA and EJB3 RC9 on Java 1.5.0_06 (WinXP). Have created an entity bean with the container's timer service injected. When I reference the timer service, it is null. Under the same conditions, I am successful at injecting the timer service into both a MDB and a stateless session bean. No errors or warnings in compile or deployment with verbose output, only the NullPointerException when attempting to use the timer service. Here is what I am doing (simplified): @Entity public class MyEntity implements Serializable { @Resource private TimerService timerService; ... public createMyTimer() { try { if((timerService.getTimers()).isEmpty() == false) { ... The call to getTimers() throws the NullPointerException. I'm starting with a feature request, not sure this is a bug just yet. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-44) Dynamic proxy for shadow fact support

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-44?page=comments#action_12344641 ] Edson Tirelli commented on JBRULES-44: -------------------------------------- Shadow proxies integrated into core in revision #6602. Still pending issues are: 1. rename package when proxying java.* and javax.* classes 2. proxy all methods, not only "read" methods 3. change compiler to support proxy > Dynamic proxy for shadow fact support > ------------------------------------- > > Key: JBRULES-44 > URL: http://jira.jboss.com/jira/browse/JBRULES-44 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo, Manual, Drl Parser/Builder > Affects Versions: 3.1-m1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3742) Can't use . in username when using BaseCertLoginModule

by Scott M Stark (JIRA)

Can't use . in username when using BaseCertLoginModule ------------------------------------------------------ Key: JBAS-3742 URL: http://jira.jboss.com/jira/browse/JBAS-3742 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Scott M Stark Assigned To: Scott M Stark Attachments: patch.txt I have trying to use mod_jk + SSL + jboss and I have found that I can't have a '.' in the username. I am trying with the following user: +++ EMAILADDRESS=support(a)jboss.com, CN=support, OU=Jboss, O=Redhat, L=Neuchatel, ST=Neuchatel, C=CH +++ Find attached a patch thanks for committing it. (The patch is for jbossas-4.0.x). Cheers Jean-Frederic -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-589) DefaultClusteredPostOfficeTest::testClusteredNameUniqueness is failing

by Tim Fox (JIRA)

DefaultClusteredPostOfficeTest::testClusteredNameUniqueness is failing ---------------------------------------------------------------------- Key: JBMESSAGING-589 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-589 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Alpha1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 1) testClusteredNameUniqueness(org.jboss.test.messaging.core.plugin.postoffice.c luster.DefaultClusteredPostOfficeTest)java.lang.ClassCastException at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultRouter.add( DefaultRouter.java:90) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPo stOffice.addToConditionMap(DefaultClusteredPostOffice.java:1093) at org.jboss.messaging.core.plugin.postoffice.DefaultPostOffice.addBindi ng(DefaultPostOffice.java:553) at org.jboss.messaging.core.plugin.postoffice.DefaultPostOffice.bindQueu e(DefaultPostOffice.java:188) at org.jboss.test.messaging.core.plugin.postoffice.cluster.DefaultCluste redPostOfficeTest.testClusteredNameUniqueness(DefaultClusteredPostOfficeTest.jav a:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(Selecti veTestRunner.java:58) -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-147) Document Design Notes on Interaction Differences in the New Architecture

by John Gilbert (JIRA)

Document Design Notes on Interaction Differences in the New Architecture ------------------------------------------------------------------------ Key: JBESB-147 URL: http://jira.jboss.com/jira/browse/JBESB-147 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Reporter: John Gilbert Assigned To: Mark Little Priority: Minor Wiki Page: http://wiki.jboss.org/wiki/Wiki.jsp?page=InteractionDifferencesInTheNewAr... -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-571) Get unicast to work with clustering

by Tim Fox (JIRA)

Get unicast to work with clustering ----------------------------------- Key: JBMESSAGING-571 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-571 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 Currently we are using multicast in all cluster message sending, even when unicast will do. This is because when i tried unicast, the messages didn't get received. This should be fixed so unicast can be used in appropriate situations. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBSEAM-178) Cascading Message Bundles

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-178?page=all ] Gavin King updated JBSEAM-178: ------------------------------ Component/s: JSF (was: Core) Fix Version/s: 1.1 Priority: Major (was: Minor) The delimiited set of bundle names is great. I'm wondering if it also makes sense to support messages_foo.properties where /foo.jsp is the current viewId. > Cascading Message Bundles > ------------------------- > > Key: JBSEAM-178 > URL: http://jira.jboss.com/jira/browse/JBSEAM-178 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: James Woodward > Fix For: 1.1 > > > Would it be possible to get the Seam i18n features to scan for multiple resource bundles, so that common resources can be shared across mutliple applications? > Here's a few ways this could be accomplished: > 1) Rename the default bundle "messages.properties" to "seam-messages.properties", and scan for multiple seam-messages.properties in the EAR. > 2) Add a new property name, or change the resourceBundle.bundleName property, to handle a delimited list of resourceBundles. So the default implementation uses a single bundle "messages.properties", but by adding a configuration property you can get it to scan multiple resource bundles in the order specified. > e.g. > resourceBundle.bundleName=Messages.properties,GlobalMessages.properties > 3) Implement a cascading scheme, similar to the sample posted in the forum. -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006