September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3409) Deploy a .ear file with no deployment descriptor(META-INF/application.xml)

by Rajesh Rajasekaran (JIRA)

Deploy a .ear file with no deployment descriptor(META-INF/application.xml) -------------------------------------------------------------------------- Key: JBAS-3409 URL: http://jira.jboss.com/jira/browse/JBAS-3409 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta Reporter: Rajesh Rajasekaran Assigned To: Dimitris Andreadis Priority: Blocker Fix For: JBossAS-5.0.0.Beta The javaee5 spec (EE8.4.2 Deploying a Java EE application) has a set of rules to deploy an application .ear file which does not have a deployment descriptor. (descriptorMETA-INF/application.xml) Currently we get a RunTimeException when the application.xml is not found. org.jboss.deployment.spi.DeploymentManagerImpl@16b8f8eb java.lang.RuntimeException: cannot obtain module type 07-21-2006 13:12:57: Harness - Deployment of app(s) from: /home/rrajasekaran/tck5/javaeetck/dist/com/sun/ts/tests/samples/javamail/ee/transport failed! at org.jboss.deployment.spi.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:481) at org.jboss.deployment.spi.DeploymentManagerImpl.distribute(DeploymentManagerImpl.java:348) The moduleType in org.jboss.deployment.spi.DeploymentManageImpl.createDeployment() is not set when the application.xml is not set. All CTS tests deploy .ear files with no application.xml I ve made this issue a blocker because unless this is fixed we would be unable to run the cts tests. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3656) Disconnect HAPartition channel upon failure in startService()

by Brian Stansberry (JIRA)

Disconnect HAPartition channel upon failure in startService() ------------------------------------------------------------- Key: JBAS-3656 URL: http://jira.jboss.com/jira/browse/JBAS-3656 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1 If an exception is thrown in ClusterPartition/HAPartition startService() after the channel is connected, the channel must be disconnected, or we've left a zombie member of the group. Particularly in 4.0.x where the ServiceController will not undeploy a service that fails in start(). Need to ensure stopService() properly handles a disconnected 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1062) ApacheDS for ldap integration testing

by Boleslaw Dawidowicz (JIRA)

ApacheDS for ldap integration testing ------------------------------------- Key: JBPORTAL-1062 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1062 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Test Affects Versions: 2.6.Alpha1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Alpha1 - make embedded ApacheDS service to use in testing framework -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)

by Tom Elrod (JIRA)

can not do connection validation with ssl transport (only impacts detection) ---------------------------------------------------------------------------- Key: JBREM-581 URL: http://jira.jboss.com/jira/browse/JBREM-581 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: detection Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) When a detector gets the detection message from a server, the detection message does not include (nor should it), the ssl info needed to make the ping invocation on that server to verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation if transport supports ssl. This means that never does the ping invocation to ensure that the server is really down (and not just lack of getting detection message update), but instead will just consider it dead if detection message is stale. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-994) UI enhancements to bundled portlets

by Roy Russo (JIRA)

UI enhancements to bundled portlets ----------------------------------- Key: JBPORTAL-994 URL: http://jira.jboss.com/jira/browse/JBPORTAL-994 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6 Final Reporter: Roy Russo Assigned To: Roy Russo userportlet roleportlet cmsadmin cms content managementportlet -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-504) Cannot use the object's property named as "attributes" in a rule

by Vineeth Varghese (JIRA)

Cannot use the object's property named as "attributes" in a rule ---------------------------------------------------------------- Key: JBRULES-504 URL: http://jira.jboss.com/jira/browse/JBRULES-504 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Environment: Windows 2000 with Jdk1.5 Reporter: Vineeth Varghese Assigned To: Mark Proctor Attachments: src.zip The word "attributes" seem to be a keyword in JBoss Rules. Basically if I have an Object that has a property named as "attributes", I cannot use it in the IDE or create a rulebase out of it. We end up getting the following error:- org.drools.rule.InvalidRulePackage: unknown:9:19 Unexpected token 'attributes' at org.drools.rule.Package.checkValidity(Unknown Source) at org.drools.common.AbstractRuleBase.addPackage(Unknown Source) at com.sample.DroolsTest.readRule(DroolsTest.java:72) at com.sample.DroolsTest.main(DroolsTest.java:23) Even the IDE highlights this as an error. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-484) refactor the core reteoo code for sinle and composite propagations

by Mark Proctor (JIRA)

refactor the core reteoo code for sinle and composite propagations ------------------------------------------------------------------- Key: JBRULES-484 URL: http://jira.jboss.com/jira/browse/JBRULES-484 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 The profiling shows that much time is spent in iteration loops. So we should look at using Single and Composite Adapters for propagations. Further we should avoid using ArrayLists and instead use our own custom LinkedList or arrays. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-505) Using a GLOBAL value in predicates in more than one rule - rule fails to evaluate correctly.

by Matt Green (JIRA)

Using a GLOBAL value in predicates in more than one rule - rule fails to evaluate correctly. -------------------------------------------------------------------------------------------- Key: JBRULES-505 URL: http://jira.jboss.com/jira/browse/JBRULES-505 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 3.0.4 Environment: Windows XP, JBoss 4.0.3SP1, JRules3.0.4, PackageBuilderConfiguration.JANINO Reporter: Matt Green Assigned To: Mark Proctor SAMPLE CODE: =============================================== package net.rockshore.rmf.rules #list any import classes here. import net.rockshore.rmf.entities.SubscriptionLocal; import net.rockshore.rmf.entities.EventLocal; import java.lang.String; #declare any global variables here global java.util.Collection resultsCollection; global java.lang.String eventType; rule "KeepSubscriptionsToEventType" when subscription : SubscriptionLocal (eventTypeDiscriminator == (eventType)) then resultsCollection.add(subscription); System.out.println("Keeping Subscription:" + subscription + " is of type:" + eventType); end rule "DiscardSubscriptionsToWrongEventType" when wrongSubscription : SubscriptionLocal (eventTypeDiscriminator != (eventType)) then System.out.println("Discarding Subscription:" + wrongSubscription + " NOT of type:" + eventType); retract (wrongSubscription); end =============================================== TEST DATA SET: ------------------------- SubscriptionLocal objects asserted key eventTypeDiscriminator --------------------------------------------------------------------------------------------------------- 5c4o12-mexdpy-esmukytr-1-esmx439o-58 net.rockshore.rmf.entities.events.business.TravelAlertEvent 5c4o12-mexdpy-esmukytr-1-esmx438t-57 net.rockshore.rmf.entities.events.business.FlightDelayEvent 5c4o12-mexdpy-esmukytr-1-esmx438t-56 net.rockshore.rmf.entities.events.business.FlightDelayEvent eventType = "net.rockshore.rmf.entities.events.business.FlightDelayEvent" PROBLEM DESCRIPTION: ------------------------------------- When firing the above rules with data shown above, the result shows that "DiscardSubscriptionsToWrongEventType" rule was fired for Subscriptions with keys ending 57 and 56. This is the wrong way round as that rule should have fired only with Subscription 58. Further, rule "KeepSubscriptionsToEventType" did not fire. FURTHER ANALYSIS: ------------------------------- If one rule OR the other is deleted then the remaining rule fires correctly. If both rules have the predicate replaced with a String literal "net.rockshore.rmf.entities.events.business.FlightDelayEvent" then both rules fire correctly. The problem still occurs when eventType predicate is replaced with eventType.toString() -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-134) Content-based routing support

by Mark Little (JIRA)

Content-based routing support ----------------------------- Key: JBESB-134 URL: http://jira.jboss.com/jira/browse/JBESB-134 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1054) Invalid HTML in divRenderer

by Johnny Healey (JIRA)

Invalid HTML in divRenderer --------------------------- Key: JBPORTAL-1054 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1054 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.4 Final Environment: CentOS release 4.4 (Final), jdk1.5.0_06 Reporter: Johnny Healey Assigned To: Julien Viet Minimize/Maximize buttons have urls containing unescaped ampersands. "&windowstate=minimized" should read "&windowstate=minimized" -- 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, 6 months

3
5
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