February 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Duplicated client IDs

by timfox

Clebert - why have you added a new query: | SELECT_EXISTS_REF=SELECT MESSAGEID FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID = ? AND MESSAGEID = ? | +SELECT_EXISTS_REF_MESSAGEID=SELECT MESSAGEID FROM JMS_MESSAGE_REFERENCE WHERE MESSAGEID = ? | There's one already there, please use that. You need the channel id anyway. Just query for the message id without specifying the channel id means nothing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012325#4012325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012325

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: various questions

by tom.baeyens＠jboss.com

"Fady" wrote : First of all, each workflow instance should be given a subject | ... | the | subject field provides with a quick way of identifying a task. | you mean as a variable ? what data should be filled in ? i don't think that it is a good idea to force the user to enter a subject. apart from that, the process definition contains a name and a description. also the task definition has a name that is copied into the task instance as a kind of default value. after that, the task instance name is changeable. don't know if the UI allows this currently, though. would the task instance name cover your requirements ? or how is your subject different ? "Fady" wrote : and a | priority. | ... | The | priority fields highlights the criticality of the task | task definitions already have a priority. this priority is copied into a task instance when it is created. then the priority can be changed for that specific task instance. is that what you're looking for ? "Fady" wrote : | Moreover, is there any extra documentation outside the repository? For | instance I want to know what each JBPM tag is doing without having to | go into the actual code. An architecture document if available would | be very helpful. | currently i'm the architecture document :-( feel free to use me for this purpose. maybe i should respond to all your questions in a wiki page so that can grow to become the architecture document... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012321#4012321 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012321

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - various questions

by tom.baeyens＠jboss.com

taking the liberty to post Fady's questions here so everyone can follow the conversation and join in. "Fady" wrote : Dear Tom, | I have been reviewing the code of JBPM in CVS and the code of the | web-console specifically. | And I believe a number of enhancements need to take place. | | First of all, each workflow instance should be given a subject and a | priority. Those fields can be hidden for some users. The benefits of | them come when someone is dealing with a large number of tasks. The | priority fields highlights the criticality of the task while the | subject field provides with a quick way of identifying a task. | | Moreover, is there any extra documentation outside the repository? For | instance I want to know what each JBPM tag is doing without having to | go into the actual code. An architecture document if available would | be very helpful. | | Waiting for your feedback, | | Best Regards, | Fady | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012314#4012314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012314

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - JAX-WS documentation

by thomas.diesler＠jboss.com

Folks, JAX-WS documentation work has started on http://tddell.dyndns.org/mediawiki Please fill in your bits at your earliest convenience. http://jira.jboss.org/jira/browse/JBWS-1307 This needs to get done before we can actually release jbossws-1.2.0 (which is now functionally complete). This work takes priority over CTS, because it is targeted for jboss-4.2 cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012310#4012310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012310

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Descriptive element name a.k.a. label attribute

by paolodt

Nice! Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012309#4012309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012309

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

I only looked at the specs for SOAPBody. Could you please look at the other SOAP elements before we jump to the conclusion that text is generally allowed/disallowed. Once we found out we challege the CTS with our findings. SOAP-1.1 Envelope: ? Header: ? HeaderElement: ? Body: no BodyElement: ? SOAP-1.2 Envelope: ? Header: ? HeaderElement: ? Body: yes BodyElement: ? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012308#4012308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012308

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

SOAP-1.1 is also clear and does not allow text http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383503 anonymous wrote : | 4.3 SOAP Body | | The SOAP Body element provides a simple mechanism for exchanging mandatory information intended for the ultimate recipient of the message. Typical uses of the Body element include marshalling RPC calls and error reporting. | | The Body element is encoded as an immediate child element of the SOAP Envelope XML element. If a Header element is present then the Body element MUST immediately follow the Header element, otherwise it MUST be the first immediate child element of the Envelope element. | | All immediate child elements of the Body element are called body entries and each body entry is encoded as an independent element within the SOAP Body element. | | The encoding rules for body entries are as follows: | | 1. A body entry is identified by its fully qualified element name, which consists of the namespace URI and the local name. Immediate child elements of the SOAP Body element MAY be namespace-qualified. | 2. The SOAP encodingStyle attribute MAY be used to indicate the encoding style used for the body entries (see section 4.1.1). | | SOAP defines one body entry, which is the Fault entry used for reporting errors (see section 4.4). | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012304#4012304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012304

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

The SOAP-1.2 spec is clear aout text in body and bodyElement http://www.w3.org/TR/soap12-part1/#soapbody anonymous wrote : | 5.3 SOAP Body | | A SOAP body provides a mechanism for transmitting information to an ultimate SOAP receiver (see 2.5 Structure and Interpretation of SOAP Bodies). | | The Body element information item has: | | * A [local name] of Body . | * A [namespace name] of "http://www.w3.org/2003/05/soap-envelope". | * Zero or more namespace qualified attribute information items in its [attributes] property. | * Zero or more namespace qualified element information items in its [children] property. | | The Body element information item MAY have any number of character information item children whose character code is amongst the white space characters as defined by XML 1.0 [XML 1.0]. These are considered significant. | anonymous wrote : | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012303#4012303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012303

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ProfileServiceUnitTestCase tests failing

by scott.stark＠jboss.org

The profile service aspects were not being applied again. I have updated the bootstrap-repo.xml with aop:lifecycle-configure and the tests are now passing for me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012287#4012287 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012287

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

Kabir, now none of the aspects configured via the AspectManager ctor xml are being applied, even when I add org.jboss.deployers to the include list. I have to specify the aspects via the aop:lifecycle-configure to get them to be applied. There does not appear to be any support for specifying which method in an aspect to use via the aop:lifecycle-configure element. How would I map these aop.xml element to an aop:lifecycle-configure equivalent? | <aspect name="track" class="org.jboss.profileservice.aop.TrackingAdvice"/> | <bind pointcut="execution(* $instanceof{org.jboss.deployers.spi.attachments.Attachments}->addAttachment(..))"> | <advice name="addAttachment" aspect="track"/> | </bind> | <bind pointcut="execution(* $instanceof{org.jboss.deployers.spi.attachments.Attachments}->removeAttachment(..))"> | <advice name="removeAttachment" aspect="track"/> | </bind> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012283#4012283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012283

19 years, 2 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 February 2007