Persistence.xml in Hybrid Flex-Java
Hi all,
I've started working on a Hybrid project of Flex-Java using a new setup that is available since Flex Builder 3 Final. It creates 1 project that will hold a flex_src folder, java_src folder and WebContent folder where the compiled files will go to using an internal Eclipse Tomcat server.
Now I want to use persistence.xml for hibernate. But I can't figure out where to place this file inside this project? Is there someone here who does know? Thanks a lot in advance.
Cheers,
Rick
Create a META-INF subdirectory of src and place it in there. This will then be deployed in the resulting WAR file to <appbase>/WEB-INF/classes/META-INF/persistence.xml which is where it needs to end up.
Similar Messages
-
How To Populate An Advanced Data Grid In Flex With An XML Document Created In JAVA
Flex Code:
<?xml version="1.0" encoding="utf-8"?>
<mx:Module xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" width="856" height="698" initialize="onInitData()">
<mx:RemoteObject destination="utilityUCFlexRO" id="utilityUCFlexRO">
<mx:method name="updateStationDetails" result="handleUpdateStationDetailsResult(event)" fault="handleUpdateStationDetailsFault(event)"/>
</mx:RemoteObject>
<mx:RemoteObject id="uniqueIdMasterUCFlexRO" destination="uniqueIdMasterUCFlexRO">
<mx:method name="readByCustomerName" result="handleReadByCustomerNameResult(event)" fault="handleReadByCustomerNameFault(event)"/>
<mx:method name="getCustomerAcDetails" result="handlegetCustomerAcDetailsResult(event)" fault="handlegetCustomerAcDetailsFault(event)"/>
</mx:RemoteObject>
<mx:Script>
<![CDATA[
import mx.events.ListEvent;
import mx.collections.ItemResponder;
import com.citizen.cbs.model.UniqueIdMaster;
import mx.managers.PopUpManager;
import mx.controls.ProgressBarMode;
import mx.effects.Fade;
import mx.controls.ProgressBar;
import com.citizen.cbs.CitizenApplication;
import mx.core.Application;
import mx.messaging.messages.ErrorMessage;
import mx.rpc.events.FaultEvent;
import mx.rpc.events.ResultEvent;
import mx.collections.ArrayCollection;
import mx.controls.Alert;
private var moduleCloseFlag:Boolean=false;
private var v:UniqueIdMaster;
[Bindable]
private var customerDetails:ArrayCollection;
[Bindable]
private var branch:int=0;
[Bindable]
private var XMLDocument:XML;
[Bindable]
private var acDetails:XMLList;
private var _progBar:ProgressBar = new ProgressBar();
private function showLoading(e:Event = null):void
_progBar.width = 200;
_progBar.indeterminate = true;
_progBar.labelPlacement = 'center';
_progBar.setStyle("removedEffect", Fade);
_progBar.setStyle("addedEffect", Fade);
_progBar.setStyle("color", 0xFFFFFF);
_progBar.setStyle("borderColor", 0x000000);
_progBar.setStyle("barColor", 0x6699cc);
_progBar.label = "Please wait.......";
_progBar.mode = ProgressBarMode.MANUAL;
PopUpManager.addPopUp(_progBar,this,true);
PopUpManager.centerPopUp(_progBar);
_progBar.setProgress(0, 0);
private function onInitData():void
utilityUCFlexRO.updateStationDetails(CitizenApplication.menuParameters["modulecode"]);
private function handleUpdateStationDetailsResult(event:ResultEvent):void
if(moduleCloseFlag==true)
Application.application.unloadModule();
private function handleUpdateStationDetailsFault(event:FaultEvent):void
var errorMessage:ErrorMessage = event.message as ErrorMessage;
Alert.show(errorMessage.rootCause.message);
private function onSearch():void
if(txtName.text=="" || txtName.text==null)
Alert.show("Enter a name for search");
return;
if((txtName.text).length < 4)
Alert.show("Search should contain more than 3 alphabets");
return;
var d:String = txtName.text;
branch = CitizenApplication.initInfo.registeredUser.branchDetails.bdBranchNo;
uniqueIdMasterUCFlexRO.readByCustomerName(d,branch);
showLoading();
private function handleReadByCustomerNameResult(event:ResultEvent):void //In handle if record does not exists, dsiplays error message and resets the field
customerDetails =ArrayCollection(event.result);
PopUpManager.removePopUp(_progBar);
if(customerDetails.length==0)
Alert.show("Record Not Found, Enter Proper Name ");
onReset();
private function handleReadByCustomerNameFault(event:FaultEvent):void
Alert.show(event.fault.faultDetail + " -- " + event.fault.faultString + "handleReadByCustomerNameFault");
private function onReset():void
customerDetails=new ArrayCollection();
txtName.text="";
private function onCancel():void
utilityUCFlexRO.updateStationDetails("MM0001");
moduleCloseFlag=true;
private function btnBackClick():void
view1.selectedIndex=0;
private function btnBackClick1():void
view1.selectedIndex=1;
private function onItemClick( e:ListEvent ):void
if(dgCustDetails.selectedItem == null)
Alert.show("Select Proper Record");
else
lblId.text = e.itemRenderer.data.uimCustomerId;
lblName.text = e.itemRenderer.data.uimCustomerName;
var custId:int = Number(lblId.text);
uniqueIdMasterUCFlexRO.getCustomerAcDetails(custId,branch);
showLoading();
private function handlegetCustomerAcDetailsResult(event:ResultEvent):void
//XMLDocument = event.result as XML;
acDetails = new XMLList(event.result.menu);
//Alert.show("Name: "+event.result.@name);
PopUpManager.removePopUp(_progBar);
view1.selectedIndex=1;
//adg1.dataProvider=acDetails;
private function handlegetCustomerAcDetailsFault(event:FaultEvent):void
PopUpManager.removePopUp(_progBar);
Alert.show(event.fault.faultDetail + " -- " + event.fault.faultString + "handlegetCustomerAcDetailsFault");
]]>
</mx:Script>
<mx:ViewStack height="688" width="856" id="view1">
<mx:Canvas>
<mx:Panel x="51" y="25" width="754" height="550" layout="absolute" title="Customer Search Page">
<mx:HBox x="174" y="26" horizontalAlign="center" verticalAlign="middle">
<mx:Label text="Enter Name:"/>
<mx:TextInput id="txtName" width="228"/>
<mx:LinkButton label="Search" click="onSearch()"/>
</mx:HBox>
<mx:Label text="--" id="lblId" x="40" y="194"/>
<mx:Label text="--" id="lblName" x="40" y="226"/>
<mx:DataGrid dataProvider="{customerDetails}" id="dgCustDetails" allowMultipleSelection="false" editable="false"
showHeaders="true" draggableColumns="false" width="718" height="373" itemClick="onItemClick(event);" x="10" y="61">
<mx:columns>
<mx:DataGridColumn headerText="Customer Id" dataField="uimCustomerId" width="150"/>
<mx:DataGridColumn headerText="Customer Name" dataField="uimCustomerName"/>
</mx:columns>
</mx:DataGrid>
<mx:ControlBar>
<mx:Button label="CANCEL" click="onCancel()" width="80"/>
<mx:Button label="RESET" click="onReset()" width="80"/>
</mx:ControlBar>
</mx:Panel>
</mx:Canvas>
<mx:Canvas>
<mx:TitleWindow x="10" y="10" width="836" height="421" layout="absolute">
<mx:AdvancedDataGrid x="6.5" y="10" id="adg1" designViewDataType="tree" variableRowHeight="true" width="807" height="278" fontSize="14">
<mx:dataProvider>
<mx:HierarchicalData source="{acDetails}"/>
</mx:dataProvider>
<mx:groupedColumns>
<mx:AdvancedDataGridColumn headerText="Type Of A/c" dataField="@Name" width="150"/>
<mx:AdvancedDataGridColumn headerText="Details Of A/c"/>
</mx:groupedColumns>
<mx:rendererProviders>
<mx:AdvancedDataGridRendererProvider id="adgpr1" depth="2" columnIndex="1" renderer="AcDetails1" columnSpan="0"/>
</mx:rendererProviders>
</mx:AdvancedDataGrid>
<mx:ControlBar height="56" y="335">
<mx:Button label="BACK" width="80" click="btnBackClick()"/>
<mx:Spacer width="100%"/>
<mx:Button label="EXIT" click="onCancel()" width="80"/>
</mx:ControlBar>
</mx:TitleWindow>
</mx:Canvas>
</mx:ViewStack>
</mx:Module>
XML File Generated In JAVA:
<?xml version="1.0" encoding="UTF-8"?>
<menu>
<AcType Name="Savings">
<SavingAcDetails AcName="Mr. MELROY BENT" AccountNo="4" ClearBalance="744.18" ProductID="SB" TotalBalance="744.18">
<SavingMoreAcDetails AcStatus="OPERATIVE" AcType="NORMAL" FreezeCode="No Freeze" ModeOfOper="AnyOne Single Or Survivor"/>
</SavingAcDetails>
</AcType>
<AcType Name="TermDeposit">
<TDAcDetails AcName="Mr. BENT MELROY" AccountNo="1731" ProductID="TD">
<TDMoreAcDetails AcStatus="OPERATIVE" AcType="NORMAL" FreezeCode="No Freeze" ModeOfOper="Either or Survivor"/>
</TDAcDetails>
<TDAcDetails AcName="Mr. BENT MELROY" AccountNo="2287" ProductID="TD">
<TDMoreAcDetails AcStatus="NEW" AcType="NORMAL" FreezeCode="No Freeze" ModeOfOper="Self"/>
</TDAcDetails>
<TDAcDetails AcName="Mr. BENT MELROY" AccountNo="78" ProductID="TD">
<TDMoreAcDetails AcStatus="OPERATIVE" AcType="NORMAL" FreezeCode="No Freeze" ModeOfOper="Self"/>
</TDAcDetails>
</AcType>
</menu>
Tried Alot Of Examples Online But In Vain....
Need Help....
Thanks In Advance....Please help me !!!! I have been stuck up with this issue for the past two days and I need to atleast figure out if this is possible or not in the first place.
-
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?
DrikusJust 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 -
Generating an XML representation of arbitrary Java objects
Hi. Just for fun, I'm attempting to write some code which creates an XML representation of an arbitrary java object using reflection. The idea is that only properties with get/set methods should come through in the XML.
Here is the code:
package com.uhg.aarp.compas.persistence.common.xml;
import java.io.IOException;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.w3c.dom.Document;
import org.w3c.dom.DOMException;
import org.w3c.dom.Node;
import java.util.Stack;
public class XMLDAO {
public static String getXMLWithHeader(Object obj){
return "<?xml version=\"0\"?>" + getXML(obj);
* Returns an XML representation of an arbitrary object
public static String getXML(Object obj){
StringBuffer buffer = new StringBuffer();
AccessorMethod[] accessorMethods = getAccessorMethods(obj);
buffer.append("<" + obj.getClass().getName() + ">\n");
//List
if(obj instanceof List){
List objList = (List)obj;
Iterator iterator = objList.iterator();
while(iterator.hasNext()){
buffer.append(getXML(iterator.next()));
else{
for(int i = 0; i < accessorMethods.length; i++){
Object fieldObj = null;
try{
fieldObj = accessorMethods.invoke();
1. Primitive Wrapper or String(base case)
if(fieldObj instanceof Integer || fieldObj instanceof Float || fieldObj instanceof Double
|| fieldObj instanceof Long || fieldObj instanceof String){
buffer.append("<" + accessorMethods[i].getAccessorFieldName() + ">");
buffer.append(accessorMethods[i].invoke());
buffer.append("</" + accessorMethods[i].getAccessorFieldName() + ">\n");
else if(fieldObj instanceof Object[]){
buffer.append("<" + accessorMethods[i].getAccessorFieldName() + ">\n");
Object[] fieldArray = (Object[])fieldObj;
for(int j = 0; j < fieldArray.length; j++)
buffer.append(getXML(fieldArray[i]));
buffer.append("</" + accessorMethods[i].getAccessorFieldName() + ">\n");
}catch(Exception e){
System.out.println("Couldn't invoke method: " + accessorMethods[i].getName());
buffer.append("</" + obj.getClass().getName() + ">\n");
return buffer.toString();
* Returns the Object representation for the XML - used to rebuild Java objects
* converted to XML by XMLDAO.getXML().
public static Object getObject(String xmlString) throws ParserConfigurationException,
SAXException, IOException{
//the root element is the class name
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlString);
Stack objectStack = new Stack();
return getObject(document);
private static Object getObject(Node n){
//every document is either an object or a bean property
//all bean properties have values
//no object has a value, it can only have bean properties
//the base case occurs when the document has a value
String nodeName = n.getNodeName();
if(n.getNodeValue() == null){
System.out.println("node " + nodeName + " is an object");
else{
System.out.println("node " + nodeName + " is a bean property");
return null;
* Returns all of the "getter" methods for the given object
private static AccessorMethod[] getAccessorMethods(Object obj){
Class theClass = obj.getClass();
Method[] objMethods = theClass.getMethods();
ArrayList methodList = new ArrayList();
for(int i = 0; i < objMethods.length; i++){
try{
methodList.add(new AccessorMethod(obj, objMethods[i]));
}catch(IllegalArgumentException e){}
return (AccessorMethod[])methodList.toArray(new AccessorMethod[methodList.size()]);
* Invokes the specified "getter" method and returns the result as an Object
private Object invokeAccessorMethod(Object obj, Method m) throws IllegalAccessException,
InvocationTargetException{
return m.invoke(obj, null);
package com.uhg.aarp.compas.persistence.common.xml;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;
* Represents an AccessorMethod (i.e. getField()) on an Object
public class AccessorMethod{
private Object obj;
private Method m;
private String accessorFieldName;
* Constructor for AccessorMethod
public AccessorMethod(Object obj, Method m) throws IllegalArgumentException{
1. Method name starts with get
2. Method name does not equal get
3. Method takes no arguments
4. Method return type is not void
String methodName = m.getName();
if(methodName.indexOf("get") != 0 || methodName.length() == 3 &&
m.getParameterTypes().length != 0 && m.getReturnType() != null){
throw new IllegalArgumentException("Not a valid getter method " + methodName);
this.obj = obj;
this.m = m;
String tempName = m.getName().substring(3, m.getName().length());
this.accessorFieldName = Character.toLowerCase(tempName.charAt(0)) + tempName.substring(1, tempName.length());
public Object invoke() throws IllegalAccessException, InvocationTargetException{
return m.invoke(obj, null);
* Gets the m
* @return Returns a Method
public Method getM() {
return m;
* Sets the m
* @param m The m to set
public void setM(Method m) {
this.m = m;
* Gets the accessorFieldName
* @return Returns a String
public String getAccessorFieldName() {
return accessorFieldName;
* Sets the accessorFieldName
* @param accessorFieldName The accessorFieldName to set
public void setAccessorFieldName(String accessorFieldName) {
this.accessorFieldName = accessorFieldName;
* Gets the obj
* @return Returns a Object
public Object getObj() {
return obj;
* Sets the obj
* @param obj The obj to set
public void setObj(Object obj) {
this.obj = obj;
public String getName(){
return this.m.getName();
I'm having some trouble figuring out how to implement the XMLDAO.getObject(Node n) method. I was thinking of maintaining a Stack of the previous Objects as I traverse the DOM, but I think that might be unnecessary work. Basically I'm wondering how I determine what the last "object" is in the DOM from any given node. Anyone have any input?I think the end of my post got cut off:
I'm having some trouble figuring out how to implement the XMLDAO.getObject(Node n) method. I was thinking of maintaining a Stack of the previous Objects as I traverse the DOM, but I think that might be unnecessary work. Basically I'm wondering how I determine what the last "object" is in the DOM from any given node. Anyone have any input? -
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
PaulHave 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.plHi 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 -
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
AbhiActually 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 -
Deploying persistence.xml in ejb-jar componts
Hi,
If you are deploying ejb-jar components which are packaged independently and are remote components but they all access the same database, do you put the persistence.xml in the META-INF of each component (ejb-jar). If not, where would it go?
I can find lots of references to having a single persistence.xml with many configurations but if (theoretically) each bean is deployed on a separate JVM/Container how would it access the persistence.xml?
Thanks.If you are deploying the EJB JARs to different Java EE servers, then yes, each EJB JAR needs its own persistence.xml. You would configure each Java EE server to point to the same JDBC resource.
If you are deploying them all to the same server, you should package the entity classes into a single JAR file, and include that JAR file in an EAR with the other EJB JARs. In that scenario, persistence.xml is in the JAR's META-INF directory. The JAR file can either be in the top-level of the EAR, or in the EAR's library directory. In this case, the scope of the persistence unit is the entire EAR.
-ian -
Share persistence.xml file between two EJB modules in EAR
Hello, everybody!
First of all, I would like to say that I already posted this question in another forum:
[http://community.jboss.org/thread/154128?tstart=0]
But as I haven't got any answer from there and this issue is very crucial to me I'm posting it here too in the hope that I get an answer. So, here it goes:
I have two EJB modules in an EAR module. I would like to know how to share a single persistence.xml file with these two EJB modules. If I replicate the persistence.xml file in the two EJB modules, the EAR project deploys ok, but of course that's not what we want. If I remove the persistence.xml file from any of the EJB projects, the EAR doesn't deploy properly. I'm stuck with this. I've already tried many kind of configurations but none worked. I really would like to have some help with this issue to proceed working. This is my EAR structure:
solicitacoes-ejb.jar (EJB session beans)
solicitacoes-dao.jar (EJB interfaces)
solicitacoes-dao-jpa.jar (EJB session beans)
solicitacoes-ejbClient.jar (entities and EJB interfaces)
solicitacoes-web.war
META-INF/This is my application.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<application
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
version="5">
<display-name>solicitacoes-ear</display-name>
<module>
<ejb>solicitacoes-ejb.jar</ejb>
</module>
<module>
<ejb>solicitacoes-dao-jpa.jar</ejb>
</module>
<module>
<web>
<web-uri>solicitacoes-web.war</web-uri>
<context-root>solicitacoes</context-root>
</web>
</module>
</application>If I remove the persistence.xml file from one of the EJB modules, let's say solicitacoes-dao-jpa.jar, I get this error when deploying the EAR file:
... 39 more
Caused by: java.lang.IllegalArgumentException: Can't find a persistence unit named 'null' in AbstractVFSDeploymentContext@28359170{vfs:///C:/jboss-6.0.0.20100429-M3/server/default/deploy/solicitacoes-ear.ear/solicitacoes-dao-jpa.jar/}
at org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107) [:1.0.2-alpha-1]
at org.jboss.ejb3.Ejb3Deployment.resolvePersistenceUnitSupplier(Ejb3Deployment.java:778) [:1.3.1]
at org.jboss.ejb3.EJBContainer.resolvePersistenceUnitSupplier(EJBContainer.java:1517) [:1.3.1]
at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:130) [:1.3.1]
... 43 moreI need help with this issue. As you could see, the EJB container doesn't like to see an EJB module without a persistence.xml file. This is clearly a dumb decision though. I agree with it if there was only one EJB module in an EAR. But the container should have been smart enough to require only one persistence.xml file in an EAR module with more than one EJB module, and share that persistece context with the whole EAR.
Acting the way it is acting now, the container forces us to duplicate the persistece.xml file and kill our application modularity. This is clearly wrong. I've already tried to put the entity classes and persistence.xml file in the lib directory of the EAR, but it didn't work either. The container needs to have the persistence.xml file in both EJB modules.
I don't know if this is a JBoss implementation decision or if it comes from the Java EE 6 specification. Whatever it is, it goes against all good modular and good design decision. Please if some of you know how to solve this, took a little time to tell me how. I would be very grateful.
Thank you in advance.
MarcosDear Mr. gimbal2,
In another occasion I would not reply to such a 'helpful' answer like the one you gave me (yes, it is undoubtedly an answer because that's how you classified it in the beginning of your reply), but as today I have plenty of time here in my job, for this week we're not working full time as usual, I decided to reply to it.
You have to completely overhaul your attitude.I really didn't know I was taking so personal on this issue to have to 'completely overhaul my attitude'. Thank you for pointing that out.
In stead of calling the technology dumb, admit to yourself that perhaps you don't understand it properly and that your ideas of what is correct design perhaps is a little lacking. I didn't call the technology dumb because I stated very clearly that I don't know for sure if it is working this way. I said in the last paragraph:
+"I don't know if this is a JBoss implementation decision or if it comes from the Java EE 6 specification. Whatever it is, it goes against all good modular and good design decision."+
So, I let implicit the fact that the technology or the implementation of the technology is dumb only if it doesn't allow this possibility. Regarding the fact that your said that I should
admit to myself that perhaps I don't understand it properly, where did I stated in my question that I understand it completely? It's clear in the last paragraph that I don't. If I'm asking that's because I have doubts. Maybe my ideas of what is correct is wrong, and that's why I'm here in this forum. But everyone with a good sense knows that what I propose in this discussion is by no means a wrong design decision. Where is it a sin to have more than one EJB module in a EAR and a persisntece.xml file shared for the whole EAR? Does everyone that has more than one EJB module in an EAR module need to connect to more than one database? Is it wrong to want to have your DAO implementation in a separate EJB module in order to make deployment easy and also changes, if you later want to replace that implementation with another one without affecting
the other modules? I don't think that a design decision that seeks this is lacking. I don't think that Java EE today is a dumb technoloby, but everyone knows that before it gets to the present level, it was a technology known to have made big dumb decisions that the community latter corrected, with ideas like O/R mapping (Hibernate), dependency injection (Spring), Struts and lots of other examples that we all know. No one can deny this and lots of wrong things will continue to be fixed in later releases.
Maybe when you rise yourself back to that level, you open yourself up again to thinking in correct solutions in stead of trying to hammer through your own poorly chosen one.To be sincere, I see you took very personal about this issue. You really shows to be someone that has no respect to other people and you judge them too. I must say that I got surprised by the way you answered my post. I didn't expect to get such sarcastic answer to what I asked. I personally don't act this way. If I can't help a person, I also don't try to ridicularize him.
Marcos -
Deploy failure due to jta-data-source in persistence.xml
Hey All,
This is driving me insane. Every example, including the Sun tutorials (which don't work on my instance of Glassfish), list persistence.xml files like:
"<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0">
<persistence-unit name="persistence_sample">
<provider>oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider</provider>
<jta-data-source>jdbc/SamplesDB</jta-data-source>
<non-jta-data-source>jdbc/SamplesDB__nontx</non-jta-data-source>
</persistence-unit>
</persistence>"
I've tried every combination of <persistence...> tags, with namespace definitions, posted in examples on the internet, but my problem is, any time I deploy my ear with a "<jta-data-source>" tag specified, I receive the following failure from the App Server:
"Error loading deployment descriptors for module [pi-0] Line 26 Column 24 -- Deployment descriptor file META-INF/persistence.xml in archive [pi-ejb.jar]. cvc-complex-type.2.4.a: Invalid content was found starting with element 'jta-data-source'. One of '{"http://java.sun.com/xml/ns/persistence":class, "http://java.sun.com/xml/ns/persistence":exclude-unlisted-classes, "http://java.sun.com/xml/ns/persistence":properties}' is expected.
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:352)
at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:327)
at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:332)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:182)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jta-data-source'. One of '{"http://java.sun.com/xml/ns/persistence":class, "http://java.sun.com/xml/ns/persistence":exclude-unlisted-classes, "http://java.sun.com/xml/ns/persistence":properties}' is expected.
at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:285)
at com.sun.enterprise.deployment.archivist.Archivist.readPersistenceDeploymentDescriptor(Archivist.java:1718)
at com.sun.enterprise.deployment.archivist.EjbArchivist.readPersistenceDeploymentDescriptors(EjbArchivist.java:239)
at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:301)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:200)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readModulesDescriptors(ApplicationArchivist.java:308)
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:316)
... 11 more"
Note that this only happens when I have a <jta-data-source> element in the persistence.xml file. When I comment out the jta-data-source, it deploys without problems (though it doesn't do much). Here's my persistence-unit code:
<persistence-unit name="prodcontext" transaction-type="JTA">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>OneOfMyClasses</class>
<jta-data-source>jdbc/SamplesDB</jta-data-source>
</persistence-unit>
Please help.
Thank you,
ToddOkay okay, my mistake (staring at this thing too long).
The solution is, I confess I overlooked it, the jta-data-source node in the xml has to follow the exact order specified in the xsd. I was putting it below the class nodes, which is a no-no. -
How dos the application will know the path of persistence.xml file
Hi ,
I am seeing examples for ConatierManaged EntityManager
@PersistenceContext
public class Test extends HttpServlet
public void doGet()
EntityManager em
// JnDI Lookup code
em = (EntityManager) ctx.lookup("java:comp/env/persistence/em");
em.persist(Employee)
}Inside web.xml file
<web-app>
<persistence-context-ref>
<persistence-context-ref-name>persistence/em</persistence-context-ref-name>
<persistence-unit-name>my-pu</persistence-unit-name>
</persistence-context-ref>
</web-app>Please tell me how the Application will know the path of persistence.xml file .
Thank you for readingit is predefined; JPA always looks for the persistence.xml file in the META-INF folder.
-
JPA - the container - persistence.xml file
Hi,
I'm just starting out with JPA so these are basic questions.
Firstly, this is what I've done:
1) Created JPA entities from tables
2) I've used JDeveloper to create a Java Service Facade using the wizards.
3) Created a persistence unit and added the JPA entities to this.
The resulting persistence.xml is in a project with only JPA stuff in it (in META-INF).
The project which is run (some EJB 2.0 session beans and message driven beans, all specified in the ejb-jar.xml) has the JPA's projects classpath on its classpath.
The JPA code itself accesses the entity manager programatically i.e. it does not make use of any J2EE container services.
My question is:
Are my JPA entities fully fledged EJB 3.0 entities i.e. are they being managed by the container? I'm accessing the JPA entities in a J2SE way, they just happen to be running within a J2EE container.Are my JPA entities fully fledged EJB 3.0 entities
i.e. are they being managed by the container? I'm
accessing the JPA entities in a J2SE way, they just
happen to be running within a J2EE container.The meaning of "managed" for Entities has changed from EJB 2 to 3. In JPA, Entities are managed by a Persistence Provider and not by the container per se. This is why you can have a managed Entity in a Java SE environment.
But to answer your question, yes your classes are full fledged JPA Entities if read through, merged, or persisted with an EntityManager. You can find out more about the JPA definition of "managed" in section 3.2 of the JPA Spec.
--Shaun -
Multiple Persistence Units in persistence.xml
Hi,
in my session bean I want to read data from two ORACLE-database tables, which are located in two ORACLE-schemas (same ORACLE-instance). So I have defined two datasources, one for each schema. Then I defined two persistence-units in my persistence.xml:
<?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="DACC/AEMA">
<jta-data-source>AEMA</jta-data-source>
</persistence-unit>
<persistence-unit name="DACC/ALLGEMEIN">
<jta-data-source>ALLGEMEIN</jta-data-source>
</persistence-unit>
</persistence>
In NetWeaver Development Studio this result in the following error:
"2 persistence units are found. Only exactly one persistence unti is supported."
What's the solution here? Of course I could define two session beans. But this would result in two development components (DC) as well, because there is only 1 persistence.xml per DC (is this correct?). I don't think this is a good idea. Any other suggestions?
Kind regards,
ChristophHi Christoph,
From a Java EE server perspective there are no issues with multiple PUs in a persistence.xml. This is a limitation of NWDS, or WTP (Dali), to be precise. So, you could try to ignore this error and deploy on the server.
HTH!
\-- Vladimir -
Persistence.xml under classes/META-INF makes other jar references to miss
Hi,
When I am adding persistence.xml to classes/META-INF folder where classes folder got other packages under it, classes in such packages are not getting reference to respective jar files in lib folder. So, deployment of the web project in OAS (Oracle application server) 10g fails mentioning NoClassDef found for classes from library jars referred. If I remove persistence.xml from here, the war file is getting deployed. Deployment fails even when the persistence.xml is available anywhere in classpath (like WEB-INF).
What is the reason & how to correct it?Any alternative approach like manifest or use some settings in OAS?Hi,
To be accessible to the EJB JAR, WAR, or EAR file, a class or a JAR file must be on the deployment classpath. You can achieve this in one of the following ways:
Put the JAR file in the manifest classpath of the EJB JAR or WAR file. Do this by adding a classpath entry to the META-INF/MANIFEST.MF file in the JAR or WAR file. You may specify one or more directories or JAR files, separating them by spaces. The following example shows how the manifest file classpath entry adds the employee/emp-classes.jar file and the employee/classes directory to the classpath of the JAR file that contains the manifest file:
Class-Path: employee/emp-classes.jar employee/classes
Place the JAR file in the library directory of the EAR filethis will make this JAR file available on the application classpath and accessible by all of the modules deployed within the EAR file. By default, this would be the lib directory of the EAR file, although you may configure it to be any directory in the EAR file using the library-directory element in the application.xml deployment descriptor. The following example shows the application.xml file:
<application ...>
<library-directory>myDir/jars</library-directory>
</application>
Java EE allows for persistence support in a variety of packaging configurations. You can deploy your application to the following module types:
EJB modules: you can package your entities in an EJB JAR. When defining a persistence unit in an EJB JAR, the persistence.xml file is not optionalyou must create and place it in the META-INF directory of the JAR alongside the deployment descriptor, if it exists.
Web modules: you can use WAR file to package your entities. In this case, place the persistence.xml file in the WEB-INF/classes/META-INF directory. Since the WEB-INF/classes directory is automatically on the classpath of the WAR, specify the mapping file relative to that directory.
Persistence archives: a persistence archive is a JAR that contains a persistence.xml file in its META-INF directory and the managed classes for the persistence unit defined by the persistence.xml file. Use a persistence archive if you want to allow multiple components in different Java EE modules to share or access a persistence unit. The following example shows how to package entities in a persistence archive:
emp.ear
emp-persitence.jar
META-INF/persistence.xml
META-INF/orm.xml
examples/model/Employee.class
examples/model/Phone.class
examples/model/Address.class
examples/model/Department.class
examples/model/Project.class
Once you created a persistence archive, you can place it in either the root or the application library directory of the EAR. Alternatively, you can place the persistence archive in the WEB-INF/lib directory of a WAR. This will make the persistence unit accessible only to the classes inside the WAR, but it enables the decoupling of the definition of the persistence unit from the web archive itself.
Regards,
Vinay
Maybe you are looking for
-
Windows Vista boot-time reads of iTunes media
I sure hope someone here know SOMETHING about why this happening. I have a few movies in my iTunes library. I never watch them within iTunes, instead I always sync them to my iPod touch to watch them. However, a short time ago, I accidentally double-
-
CAN NOT TRANPORT INFOSPOKE FLAT FILE DESTINATION PATH
Hi, I am writing from infospoke to a flat file in application server. When I transported this to QA, Application server Check box is unchecked and path is changed to path in QA. Do I need to have Logical File name in order to transport. If I ha
-
Page order when reading an Arabic PDF
Hi everybody, I need help with an issue I am having. When I view a book on the two -page scrolling view, the order of the pages is odd paged number is on the left and the even numbered page on the right. When reading arabic, it is read from right to
-
Error on Full Export - missing SYS.DBMS_REPUTIL
Hi, I´m trying to make a full export of my database (8.1.7.0) and I´m getting the folowwing error when it´s almost finishing: . exporting posttables actions EXP-00008: ORACLE error 6550 encountered ORA-06550: line 1, column 18: PLS-00201: identifi
-
Network Device Repository/Database to keep Inventory & other info
I need your help to find a solution/tool which can serve as network repository for our organization. This tool can be database of all network device including servers to keep Visio diagrams, change logs, specify location, escalations, primary and se