August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Tim Fox updated JBMESSAGING-412: -------------------------------- Assignee: (was: Sergey Koshcheyev) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Priority: Minor > Fix For: 2.0.0 Beta 1 > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1029) Deadlock in messaging postoffice

by Tim Fox (JIRA)

Deadlock in messaging postoffice -------------------------------- Key: JBMESSAGING-1029 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1029 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1616) Portal link should redirect to the default page of the default portal

by Thomas Heute (JIRA)

Portal link should redirect to the default page of the default portal --------------------------------------------------------------------- Key: JBPORTAL-1616 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1616 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.1 Final Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.2 Final -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1078) Allow static expressions in value restrictions

by Alexandre Gattiker (JIRA)

Allow static expressions in value restrictions ---------------------------------------------- Key: JBRULES-1078 URL: http://jira.jboss.com/jira/browse/JBRULES-1078 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexandre Gattiker Assigned To: Mark Proctor Would it be possible to allow the following two rules to work? In 4.0.0.GA, I get parsing errors for both. rule "sample rule 1" when Object(toString == String.valueOf("196071")) then System.out.println("ok"); end rule "sample rule 2" when Object(toString == new String("196071")) then System.out.println("ok"); end (In my particular case, I need to compare BigDecimal values). -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBAOP-200) Make sure the batch and sh files work

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-200?page=comments#action_12371856 ] Kabir Khan commented on JBAOP-200: ---------------------------------- So fix the encoding :-) > Make sure the batch and sh files work > ------------------------------------- > > Key: JBAOP-200 > URL: http://jira.jboss.com/jira/browse/JBAOP-200 > Project: JBoss AOP > Issue Type: Bug > Reporter: Kabir Khan > Assigned To: Stale Pedersen > Fix For: 2.0.0.GA > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-111) Add ability to forward and reverse map Semantic Elements to/from Dom Node/Xml Adapters jpdl

by Matthew Sandoz (JIRA)

Add ability to forward and reverse map Semantic Elements to/from Dom Node/Xml Adapters jpdl ------------------------------------------------------------------------------------------- Key: GPD-111 URL: http://jira.jboss.com/jira/browse/GPD-111 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Environment: all? :) Reporter: Matthew Sandoz Assigned To: Koen Aers Addresses need to add new semantic elements without adding new xml types. Current mapping forces 1-1 mapping between them. this change allows one-to-many mapping between elements by introducing a mapping object for each semantic element. this mapping object's responsibility is to determine if a chunk of xml should map to a semantic element and xml adapter or not. the xml adapter registry holds a set of these mappers and loops through them all, giving each a chance to accept the xml chunk. all accepting mappers are then sorted by priority and the lowest priority number is selected. mappings with no priority are given Integer.MAX priority. Mappings with no mapperClass are given a default mapper class of ConfiguredSemanticElementDomMapper so that existing plugin.xml should continue to function normally. The priority property allows the maintainer of the plugin.xml to change priorities for different circumstances, giving different potentially conflicting mappers a specific preference order. Details of change: Added two elements to xmlMappings.exsd: mapperClass and mapperClassPriority Created interface SemanticElementDomMapper to determine if a given Dom Node can be assigned to a semantic element Created class ConfiguredSemanticElementDomMapper as a base implementation of the SemanticElementDomMapper. This default implementation checks the current configured xml node name against the node name of the passed Dom Node. This should duplicate the existing functionality for existing standard jpdl xml node types. JythonNodeDomMapper is included as an example but should not be committed to the project as it is for specialized use. XmlAdapterRegistry constructs a HashMap of Mappers and has a new getConfigurationElementByNode method. XmlAdapter has 2 lines modified in the createSemanticElementFor method to use the new registry method. XmlAdapterFactory has modifications in createAdapter and createAdapterFromModel -- 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, 11 months

3
36
0 / 0

[JBoss JIRA] Created: (GPD-137) problem configuriing exception class

by Koen Aers (JIRA)

problem configuriing exception class ------------------------------------ Key: GPD-137 URL: http://jira.jboss.com/jira/browse/GPD-137 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.CR Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.GA -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Assigned: (JBFORUMS-2) Search Engine

by Przemyslaw Dej (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-2?page=all ] Przemyslaw Dej reassigned JBFORUMS-2: ------------------------------------- Assignee: Przemyslaw Dej (was: Ryszard Kozmik) > Search Engine > ------------- > > Key: JBFORUMS-2 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-2 > Project: JBoss Forums > Issue Type: Task > Components: Forum View Layer, Forum Enhancements, Forum Model Layer > Reporter: Ryszard Kozmik > Assigned To: Przemyslaw Dej > Priority: Blocker > Fix For: 1.1.0 Alpha > > > JBoss Forums definitely needs a search engine. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBAS-4603) How to Find out client login time,logout time and what he did in JBoss log

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4603?page=all ] Dimitris Andreadis deleted JBAS-4603: ------------------------------------- > How to Find out client login time,logout time and what he did in JBoss log > -------------------------------------------------------------------------- > > Key: JBAS-4603 > URL: http://jira.jboss.com/jira/browse/JBAS-4603 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Reporter: Jaya prakash > Priority: Blocker > > Here i am facing the issue to find out the user(client) log-in time and log-out time, If he done any thing what he done. I searched in log file but i didn't find out that clearly . > Please advise me. > Regards, > Red -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JGRP-20) Address translation in transport (NAT support)

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-20?page=all ] Bela Ban updated JGRP-20: ------------------------- Fix Version/s: 2.x (was: 2.6) May not be needed anymore, together with logical addresses > Address translation in transport (NAT support) > ---------------------------------------------- > > Key: JGRP-20 > URL: http://jira.jboss.com/jira/browse/JGRP-20 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.x > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > On multi-homed systems, the identity of a member is bound to a NIC (either chosen by the OS, or by the > user through bind_addr): Address. When a message is sent, the msg contains this address as the sender's > address. Responses go to the same address. > However, if that NIC breaks, and the sender's OS chooses a different NIC for the datagram packets, the > receiver will still send the response back to the old address (the identity of the sender cannot > change). > If we set the sender's address in any Message on *reception* of the message, we would be able to send > the response back to a valid NIC in the above case. However, this means the *identity* of the sender > changes, which JGroups cannot handle. > SOLUTION I: we could introduce a logical address, which contains the physical address of the NIC > through which it was sent. Problem: a lot of code would have to change. > SOLUTION II: we maintain, in each transport, a table of sender's address as defined in the Message, and > physical address of the {Datagram,Multicast}Packet received. Whenever we send a unicast message, we get > the destination address from this table through a lookup in which dest_msg.dest_addr is the key. > We need to reap the table every now and then to purge old addresses, we could use view changes to do > so. > Example for SOLUTION II: > - Member P: address=1.2.3.4:5555 > - P's box has 2 NICs: 1.2.3.4 and 5.6.7.8 > - Receiver R receives a message from P: P.src_addr=1.2.3.4:5555, datagram's address is 1234:5555 > - R doesn't add an entry to the translation table, because the addresses are the same > - R sends a response: it looks up 1.2.3.4:5555 (dst) in the translation table > - There is no entry, therefore R sends the response to 1.2.3.4:5555 > - P's NIC 1.2.3.4 is unplugged > - P sends a message through NIC 5.6.7.8 > - R receives a message M.src_addr=1.2.3.4:5555, datagram's address is 5.6.7.8:5555 > - R adds an entry to its translation table: 1.2.3.4:5555 --> 5.6.7.8:5555 > - R sends a response to 1.2.3.4:5555, since there is an entry for 1.2.3.4:5555, it uses 5.6.7.8:5555 > as the destination address of the datagram packet > SOLUTION II allows us to reuse the existing code, but provides for changing underlying IP addresses. -- 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, 11 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 August 2007