[jboss-user] [Installation, Configuration & DEPLOYMENT] - UnsatisfiedLinkError with third-party DLL

2007-07-09 Thread psyllogism
Hi all, I'm developing an application on JBoss that uses a third-party DLL utility accessed through the third-party's Java API. Both of these are proprietary and I have no control over their content. When my application tries to use the API, I get an UnsatisfiedLinkError with the following sta

[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: *-ds.xml in EAR

2007-06-19 Thread psyllogism
Through much toil and searching, the solution I found was to put the following into my EAR's application.xml file: | | *-ds.xml | | and it worked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055730#4055730 Reply to the pos

[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - *-ds.xml in EAR

2007-06-11 Thread psyllogism
Hi all, Is it possible to put your *-ds.xml in an EAR so that you can deploy your app as a single unit? I tried just sticking it at the top level of the EAR but that didn't work. Is there some file I have to configure to get this to work? Thanks for your help! View the original post : http://

[jboss-user] [Installation, Configuration & Deployment] - Re: Dynamically loading a class at JBoss startup that uses a

2007-06-08 Thread psyllogism
Never mind, all. Upon further inspection I don't believe this to be a JBoss issue but instead an issue with the third-party library. The third-party jar uses its own custom ClassLoader that I need to fiddle with instead. So if anyone knows how to get GATE ( http://gate.ac.uk ) to play well with

[jboss-user] [Installation, Configuration & Deployment] - Dynamically loading a class at JBoss startup that uses a thi

2007-06-08 Thread psyllogism
I am using JBoss 4.04 installed with EJB 3.0 I have an application that I am trying to deploy in an EAR, and in this application I have an MBean that tries to dynamically load a non-EJB class as JBoss is starting up. The MBean basically looks like this: @Service(objectName="jboss.mx:service=Cla

[jboss-user] [EJB 3.0] - Re: Get an MBean to start on JBoss startup

2007-06-07 Thread psyllogism
Thanks, that worked. I had tried that earlier and it didn't work; but I must have typo-ed the attributes in the annotation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052249#4052249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=postin

[jboss-user] [EJB 3.0] - Get an MBean to start on JBoss startup

2007-06-07 Thread psyllogism
I am using jboss4.0.4 installed with ejb3. I would like to get an MBean's start() method to run as JBoss is starting up. Right now, the only way I know how to do this is to add the following to my %JBOSS_HOME%/server/default/conf/jboss-service.xml file: | | |

[jboss-user] [EJB 3.0] - Re: javax.naming.NotContextException

2007-06-06 Thread psyllogism
I solved it! I needed to add: jboss-ejb3-client.jar jboss-aspect-jdk50-client.jar jboss-aop-jdk50-client.jar to my build path. Now I get to move on to my next error(s), which does not seem to be JBoss/EJB3 related. Thanks for being patient with me! View the original post : http://www.jboss.

[jboss-user] [EJB 3.0] - Re: javax.naming.NotContextException

2007-06-06 Thread psyllogism
Yes, I am using EJB 3.0. I currently do not have an ejb-jar.xml file. I have not developed with EJBs before but I thought that EJB 3.0 does not need one? The lookup code: // Lookup the meta-agent | Properties p = new Properties(); | p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.

[jboss-user] [EJB 3.0] - Re: javax.naming.NotContextException

2007-06-06 Thread psyllogism
Okay. Then on this line: m_metaAgent = (MetaAgent) PortableRemoteObject.narrow(ref, MetaAgent.class); I get the exception: java.lang.ClassCastException | at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(Unknown Source) | at javax.rmi.PortableRemoteObject.narrow(Unknown

[jboss-user] [EJB 3.0] - javax.naming.NotContextException

2007-06-06 Thread psyllogism
Help me please! I am getting the following exception when I try to connect my client application to my server: javax.naming.NotContextException: Reference Class Name: java.lang.Object | Type: FACTORY | Content: MetaAgentImplStatefulProxyFactory | is not a Context | at org.jnp.interfa