November 2006 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by timfox

The connection factory specifies which connector to use http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone... There can be many connectors active at any one time per server peer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985835#3985835 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985835

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - coolest feature ever

by tom.baeyens＠jboss.com

wow. i just added the coolest feature ever. an email server web application ! :-) in the jpdl/dist build file, there is a target to deploy a webapp through the jboss jmx console. That web app contains one servlet. The servlet will launch a simple mail server on port 25. It will collect all emails that are sent to local host via SMTP (the default configuration for sending mail in jbpm happens to be localhost --what a lucky coincidence--) now you can start executing processes that include mail notifications and reminders and just check the emails in your browser to see if they are cent ok. the page even refreshes itself! i have also added a mail example that just sends one mail. cool, huh ! ENJOY View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985831#3985831 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985831

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by clebert.suconic＠jboss.com

Ron: What's the relationship between multiple invokers (HTTP, Socket), ConnectionFactories and ServerPeer? I'm working with HA support, and I need to know how we would have these relationships on the code. Clebert Suconic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985827#3985827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985827

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Hibernate and Web Console

by falazar

We are updating our web console display inbox that shows all the taskinstances available for a user, and have converted it into a datatable, and added sorting and paging. On the inbox we show the Process Name Task Name Process Initiator Task Start Date Task Due Date Task Variable Doc ID Task Variable URL What is the simplest way to create a Hibernate query to return all these fields, (in general) where it is joining across several tables. We first were using the internal findTaskInstances() which calls the Named Query: TaskMgmtSession.findTaskInstancesByActorId And then calling functions to get the other variables, saving all as a list of objects, and sorting. This was very ineffecient and slow. So I am looking for a way to use hibernate to return maybe a general generic object that we could contain all of these with. I looked at the Criteria package as well, but it seems to only return a single Class object. James View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985818#3985818 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985818

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: improving the build

by tom.baeyens＠jboss.com

"david.lloyd(a)jboss.com" wrote : I only say it because then we can be able to state dependencies on tested versions of software. It is always possible for us to miss something during testing; but if we use tested and "supported" releases of software, it decreases the likelihood that there's a problem that we missed. Also, if customers want to build on what we have, it makes their life a little easier if they know what versions of support libraries they're running. | | That said, it's more of a recommendation than a mandate. :-) for third party libs this is automatically the case (except for the snapshot libs that should be avoided in final releases). for internal jbpm dependencies this doesn't have to be the case cause the sources are tagged. so the complete build is reproducable. the suite bundle serves as the base line. many of the jbpm sub projects are tied together and used together. (just like the jboss components are mostly used in the jboss overall distribution). i don't want to get into a situation where we are forced to label and upload every single internal subproject just to do an overall build. tagging the overall sources should be enough. only if we want to use a specific version of a jbpm subproject, then it should be tagged separate and uploaded and referenced. that was the overall idea. not sure yet if it covers all the needs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985810#3985810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985810

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: improving the build

by david.lloyd＠jboss.com

I only say it because then we can be able to state dependencies on tested versions of software. It is always possible for us to miss something during testing; but if we use tested and "supported" releases of software, it decreases the likelihood that there's a problem that we missed. Also, if customers want to build on what we have, it makes their life a little easier if they know what versions of support libraries they're running. That said, it's more of a recommendation than a mandate. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985802#3985802 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985802

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Attribute handler on ServerPeer

by clebert.suconic＠jboss.com

anonymous wrote : It shouldn't be null though. It's set in initializeRemoting(): I meant values inside handler. Things like serverInvoker, callBackHandlers... everything was null. I have removed the property from HA branch. I will double check the change when we merge. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985801#3985801 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985801

19 years, 4 months

1
0
0 / 0

[Design of JBoss ESB] - httpListener! and interaction with BPEL

by wmhajee

I'm currently trying the Beta version of JBossESB and I'm a bit puzzled! I'm reading the Programmer Guide and found: "Process orchestration, typical via WS-BPEL". But I can't find the httplistener! (or SOAP listener) I found a thread that mention a httplistener. Whats the status and how does you think it could interact with jBPM-BPEL Regards Hans View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985746#3985746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985746

19 years, 4 months

1
0
0 / 0

[Design of JBossCache] - Re: static field replication in PojoCache

by ben.wang＠jboss.com

Yes, with the latest proposal, I am going to allow it unless I see other problems. Originally, I propsed it is ok to have complex Serializable type but just not "aspectized" POJO that needs internall mapping. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985745#3985745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985745

19 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by kabir.khan＠jboss.com

"bstansberry(a)jboss.com" wrote : | 1) JMXIntroduction could just try to register context.getTarget(), catch NotCompliantMBeanException, and then create and register the StandardMBean. Problem is this approach ignores the @JMX.exposedInterface value -- what if the bean is Foo implements FooMBean, Bar, and @JMX.exposedInterface=Bar.class? Kind of an edge case, but not clean. | We could probably do some checking of the exposed interface to see if that matches the standard mbean naming rules? "bstansberry(a)jboss.com" wrote : | 2) JMXIntroduction could try to register context.getTarget() only if @JMX.exposedInterface=null. This would be a clean solution. Problem is null is not a valid value for an annotation attribute, and the attribute type is Class, so you can't use the "" means null trick. (Hacky idea -- make it "Class exposedInterface() default void.class". The compiler accepts that.) | Sounds fine by me "bstansberry(a)jboss.com" wrote : | 3) I tried adding another attribute "boolean registerDirectly() default false;" to @JMX. But the deployment of any beans where it didn't specify the attribute failed in SimpleAnnotationValidator, which makes no attempt to read default values. Default values can be read, but the java reflection api kindly does not allow us a way to read them. If javassist is on the classpath these values can be read. Since the container jars are in jboss/lib: a) We need to move javassist from jboss/server/xxx/lib to jboss/lib so that the mc classloader can see javassist OR b) I could do something similar to what I have done for the other AOP integration and do a check for when javassist has been deployed. I will look into b), but for now you should be able to make progress with a) (which is what we might end up with anyway :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985741#3985741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985741

19 years, 4 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 November 2006