June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1485) patch facelet

by Prabhat Jha (JIRA)

patch facelet ------------- Key: JBPORTAL-1485 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1485 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Prabhat Jha Assigned To: Prabhat Jha Fix For: 2.6 Final As per our call today, I am trying to patch facelet so that we have one less issue to deal with as far as running 2.6 with 4.2 is concerned. I have checked out source code from https://facelets.dev.java.net/files/documents/3448/31342/facelets-1.1.1.zip and applied Julien's patch to com.sun.facelets.impl.DefaultFaceletContext which is to add couple of methods: public boolean isPropertyResolved() { return this.ctx.isPropertyResolved(); } public void setPropertyResolved(boolean resolved) { this.ctx.setPropertyResolved(resolved); } However, couple of classes com.sun.facelets.tag.jsf.ActionSourceRule uses jsf1.2 classes such as ActinSource2 because of which I am not able to compile it with jdk1.4 and jsf1.1. Since it has been done before and I am sure there is a way out for this but I dont know yet. I have started a thread in facelet users mailing list and I will wait to see if anybody has any solution. Retroweaving jsf 1.2 jar does not seem to be the right solution to me. -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (GPD-93) revision of the delegation configuration form

by Koen Aers (JIRA)

revision of the delegation configuration form --------------------------------------------- Key: GPD-93 URL: http://jira.jboss.com/jira/browse/GPD-93 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0.alpha4 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 Removal of the scrolled pagebook; switched the text fields from 'default selection' behaviour to 'focus lost' behaviour (also the for the table); revision of the layout. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1086) Test PojoCache against JDK 1.6

by Manik Surtani (JIRA)

Test PojoCache against JDK 1.6 ------------------------------ Key: JBCACHE-1086 URL: http://jira.jboss.com/jira/browse/JBCACHE-1086 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Manik Surtani Assigned To: Jason T. Greene Fix For: 2.0.0.CR3, 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-960) CascadeType REMOVE in relationships doesn't appear to cascade anymore.

by Fritz Feuerbacher (JIRA)

CascadeType REMOVE in relationships doesn't appear to cascade anymore. ---------------------------------------------------------------------- Key: EJBTHREE-960 URL: http://jira.jboss.com/jira/browse/EJBTHREE-960 Project: EJB 3.0 Issue Type: Bug Environment: Windows XP, JBoss AS 4.0.5.GA Reporter: Fritz Feuerbacher Since I upgraded from JBoss 4.0.4.GA to 4.0.5.GA I have encountered this problem. Whenever I have an entity bean that has a relation in it I get strange behavior that I didn't have in 4.0.4.GA. Examples: Say I have an entity bean with a relation in it like: @OneToMany (mappedBy="user", cascade={cascadeType.ALL}), fetch=fetchType.EAGER) public List<UserAndRole> getUserAndRoles() { return userAndRoles; } This works fine, and will cascade in all instances except if I take an existing bean and set the list to an empty list like: userAndRoles = new ArrayList<UserAndRole>(); and then call merge on the entity bean. It appears to remove the relationship in the the bean, however, the old entries in the table are still there. In JBoss 4.0.4.GA, doing this would also remove the entries in the UserAndRoles table that corresponded to the items that were in the original userAndRoles list. Definately something has changed between the versions. I just can't figure out what. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4429) Classloader leak to JBossTS ReaperThread

by Brian Stansberry (JIRA)

Classloader leak to JBossTS ReaperThread ---------------------------------------- Key: JBAS-4429 URL: http://jira.jboss.com/jira/browse/JBAS-4429 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-4.2.0.GA Reporter: Brian Stansberry Assigned To: Scott M Stark ClassloaderLeakUnitTestCase is showing a classloader leak when the test does remote calls to EJB2 SLSBs. See http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-testsuite-1.5?lo... JBoss Profiler analysis (see attached) shows the leak is to the JBossTS ReaperThread -- the DelegatingClassLoader for the ejb jar deployment is set as the TCCL on that thread. Oddities I observed while trying to track this down: 1) The leak doesn't occur if JMS is deployed. By mistake I changed the AS config for the test such that JBossMQ no longer gets deployed; that's when the leak appeared. The test doesn't use JMS in any way. Can only speculate that if MQ is running the TCCL on the ReaperThread gets cleared or changed somehow or never gets set to the ejb's DelegatingClassLoader. 2) The test class includes 3 different tests that basically make the same calls. The differences between the tests is just how the ejbs are packaged -- one in a plan jar, one with an ear and the plain jar, one with the ear but a loader-repository configured. Only the first of these that gets executed fails; the other two pass. I changed the order in which the tests execute, and whichever was first failed. Hence the success/failure doesn't appear to be a function of the packaging. -- 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, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-932) Parser not working for complex field expression

by Edson Tirelli (JIRA)

Parser not working for complex field expression ------------------------------------------------ Key: JBRULES-932 URL: http://jira.jboss.com/jira/browse/JBRULES-932 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.MR2 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.0.MR3 // the bellow expression must generate the following tree: // // AND // | // OR // /---------------+-------------------\ // AND AND AND // /---+---\ /---+---\ /---+---\ // FC FC FC FC FC OR // /---+---\ // FC FC // final String text = "Person( ( age ( > 60 && < 70 ) || ( > 50 && < 55 ) && hair == \"black\" ) || ( age == 40 && hair == \"pink\" ) || ( age == 12 && ( hair == \"yellow\" || hair == \"blue\" ) ))"; The above expression is not working. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-993) Temporary destinations should not be bound to JNDI

by Sergey Koshcheyev (JIRA)

Temporary destinations should not be bound to JNDI -------------------------------------------------- Key: JBMESSAGING-993 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-993 Project: JBoss Messaging Issue Type: Bug Components: JMS Destination Manager Reporter: Sergey Koshcheyev Assigned To: Sergey Koshcheyev Fix For: 1.4.0.CR1 -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-928) MVELDataProvider is not serialisable

by Mark Proctor (JIRA)

MVELDataProvider is not serialisable ------------------------------------ Key: JBRULES-928 URL: http://jira.jboss.com/jira/browse/JBRULES-928 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.0.MR3 The DataProvder interface should extend Serialisable -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Updated: (JBPM-426) enable jpdl schema extension via namespaces

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-426?page=all ] Ronald van Kuijk updated JBPM-426: ---------------------------------- Affects Version/s: jBPM 3.3 (was: jBPM 3.0.1) Would be great to have this for 3.3. Can anyone estimate the amount of work? > enable jpdl schema extension via namespaces > ------------------------------------------- > > Key: JBPM-426 > URL: http://jira.jboss.com/jira/browse/JBPM-426 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.3 > Reporter: Martin Dirichs > Assigned To: Tom Baeyens > > Customizing jpdl elements in a process definition via application-specific XML-elements is currently only possible outside of any schema validation. XML namespaces are the canonical way to allow for the extension of jpdl so that configuration data of delegation classes may be defined within an application-specific namespace and associated XML schema. In particular, this would be necessary to enable customization of jpdl elements > - action > - assignment > - handler > - controller > - task > Bug #JBPM-332: > http://jira.jboss.com/jira/browse/JBPM-332 > is somewhat related to this issue. However, resolution of JBPM-332 > - only allows for arbitrary elements to appear inside jpdl files (without schema validation) > - and only for customizing assignments (leaving out action, handler, controller and task). > Implementation of this feature request would be done via a more intelligent version of an EntityResolver (defined in org.jbpm.jpdl.xml.SchemaValidationHandle) that can return application specific schemas in addition to the default one for jpdl. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4464) NPE on shutdown in jacorb connection layer

by Scott M Stark (JIRA)

NPE on shutdown in jacorb connection layer ------------------------------------------ Key: JBAS-4464 URL: http://jira.jboss.com/jira/browse/JBAS-4464 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: IIOP service Affects Versions: JBossAS-4.2.0.GA Reporter: Scott M Stark Assigned To: Francisco Reverbel Priority: Minor The current 4.2 branch using 2.3.0jboss.patch2 is producing a NPE in the jacorb connection layer on shutdown. 08:40:17,751 ERROR [giop] unexpected exception during doWork java.lang.NullPointerException at org.jacorb.orb.etf.StreamConnectionBase.read(StreamConnectionBase.java:142) at org.jacorb.orb.giop.GIOPConnection.getMessage(GIOPConnection.java:325) at org.jacorb.orb.giop.GIOPConnection.receiveMessages(GIOPConnection.java:464) at org.jacorb.orb.giop.MessageReceptor.doWork(MessageReceptor.java:71) at org.jacorb.util.threadpool.ConsumerTie.run(ConsumerTie.java:61) at java.lang.Thread.run(Thread.java:595) -- 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, 1 month

3
7
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 June 2007