[JNDI/Naming/Network] - Problem with deploying
by Infest696
Hello,
I get the following exception if I deploy my ear file to jboss. I have searched in the internet, but i can't find anything about this problem. Maybe sombody can help me.
2007-04-28 12:36:11,687 INFO [org.jboss.ejb3.EJBContainer] STOPPED EJB: de.baumarkt.itemmanagement.ItemmanagementBean ejbName: ItemmanagementBean
2007-04-28 12:36:11,687 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:ear=baumarkt.ear,jar=baumarktEJB.jar,name=ItemmanagementBean,service=EJB3
java.lang.RuntimeException: could not resolve global JNDI name for @EJB for container ItemmanagementBean: reference class: de.baumarkt.itemmanagement.db.ItemmanagementDAO ejbLink: duplicated in baumarktEJB.jar
at org.jboss.injection.EjbEncInjector.inject(EjbEncInjector.java:88)
at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:538)
at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:125)
at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
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 $Proxy57.start(Unknown Source)
at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:296)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:343)
at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
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 $Proxy33.start(Unknown Source)
at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy34.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor18.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 $Proxy9.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)
If somebody has an idea, please tell me...
Thank you!
Pierre
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041629#4041629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041629
17 years, 8 months
[Installation, Configuration & Deployment] - JMS-Topic-Deployment on JBoss 5 Beta 2
by CarstenRudat
Hi all,
I have an (Session-Bean)-JAR within an EAR. Inside the JAR, there is an META-INF/jboss-service.xml witch defines a JMS-Topic "messageTopic".
A sessionBean - inside the same JAR - has an @Resource-injection with this just deployed topic - and this fails. The sessionbean will not be deployed, but after all I see the "messageTopic" in JBoss' jmx-console, so my jboss-service.xml is deployed.
I want to ask, if I do anything wrong? Perhaps, I have to give (how?) an order of deployment (first deploy the topic, then deploy the sessionbean).
Or is it just a bug, because of JBoss 5 is beta?
Additionally, I have to say, that my project worked with jboss-4.0.2.GA.
Best regards,
Carsten
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041628#4041628
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041628
17 years, 8 months
[JBoss Seam] - Re: Mathematical captcha & Email obfuscator
by petemuir
Sorry, I might have sounded a bit negative on the bug tracker - don't get me wrong - I and everyone else (being presumptuous) is really grateful for your contribution :)
"Homer J." wrote : 1. I purposefully didn't use the patch format because I thought it's easier for you to integrate this way and my code doesn't rely on existing seam code. Further my code is "fine grained" - like you demanded. So all you / the seam developers have to do is to rename the classes & merge faces-config.xml, jsf-ui.taglib.xml, taglib.tld into JBossSeam/src/ui.
I find it much easier to read a patch than a set of files - and it also means that you can submit a patch for each area of functionality (even if some patches depend upon others) - such we can see how you've built up the component. It also means that we can more easily choose to apply part of your functionality and know that it works as you intended...
At the end of the day, Gavin will need to review all this anyway, and this will make it faster for him.
anonymous wrote : 2. I might be wrong but AFAIK MathCaptchaResponseValidator does the same job as org.jboss.seam.captcha.CaptchaResponseValidator - that means it gets called by the hibernate validator and relays validation to the MathCaptcha component.
Sorry, my bad, yes you are completely correct.
anonymous wrote : 3. please see 1.
Just far less source of errors - someone forgets to rename something somewhere and it all goes wrong :( If you say - I've developed and tested this patch against Seam head and it works great - then we can apply it with much less work!
anonymous wrote : 4. This part I don't understand: "Further, we are currently trying to work out what the role of JSF components is in Seam. I think we need to hold on commiting the JSF components for now." My hopes just were that you include it in jboss-seam-ui.jar so it can be used like s:link, s:cache, ...
So, with the addition of the Ajax4jsf, RichFaces etc. projects to jboss.org, we are considering what role JSF components have in Seam, and whether some of the controls should be moved to other jboss.org projects. We haven't finished discussing this yet afaik :) So I was just suggesting that we hold of committing this until we have a roadmap for JSF components in Seam. We are still quite a way off 1.3.0.GA so this should be resolved by then!
anonymous wrote : However: My intention was to give you a working example as proof of concept but if you insist on using the patch format I can give it a try (I haven't used it before but I have trust in my eclipse so this will probably work ;)).
I always had problems with Eclipse and CVS patch on the anoncvs connection (it mangles whitespace and newines) and had much more success with command line cvs (looks like you are on a unix machine so this shouldn't be a problem :) ).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041625#4041625
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041625
17 years, 8 months
[JBoss Seam] - If NoResultException, then logic in JSF or Java
by saeediqbal1
In my simple application that i am writing, now i can edit records if a single resultset exist in database, pull it in the form and edit it and click save to modify the contents fine.
Now the problem is that when nothing is returned from that database, for example an activity record for that user, if it doesn't already exist. then i am having a hard time figuring out what to do.
Should i use JSF like in other examples to check if
<s:div rendered="#{reportActivity.value == null}">
| PUT THE FORMS HERE
| </s:div> ... for some reason i'm not sure if the object returned is null even if no row is found but i dont know
if that happens then i put the forms inside the s div tags. and if it is not null then put the forms with value binding in between those s divs at the bottom. Or currently i am playing with creating a new object and putting sample values in it in the .java files. check this
@Create
| public String reportActivity() {
| try {
| value = (Activity) em
| .createQuery(
| "select o from Activity o where o.username = #{identity.username}")
| .getSingleResult();
|
| }
| catch(javax.persistence.NoResultException ex) {
|
| value = (Activity) new Activity();
| value.setUsername("#{identity.username}");
| value.setFirstact("Not Available");
| value.setSecondact("Not Available");
| value.setThirdact("Not Available");
| value.setFourthact("Not Available");
| value.setFifthact("Not Available");
| em.persist(value);
| log.info("reportActivity.reportActivity() action called with: #{reportActivity.value}" + getUsername());
| return "failure";
| }
|
| return "success";
| }
that one is going horribly wrong, it doesn't even pick up the username. and when submitted it enters data in mysql twice 2 rows instead of one and puts in #identity.username instead of the username.
In addition the page flow xml file seems to not work properly either. When my method above should return failure it should go to a different page but it doesnt.
see
<page view-id="/reportActivity.xhtml" login-required="true">
| <navigation>
| <rule if-outcome="failure">
| <redirect view-id="/ActivityEdit.xhtml"/>
| </rule>
| </navigation>
| <navigation from-action="#{reportActivity.updateActivity}">
| <redirect view-id="/ActivityList.xhtml"/>
| </navigation>
| </page>
what are the best practices for this? I know im still stuck at the basics. sorry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041620#4041620
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041620
17 years, 8 months