[JBoss Seam] - Re: Seam-gen
by avbentem
"cormet" wrote : I am not too sure about Jboss seam only support ejb3. if this is the case, then i shouldn't use it because i'll use hibernate.
You can surely use Hibernate along with EJB3; all Seam examples use it too.
If the Seam Gen generated project gives you an EAR then I think you'll need to deploy that (and not just the WAR file that you might find within that EAR).
Alternatively, you'll need to tell Seam Gen to generate a WAR-only project -- if it can do that (searching for "embedded EJB3 might help you to find the answer; but using EJB3 might be easier).
Your Could not create Component: org.jboss.seam.core.init without any further details will not be enough for people to tell you what's wrong.
Arjan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049790#4049790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049790
19 years
[JNDI/Naming/Network] - Servlets being deployed before session beans in 4.0.5GA
by asylumx
Hello.
I'm trying to move my application from Jboss 4.0.4GA to Jboss 4.0.5GA and I'm coming across the following problem:
| 14:53:01,778 ERROR [STDERR] com.mycompany.myapp.shared.service.DelegateInitializationException: javax.naming.NameNotFoundException: myapp not bound
| 14:53:01,779 ERROR [STDERR] at com.mycompany.myapp.shared.service.SystemDelegate.<init>(Unknown Source)
| 14:53:01,779 ERROR [STDERR] at com.mycompany.myapp.webclient.servlet.SystemCodeContextListener.contextInitialized(Unknown Source)
| 14:53:01,779 ERROR [STDERR] at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
| 14:53:01,779 ERROR [STDERR] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
| 14:53:01,780 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
| 14:53:01,780 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
| 14:53:01,780 ERROR [STDERR] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
| 14:53:01,780 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
I have an HttpServlet (SystemDelegate), which is initialized via a context listener (SystemCodeContextListener) on deployment, that looks up a bunch of session beans in its constructer so that they are ready to go when they are actually needed. This listener is being deployed before the session beans in 4.0.5GA even though it was deployed after in 4.0.4GA which means the session beans don't exist yet - hence the naming exception.
The entire app is deployed in an earfile named myapp.ear and this all works fine on 4.0.4GA but I get the error above when attempting to deploy on 4.0.5GA.
Is there any way to force the app to deploy the context listener AFTER the session beans? We have a similar problem in another application, as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049787#4049787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049787
19 years
[JBoss jBPM] - Re: Process definition instantiation (java call)
by Wash
"Wash" wrote : Hi Guys !
|
| We are trying to start a new jBPM process instance from java code, is there any sample code to perform it properly? We are able to send a notification for an suspended instance, but when we try to create an instance, then we don't have a jobId which must be specified.
|
| As we know a JobID is normally related to a pending task and not for a creation.
|
| Our code looks like:
|
|
|
|
| InitialContext ic = new InitialContext();
| | QueueConnectionFactory qcf = (QueueConnectionFactory) ic.lookup("XAConnectionFactory");
| | qc = qcf.createQueueConnection();
| | qc.start();
| | session = qc.createQueueSession(true, QueueSession.AUTO_ACKNOWLEDGE);
| | Queue queue = (Queue) ic.lookup("queue/JbpmCommandQueue");
| | QueueSender sender = session.createSender(queue);
| |
| | //ObjectMessage msg = session.createObjectMessage();
| | ObjectMessage om = session.createObjectMessage();
| |
| | HashMap<String, Object> map = new HashMap<String, Object>();
| | map.put("long99", new Long(99));
| | map.put("stringABC", "ABC");
| | map.put("boolean", new Boolean(false));
| | om.setObject(map);
| |
| | org.jbpm.command.NewProcessInstanceCommand newProcessInstanceCmd = new org.jbpm.command.NewProcessInstanceCommand();
| |
| | newProcessInstanceCmd.setActorId("ernie");
| | newProcessInstanceCmd.setCreateStartTask(true);
| | newProcessInstanceCmd.setProcessId(38L);
| | newProcessInstanceCmd.setProcessName("ProcessName");
| | newProcessInstanceCmd.setVariables(map);
| |
| | om.setObject(newProcessInstanceCmd);
| | //om.setLongProperty("jobId", 286L);
| | sender.send(om);
| | sender.close();
| | session.commit();
|
|
|
| Wash
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049785#4049785
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049785
19 years
[Clustering/JBoss] - Re: topic not bound in HAJMS
by anaholzbach
Hi Brian,
Thanks for the quick reply. That would make sense. Here's the stack trace:
| javax.naming.NameNotFoundException: topic 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.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at flex.messaging.services.messaging.adapters.JMSProxy.getDestination(JMSProxy.java:186)
| at flex.messaging.services.messaging.adapters.JMSTopicConsumer.start(JMSTopicConsumer.java:59)
| at flex.messaging.services.messaging.adapters.JMSAdapter.manage(JMSAdapter.java:345)
| at flex.messaging.services.MessageService.manageSubscriptions(MessageService.java:571)
| at flex.messaging.services.MessageService.serviceCommand(MessageService.java:152)
| at flex.messaging.MessageBroker.routeCommandToService(MessageBroker.java:622)
| at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:298)
| at flex.messaging.endpoints.rtmp.AbstractRTMPServer.dispatchMessage(AbstractRTMPServer.java:682)
| at flex.messaging.endpoints.rtmp.NIORTMPConnection$RTMPReader.run(NIORTMPConnection.java:665)
| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:643)
| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
| at java.lang.Thread.run(Thread.java:595)
Will do as you say and in the meantime try to come up with a workaround. How hard would it be to implement the getJndiProperties() method in DeploymentUnit to read the properties you mentioned ?
Thanks again,
Ana
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049784#4049784
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049784
19 years