[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
[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
[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
[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