September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-361) When creating entity bean, multiple radio buttons from the same group are checked

by Stephen Parry (JIRA)

When creating entity bean, multiple radio buttons from the same group are checked --------------------------------------------------------------------------------- Key: JBIDE-361 URL: http://jira.jboss.com/jira/browse/JBIDE-361 Project: JBoss IDE Issue Type: Bug Affects Versions: 1.6 Environment: Windows XP SP2 JBoss 4.0.4 GA Eclipse 3.1.2 IDE 1.6.0 from update site Reporter: Stephen Parry - Added new J2EE 1.4 project JiraTest with source folder src with output bin - Added new package: jiratest.ejb - Right click on package, select New -> Other -> Entity Bean New Entity Bean wizard appears, but the radio buttons are 'confused'; both CMP 1.x and CMP 2.x are selected and both Remote and Local are selected, but not Both (!). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3629) org.jboss.naming.ExternalContext.SerializableInitialContext should be included in [jboss]/client/jbossall-client.jar

by Jim Moran (JIRA)

org.jboss.naming.ExternalContext.SerializableInitialContext should be included in [jboss]/client/jbossall-client.jar -------------------------------------------------------------------------------------------------------------------- Key: JBAS-3629 URL: http://jira.jboss.com/jira/browse/JBAS-3629 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Naming Affects Versions: JBossAS-4.0.5.CR1 Reporter: Jim Moran Assigned To: Ruel Loehr Priority: Minor org.jboss.naming.ExternalContext.SerializableInitialContext exists in server/default/lib/jboss.jar but it does not exist for a client that uses [jboss]/client/jbossall-client.jar. As a result if a client app needs to lookup an ExternalContext on a remote JBoss instance, the client must enable RMI classloader or include server/default/lib/jboss.jar It would be nicer if ExternalContext was included with jbossall-client.jar -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (BPEL-190) web app generation tool

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-190?page=comments#action_12342968 ] Alejandro Guizar commented on BPEL-190: --------------------------------------- Actually, WSDL includes a binding for HTTP's GET and POST methods, so that apps other than web browsers are able to interact with a web site. This binding makes an html-based webapp a formal webservice. The ex-CEO probably did not realize how right he was :-) The WSDL spec URL: http://www.w3.org/TR/wsdl#_http As useful as it could be, potentially saving years of typing into HTML forms, it lacks support in WS stacks. Even Apache WSIF does not support the HTTP binding. Most works focus on the SOAP binding and leave other bindings out. So many paths, so little time :-\ > web app generation tool > ----------------------- > > Key: BPEL-190 > URL: http://jira.jboss.com/jira/browse/BPEL-190 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > create a tool for generating web application artifacts -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-470) Update JBoss Cache to use JGroups 2.4 and Multiplexer

by Jerry Gauthier (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-470?page=all ] Jerry Gauthier closed JBCACHE-470. ---------------------------------- Resolution: Done Multiplexer integration has been enabled for JBossCache 2.0. Documentation has been updated and sample configuration files have been modified to demonstrate how to configure the multiplxer with JBossCache. > Update JBoss Cache to use JGroups 2.4 and Multiplexer > ----------------------------------------------------- > > Key: JBCACHE-470 > URL: http://jira.jboss.com/jira/browse/JBCACHE-470 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Replication > Affects Versions: 1.2.4 > Reporter: Manik Surtani > Assigned To: Jerry Gauthier > Priority: Blocker > Fix For: 2.0.0 > > > Use a ChannelFactory that looks up the MBean server to potentially create a JGroups multiplexer channel -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-37) Modifications for the OASIS Standard

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-37?page=comments#action_12342954 ] Kevin Conner commented on JBTM-37: ---------------------------------- The protocol for the OASIS WS-TX 1.1 AtomicTransaction and Coordination specifications was written as part of JBTM-38. This still has to be integrated into the current WS-TX implementation. > Modifications for the OASIS Standard > ------------------------------------ > > Key: JBTM-37 > URL: http://jira.jboss.com/jira/browse/JBTM-37 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.6 > > > Preliminary support for the OASIS WS-TX standard. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-619) PojoCache to support JDK5.0 Enum

by Colin Walters (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-619?page=comments#action_12342953 ] Colin Walters commented on JBCACHE-619: --------------------------------------- So as I understand it, without this bug fix it is not possible to use enum values in entity objects when using the EJB3 entity cache? Is there a workaround? I found this JIRA from this forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=71311&view=previous > PojoCache to support JDK5.0 Enum > -------------------------------- > > Key: JBCACHE-619 > URL: http://jira.jboss.com/jira/browse/JBCACHE-619 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: PojoCache 2.1.0 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > In JDK5.0, Enum is Serializabe. We need to look into whether it is possible to intercept Enum operation as well. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBTM-37) Modifications for the OASIS Standard

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-37?page=all ] Mark Little updated JBTM-37: ---------------------------- Fix Version/s: 4.6 (was: 4.4) Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial] (was: [Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)]) > Modifications for the OASIS Standard > ------------------------------------ > > Key: JBTM-37 > URL: http://jira.jboss.com/jira/browse/JBTM-37 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.6 > > > Preliminary support for the OASIS WS-TX standard. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-108) Make number of transactions rolled back per reaper sweep configurable

by Mark Little (JIRA)

Make number of transactions rolled back per reaper sweep configurable --------------------------------------------------------------------- Key: JBTM-108 URL: http://jira.jboss.com/jira/browse/JBTM-108 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.4 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBTM-37) Modifications for the OASIS Standard

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-37?page=all ] Mark Little updated JBTM-37: ---------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial] (was: [Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)]) Assignee: Kevin Conner (was: Mark Little) > Modifications for the OASIS Standard > ------------------------------------ > > Key: JBTM-37 > URL: http://jira.jboss.com/jira/browse/JBTM-37 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.4 > > > Preliminary support for the OASIS WS-TX standard. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-38) Interoperability demo

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-38?page=all ] Kevin Conner closed JBTM-38. ---------------------------- Resolution: Done > Interoperability demo > --------------------- > > Key: JBTM-38 > URL: http://jira.jboss.com/jira/browse/JBTM-38 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2.2 > > Time Spent: 1 week, 4 days > Remaining Estimate: 0 minutes > > Demonstrate interoperability with IBM and Microsoft. Important for the specification as well as our product. -- 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, 8 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 September 2006