[JBoss JIRA] Created: (JBAS-6688) expose ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
by Ian Springer (JIRA)
expose ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
-----------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently exposed as a complicated CompositeValueSupport type that contains a String and a Properties child value:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's exposed today, just to get it into a usable format, the client would have to write code to convert the CompositeValue into an ObjectName, rather than being able to simply call new ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBRULES-2011) Calling addPackage causes rules that use "collect" to incorrectly fire.
by Janneman Robinson (JIRA)
Calling addPackage causes rules that use "collect" to incorrectly fire.
-----------------------------------------------------------------------
Key: JBRULES-2011
URL: https://jira.jboss.org/jira/browse/JBRULES-2011
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.7
Environment: Windows XP using Java version 1.6.
Reporter: Janneman Robinson
Assignee: Mark Proctor
Steps to reproduce:
1. Create a rulebase containing at least one Package. The package should contain at least one rule that uses the "collect" statement (ie, with a condition on how many elements are collected) and no additional conditional elements in the LHS of the rule.
2. Request a new StatefulSession using myRuleBase.newStatefulSession() or myRuleBase.newStatefulSession(true).
3. Add an altered package to the RuleBase using myRuleBase.addPackage(x);
Expected:
nothing
Result: the call to addPackage causes a "fireAllRules". During this process, rules that depend on a "collect" statement are executed whether or not the conditioned number of facts collected was met.
Below is a testcase that demonstrates the behaviour. Note: myRuleBase.newStatefulSession(false) does not cause this behaviour.
public class TestAddPkg extends TestCase {
private static boolean alarmRaised;
public static void raiseAlarm() {
alarmRaised = true;
}
public void testKeepReferenceFalse() throws Exception {
alarmRaised = false;
RuleBase rules = null;
rules = addSourceToRules(createRule1(), rules);
rules.newStatefulSession(false);
rules = addSourceToRules(createRule2(), rules);
// We never inserted any alarms, so...
assertFalse(alarmRaised);
}
public void testKeepReferenceTrue() throws Exception {
alarmRaised = false;
RuleBase rules = null;
rules = addSourceToRules(createRule1(), rules);
rules.newStatefulSession(true);
rules = addSourceToRules(createRule2(), rules);
// We never inserted any alarms, so...
assertFalse(alarmRaised);
}
private RuleBase addSourceToRules(String source, RuleBase rules) throws DroolsParserException, IOException,
Exception {
System.out.println(source);
StringReader reader = new StringReader(source);
PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl(reader);
Package pkg = builder.getPackage();
if (rules == null) {
rules = RuleBaseFactory.newRuleBase();
rules.addPackage(pkg);
}
else {
Package[] packages = rules.getPackages();
for (Package pack : packages) {
if (pack.getName().equals(pkg.getName())) {
Vector<Rule> rulesVector = new Vector<Rule>();
Rule[] packageRules = pack.getRules();
{
for (Rule rule : packageRules) {
rulesVector.add(rule);
}
}
rules.removePackage(pack.getName());
for (Rule rule : rulesVector) {
pkg.addRule(rule);
}
}
}
rules.addPackage(pkg);
}
return rules;
}
public class Alarm {
private String level;
public Alarm(String level) {
this.level = level;
}
public void setLevel(String level) {
this.level = level;
}
public String getLevel() {
return level;
}
}
private String createRule2() {
StringBuilder sb = new StringBuilder();
sb.append("package alarms; \n");
sb.append("import java.util.ArrayList; \n");
sb.append("TestAddPkg; \n");
sb.append("TestAddPkg.Alarm; \n");
sb.append("rule highLvlAlarm \n");
sb.append("when \n");
sb.append(" $a : ArrayList(size > 0) from collect (Alarm( level != \"low\") )\n");
sb.append("then \n");
sb.append(" // callTheCops(); \n");
sb.append(" QuickTest.raiseAlarm(); \n");
sb.append(" System.out.println(\">>>Police alerted.<<<\"); \n");
sb.append("end \n");
return sb.toString();
}
private String createRule1() {
StringBuilder sb = new StringBuilder();
sb.append("package alarms; \n");
sb.append("import java.util.ArrayList; \n");
sb.append("import TestAddPkg; \n");
sb.append("import TestAddPkg.Alarm; \n");
sb.append("rule lowLvlAlarm \n");
sb.append("when \n");
sb.append(" $a : ArrayList(size > 0) from collect (Alarm( level == \"low\")) \n");
sb.append("then \n");
sb.append(" // quietlyInvestigateLowLvlAlarms(); \n");
sb.append(" System.out.println(\"All is good.\"); \n");
sb.append("end \n");
return sb.toString();
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBPORTAL-2267) Ability to override global transaction timeout value for CMS component
by Magesh Kumar B (JIRA)
Ability to override global transaction timeout value for CMS component
----------------------------------------------------------------------
Key: JBPORTAL-2267
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2267
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.7.0 Final
Reporter: Magesh Kumar B
Assignee: Sohil Shah
Uploading large files in CMS times out with the message:
javax.servlet.ServletException: Transaction is not active: tx=TransactionImpl:XidImpl
However this could be overcome by increasing the TransactionTimeout value for the org.jboss.tm.TransactionManagerService mbean in server/<server-config>/conf/jboss-service.xml. Now this affects the timeout value for all applications deployed in JBossPortal server, which is not what is needed. Instead a facility to increase the timeout value for only the CMS component is desired.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBPORTAL-2362) Improve german language-resource-files in portal-cms.war, portal-admin.war and portal-users-samples.war
by Hardy Massen (JIRA)
Improve german language-resource-files in portal-cms.war, portal-admin.war and portal-users-samples.war
-------------------------------------------------------------------------------------------------------
Key: JBPORTAL-2362
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2362
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.7.2 Final
Reporter: Hardy Massen
Some german language-resource-files need corrections:
1.
file jboss-portal.sar/portal-cms.sar/portal-cms.war/WEB-INF/classes/Resource_de.properties:
CMS_MSG_UPLOADARCHIVE_ASYNC=Ihr Archiv wurde zur Verarbeitung akzeptiert. Sobald die Verarbeitung abgeschlossen ist, wird die Ressource wird in Ihrem Verzeichnis gelistet werden.
should be:
CMS_MSG_UPLOADARCHIVE_ASYNC=Ihr Archiv wurde zur Verarbeitung akzeptiert. Sobald die Verarbeitung abgeschlossen ist, wird die Ressource in Ihrem Verzeichnis gelistet werden.
2.
also file jboss-portal.sar/portal-cms.sar/portal-cms.war/WEB-INF/classes/Resource_de.properties:
CMS_LINK_TO_RESOURCES=Verweise auf Ressourcen innerhalb dieses Portals sollten absolut sein. Beispiel: Ein Verweis auf ein Bild mit dem Pfad default/images/back.gif sollte genau wie hier aufgef\u00fchrt eingegeben werden. Stellen Sie dem Ressourcenpfad kein Slash (/) voran. Sie k\u00f6nnen den Verweis \u00fcberpr\u00fcfen, indem Sie auf den Vorschau-Button im Editor klicken.
should be:
CMS_LINK_TO_RESOURCES=Verweise auf Ressourcen innerhalb dieses Portals sollten relativ sein. Beispiel: Ein Verweis auf ein Bild mit dem Pfad default/images/back.gif sollte genau wie hier aufgef\u00fchrt eingegeben werden. Stellen Sie dem Ressourcenpfad kein Slash (/) voran. Sie k\u00f6nnen den Verweis \u00fcberpr\u00fcfen, indem Sie auf den Vorschau-Button im Editor klicken.
In my opinion, the "absolute path" should be a "relative path", like the example "default/images/back.gif" say.
/path/from/root = absolute
path/from/somewhere = relative
This is also wrong in all other existing language-versions.
3.
file jboss-portal.sar/samples/portal-users-samples.sar/portal-users-samples.war/WEB-INF/classes/Resource_de.properties:
ONE_USER_ONLINE=Sie sind der einizge Benutzer online
should be:
ONE_USER_ONLINE=Sie sind der einzige Benutzer online
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JASSIST-68) Remove limitation on public constructors
by Erik Putrycz (JIRA)
Remove limitation on public constructors
----------------------------------------
Key: JASSIST-68
URL: https://jira.jboss.org/jira/browse/JASSIST-68
Project: Javassist
Issue Type: Feature Request
Affects Versions: 3.8.1.GA
Reporter: Erik Putrycz
Assignee: Shigeru Chiba
Currently when extending a class with javassist, it is required that the superclass has a public constructor. However, in some cases, this is not a necessary constraint.
For instance when extending a class and generating a factory with Javassist, it is better to hide the constructor to prevent users to bypass the factory, and this is not possible currently.
This would involve a minor change in inheritAllConstructors() in class CtNewClass
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months