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

[Design of Clustering on JBoss] - JBOSS Cluster Agent for Solaris Cluster Tools

by krabhishek

Hi I am new to this community and I wish to develop a HA Cluster Agent for JBOSS to port JBOSS on Solaris Open High Availability cluster. This is my first attempt to write a HA Cluster Agent, so any pointers to JBOSS internals would be great. Thanks in advance, Abhishek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181374#4181374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181374

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Getting rid of conf/jboss-service.xml

by scott.stark＠jboss.org

I have this working with the naming beans in a naming-jboss-beans.xml and the legacy-conf-service.xml. I'm looking through the current https://svn.jboss.org/repos/jbossas/projects/docs/community/5/Installatio... and we have a lot to update if we are going to restructure conf, possibly including moving out some of the bootstrap beans files as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181358#4181358 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181358

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Depends on @JMX mbean name

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : Actually this is working. I had forgot that beans deployments now need to end in jboss-beans.xml and so none of the naming beans were even being deployed. | I spent 30 mins of my time yesterday in tracing the log wondering why my xxx-beans.xml was not getting processed. How can we help users with this? Maybe some warning message hinting at xxx-jboss-beans.xml? I did spend another 30mins figuring out why the ENC to obtain the JBoss security manager was not working. I had forgotten the "java:/jaas" prefix in the jboss-web.xml security domain configuration. https://jira.jboss.org/jira/browse/JBAS-6060 It is our own conventions biting us after few days/months. ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181351#4181351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181351

16 years, 3 months

1
0
0 / 0

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

by scott.stark＠jboss.org

The http invoker service depends on the legacy jmx invoker approach as welling as naming service details that are not going to remain the same. I think we should drop this and just have a remoting via http configuration documented/tested in its place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181346#4181346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181346

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Depends on @JMX mbean name

by scott.stark＠jboss.org

Actually this is working. I had forgot that beans deployments now need to end in jboss-beans.xml and so none of the naming beans were even being deployed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181344#4181344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181344

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: meeting context

by jeffdelong

I have not been following this dialog too closely, but just want to throw out some first hand experience with BPMN working on a project with a customer that plans to take the BPMN models and map them to jBPM. My role has been to review BPMN diagrams created by a third party subscontractor. - it is very useful - it does have a lot of symbols - even with guidelines, many users (not just business users, but also developer types) use it in a fairly inconsistent manner It will be a month or two before we map the BPMN diagrams to jPDL; I will let you know how well we do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181324#4181324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181324

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: meeting context

by koen.aers＠jboss.com

"alejandro" wrote : Even if it provides a visual notation and semantics it does not (and should not) define an execution model. Hence BPMN should be an influence and not an objective. Chapter 10 of the BPMN 2.0 draft specifies in about 15 pages the runtime semantics of BPMN. So the committee is clearly not agreeing with your point of view. ;-) That being said, the specified semantics are described in natural language and thus very unclear and confusing. The execution semantics of an activity are *very* complicated. It is specified by a state diagram that contains no less than 20 nodes. It remains to be seen if such a complicated model will get a lot of supporters/implementers. "ronald" wrote : Afaik, but could not find it directly, BPMN is based on structured graphs This is not completely true. BPMN allows for unstructured or 'free' graphs, multiple branches of sequence flow ending in random end events, etc. However, the earlier mentioned runtime semantics specify that some of these constructions are invalid (but of course this would only appear at runtime) as you can see in the following exerpt: anonymous wrote : The Inclusive Gateway is activated if at least one incoming sequence flow has at least one Token and for each empty incoming sequence flow, there is no corresponding Token in the graph anywhere upstream of this sequence flow, i.e. there is no path from a Token to this sequence flow unless the path visits a dominator or postdominator of a non-empty incoming sequence flow of the gateway Aside from all this, I believe indeed that it would be good to discuss the different concepts as much as possible and see where we can 'borrow' from the spec. I saw that the new Choreography part is entirely optional and that the compliance part is still to be defined (if at all possible). So I am not sure how this is going to look when the spec goes final but I am hopeful that we will be able to comply somehow. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181322#4181322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181322

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: meeting context

by alex.guizar＠jboss.com

First and foremost I believe that evaluating and incorporating BPMN terminology and semantics into the product is generally positive. People at conferences and courses often ask about it and it would be good to have a concrete story to tell. That said, BPMN is far from feature complete. Even if it provides a visual notation and semantics it does not (and should not) define an execution model. Hence BPMN should be an influence and not an objective. Second, regarding the API, I believe that making it useful for any process language is an exercise best suited for research rather than practical applications. The differences between process languages are being somewhat downplayed to the point of calling them dialects. For example, you do not normally interact with a BPEL process through an API to begin with. You interact it through the WSDL interfaces defined by the process author. However, a generic API to cover the common subset of all process languages is certainly desirable and in fact already exists in the PVM. I think the meeting should be about the specific API to cover the features of our preferred process language. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181317#4181317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181317

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Depends on @JMX mbean name

by scott.stark＠jboss.org

I'm looking at moving the naming services over to a beans.xml deployment, and one problem I'm seeing is that the mbean name associated with the @JMX annotation is not associated with the bean. This causes dependencies on the mbean name to fail: | *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} | | WebServer | -> jboss:service=Naming{Create:** NOT FOUND Depends on 'jboss:service=Naming' **} | | jboss.admin:service=PluginManager | -> jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor{Create:Configured} | | jboss.ejb:service=EJB3TimerService | -> jboss:service=Naming{Create:** NOT FOUND Depends on 'jboss:service=Naming' **} | | How can we get these depends to continue to work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181316#4181316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181316

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JSR77 View

by scott.stark＠jboss.org

Its the tree of mbeans found in the jbossas/management project in the org.jboss.management.j2ee package. We had discussed making this part of the management interface by adding support for the location of the ManagedDeployment/ManagedComponent in the jsr77 mbean namespace so that the jsr77 view was just a derivative of the profile service mangement view. That requires: - Updating jboss-managed to have an additional jsr77 name component. - Getting management annotation on all ear/ejb/war/car/rar deployer metadata - Create a JSR77Deployer that outputs the ServiceMetaData for the jsr77 mbeans. If we just want to get the basic jsr77 mbean structure that shows the component names, the JSR77Deployer could just be written to map a deployment attachment type to a jsr77 mbean from the org.jboss.management.j2ee package creating the name from the deployment metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181313#4181313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181313

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008