Classnot found exception- persistence.xml

While Executing Unit test from Eclipse itself, Keep getting exception saying......Unable to load entity class, it's not on the classpath, check your persistence.xml
if anyone have some clue on that?
Entity classes are in some different project in eclipse & have added those Entities jars in My classpath.

Nicky26 wrote:
While Executing Unit test from Eclipse itself, Keep getting exception saying......Unable to load entity class, it's not on the classpath, check your persistence.xml
if anyone have some clue on that?
Entity classes are in some different project in eclipse & have added those Entities jars in My classpath.Java does not agree with you and Java is the boss.
A thought: perhaps the wrong persistence.xml is loaded? In other words, do you have multiple persistence.xml files on the classpath?

Similar Messages

How to clear ClassNot found Exception

Hi
I am running a simple RMI program in linux. It will give class not found exception.(could not find class(Hello_stub) at code base() )
1.HelloInterface.java( Remote Interface)
2.Hello.java(Remote Object Implementation)
3.HelloClient.java(Client program that invokesa method of the remote interface)
Steps are followed.
1.compilation can be done successfully.
javac HelloInterface.java Hello.java HelloClient.java
2.run the rmiregistry command. this step also successfully done.
rmiregistry &
3.rmic Hello
this step also done suceessfully.
this step was create a stub and skeleton classes in the current folder
All the java codes and the class files are there in a single folder.
/home/manohar/
4.Then next step is to run the server program. Here i got an exception ;
java Hello &
Exception in SERVER undeclared Checked Exception: nested exception is:
java.lang.ClassNotFoundException: could not find(Hello_stub) class at codebase().
This RMI example program run in the windows.
I am a fresher and new to RMI.If any one knows please help me.
Thanks and Regards
Manohar.M

You either need to have the stub and interface files available in the classpath of the client and server, OR, you need to tell the server JVM to tell the client where it can find RMI files not in the client classpath:
-Djava.rmi.server.codebase="file:///jars/shared.jar"

Skel classnot found exception

ih
I have made a client nd a server.
My server is in a package called bridgeserver
My client is in a package called bridgeclient
from jdk1.3 I do the following :
rmic bridgeclient.BridgeClient
and
rmic bridgeserver.BridgeServer
but the skels and stubs are made inthe jdk1.3 directory
and not inthe respective packages
resulting in
bridgeserver.BridgeServer_Skel not found exception :
classnotfoundexception.
Isthere something wrong in the classpath ?
my classpath is
CLASSPATH= ..................lots of stuff......;c:\jdk1.3;.

Cross Post!:
http://forum.java.sun.com/thread.jsp?forum=4&thread=184792

Internal Exception: oracle.xml.parser.v2.XMLParseException xsi:type "toplin

i am using toplink 10.1.3.0.0 with oracle app server 10.1.2.2, i am using change field optimistic locking and generating the project xml,
application runs great locally in the jdeveloper, but when it is deployed on app server getting following error
here are the headers from both my project.xml as well as session xml..
<?xml version="1.0" encoding="UTF-8"?>
<toplink:object-persistence version="Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)" xmlns:opm="http://xmlns.oracle.com/ias/xsds/opm" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:toplink="http://xmlns.oracle.com/ias/xsds/toplink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<opm:name>PROJ</opm:name>
<opm:class-mapping-descriptors>
<opm:class-mapping-descriptor xsi:type="toplink:relational-class-mapping-descriptor">
<?xml version="1.0" encoding="UTF-8"?>
<toplink-sessions version="4.5" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<session xsi:type="server-session">
<name>PROJSession</name>
<event-listener-classes/>
<logging xsi:type="toplink-log">
<log-level>finer</log-level>
</logging>
<primary-project xsi:type="xml">PROJ.xml</primary-project>
<login xsi:type="database-login">
<platform-class>oracle.toplink.platform.database.oracle.OraclePlatform</platform-class>
<user-name></user-name>
any help/idea appreciated...
Exception [TOPLINK-9005] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.SessionLoaderException
Exception Description: An exception was thrown while loading the <project-xml> file [PROJ.xml].
Internal Exception: Exception [TOPLINK-25004] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.XMLMarshalException
Exception Description: An error occurred unmarshalling the document
Internal Exception: Exception [TOPLINK-27101] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.platform.xml.XMLPlatformException
Exception Description: An error occurred while parsing the document.
Internal Exception: oracle.xml.parser.v2.XMLParseException: xsi:type "toplink:changed-field-locking-policy" not resolved to a type definition
at oracle.toplink.exceptions.SessionLoaderException.failedToLoadProjectXml(SessionLoaderException.java:74)
at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.loadProjectConfig(TopLinkSessionsFactory.java:316)
at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.createSession(TopLinkSessionsFactory.java:241)
at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildServerSessionConfig(TopLinkSessionsFactory.java:215)
at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildSession(TopLinkSessionsFactory.java:168)
at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildTopLinkSessions(TopLinkSessionsFactory.java:124)
at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:103)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:367)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:334)
at myProjectPackage.common.data.toplink.ToplinkDataManagerPeer.<init>(ToplinkDataManagerPeer.java:41)
at myProjectPackage.common.data.DataManagerFactory.getDataManagerInstance(DataManagerFactory.java:40)
at myProjectPackage.common.servlet.NYSDOTFilter.getDataManager(NYSDOTFilter.java:964)
at myProjectPackage.common.servlet.NYSDOTFilter.doFilter(NYSDOTFilter.java:144)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at myProjectPackage.caf.servlet.NYSDOTCAFFilter.doFilter(NYSDOTCAFFilter.java:90)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
at myProjectPackage.common.servlet.NYSDOTLoginFilter.doFilter(NYSDOTLoginFilter.java:95)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:669)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:340)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:228)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:570)

first thanks for your reply,
i already figured that out and deployed it using 10.1.3.1 jars
my question
1) if it is a bug , how come it works fine with jdeveloper (
i would appreciate if you could provide any info about it.
2) i dont want to sound sarcastic , but 10.1.3.1 has of optimistic locking and the recommended solution i found was to use descriptor.getQueryManager().setUpdateCallCacheSize(0);
looks like 10.1.3.1 fixed one bug and introduced other one which was working fine earlier...
is there any other way of fixing optimistic locking issue other than using the
descriptor.getQueryManager().setUpdateCallCacheSize(0);
where i can find the latest/greatest (up to date patched version of toplink)
thanks again for your help

Problem with Persistence.xml in JDev final after migration

Hi,
I am trying to migrate a current project from JDev 11gTp4 to the JDev production release. When deploying the EJB module I get the following problem though (Stack from DefaultServer.log)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Nexus-NexusModel-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
     at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.setupDocumentBuilderFactory(RegistryDocumentBuilder.java:393)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.getDefaultDocumentBuilderFactory(RegistryDocumentBuilder.java:359)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.getDocumentBuilder(RegistryDocumentBuilder.java:298)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:150)
     at org.eclipse.persistence.platform.xml.jaxp.JAXPParser.parse(JAXPParser.java:163)
     at org.eclipse.persistence.platform.xml.jaxp.JAXPParser.parse(JAXPParser.java:197)
     at org.eclipse.persistence.internal.oxm.record.DOMUnmarshaller.unmarshal(DOMUnmarshaller.java:213)
     at org.eclipse.persistence.oxm.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:309)
     at org.eclipse.persistence.internal.jpa.metadata.xml.XMLEntityMappingsReader.read(XMLEntityMappingsReader.java:72)
     at org.eclipse.persistence.internal.jpa.metadata.xml.XMLEntityMappingsReader.read(XMLEntityMappingsReader.java:112)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadStandardMappingFiles(MetadataProcessor.java:343)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadMappingFiles(MetadataProcessor.java:271)
     at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:294)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:830)
     at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:189)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330)
     at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
     at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
     at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209)
     at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310)
     at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:376)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
My persistence.xml looks like
<?xml version="1.0" encoding="windows-1252" ?>
<persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0" xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="Nexus-ejbPU">
<provider>
org.eclipse.persistence.jpa.PersistenceProvider
</provider>
<jta-data-source>
jdbc/NexusPoolDS
</jta-data-source>
<mapping-file>
META-INF/orm.xml
</mapping-file>
<properties>
<property name="eclipselink.target-server" value="WebLogic_10"/>
<property name="eclipselink.logging.file" value="Toplink.log"/>
<property name="eclipselink.logging.timestamp" value="true"/>
<property name="eclipselink.logging.exceptions" value="true"/>
<property name="eclipselink.logging.session" value="true"/>
</properties>
</persistence-unit>
</persistence>
orm.xml looks like this
<?xml version="1.0" encoding="windows-1252" ?>
<entity-mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence/orm">
<persistence-unit-metadata>
<persistence-unit-defaults>
<schema>
XXX
</schema>
</persistence-unit-defaults>
</persistence-unit-metadata>
<package>
za.co.medscheme.model.persistence.xxx
</package>
<schema>
XXX
</schema>
</entity-mappings>
I have noticed that the persistence.xml file have changed quite drastically from the version we had in TP4 release during project upgrade, but can not explain the problem we are getting. I have also tried to just create a dummy project and create a persistence unit, and the file looks exactly the same afterwards. Any thoughts?
Drikus

Just thought I would add a temporary solution to the problem for those of you sitting with the same issue.
In the root folder of your application you will find a src folder with a meta-inf folder and weblogic-application.xml inside.
Add the following before the closing weblogic-application tag...
<xml>
<parser-factory>
<saxparser-factory>
weblogic.xml.jaxp.WebLogicSAXParserFactory
</saxparser-factory>
<document-builder-factory>
weblogic.xml.jaxp.WebLogicDocumentBuilderFactory
</document-builder-factory>
<transformer-factory>
weblogic.xml.jaxp.WebLogicSAXTransformerFactory
</transformer-factory>
</parser-factory>
</xml>
If there wasnt an xml tag in the file, it seems that JDeveloper somehow adds one on the fly for you pointing to an oracle xml parser that does not contain the setSchema method required by weblogic on deployment.
Hope this helps anybody else that has this problem.
Regards
Drikus Britz

Urgent Plz reply: java.lang.Class not found exception

Hi All,
I am novice to j2me, I am tryiing communicate data between client and Java server. I have given project name client and midlet class name FileViewer.java.
It is compiling succesfully
but when I run it , it is giving error
Unable to create Midlet FileViewer.java
java.lang.classnot found excetption: FileViewer.java
at com.sun.midp.midlet.selector.commandaction(+47)
at javax.microedition.lcdui.Display$displayaccessor.commandaction.(+152)
at com.sun.kvem.midp.lcdui.EmulEventHandler$eventloop.run(+459)
Here is the code
import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
import javax.microedition.io.*;
import java.io.*;
public class FileViewer extends MIDlet implements CommandListener
private Display display; // Reference to Display object
private TextBox tbViewer; // View file contents in a textbox
private Command cmView; // Command to view file
private Command cmExit; // Command to exit
private String url = "http://www.corej2me.com/midpbook_v1e1/scratch/fileViewer.hlp";
public FileViewer()
display = Display.getDisplay(this);
// Define commands
cmView = new Command("View", Command.SCREEN, 2);
cmExit = new Command("Exit", Command.EXIT, 1);
tbViewer = new TextBox("Viewer", "", 250, TextField.ANY);
tbViewer.addCommand(cmView);
tbViewer.addCommand(cmExit);
tbViewer.setCommandListener(this);
public void startApp()
display.setCurrent(tbViewer);
private void viewFile() throws IOException
HttpConnection http = null;
InputStream iStrm = null;
try
// Create the connection
http = (HttpConnection) Connector.open(url);
// Client Request
// 1) Send request method
http.setRequestMethod(HttpConnection.GET);
// 2) Send header information (this header is optional)
http.setRequestProperty("User-Agent", "Profile/MIDP-1.0 Configuration/CLDC-1.0");
// 3) Send body/data - No data for this request
// Server Response
// 1) Get status Line
System.out.println("Msg: " + http.getResponseMessage());
System.out.println("Code: " + http.getResponseCode());
// 2) Get header information
if (http.getResponseCode() == HttpConnection.HTTP_OK)
// 3) Get data (show the file contents)
iStrm = http.openInputStream();
int length = (int) http.getLength();
if (length > 0)
byte serverData[] = new byte[length];
iStrm.read(serverData);
tbViewer.setString(new String(serverData));
Alert alTest = new Alert("Alert Test", new String(serverData), null, null);
display.setCurrent(alTest);
finally
// Clean up
if (iStrm != null)
iStrm.close();
if (http != null)
http.close();
public void pauseApp()
public void destroyApp(boolean unconditional)
public void commandAction(Command c, Displayable s)
if (c == cmView)
try
viewFile();
catch (Exception e)
System.out.println(e.toString());
else if (c == cmExit)
destroyApp(false);
notifyDestroyed();
If some body has knowledge why this error is coming plz share wiht me Its urgent .
Thanks in advance.
Thanx

No, the "-g" version just means it has the debug flag turned on when they compile it.
Your problem is CLASSPATH and how to set it properly.
Use the -classpath option on java.exe when you run. Read the javadocs on the tools to find out how.
%

Override JNDI names in persistence.xml and @resource annotation

I have a Java EE 7 application that I am developing for use with both GlassFish and WildFly, but I have discovered that both application servers use a slightly different format for specifying JNDI names.
In GlassFish the persistence.xml file references the data source jdbc/myDataSouce, but in WildFly the data source needs to be java:/jdbc/myDataSource.The same is also true for classes that are annotated with @Resource. In GlassFish the annotation for a class using JavaMail would be @Resource(name = "mail/myMailSession"), but to deploy onto WildFly this would need to be @Resource(name = "java:mail/myMailSession").
The only solution I've got at present is using Maven to create two different releases of the EAR file, with one EAR file containing a persistence.xml file with the data source jdbc/myDataSouce for use with GlassFish, and the second EAR file containing a persistence.xml file with the data source java:/jdbc/myDataSource for use with WildFly. Unfortunately, I haven't found a solution for the @Resource annotation.
I've taken a look at the documentation for glassfish-application.xml and glassfish-ejb-jar.xml and have tried using resource-ref to override the JNDI names but the application fails to deploy due to an error in the name.
My question is does GlassFish provide any capability to override the JNDI names specified in the persistence.xml file and classes with the @resource annotation?
Many Thanks
Paul

Have you been able to solve this? I'm attempting to understand what Web Server 7 can do with regard to Java Persistence and what elements of it require Glassfish.
I've also spent great amounts of time in WS6.1 trying to figure out why a JNDI resource couldn't be found. The rules of thumb I've learned are:
- Try dropping the *'java:/comp/env/* prefix; just use jdbc/pact part
- Make sure all referrences (in web.xml and sun-web.xml) are identical with regard to that name.
I'm hoping you're not still dealing with this (it's been two months!) but if anybody else stumbles on this, maybe it'll help them.
Dave

Problems with deploy on OC4J 10.1.3.2 with hibernate persistence.xml

Hi all,
I can't deploy an EAR/WAR into oc4j 10.3.2.0 stand-alone, I have the following error message :
2008-03-26 19:50:38.721 NOTIFICATION Binding opsky-webapp-1.0-SNAPSHOT web-module for application opsky to site default-web-site under context root /opsky
08/03/26 19:50:38 oracle.oc4j.admin.internal.DeployerException: [opsky:opsky-webapp-1.0-SNAPSHOT] - Exception creating EntityManagerFactory using PersistenceProvider class org.hibernate.ejb.HibernatePersistence for persistence unit ApplicationEntityManager.
08/03/26 19:50:38 at com.evermind.server.ejb.exception.DeploymentException.exceptionCreatingEntityManagerFactory(DeploymentException.java:130)
08/03/26 19:50:38 at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.createContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:197)
08/03/26 19:50:38 at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initializePersistenceUnit(PersistenceUnitManagerImpl.java:159)
08/03/26 19:50:38 at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initialize(PersistenceUnitManagerImpl.java:86)
08/03/26 19:50:38 at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:733)
08/03/26 19:50:38 at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
08/03/26 19:50:38 at com.evermind.server.Application.getHttpApplication(Application.java:571)
08/03/26 19:50:38 at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
08/03/26 19:50:38 at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
08/03/26 19:50:38 at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1606)
08/03/26 19:50:38 at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
08/03/26 19:50:38 at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:99)
08/03/26 19:50:38 at oracle.oc4j.admin.internal.ApplicationDeployer.bindWebApp(ApplicationDeployer.java:547)
08/03/26 19:50:38 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:202)
08/03/26 19:50:38 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
08/03/26 19:50:38 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
08/03/26 19:50:38 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
08/03/26 19:50:38 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
08/03/26 19:50:38 at java.lang.Thread.run(Thread.java:619)
2008-03-26 19:50:38.987 NOTIFICATION Application Deployer for opsky FAILED.
2008-03-26 19:50:38.987 NOTIFICATION Application UnDeployer for opsky STARTS.
I'm using hibernate 3 with spring, here is my persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0">
<persistence-unit name="ApplicationEntityManager" transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>org.appfuse.model.User</class>
<class>org.appfuse.model.Role</class>
</persistence-unit>
</persistence>
Does enyone know anything about this issue?

Hi,
It would be helpful if you copied and pasted the error messages you get.
For what its worth, it probably isn't a bug, just a configuration problem. You may need to alter more than your application.xml file.
If you developed the EJBs with JDeveloper, you can create a deployment descriptor that adds the necessary configuration files for the OAS platform, and package them into a WAR or EAR. Use Enterprise Manager to deploy the WAR/EAR to the OAS OC4J and everything will be placed where its needed.
More info in the JDeveloper and OAS 10.1.3 documentation.
Jim

Multiple PUs in a single persistence.xml

Hi,
I'm trying to define two different PUs for a standalone and Java EE environments, so a single persistence.xml could be used.
Here goes the persistence.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="derbyPU" transaction-type="RESOURCE_LOCAL">
    <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
    <class>pl.jaceklaskowski.jsf.tomahawk.entities.Pracownik</class>
    <properties>
      <property name="openjpa.ConnectionDriverName" value="org.apache.derby.jdbc.EmbeddedDriver" />
      <property name="openjpa.ConnectionURL" value="jdbc:derby:target/derbyDB;create=true" />
      <property name="openjpa.ConnectionUserName" value="app" />
      <property name="openjpa.ConnectionPassword" value="app" />
      <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema" />
      <property name="openjpa.Log" value="DefaultLevel=WARN,SQL=TRACE" />
    </properties>
</persistence-unit>
<persistence-unit name="Kadry">
    <jta-data-source>jdbc/derby</jta-data-source>
    <class>pl.jaceklaskowski.jsf.tomahawk.entities.Pracownik</class>
</persistence-unit>
</persistence>and here goes the managed bean of a JSF application I'm developing.
package pl.jaceklaskowski.jsf.tomahawk;
import java.util.List;
import javax.faces.model.DataModel;
import javax.faces.model.ListDataModel;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
public class Pracownicy {
    @PersistenceContext(name="Kadry")
    EntityManager em;
    DataModel pracownicy = new ListDataModel();
    public DataModel getLista() {
        List resultList = em.createQuery("SELECT p FROM Pracownik p ORDER BY p.lastName").getResultList();;
        pracownicy.setWrappedData(resultList);
        return pracownicy;
}When I run it on GF v2b36 I'm getting the following exception:
com.sun.enterprise.deployment.backend.IASDeploymentException: Deployment Error -- Could not resolve a persistence unit corresponding to the persistence-context-ref-name [Kadry] in the scope of the module called [C:\projs\myfaces-tomahawk\target\myfaces-tomahawk]. Please verify your application.
        at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPCRefs(BundleDescriptor.java:689)
        at com.sun.enterprise.deployment.WebBundleDescriptor.findReferencedPUs(WebBundleDescriptor.java:709)
        at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.getAllPersistenceUnitDescriptors(PersistenceProcessor.java:158)
        at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:119)
        at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:198)
        at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:159)
        at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:109)
        at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:66)
        at com.sun.enterprise.deployment.backend.ModuleDeployer.handlePostDeployEvent(ModuleDeployer.java:618)
        at com.sun.enterprise.deployment.backend.ModuleDeployer.postDeploy(ModuleDeployer.java:607)
        at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:172)
        at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:174)
        at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:892)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:761)
        at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
        at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)I double-checked that the jar with the Kadry PU is in WEB-INF/lib directory of the web application.
Does anyone have any idea what might be wrong?
Jacek
Jacek Laskowski
http://www.jaceklaskowski.pl

Hi Jacek,
The attribute you should set is unitName(), not name(). name() defines the location of the
@PersistenceContext dependency within the component environment (java:comp/env). It
is independent of the dependency type and appears on all Java EE environment annotations :
@EJB, @Resource, etc.
unitName() specifies the name of the associated persistence unit. If there is only one defined it's
not needed. However, in your case there are two so since it's not specified there isn't enough
information to resolve the correct one.
--ken

Exception in XML Parser

Hi all,
I have a file-XI-file scenario.
In this scenario the Transport Protocol used is FTP.
The remote sender and the receiver system have Golden FTP server installed.
The xml file is getting properly picked from the sender system. The format of this file is:
<?xml version="1.0" encoding="UTF-8" ?>
<ns:file_mt xmlns:ns="http://namespace4BPM1">
<file_type>binary</file_type>
<file_name>input</file_name>
<file_ext>txt</file_ext>
<content_dt>
<firstname>neetu</firstname>
<middlename>k</middlename>
<lastname>gupta</lastname>
</content_dt>
</ns:file_mt>
But the reciever file adapter is giving the following error:
Receiver Adapter v1027 for Party '', Service 'Receiver_Service':
Configured at 10:21:05 2006-06-05
Last message processing started 10:21:35 2006-06-05, Error: Message processing failed with java.lang.Throwable: ftp access error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns:file_mt' found in document', probably configuration error in file adapter (XML parser error)'
The parameters specified in the receiver adapter are:
Connect mode: per file transfer
Transfer mode: Binary
put file: directly
file type : binary
I also tried sending the file after removing the structure 'ns:file_mt', but it gave the structure missing error message.
Pls if anybody could guide me as to what should be done.
Thanks in advance.
Regards
Neetu

check the document name in file adapter configuration channel and message type name of the interface and name space..both should have same name...
check thz blog for more inputs
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Go through them and cross check ur config..

Java applet class not found exception for check scan

I am getting a class not found exception when trying to scan a check into a banking website. The application uses Java and the exception error has the name "com.epaysol.checkscanAppletV2" in the message. I have the latest Firefox and the latest Java installed. I tried going to an earlier version of Firefox and of Java where this app worked in the past and it does not work now in the earlier versions either. So I am now back to the latest version of everything.

Try to clear the Java cache:
* http://www.java.com/en/download/help/5000020300.xml
Control Panel > Java > General tab > "Temporary Internet Files" > Settings > Delete Files
*XP: C:\Documents and Settings\<user>\Application Data\Sun\Java\Deployment\cache\
*Vista: C:\Users\<user>\AppData\LocalLow\Sun\Java\Deployment\cache\

Attempt to process file failed with Exception in XML Parser-format problem

Hi all,
Iam getting an unusual error in the J2EE stack in XI.
And the message is:
006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
This means that error occured during content conversion of XML to the prescribed file format.
Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
Thanks in advance...
karun

Hi Bhavesh,
Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
2006-11-30 17:30:50 Success Start converting XML document content to plain text
2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
2006-11-30 17:31:07 Error Exception caught by adapter framework: null
2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
2006-11-30 17:31:07 Success The message status set to WAIT.
2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

Hibernate in Weblogic10 : class not found exception

Hi All,
I am using JPA/Hibernate in Weblogic 10. While running the application, I am getting the following exception. Can someone help on this.
Exception caught is : java.lang.IllegalArgumentException : org.hibernate.QueryException : ClassNotFoundException : org.hibernate.hql.ast.HqlToken [select p from ParentProfileEntity p where p.email=?1]
I am using JBoss's seam framework . Copy of the persistence.xml is given below.
     <persistence-unit name="userDatabase" transaction-type="JTA">
     <provider>org.hibernate.ejb.HibernatePersistence</provider>
     <jta-data-source>PNDataSource</jta-data-source>
     <properties>
     <property name="hibernate.archive.autodetection" value="class, hbm"/>
          <property name="hibernate.show_sql" value="true"/>
          <property name="hibernate.format_sql" value="true"/>
          <property name="use_sql_comments" value="true"/>
          <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>
          <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/>
     </properties>
     </persistence-unit>
     </persistence>

Hi,
It's a problem with the antlr lib that also exist in weblogic.
You can configure the class loader search order:
Add a file META-INF/weblogic-application.xml in your EAR:
<?xml version="1.0" encoding="ISO-8859-1"?>

<weblogic-application>
     <prefer-application-packages>
           <package-name>antlr.*</package-name>
     </prefer-application-packages>
</weblogic-application>You must provide the antlr lib within the EAR.
Should be ok after that....
Olivier

ORABPEL-11627 Mapping Not Found Exception

Hi,
I am getting into this error . Any idea how I can overcome this.
Invoke_1 (faulted)
[2006/05/16 18:03:20] "{http://schemas.oracle.com/bpel/extension}bindingFault" has been thrown. less
<bindingFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/D:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_check3xml_1.0.jar/write_good_file.wsdl [ write_good_file_ptt::merge(Ebill1500HdrStagingCollection) ] - WSIF JCA Execute of operation 'merge' failed due to: Mapping Not Found Exception. The mapping [ebill1500DtlStagingCollection] for descriptor [class bpel___localhost_default_check3xml_1_0__MD5_1599fb090298a18cd7a14175df888307_.check3xml.Ebill1500HdrStaging] could not be found. The input xml record had an element [Ebill1500HdrStaging/ebill1500DtlStagingCollection]. ; nested exception is: ORABPEL-11627 Mapping Not Found Exception. The mapping [ebill1500DtlStagingCollection] for descriptor [class bpel___localhost_default_check3xml_1_0__MD5_1599fb090298a18cd7a14175df888307_.check3xml.Ebill1500HdrStaging] could not be found. The input xml record had an element [Ebill1500HdrStaging/ebill1500DtlStagingCollection]. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</bindingFault>
thanks in advance

Hi,
I too get the same type of error. But in my case, i don't have two partner links. I have created only one and it throws the same error.
Error details:
<bindingFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/usr/oracle/midtier/integration/orabpel/domains/Dev/tmp/.bpel_DBSample_1.0.jar/DBInsert.wsdl [ DBInsert_ptt::merge(TestQueueCollection) ] - WSIF JCA Execute of operation 'merge' failed due to: Mapping Not Found Exception. The mapping [TestQueue] for descriptor [class bpel___localhost_Dev_DBSample_1_0__MD5_354f16a7145fe31c41b6d41f55336740_.DBSample.TestQueue] could not be found. The input xml record had an element [TestQueue/TestQueue]. ; nested exception is: ORABPEL-11627 Mapping Not Found Exception. The mapping [TestQueue] for descriptor [class bpel___localhost_Dev_DBSample_1_0__MD5_354f16a7145fe31c41b6d41f55336740_.DBSample.TestQueue] could not be found. The input xml record had an element [TestQueue/TestQueue]. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</bindingFault>
Can you please help me to solve this problem?
Thanks

SAPUI5 Project - Missing persistence.xml

Hi,
I have created a simple SAPUI5 application having an Employee form. The values should be saved in the HANA DB. As there are multiple ways to save the data in HANA, I am exploring the JPA based approach.
I am following the Container-Managed Persistence Example and able to create the project. Instead of Dynamic Web project, I have created SAPUI5 project and also changed the project facets as mentioned in the tutorial.
Now the problem is that I am not able to deploy the project on SAP HCP. It is giving me following error -
2014 09 04 07:45:24#+00#ERROR#unknown.jul.logger##anonymous#fs-watcher##p137653trial#jadyn#web##Unable to load Persistence Unit from EAR: /usr/sap/ljs/webapps/jadyn, module: file:/usr/sap/ljs/webapps/jadyn/WEB-INF/classes/. Exception: unexpected element (uri:"http://xmlns.jcp.org/xml/ns/persistence", local:"persistence"). Expected elements are <{http://java.sun.com/xml/ns/persistence}persistence>javax.xml.bind.UnmarshalException: unexpected element (uri:"http://xmlns.jcp.org/xml/ns/persistence", local:"persistence"). Expected elements are <{http://java.sun.com/xml/ns/persistence}persistence>
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:647)....
2014 09 04 07:45:27#+00#ERROR#unknown.jul.logger##anonymous#fs-watcher##p137653trial#jadyn#web##FAIL ... EmpBean:
Missing required persistence.xml for @PersistenceContext ref "em" to unit ""|
2014 09 04 07:45:27#+00#ERROR#unknown.jul.logger##anonymous#fs-watcher##p137653trial#jadyn#web##Invalid EjbModule(name=jadyn, path=/usr/sap/ljs/webapps/jadyn)|
2014 09 04 07:45:27#+00#ERROR#unknown.jul.logger##anonymous#fs-watcher##p137653trial#jadyn#web##FAIL ... jadyn:
Missing required persistence.xml for @PersistenceContext ref "em" to unit ""|
2014 09 04 07:45:27#+00#ERROR#unknown.jul.logger##anonymous#fs-watcher##p137653trial#jadyn#web##Invalid WebModule(name=jadyn, path=/usr/sap/ljs/webapps/jadyn)|
2014 09 04 07:45:27#+00#ERROR#org.eclipse.virgo.web.enterprise.openejb.deployer.VirgoDeployerEjb##anonymous#fs-watcher##p137653trial#jadyn#web##Error while deploying application with real path '/usr/sap/ljs/webapps/jadyn' and web context path '/jadyn'org.apache.openejb.config.ValidationFailedException: Module failed validation. AppModule(name=jadyn)
Anyone has any idea on what wrong I am doing. Please check the attached error log for more details. Thanks!
Regards
Abhi

Actually yes - please get familiar with The SCN Rules of Engagement! In particular, don't push if you haven't received an answer after 3 hours or so.
Now, I am not sure how a UI5 project is exported and what it packages but I would recommend using a Dynamic Web project which is intended for Java web development and supports JPA. You can also have your HTML and JS static resources in it.
Cheers,
--Vlado

Classnot found exception- persistence.xml

Similar Messages

Maybe you are looking for