April 2009 - jboss-dev-forums - Jboss List Archives

[QA of JBoss Portal] - Jboss portlet Development tools

by oyesiji77

I have been a Websphere Portlet Developer (JSF based portlets) using RAD, I have looked at Jboss Portal and i really do like the Server. But are there IDEs available for portlet development View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225466#4225466 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225466

16 years, 12 months

1
0
0 / 0

[Design of Management Features on JBoss] - Applying persisted changes.

by emuckenhuber

One of the failures i mentioned was about restoring JMS destinations. The updates does not work when the ManagedObjectClass(..) is not present in the deployment descriptor. So the tests with this annotation element are passing, the one without is failing. One other problem i think we could have is that ManagedObjectFactory.initMO does not create the same output, as ManagementView (as this would require e.g. KernelDeploymentManagedObjectCreator) Additionally the failures which can be seen during the bootstrap (https://jira.jboss.org/jira/browse/JBAS-6524) seem also somehow related to this - as when processing the collection in the ManagedObjectFactory, does not have access to the ComponentDeploymentContext.getMetaData() for each bean. Not really sure about this, as it's been a while since i last looked into this. So the main issue with that is when restoring the persisted information it is (of course) relying on the same ManagedObject structure as it was persisted before. Only the values are getting persisted and restored (which makes sense, as the metaType should not change) Therefore i think that this kind of 'override' done by the InstanceClassFactories (getManagedObjectClass), should be done outside the deployers - e.g. in ManagementView when creating the ManagedComponents. So that it always creates the same MO for the attachment persistence. Maybe a related topic Scott created: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222668 This does not not cover partial persistence and removing components, but i think we can discuss that later. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225465#4225465 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225465

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Thread pools...

by clebert.suconic＠jboss.com

Please, ignore this... I was seeing these references, when I was navigating through the memory using JVMTI. Those runnables were being executed at the same time the printReferences was called. If I waited 5 seconds to print the references, all of this went away. !--!-- FieldReference final java.lang.Runnable java.util.concurrent.Executors$RunnableAdapter.task=OBJ(java.util.concurrent.Executors$RunnableAdapter@884010469) | !--!--!-- FieldReference private final java.util.concurrent.Callable java.util.concurrent.FutureTask$Sync.callable=OBJ(java.util.concurrent.FutureTask$Sync@1691493474) | !--!--!--!-- FieldReference private final java.util.concurrent.FutureTask$Sync java.util.concurrent.FutureTask.sync=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@490829456) | !--!--!--!--!-- arrayRef [Ljava.lang.Object;[6] id=@885978865 | !--!--!--!--!--!-- FieldReference private transient java.lang.Object[] java.util.PriorityQueue.queue=OBJ(java.util.PriorityQueue@1602698930) | !--!--!--!--!--!--!-- FieldReference private final java.util.PriorityQueue java.util.concurrent.DelayQueue.q=OBJ(java.util.concurrent.DelayQueue@673532189) | !--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.DelayQueue::take | !--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.DelayQueue::take | !--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.DelayQueue::take | !--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.DelayQueue::take | !--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.DelayQueue::take | !--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.DelayQueue java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.dq=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue@669197186) | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue::take | !--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.BlockingQueue java.util.concurrent.ThreadPoolExecutor.workQueue=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor@1456146415) | !--!--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ThreadPoolExecutor::getTask | !--!--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ThreadPoolExecutor::getTask | !--!--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ThreadPoolExecutor::getTask | !--!--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ThreadPoolExecutor::getTask | !--!--!--!--!--!--!--!--!--!-- Reference inside a method - java.util.concurrent.ThreadPoolExecutor::getTask | !--!--!--!--!--!--!--!--!--!-- StaticFieldReference private static java.util.concurrent.ScheduledThreadPoolExecutor org.jboss.messaging.core.client.impl.ConnectionManagerImpl.pingExecutor | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker.this$0=OBJ(java.util.concurrent.ThreadPoolExecutor$Worker@431709193) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker.this$0=OBJ(java.util.concurrent.ThreadPoolExecutor$Worker@1871151428) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker.this$0=OBJ(java.util.concurrent.ThreadPoolExecutor$Worker@1155557696) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker.this$0=OBJ(java.util.concurrent.ThreadPoolExecutor$Worker@1608577782) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ThreadPoolExecutor java.util.concurrent.ThreadPoolExecutor$Worker.this$0=OBJ(java.util.concurrent.ThreadPoolExecutor$Worker@1567434291) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@729155693) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@148643588) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@490829456) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@1278255007) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@729302055) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@1690464956) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@435865682) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@527797457) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1584397689) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@174736223) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1181554512) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@605399375) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@169776139) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@1569284957) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference final java.util.concurrent.ScheduledThreadPoolExecutor java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.this$0=OBJ(java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1725603492) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private final java.util.concurrent.ScheduledExecutorService org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.pingExecutor=OBJ(org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl@451237309) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!--!--!--!--!--!-- FieldReference private java.lang.Object java.lang.ref.Reference.referent=OBJ(java.lang.ref.Finalizer@1188706162) | !--!--!--!--!--!--!--!--!--!--!--MaxLevel | !--!--!--!--!-- FieldReference final java.util.concurrent.FutureTask java.util.concurrent.FutureTask$Sync.this$0=OBJ(java.util.concurrent.FutureTask$Sync@1691493474) | !--!--!--!--!--!-- object instanceOf class java.util.concurrent.FutureTask$Sync@1691493474 was already described before on this report | !--!--!--!--!-- FieldReference private java.util.concurrent.ScheduledFuture org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.future=OB | ... | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225460#4225460 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225460

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by bradsdavis

@tom, which section of the userguide should I take a look at? Are you saying to look at the Email section of the user guide or use cases elsewhere in the userguide? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225458#4225458 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225458

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by tom.baeyens＠jboss.com

have a look at the userguide. i want to discuss the mail schema further in terms of use cases just like in the userguide. is that ok ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225457#4225457 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225457

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by tom.baeyens＠jboss.com

could you work out a set of examples that explain the schema ? the template example i have already: <mail template="managerNotification" /> that could be used as an activity or an event-listener what about other use cases ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225456#4225456 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225456

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by tom.baeyens＠jboss.com

"alex.guizar(a)jboss.com" wrote : How about the following proposal on the body. | <body type="text"> | <body type="html"> | ok. a type attribute is best. "alex.guizar(a)jboss.com" wrote : Indeed, the attachment name can be deduced from the URL/resource/file but we can have an attribute to specify a different name. | distilling the file name from the url/resource/file is ok "alex.guizar(a)jboss.com" wrote : @tom, I think of the producer as the "Mail" class in jBPM 3, only truly replaceable. | i got that. MailSession should become what Mail was before: the impl class that exposed the functionality that we have implemented. Customisation of mail functionality should be another level. E.g. our base class MailActivity can be customized by users into a CustomMailActivity. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225455#4225455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225455

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by bradsdavis

@alejandro: Don't forget for HTML emails that you can have both regular text [for users that cant render HTML in their email client] and HTML body text. Keeping that in mind, make sure that it can take both of those within the template. Brad View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225445#4225445 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225445

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by alex.guizar＠jboss.com

How about the following proposal on the body. <body type="text"> | <body type="html"> Indeed, the attachment name can be deduced from the URL/resource/file but we can have an attribute to specify a different name. @tom, I think of the producer as the "Mail" class in jBPM 3, only truly replaceable. @brad, the templates and the activity are the same, the only difference is the option to refer to a template in the activity. I will take your suggestion to specify the producer in the template itself, and add a getProducer() method to the MailTemplate class. If you can, please take a look at what I have so far. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225418#4225418 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225418

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Thread pools... (Repost)

by clebert.suconic＠jboss.com

During the process of looking for the QueueControl leak today, the profiler was indirectly showing lots references on RemotingConnectionImpl, going through two static fields, that are using some sort of thread pool: - InVMConnection::factory - ConnectionManagerImpl::pingExecutor The references were aways inside some method on a thread. Probably those references would be gone as soon as the pool is used, but it would be much easier to cleanup leaks if we aways recreate those pools on tearDowns(). (a simple kill -3 would show a cleaned memory if setting the dump-memory option on the VM) I was thinking about creating a method named recreatePingExecutor on ConnectionManagerImpl and another named recreateFactory on InVMConnection, and those methods would be marked to be used by tests only. Is there a problem on that approach? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225416#4225416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225416

16 years, 12 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 April 2009