September 2008 - jboss-dev-forums

[Design of POJO Server] - Re: Testing Bootstrap Dependencies

by alesj

"bstansberry(a)jboss.com" wrote : | Note that I *think* Adrian Brock wants the way those org.jboss.test.deployers unit tests work changed though. I don't recall the specifics; just recall a comment along those lines. | Adrian probably wanted them to be ported to ProfileService API, due to using the right API - not using impl details. And that's what I did: - https://jira.jboss.org/jira/browse/JBAS-5823 But you need to use profileservice AS config to run them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178093#4178093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178093

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Status of documentation in Branch_1_4

by clebert.suconic＠jboss.com

That's one of the questions I had on the 'Merging Branch_Stable and Branch_CP as a single branch..." thread. The documentation on JBoss5 could for instance reflect things that are specific to JBoss5 (For instance the ChannelFactory for JGroups can only be used on JBoss5, the properties for the new binding-manager, the SecurityMetaDataStore on JBoss5). I think we should reformulate the documentation a little bit to be version independent. Maybe adding a chapter "JBoss5 specific"/ "JBoss4 specific"/EAP Specific.. I don't know... something along that line. We still have also the versions written on the doc, the remoting version required on EAP/JBoss.. and some other things. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178090#4178090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178090

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Expression Evaluation in ActionHandler Properties

by brittm

(I've posted this against the JIRA issue, but I'm also posting it here for any who might be searching/following the thread.) I have a fear that automatic expression evaluation for ActionHandler configuration could interfere with the ability to solve some interesting problems. I'll provide an example below. A recommendation: Rather than hard coding the expression handling logic, provide an example of a base class that users can extend if they want to take advantage of expression handling/syntax in any of their Handlers. With a base class, users can take advantage of expression handling when they want to, customize it if they need to, or intentionally ignore it. Below is a class that I use consistently--if you like it, just re-brand it, re-write it or whatever you like. As an example of customizing the handling of expressions, this particular class provides a specialized 'concatenateEL' method--for instance, if you want to assign swimlanes to a particular Sales queue based on Market, in your AssignmentHandler configuration you could write <group>Sales-#{market}</group> which would evaluate to something like "Sales-London". The stock JbpmExpressionEvaluator doesn't provide for this type of evaluation (and I really don't know if it should.) No, this is not completely automatic for the user, they have to call one of the methods from their Handler, but it does allow them much more flexibility. | /* | * GenericHandler.java | * Created on April 1, 2008, 7:06 PM | * Copyright 2008, Britt Miner. | */ | package org.bminer.jbpm.pd; | | import java.util.regex.*; | import org.jbpm.graph.exe.ExecutionContext; | import org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator; | | /** | * @author bminer | */ | public abstract class GenericHandler { | | // Prepare to identify any EL expressions, #{...}, regex: "#\{.*?}" | String elPatternStr = "#\\{.*?}"; | Pattern elPattern = Pattern.compile(elPatternStr); | | protected String conditionExpression = null; | | /* Evaluate the input as a possible EL expression. */ | protected Object evaluateEL(String inputStr, ExecutionContext ec) { | if (inputStr == null) { | return null; | } | | Matcher matcher = elPattern.matcher(inputStr); | if (matcher.matches()) { //input is one big EL expression | return JbpmExpressionEvaluator.evaluate(inputStr, ec); | } else { | return inputStr; | } | } | | /* Treats input as a possible series of EL expressions and concatenates what | * is found. | */ | protected String concatenateEL(String inputStr, ExecutionContext ec) { | if (inputStr == null) { | return null; | } | | Matcher matcher = elPattern.matcher(inputStr); | StringBuffer buf = new StringBuffer(); | while (matcher.find()) { | // Get the match result | String elExpr = matcher.group(); | // Evaluate EL expression | Object o = JbpmExpressionEvaluator.evaluate(elExpr, ec); | String elValue = ""; | if (o != null) { | elValue = String.valueOf(JbpmExpressionEvaluator.evaluate(elExpr, ec)); | } | // Insert the calculated value in place of the EL expression | matcher.appendReplacement(buf, elValue); | } | matcher.appendTail(buf); | | // Deliver result | if (buf.length() > 0) { | return buf.toString(); | } else { | return null; | } | } | | /* Returns true if the value is a String which contains the pattern delineating | * an EL expression. | */ | protected boolean hasEL(Object value) { | if (value instanceof String) { | Matcher matcher = elPattern.matcher((String) value); | return matcher.find(); | } | return false; | } | | /* Returns true if the value is a String which in its entirety composes | * one EL expression. | */ | protected boolean isEL(Object value) { | if (value instanceof String) { | Matcher matcher = elPattern.matcher((String) value); | return matcher.matches(); | } | return false; | } | | public void setConditionExpression(String condition) { | this.conditionExpression = condition; | } | | public void setCondition(String condition) { | this.conditionExpression = condition; | } | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178088#4178088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178088

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Testing Bootstrap Dependencies

by bstansberry＠jboss.com

You shouldn't add the Ejb3Deployer tag. The fact that the deployers are deployed before anything in deploy/ is one of the things being tested. Have a look at the tests in the testsuite module org.jboss.test.deployers package, e.g. org.jboss.test.deployers.ear.test.EARDeploymentUnitTestCase. Those tests work by deploying something into a running AS and then using some utilities to remotely invoke on the MainDeployer and check the status of the deployments. Yours could do much the same thing, except you ensure the deployment is already there before the AS even starts. Note that I *think* Adrian Brock wants the way those org.jboss.test.deployers unit tests work changed though. I don't recall the specifics; just recall a comment along those lines. Also, as you confirm failures, please open separate JIRA issues for each; if its an EJB3 failure, in EJB3 project, otherwise in JBAS. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178085#4178085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178085

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Merging Branch_Stable and Branch_CP as a single branch..

by clebert.suconic＠jboss.com

"timfox" wrote : Ok I worked out why it is broken. | | If I check out the project first into the directory Branch_1_4 (the default) and try to import into eclipse, it doesn't work since eclipse mandates the directory name is the same as the project name. | | But the project name in the project file is jboss-messaging not Branch_1_4. This works ok if you check out project directly from inside eclipse since Eclispe puts it in a directory called jboss-messaging That's weird. On the Eclipse-version I use it aways ask the project name I want to use. Maybe that's something that used to happen on older Eclipse versions? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178083#4178083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178083

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by clebert.suconic＠jboss.com

I could also read all-pages to recover the nextID, but that didn't seem the best choice. Unless you have a new requirement to generate IDs before Paging, that's not a problem at this moment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178082#4178082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178082

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by clebert.suconic＠jboss.com

yes.. there is a reason. If you restart the server, the IDSequence (LastID) is captured from the Journal. After restart a producer would be generating duplicated IDs. My first option to fix that was to read the last page only, but then I realized that under load you could have those IDs recorded out of order (due to transactions for instance) The best option then was to not generated IDs at all while on Paging. Paging is a buffer working as a client-producer, so that wasn't a problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178081#4178081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178081

17 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Too strict pattern matching in PackageClassFilter

by alesj

"alesj" wrote : | Or is this intentional? | I put back previous behavior and fixed the test to work accordingly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178078#4178078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178078

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Branch_1_4 build-messaging.properties...

by clebert.suconic＠jboss.com

This could stay only on build.xml without any problems. As soon as you release the next EAP-CP release for instance, you tag the Branch and that will contain the release information for that TAG. Unless you want this to have a better/easier control of those names/IDs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178077#4178077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178077

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Differences in config between eap 43 and as 5

by clebert.suconic＠jboss.com

"Tim Fox" wrote : AFAICT the only differences should be related to differences in JBoss remoting config There are more difference you should take in account: - The JGroups config should be also different. JBoss5 will use the ChannelFactory. - messaging-service.xml will be totally different on JBoss5. They have a different SecurityMetadataStore. So, be careful with integration on JBoss5. - Soon JBossRemoting will be also different as the BindingManager is now based on property-substitution for the ports and not any more on that sausage-like XML. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178074#4178074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178074

17 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2008