October 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: JSF setting default values

by woo37830

Okay, trying to nav to two different places depending upon a variable that gets set by an action. here is the n:nav tag <n:nav outcome="transition" url="#{nid == '0' ? 'home.jsf' : 'task.jsf?id=#{nid}'}" storeMessages="true" /> Now I think that the expression parser is getting confused because there is a #{variable} inside of the outside #{string}. Is there another way to do this? I'm thinking of writing a tag that takes a trueValueVariable and a falseValueVariable and a condition and target. If the condition is true, it assigns the trueValueVariable to the target, else it assigns the falseValueVariable. NOW, the question is will the n:nav tag handle a url="#{target}" where the target was the name of the target variable in the previous assignment via the action? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186069#4186069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186069

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - JSF setting default values

by woo37830

Please direct me to the proper forum. Using jsf tag <h:inputText and not getting what I expect. <h:inputText name="ext-inputs" value="#{var['ext-inputs'] == null ? '40' : var['ext-inputs']}" type="text" ... /> On first encounter on the page, it puts a '40' on the page with no complaints. But on a return to the page ( where the variable ext-inputs has been set to '40', I get an error about a "illegal syntax for setOperation" How do I make it so I provide a set of defaults, but afterwards use the set value? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186055#4186055 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186055

15 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by kabir.khan＠jboss.com

Adrian, I have started looking at the new classloaders. Before I do any OSGi stuff, I would like to first replicate the behaviour currently used out-of-the-box in AS, i.e. import/exportAll with domains. To help my understanding, which tests in the jboss-cl project do this? After an initial look these look likely: org.jboss.test.classloader.domain.test.* org.jboss.test.classloading.dependency.test.DomainUnitTestCase org.jboss.test.classloading.dependency.test.HierarchicalDomainUnitTestCase org.jboss.test.classloading.vfs.metadata.test.DomainUnitTestCase Are there any others I should look at at this stage? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186036#4186036 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186036

15 years, 5 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: SAR Deployment Deployers Ordering

by richard.opalka＠jboss.com

To clarify our question: When we have pure .war archive (containing web services) in deploy directory, the deployment process passes on AS bootstrap (our deployers are called after Tomcat is started). When we have .sar archive containing .war archive (containing web services), the deployment process fails on AS bootstrap (our deployers are called before Tomcat is started). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186031#4186031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186031

15 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Merged ClassInfo annotation view?

by scott.stark＠jboss.org

I finally got this working, but I don't see deployment level annotations visible in the deployment scope metadata: | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <annotation>@org.jboss.managed.api.annotation.ManagementDeployment(description="JBossSX Security Beans")</annotation> | |  | <bean name="XMLLoginConfig" class="org.jboss.security.auth.login.XMLLoginConfig"> | <property name="configResource">login-config.xml</property> | </bean> | ... | The ManagementDeployment annotation is not visible via the KernelDeployment DeploymentUnit.getMetaData() mdr accessor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186029#4186029 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186029

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: GWT console project information

by camunda

Hi Heiko. I wonder why a DTO pattern was introduced. Basically I think this adds an own level of complexity and another abstraction. And the current domain objects are PJO's, so no technical need for DTO's. And basically somehow this may relate to the nebulous "API" which isn't yet decided? In the most current applications I face it was decided against DTO's, because it safes a lot of effort for a mostly unecessary abstraction... Or what do you think? Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186028#4186028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186028

15 years, 5 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - SAR Deployment Deployers Ordering

by richard.opalka＠jboss.com

Relates to: JBWS-2246 --- Usecase 1: Service archive (.sar) with POJO web service endpoint (.war archive inside). Usecase 2: Service archive (.sar) with EJB web service endpoint (.jar archive inside). Problem Description: --- Both usecases work fine when we deploy service archive to already running AS instance (using hot deploy feature). The problem appears when service archive is present in deploy directory at AS startup time. Current JBossWS Deployers Architecture: --- There are three JBossWS deployers registered with the JBoss Main Deployer which order is important: EJBDeployer < WebServiceDeployerEJB < WarDeployer WebServiceDeployerPreJSE < WarDeployer < WebServiceDeployerPostJSE Questions: --- When sar deployment (containing .war) is in place the war archive deployment order is different comparing to when war archive is deployed standalone :( Q1: Is it correct deployers behavior? Q2: Shouldn't war or ejb archive inside .sar archive be deployed later? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186027#4186027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186027

15 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: How To Handle Message Selectors in Ordering Groups

by timfox

"gaohoward" wrote : | So here I suggest not to support ordering group with message selectors at all. | | I agree View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186026#4186026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186026

15 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - How To Handle Message Selectors in Ordering Groups

by gaohoward

How To Handle Message Selectors in Ordering Groups The issue is: Messages dropped by a message selector are not really 'removed' by the JMS server, to the receiving consumer the messages seemed dropped. The ordering group cannot simply forget the dropped messages, because the messages dropped by one consumer may be acceptable by another consumer (with a different selector or even without a selector). That will make it difficult to handle. Suppose we have 10 messages, and there are two consumers with different selectors. The first consumer starts to receive with a selector only accepts the last 5 messages. The second consumer starts to receive with a selector that only accepts the first 3 messages. Suppose the two consumers work serially, under normal case both consumers can received their messages. But if the messages belong to a ordering group, after the first consumer has received the last 5 messages, the second can never get the 3 messages because if it can, the ordering is broken. Actually all the first 5 messages will stay in the JMS Server forever! In programming, handling ordering groups with selectors will cause complicated state management and subtle delivery controls, and that perhaps still wouldn't make it possibly work. I tried to change the code and stopped half way simply for fear of totally messing things up and totally ruining my previous work. So here I suggest not to support ordering group with message selectors at all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186025#4186025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186025

15 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMDR-51; Annotation equals is completely broken

by alesj

"scott.stark(a)jboss.org" wrote : Yes, a 2.0.1.GA is what we should do. OK, I need to port the changes to Branch_2_0. Then I'll do the release, probably early Monday morning. Performance wise this is quite different from what we had, but on the other hand, what we had didn't work. :-) And I don't really see how else we can do proper equals, other than comparing all members - using jboss-reflect/BeanInfo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186017#4186017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186017

15 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008