[JBoss Messaging] - Kabutar - GUI platform for Enteprise Messaging
by mskonda
Hello All,
Screen shots of Kabutar(Browze):
http://www.euroindian.com/images/stories/kabutar_screenshot1.jpg
http://www.euroindian.com/images/stories/kabutar_screenshot3.jpg
http://www.euroindian.com/images/stories/kabutar_screenshot3.jpg
I've been working on a personal project since few months. The project aims at developing a GUI for message browsing, message replay, message monitoring etc. There are quite a few thoughts in my brain and on the drawing board that have started shaping up into a broader platform when I started looking into this project with care and seriousness.
As I wish to opensource this project, I have created this project on google code. I named Kabutar as the plaform collection for all these respective functions (Pigeon is called as Kabutar in Hindi (Indian) language and I find this is the most amazing ancient communication means).
Each of these modules/functions are detailed here (although many more to evolve):
Kabutar
Kabutar is a plaform consisting of collection of Graphical User Interfaces (GUI) assisting enterprise messaging. The project is developed on Eclipse framework with different perspectives for various enterprise funcationalities.
Projects/perspectives include:
Browze(Message Monitoring),
Rekal(Message Replay),
Manaze (Message Management) and
Enkrypt (Message Enrichment)
(more on the drawing board!)
Currently the project is hosted on google code. You can visit the project here:
http://code.google.com/p/kabutar/
The purpose of this post is to request if any of you to join me in developing this next generation GUI platform.
The project is based on Eclipse RCP. Currently developed against JBossMessaging, but sure I want to have multi-provider capabilities.
Any contribution is highly appreciated. You can contact me by sending an email at madhusudhan(a)madhusudhan.com or replying to this post. I am happy listening to your thoughts, working with you, accepting contributions to make this project successful.
I will be very greatful if one of you gives it a minute of thought!
Thanks
Madhu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045055#4045055
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045055
19 years, 1 month
[Management, JMX/JBoss] - Re: Managing JBoss programmatically?
by PeterJ
Regarding a list of suffixes. This doc page gives some of that information, particularly the bullet list of deployers: http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#ch2.dep...
A more definitive list can be found in the source at system/src/main/org/jboss/deployment/DeploymentSorter.java, look at DEFAULT_SUFFIX_ORDER.
Yes, you can access the JBoss files from an application inside the container, just do not directly create or modify them, always update them in a temporary directory and then move them to the deploy directory. Otherwise the hot deployer might attempt to deploy the file while you are in the middle of creating it.
By the way, you might find the various system properties created by JBoss handy. To see them, in the jmx-console, choose the MBean jboss:type=Service,name=SystemProperties, and then click the showAll the operation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045049#4045049
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045049
19 years, 1 month
[JBoss Seam] - Re: javax.ejb.EJBNoSuchObjectException
by stu2
"sradford" wrote : True, but...
|
| However, they [POJOs] do not provide the functionality of a session bean (declarative transaction demarcation, declarative security, efficient clustered state replication, EJB 3.0 persistence, timeout methods, etc).
|
| (taken from 3.2.4 of the Seam doc)
Sorry to hijack your thread btw. I've seen the error you're asking about before, and am curious about it myself. Hopefully this topic shift will keep the post at the top of the list and get attention of one of the Seam guys.
Back to pojos vs SFSB scoped to events though. In event scope, several of the features you identified don't apply to event scope (replication, timeouts). In Seam the rest of the items in that list are handled by seam as an abstraction of the container. For instance the recommended useage pattern for seam is to use Seam Managed Persistence Contexts (section 8.3 in the docs) which work equally well with pojos, and there are lots of examples in the seam source. Security is interceptor based as well, and SFSB offer no advantages I'm aware of. I believe you have to call em.joinTransaction() from a pojo (automatic from a SFSB).
Anyway, no biggie, but an interesting question. If anyone has anything to add regarding pros and cons of pojos/SFSB in this scenario I'd be interested to hear. I've been using SFSB only when there is multi-request conversational state.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045047#4045047
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045047
19 years, 1 month
[JBoss jBPM] - jBPM concepts
by simonbaker
As I find it hard to understand code without knowing the intent of the authors, and somehow Q&A seems to help me, I'm starting this thread on high-level concepts such as scoping, containership, thread safety, transactions, etc. as pertains to jBPM. I'm trying to get some kind of model in my head of the software in order to apply it with best practices. Examples are good, but you need a lot of them to fully describe all the possibilities. I'd like to get a better understanding of the design philosophy of jBPM code to better understand how to configure it and use the objects and API effectively.
----------------------------- General Discussion ------------------------
I'm going to state some stuff, probably wrong, and welcome corrections in the spirit of a dialog to help understand the concepts behind jBPM.
What is hard for me to grasp from browsing the API is the scoping and role of objects such as process definitions, process instances, tasks, task instances, even JbpmConfigurations and JbpmContexts.
It seems a JbpmConfiguration determines which "services" are used when a JbpmContext instance is created. This includes the "persistance service". I can imagine that someone could develop a persistance service that uses more than one database, so there is no assumption that a JbpmConfiguration is mapped to a particular database. But I think a JbpmConfiguration is mapped to a single persistance service.
The JbpmContext instance is created from a particular JbpmConfiguration instance, and exposes "some services" for use in the workflow processing. I see that we can create a JbpmContext with a name as well, by using Code:
JbpmConfiguration.createJbpmContext(java.lang.String name)
-- what does that mean? Can transactions in JbpmContexts with different names occur simultaneously (without conflict).
A service of great interest is the "persistance" service, which theoretically should be abstract so we never should need to know how it works and we should never need to access a database directly, etc. The JbpmContext instance magically seems to create a transaction encompassing the various "instance" objects that we create with the JbpmContext instance object and interact with (ProcessInstance, TaskInstance, etc.). A JbpmContext instance seems to be related to a concept called a "session", which implies some kind of connection and related transaction processing ability.
I think the confusion I have is thinking that JbpmConfigurations and JbpmContexts are somehow containers for workflow objects, but they are not. The objects exist in the persistance system (typically a database), and I guess it would be possible for different JbpmConfigurations to provide services that access the same objects.
So there is no real "container" for workflow objects at the API level, you can access them by name and/or Id, although the persistance layer is probably intended to serve as a container. I'm not saying I'd want to do this, but theoretically I could configure two different persistance mechanisms to access the same database using the same table names and other conventions. Then I could create two different JbpmConfiguration objects based on these two different services. I could use one configuration and a JbpmContext instance to deploy a ProcessDefinition and create a new ProcessInstance. I could (maybe) then use the second configuration and a JbpmContext instance to retrieve that ProcessInstance by Id and work with it.
Or could I? That is a question. Does a JbpmContext know whether a ProcessDefinition has been deployed by a JbpmContext created from the same (or different) JbpmConfiguration? Or does it matter? In other words, is there any real containership implied by a JbpmConfiguration?
Normally I would think that if I deploy a ProcessDefinition with a particular JbpmConfiguration (using a JbpmContext created from that JbpmConfiguration), then I could only access that ProcessDefinition or instances of it using a JbpmContext created from the same JbpmConfiguration -- but I'm not sure.
Ok, that's as far as I can get with this. I'd like to hear others' understanding of the jBPM concepts.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045046#4045046
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045046
19 years, 1 month
