[JBoss Messaging] - JMS JNDI Names
by loewe
I ve written a simple Chat Programm, which uses the old JBossMQ JMS Provider.
In this Programm i am using subcontexts to build up a hierarchical structure of Chatrooms.
My old Service Descriptor looked like this:
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server PUBLIC "-//JBoss//DTD MBean Service 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss-service_3_2.dtd">
|
| <server>
| <mbean code="org.jboss.mq.server.jmx.Topic"
| name="jboss.mq.destination:service=Topic,name=jmschat/room/Lounge">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| </server>
|
|
I ve realized that you developed a new "JBoss Messaging" and therefore i want to rewrite the Chat for the new Provider.
I added the Classloader entry and changed the Class-Names of the Topic's and Queue's.
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server PUBLIC "-//JBoss//DTD MBean Service 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss-service_3_2.dtd">
|
| <server>
| <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
| <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
| </loader-repository>
|
| <mbean code="org.jboss.jms.server.destination.Topic"
| name="jboss.messaging.destination:service=Topic,name=jmschat/room/Lounge"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
| </server>
|
|
But when i deploy the Service Descriptor, i get the following exception. :(
| 17:42:49,765 ERROR [ExceptionUtil] Topic[null, name=jmschat/room/Lounge] startService
| javax.naming.NameNotFoundException: jmschat not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
| at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
| at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510)
| at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
| at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(DestinationJNDIMapper.java:124)
| at org.jboss.jms.server.destination.DestinationServiceSupport.startService(DestinationServiceSupport.java:129)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
| at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
I am not sure if the problem is the subcontext but it seams like it is!
You know a posible Solution or do i need to rewrite my Chat Programm?
Ralph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985514#3985514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985514
19Â years, 7Â months
[JBoss jBPM] - Re: Is this a viable scenario?
by cocampo
"apill" wrote : We have an EJB 3 application running in Jboss that is designed to track inventory. Our data model is persisted with hibernate and according to the EJB3 spec and we're using stateless session beans to execute business logic from the client application.
|
| I would like design a workflow to manage which actions can be performed upon an item of inventory at any point during it's life. For example, if it is in a repair state it can either be repaired or scrapped.
|
| From the client app it would be nice to ask the server...
| what are the current available actions for this inventory?
| then...
| 1. user selects an action
| 2. client app collects necessary data from the user for the action
| 3. client invokes the action in the workflow to move the inventory to its next state
|
| Is this a valid scenario that could be integrated with jBPM? How might i go about this? Can someone point me to some documentation that might help?
|
| The tutorial/getting started docs are fine, but they give me no clue as to how to begin integrating a workflow with my system.
|
| Adrian
Yes, it is a viable scenario to implement with jBPM. If you already read the tutorial/getting started, then you need to study the API and the manual, all the info is there.
Regarding the "user selects an action" you have two ways to implement conditions:
anonymous wrote :
| 9.3.4. Nodetype decision
|
| Actually there are 2 ways to model a decision. The distinction between the two is based on *who* is making the decision. Should the decision made by the process (read: specified in the process definition). Or should an external entity provide the result of the decision.
|
| When the decision is to be taken by the process, a decision node should be used. There are basically 2 ways to specify the decision criteria. Simplest is by adding condition elements on the transitions. Conditions are beanshell script expressions that return a boolean. At runtime the decision node will loop over its leaving transitions (in the order as specified in the xml), and evaluate each condition. The first transition for which the conditions resolves to 'true' will be taken. Alternatively, an implementation of the DecisionHandler can be specified. Then the decision is calculated in a java class and the selected leaving transition is returned by the decide-method of the DecisionHandler implementation.
|
| When the decision is taken by an external party (meaning: not part of the process definition), you should use multiple transitions leaving a state or wait state node. Then the leaving transition can be provided in the external trigger that resumes execution after the wait state is finished. E.g. Token.signal(String transitionName) and TaskInstance.end(String transitionName).
As you may see from this quote, what you're asking is in the docs. Read chapters 3, 4, 6, 7, 9 (at least these regarding integration, however it is strongly recomended that you read the remaining chapters).
If you still have doubts, then I ask you: if you have a full API (jBPM API), what can YOU do to integrate it with your application if you already know Java????
Regards.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985508#3985508
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985508
19Â years, 7Â months
[JBoss Portal] - Re: Personalized portal general question
by Peter.Coppens
Wow....a reply in less than 15 minutes! That for a start is a big difference compared with my previous experiences in the open source portal world (event the Liferay sales mailing address which I eventually tried...after becoming really very desparate did no reply the first time I tried)
...and it's ok to laugh, although I have to admit I am still laughing a little green after 2 weeks of liferay frustration.
Anyway...so first of all thanks for the answer.
Now, assume I want to throw in some development efforts of my own and that security by "obscurity" is sufficient (to start with).
Would that be feasible in a reasonable amount of time - reasonable meaning 2 weeks for someone with Java expertise but no portal/jboss knowledge?
Thanks,
Peter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985507#3985507
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985507
19Â years, 7Â months
[JBoss jBPM] - Re: Database connection
by J.E.Z
Hi again,
after some tests i discovered the true reason of the problem, but not a solution for it. If anybody know why it happens, tell me please:
| Exception in thread "JbpmCommandExecutor" java.lang.NoClassDefFoundError: org/hibernate/Session
| at org.jbpm.persistence.db.DbPersistenceServiceFactory.openService(DbPersistenceServiceFactory.java:55)
| at org.jbpm.svc.Services.getService(Services.java:136)
| at org.jbpm.svc.Services.getPersistenceService(Services.java:175)
| at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:594)
| at org.jbpm.JbpmContext.getMessagingSession(JbpmContext.java:519)
| at org.jbpm.msg.db.DbMessageService.<init>(DbMessageService.java:49)
| at org.jbpm.msg.db.DbMessageServiceFactory.openService(DbMessageServiceFactory.java:32)
| at org.jbpm.svc.Services.getService(Services.java:136)
| at org.jbpm.svc.Services.getMessageService(Services.java:172)
| at org.jbpm.msg.command.CommandExecutorThread.executeCommand(CommandExecutorThread.java:112)
| at org.jbpm.msg.command.CommandExecutorThread.run(CommandExecutorThread.java:79)
|
Thanks for help.
Regards,
Jeferson Zanim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985503#3985503
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985503
19Â years, 7Â months
[EJB 3.0] - Re: address CMP beans from session bean in other JAR but sam
by sunstarnova
So, die Lösung ist gefunden:
-Man benötigt nur einen persistence.xml - Eintrag in dem JAR mit den Entities, die andere kann leer bleiben.
-Als Verweis benutzt man dann
| @PersistenceContext(unitName="../NAMEDESANDERENJARS.jar#PERSISTENCEUNITNAME") private EntityManager em;
|
Also z.B.
| @PersistenceContext(unitName="../teec-ios-persistence-ejb.jar#ios") private EntityManager em;
|
Das ganze ist dann in der JSR 220: Enterprise JavaBeansTM,Version 3.0 beschrieben und zwar in Abschnitt 16.10.2 (einfach suchen nach "#").
---------------------------------
UPS, just noticed I was qwriting in german - so again in english :-)
So, die Lösung ist gefunden:
-You only need a single persistence.xml - entry in the entity JAR, the other persitence.xml can stay empty.
-The reference works as follows
| @PersistenceContext(unitName="../NAMEDESANDERENJARS.jar#PERSISTENCEUNITNAME") private EntityManager em;
|
For example:
| @PersistenceContext(unitName="../teec-ios-persistence-ejb.jar#ios") private EntityManager em;
|
You can find more information here: JSR 220: Enterprise JavaBeansTM,Version 3.0 Paragraph 16.10.2 (just search for "#").
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985502#3985502
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985502
19Â years, 7Â months
[JBoss Portal] - Re: Personalized portal general question
by roy.russoï¼ jboss.com
"Peter.Coppens" wrote : I would like to implement this using a portal/cms system. I did an initial attempt using Liferay, and while I have it working I did run into a lot of problems (technical problems , missing features and lack of documentation and especially lack of any feedback on the mailing list).
|
Would it be impolite to laugh? ;-)
"Peter.Coppens" wrote :
| 1/ Has anyone done something similar and how difficult/easy was it using jboss portal
|
| and/or
|
| 2/ Anyone any high level guidelines as to how I could translate my requirements to jboss portal concepts.
|
Fine-grained security over CMS nodes (folders/files) will be included in 2.6. Thats probably the one thing we're missing, that you need, in 2.4. With 2.6, you will be able to assign security restrictions on folder/file for any Role or even User.
Note, the CMS in 2.6 will also contain jBPM workflow integration.
So I would have to say at this point in time, we don't have this feature. We have an Alpha of 2.6 scheduled for December, that should have alphaversions of this included within.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985500#3985500
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985500
19Â years, 7Â months