June 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-226) New ResourceType for IDTRUST

by Anil Saldhana (JIRA)

New ResourceType for IDTRUST ---------------------------- Key: SECURITY-226 URL: http://jira.jboss.com/jira/browse/SECURITY-226 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.2.CR2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR3 -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-224) JBossSX config module that has XB dependent code

by Anil Saldhana (JIRA)

JBossSX config module that has XB dependent code ------------------------------------------------ Key: SECURITY-224 URL: http://jira.jboss.com/jira/browse/SECURITY-224 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.CR2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR3 -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-767) JChannel: open() fails

by Bela Ban (JIRA)

JChannel: open() fails ---------------------- Key: JGRP-767 URL: http://jira.jboss.com/jira/browse/JGRP-767 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 JChannel.open() fails because the properties of the previously created channel cannot be fetched correctly. If set store the setup_string, and someone changes the instance variables, e.g. via a setter (UDP.setMulticastPort()), then open() will use the *old* props ! open() used to call Channel.getProperties(), but since we cannot simply return the old 'props' value (mostly not used anymore !), we have to either generate the properties from the instance vars annotated with @Property, or somehow store a 'configuration' of the properties in the channel. Maybe a ChannelConfiguration class ? -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3343) JCA 1.5 Resource Adapter Config Properties cannot be specified

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3343?page=all ] Jesper Pedersen updated JBAS-3343: ---------------------------------- Fix Version/s: JBossAS-5.0.0.CR2 (was: JBossAS-5.1.0.CR1) > JCA 1.5 Resource Adapter Config Properties cannot be specified > -------------------------------------------------------------- > > Key: JBAS-3343 > URL: http://jira.jboss.com/jira/browse/JBAS-3343 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.4.GA > Environment: All. > Reporter: Andreas Mueller > Assigned To: Vicky Kak > Fix For: JBossAS-5.0.0.CR2 > > Attachments: ra.xml > > > A JCA 1.5 resource adapter might contain config properties in ra.xml. It is not possible in JBoss to override them with -ds.xml file. > For example, here is an excert of SwiftMQ's intraVM ra.xml: > <resourceadapter> > <resourceadapter-class> > com.swiftmq.connector.v15.ResourceAdapterImpl > </resourceadapter-class> > <config-property> > <config-property-name>ProviderURL</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>smqp://intravm/timeout=10000</config-property-value> > </config-property> > <config-property> > <config-property-name>IntraVM</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>true</config-property-value> > </config-property> > <config-property> > <config-property-name>DebugMode</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>false</config-property-value> > </config-property> > <config-property> > <config-property-name>RouterWorkingDirectory</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value><swiftmq_dir>/scripts/unix</config-property-value> > </config-property> > <config-property> > <config-property-name>ConfigurationFilename</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>../../config/router1/routerconfig.xml</config-property-value> > </config-property> > It is not possible to overwrite them during deployment. It is only possible to specify the config properties of the ManagedConnectionFactory in -ds.xml. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1387) Update Installer to Patch with Proxy Libraries

by Andrew Lee Rubinger (JIRA)

Update Installer to Patch with Proxy Libraries ---------------------------------------------- Key: EJBTHREE-1387 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1387 Project: EJB 3.0 Issue Type: Sub-task Components: installer Affects Versions: HEAD Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 EJB3 Installer Program must patch with Proxy libraries. Will also require updates of dependencies to the Plugin. -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1386) Create Proxy Client Artifact

by Andrew Lee Rubinger (JIRA)

Create Proxy Client Artifact ---------------------------- Key: EJBTHREE-1386 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1386 Project: EJB 3.0 Issue Type: Sub-task Components: proxy Affects Versions: HEAD Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 Create an assembly for classes required on the client VM for EJB3 Proxy -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-768) UDP: when ip_mcast=false, the destination of a Message is not null

by Bela Ban (JIRA)

UDP: when ip_mcast=false, the destination of a Message is not null ------------------------------------------------------------------ Key: JGRP-768 URL: http://jira.jboss.com/jira/browse/JGRP-768 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.3, 2.7 When setting ip_mcast=false in UDP, on reception of a message, the destination is a unicast address. However, it should be either null, or a multicast address. This might cause problems in cases where msg.getDest() is called. If the destination field is used as a key into a hashmap, this would be incorrect. TASK 1: verify that this leads to incorrect behavior TASK 2: fix this, to make dest null when ip_mcast=false -- 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

15 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5573) Eager fetched list missing an element when retrieved remotely

by da_alchemist (JIRA)

Eager fetched list missing an element when retrieved remotely ------------------------------------------------------------- Key: JBAS-5573 URL: http://jira.jboss.com/jira/browse/JBAS-5573 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Environment: Java: 1.5.0_15; Java HotSpot(TM) Client VM 1.5.0_15-b04 JBoss AS: 4.2.2.GA, 5.0.0.Beta4 Reporter: da_alchemist I have implemented eager fetching with a parent-to-child (many-to-many) and child-to-grandchild (many-to-many) relationship setup. After all entities are created and I retrieve the grandchildren with EAGER fetching, I am able to iterate through the list of grandchildren and view the grandchildren with it's related children and the children's related parents BEFORE leaving the JBoss server to return the results to a remote client. AFTER leaving the server and the remote client receives the results I iterate through the same grandchildren and see that the parent does not contain the same children as was present before the data left the server. I have tested this on JBoss 4.2.2.GA and 5.0.0.Beta4 and both have failed. Please see the provided JBoss forum reference which has the test code. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1196) add heartbeat

by Jeff Mesnil (JIRA)

add heartbeat ------------- Key: JBMESSAGING-1196 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1196 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Remoting Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha The new remoting code based on MINA is missing a heartbeat. This heartbeat sent by the client to its server is required to be able to clean resources on the server side when a client is dead (when it no longer sends its heartbeat) -- 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

15 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1291) Create set of examples

by Tim Fox (JIRA)

Create set of examples ---------------------- Key: JBMESSAGING-1291 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1291 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Alpha Create a set of examples for JBM 2.0 These should include a) JMS examples - these should use the standard JMS API b) Core examples - these should use the core API. The examples will also be used to provide simple performance comparisons between us and other vendors for the release. -- 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

15 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2008