[EJB/JBoss] - JBossQL IS EMPTY not acting correctly
by vandelay
All,
I am using JBossQL to query a UsersEB. Previous versions of my application I had a Image <1:1> Users CMR relationship. This was updated so that a User can have more than one image; therefore Image <N:1> Users. So the change is instead of returning one Local instance of Image (ImageLocal) it will now return a Collection for each User
For the particular query I am having trouble with, previous version had something similar to
SELECT OBJECT(u) FROM Users u WHERE u.Image IS NULL
And this worked correctly.
In my current query:
SELECT OBJECT(u) FROM Users u WHERE u.Image IS EMPTY
Does not work because in my result set, I do not get Previous version application created users that were NULL as well as Current Version application created users where their Image is EMPTY.
There is no longer a CMR field present in Users and now the CMR field in Image is UserID, which is the PK of Users
My Thinking:
- The old users were created under different circumstances therefore when changed to a N:1 relationship, they no longer were NULL but were altered to "" (Empty string in place of NULL).
-Since the application change, Users and Image will need to be recreated for my application to fully understand the new CMR.
I wanted to get some input from posters before I go this long route.
Thanks,
Blake
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105283#4105283
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105283
18 years, 8 months
[Installation, Configuration & DEPLOYMENT] - problem starting Naming service with jboss-4.2.2.GA
by veraz01170
Hello,
I am using bind address 0.0.0.0, default mode. java sdk jdk1.5.0_11.
Using jboss 4.0.5.GA is not causing any problem.
When starting jboss 4.2.2.GA I get very early in the process the following NullPointerException :
2007-11-16 00:18:25,372 DEBUG [org.jboss.naming.Naming] Creating NamingServer stub, theServer=null,rmiPort=1098,clientSocketFactory=
null,serverSocketFactory=org.jboss.net.sockets.DefaultSocketFactory(a)fbc4815d[bindAddress=/0.0.0.0]
2007-11-16 00:18:25,372 DEBUG [org.jboss.naming.NamingService]
java.lang.NullPointerException
at org.jnp.server.Main.getNamingInstance(Main.java:301)
at org.jnp.server.Main.initJnpInvoker(Main.java:354)
at org.jnp.server.Main.start(Main.java:316)
at org.jboss.naming.NamingService.startService(NamingService.java:284)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.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:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
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.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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
With both versions i am keeping original jboss-service.xml and xmdesc dependencies untouched.
-> Any ideas what the problem could be would be very,very appreciated.
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105275#4105275
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105275
18 years, 8 months
[JBoss Seam] - Re: Seam 2.0 and MyFaces
by stan.silvert@jboss.com
Are you sure that your third party library needs the MyFaces impl? Which one is it? The only one I know of that actually referred to MyFaces core impl classes was old versions of Tomahawk.
If you are still getting conflicts as Pete suggests then you should try removing the JSF impl from /deploy/jboss-web.deployer/jsf-libs. If you do that then you will also need to edit /deploy/jboss-web.deployer/conf/web.xml and comment out these listeners:
<!-- Configures JSF for a web application if the javax.faces.webapp.FacesServlet is declared -->
| <!-- in web.xml. -->
| <listener>
| <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
| </listener>
|
| <!-- Listens to all web app lifecycle events so that @PreDestroy can be called on -->
| <!-- JSF managed beans that go out of scope. You can comment this out if you -->
| <!-- don't use JSF or you don't use annotations on your managed beans. -->
| <listener>
| <listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class>
| </listener>
|
Hope that helps,
Stan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105274#4105274
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105274
18 years, 8 months