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

[Design of JBoss jBPM] - Re: jbpm3: signalling tokens through the jsf console

by kukeltje

Yep, one of the lesser used features. Certainly skipping for this release. In the future if the taskinstances related to a token are taken into account it becomes more interesting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185049#4185049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185049

15 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by tom.baeyens＠jboss.com

yes. suspending and resuming tasks individually can be considered non sense. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185040#4185040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185040

15 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: build failing ?

by tom.baeyens＠jboss.com

i got those process archive tests working now also on jdk 6. the problem was that i checked if the ProcessClassLoader found a certain class by loading the class in a process archive, then removing the class from the file system (cause there it is in the test classpath) and then deploying the archive and then using the class. the 2 tests were somehow interfering. i don't know the cause. but it turned out that the test classloader already loaded the action handler before the test began. so the even though the actionhandler was loaded with the process classloader, it was already found previously by the parent of the process classloader before. ps. kukeltje, are you already back awake ? well... in case your were, i'm sure that after reading the previous explanation you have been put back to sleep for another couple of days :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185038#4185038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185038

15 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jbpm3: signalling tokens through the jsf console

by tom.baeyens＠jboss.com

You are right. We might expose the signal as an admin operation. But that should not have priority. Can be skipped. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185035#4185035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185035

15 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by heiko.braun＠jboss.com

So, that means it's nonsense in the current console, right? Then I'll drop it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185028#4185028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185028

15 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Dropping http-invoker.sar?

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : Just an FYI followup, this was rolled back last week as there are several tests that depend on the http invoker. These would have to be refactored into a separate http-invoker testsuite config, and its not likely we'll do this for GA. | What % of tests were affected, Scott? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185025#4185025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185025

15 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Status of LargeMessages work

by timfox

"clebert.suconic(a)jboss.com" wrote : This is the status of my current work on MessageChunk and LargeMessages. | | It is committed on https://svn.jboss.org/repos/messaging/branches/Branch_Chunk_CRS2/ waiting revision before we add it to trunk. Branch_Chunk_CRS2 was just created today (r5188) | | | I - I have added a method getPacketSize on the Packet interface. The abstract class is still returning (at this point at least) the DefaultPacketSize, but MessageSend, Chunk and Receive are calculating the packetSize accordingly. | With that the InVM transport will also work for big messages, and we can avoid extra unecessary buffer creations. | What does "packetSize" represent? * As soon as we merge it on trunk, we could have all the packets implementing this. But this is not a really high priority. anonymous wrote : | II - I have added a new interface called ServerLargeMessage which will be implemented by each storage-manager we have. We have JournalServerLargeMessageImpl and NullStorageManager. The StorageManager will be responsible for the instantiation of this class. | Confusing name. The journal is a large message? anonymous wrote : | III - I have separated the reference counting of references and durable references on Messages (that fix on paging discussed on this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=144128) | | As soon as we remove the reference from the queue (ACKs) I decrement the refCount. I use that ref to delete large messages stored on files. | How is this different to how it was before? anonymous wrote : | IV - Paging could page largeMessages also. (On that case I don't take the bodySize in consideration, as that will be stored outside of the memory). | | V - The ChunkSize is configured on the ConnectionFactory, and the default is 100k | For everyone's benefit could you explain what chunkSize represents, and how it differs (or not) from minLargeMessageSize? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185019#4185019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185019

15 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Status of LargeMessages work

by timfox

"clebert.suconic(a)jboss.com" wrote : VIII - When sending very large messages, I need to make sure the server will not overuse the remoting connection running out of memory, so I've changed the ServerSide flow control to use a Semaphore instead of a AtomicInt. | | As the messages are chunked, I acquire the packetSize (or chunkSize) from availableCredits. When running out of credit ServerConsumerImpl will just wait until more credits are returned from the client. | Isn't that how it already works? I don't understand why you need to change this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185018#4185018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185018

15 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pluggable @EJB Resolvers

by wolfc

Deployment unit is the deployment containing the reference. Despite previous statement, it must be specified. For example suppose A.jar has BeanA with @EJB BeanB b; then the deployment unit will point to A.jar. If that doesn't contain BeanB, then we go to the top level deployment unit (hopefully X.ear) and start looking there. For each deployment unit the JBossMetaData attachment is queried. I don't see how a class loader works into play here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185012#4185012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185012

15 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by tom.baeyens＠jboss.com

Suspending a process instance means that the tasks won't show up in task lists and that timers don't get executed. I don't think that suspend/resume should be offered on the task or token level, but only on the process instance. Starting is optional. In jBPM 4, the lifecycle of a task is configurable with a process. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185009#4185009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185009

15 years, 6 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