[JNDI/Naming/Network] - Re: javax.naming.NoInitialContextException trying to connect
by atuljboss
Actually I tried putting that as well. But I am getting the same exception. I do have a similar other setup that does not give this problem. I am trying to find what is the difference between the two setups. The one that is giving the problem is from the jboss install archive without any changes to it.
Will keep posted if i do find something. But if anybody has a similar issue would appreciate if they can give me some hints.
Thanks.
"GRatcliffe" wrote : Hi,
|
| For remote JNDI access to the JBoss server we use the following:
|
| anonymous wrote :
| | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| | java.naming.provider.url=jnp://localhost:1099
| |
|
| The java.naming.factory.url.pkgs setting is different to your example in that it includes org.jnp.interfaces and org.jboss.naming. I don't know if this is related since I have not used this for an MDB accessing a remote queue.
|
| Gary
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072108#4072108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072108
18Â years, 9Â months
[JBoss jBPM] - Re: task-node attribute create-tasks
by warfster
A good point "...after the node has been entered...". The api is used to:
| ProcessInstance pi = context.newProcessInstanceForUpdate("myProcess");
| pid = pi.getId();
| context.close();
|
| context = getContext();
|
| ProcessInstance pi = context.getProcessInstance(processInstanceId);
|
| TaskMgmtInstance tmi = pi.getTaskMgmtInstance();
|
| TaskMgmtDefinition tmd = tmi.getTaskMgmtDefinition();
|
| Task t = tmd.getTask(taskName);
|
| TaskInstance ti = tmi.createTaskInstance(t);
| ti.setActorId(actorId);
| ti.setName(taskInstanceName);
| ti.setDescription(taskInstanceDescription);
| ti.start();
|
| context.save(ti);
| context.save(pi);
| context.close();
|
|
This happens programmatically before the processinstance has been signalled to leave the start state. The big picture is that for any given processdefinition (project) we want to post a list of all the taskinstances associated with it.
So in answer to your question, no, the task has not been created manually w/api after the node was entered. It was created manually w/api before the node was entered. Bug had not crossed my mind. It was more of a "I'm not using it correctly" concern.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072101#4072101
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072101
18Â years, 9Â months