October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (HIBERNATE-20) JDK Compatiblity Issue with Hibernate Tools project

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-20?page=all ] Max Andersen closed HIBERNATE-20. --------------------------------- Resolution: Out of Date > JDK Compatiblity Issue with Hibernate Tools project > --------------------------------------------------- > > Key: HIBERNATE-20 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-20 > Project: Hibernate > Issue Type: Bug > Environment: JDK1.4 > Reporter: hari prasad > Assigned To: Gavin King > > In the latest release of Hibernate Tools, the DAO code generated is compatible ONLY to JDK1.5. Please provide a drop that generates 1.4 compatible code also. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-600) Investigate Mulitplexer locking scopes

by Vladimir Blagojevic (JIRA)

Investigate Mulitplexer locking scopes -------------------------------------- Key: JGRP-600 URL: http://jira.jboss.com/jira/browse/JGRP-600 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.6 It seems that we are holding locks more that we need to in Multiplexer building block. Review all synchronization blocks and make changes if appropriate. -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBREM-305) Provide support for JMS transport

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380454 ] Thomas Diesler commented on JBREM-305: -------------------------------------- Whatever you want to call it, I'd like to use a jms like connection URI jms://foo > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: David Lloyd > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-305) Provide support for JMS transport

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380443 ] David Lloyd commented on JBREM-305: ----------------------------------- For the user, of course they should be able to use the JAX-WS API - but Remoting does not provide this API. My question is, what does Remoting add here? It sounds like you want Remoting to act not so much as a remote invocation layer, but rather more as a generic transport facade. Is this accurate? > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: David Lloyd > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1248) <literal-restriction> requires an 'value' attribute, but it can't be null

by Fernando Meyer (JIRA)

<literal-restriction> requires an 'value' attribute, but it can't be null -------------------------------------------------------------------------- Key: JBRULES-1248 URL: http://jira.jboss.com/jira/browse/JBRULES-1248 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1, 4.0.0.GA, 4.0.0.MR3, 4.0.0.MR2 Reporter: Fernando Meyer Assigned To: Fernando Meyer Fix For: 4.0.2 <literal-restriction> requires an 'value' attribute, but the parser fails when we use a null value. The parser should be able to parse this xml rule. <?xml version="1.0"?> <rule name="Check_NotNullof_rfqId"> <rule-attribute name="agenda-group" value="Check"/> <lhs> <pattern object-type="RFQBean"> <or-constraint-connective> <field-constraint field-name="m_rfqId"> <literal-restriction evaluator="==" value="null"/> </field-constraint> <field-constraint field-name="m_rfqId"> <literal-restriction evaluator="==" value=""/> </field-constraint> </or-constraint-connective> </pattern> </lhs> <rhs> response.setStatus("For RFQ Bean: The value of m_rfqId is null."); System.out.println(response.getStatus()); </rhs> </rule> -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBREM-305) Provide support for JMS transport

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380380 ] Thomas Diesler commented on JBREM-305: -------------------------------------- Yes, but clients want to use the JAX-WS API to send a web service request. The transport (i.e. JMS) should be a configurable aspect and should not require usage of a different API. > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: David Lloyd > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Carlo de Wolf reassigned EJBTHREE-124: -------------------------------------- Assignee: Carlo de Wolf > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Assigned To: Carlo de Wolf > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Carlo de Wolf closed EJBTHREE-124. ---------------------------------- Resolution: Deferred > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Assigned To: Carlo de Wolf > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Carlo de Wolf updated EJBTHREE-124: ----------------------------------- Fix Version/s: (was: AS 4.2.2.GA) > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1241) Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional

by Mark Proctor (JIRA)

Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional ------------------------------------------------------------------------------------------------ Key: JBRULES-1241 URL: http://jira.jboss.com/jira/browse/JBRULES-1241 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.2 add lock() and unlock() to RuleBase and setup a rulebase listener to progated the fireAllRules calls. -- 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

17 years, 2 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 October 2007