J2EE 1.4 beta 2, W2K and Petstore hopeless
Hello
I can deploy the petstore application in J2EE 1.4 beta 2. It works, but only once. After a manual restart of the app server, the I get status 404.
I recognized a message in the deploy process.
reconfig:
[echo] Reconfiguring server server
[sun-appserv-admin] Executing: reconfig port 4848 host ursus --password xx -user admin server
[sun-appserv-admin[ Unable to read system environment. No system environment will be used
Perhaps someone has an idea what this means.
It is a long log available with exceptions stacks.
Starting J2EETM 1.4 Application Server Beta 2 ...
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:50:56:317 CEST][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.1_02] from [Sun Microsystems Inc.]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:146 CEST][ADM0020:Following is the information about the JMX MBeanServer used:]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM0021:MBeanServer Implementation Name:[JMX]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM023:JMX Implementation Version:[1.2_r08]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM024:MBeanServer ID:[ursus_1059238261795]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:677 CEST][ADM0002:System MBean initialized:[ias:type=controller]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:707 CEST][ADM0002:System MBean initialized:[ias:type=configurator]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:737 CEST][ADM0001:MBeanServer initialized successfully]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:787 CEST][ADM0005:Timestamp files for configuration created for:[server]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:797 CEST][ADM0102: Starting a thread for tracking manual changes]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][26.Juli.2003 18:51:22:205 CEST][JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:/Programme/Sun/j2eesdk1.4_beta2/imq/bin].]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:23:887 CEST][S1AS AVK Instrumentation disabled]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.security][26.Juli.2003 18:51:23:907 CEST][SEC1143: Loading policy provider com.sun.enterprise.security.provider.util.PolicyWrapper.]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.transaction][26.Juli.2003 18:51:26:281 CEST][JTS5014: Recoverable JTS instance, serverId = [100]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.resourceadapter][26.Juli.2003 18:51:40:942 CEST][RAR5060: Install JDBC Datasources ...]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:47:301 CEST][Satisfying Optional Packages dependencies...]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:48:533 CEST][ADM0016:Unable to determine java home. This suggests that you are using a version of J2EE plugin incompatible with administration server.]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:48:923 CEST][[AutoDeploy] Enabling AutoDeployment service at :1059238308923]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:48:953 CEST][CORE5100:Loading system apps]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][26.Juli.2003 18:51:51:527 CEST][XML Error line : 39 The content of element type "sun-web-app" must match "(context-root?,security-role-mapping*,servlet*,session-config?,ejb-ref*,resource-ref*,resource-env-ref*,service-ref*,cache?,class-loader?,jsp-config?,locale-charset-info?,property*,message-destination*,webservice-description*)".]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:51:978 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@1a9b034]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:52:568 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
... 11 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:56:975 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@a8cd58]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:56:995 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:56:995 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:035 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: petstore
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:045 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@196649c]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:045 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:159)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:045 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:065 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: petstoreadmin
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:105 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@a75004]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:105 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:159)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:115 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:115 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: supplier
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:115 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@766b42]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:115 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.A
I have not tried out Your advice. But what has this to do with my problem?
Is in the ant build process used US locale or what?
I have also this deploytool not save problem. But I don't want to change the locale only for the app server.
There must be other solutions. Personally it would interest me how someone can come to the locale setting.
Thanks
Urs
Similar Messages
-
Using J2EE 1.4 Beta 2 on Windows 98 and Windows Me
I know J2EE isn't supported on Windows 98 and Windows Me, but like many others I've been able to get J2EE 1.3.1 and J2EE 1.4 Beta to work quite well on Windows 98 and Windows Me. However, no such luck when I tried to do the same with J2EE 1.4 Beta 2. Basically, after downloading j2eesdk-1_4-beta2-windows-eval-app.zip, extracting it into C:\j2ee_app_win, and double clicking setup.exe (or setup.dos.exe for that matter), the setup GUI doesn't appear. Has anybody gotten passed this point and gotten it to work?
Basically, J2EE 1.4 Beta 2 setup.exe doesn't work on Windows 98 or Windows Me even with 256 MB of memory. You'll see it appear on the task bar and then disappear right away. The setup task keeps running, so you have to kill it with Ctrl-Alt-Del.
However, J2EE 1.4 Beta 2 does work quite well on Windows XP Home Edition even though it's not supported by Sun. So if you don't have Windows XP Professional or Windows 2000, you can at least try it.
For help installing and getting started with J2EE 1.4 Beta 2 on Windows XP, see http://groups.msn.com/J2EETools. -
Installing J2EE 1.4 Beta 2
I downloaded and installed the J2EE 1.4 Beta 2 and I am unable to start the server. I keep getting the same message:
Starting the application server, please wait.
Could not start the domain domain1
Startup failed. Please check the server log for more details.
Could not start one or more domains
Press any key to continue . . .
I received this message during the last step of the installation notes:
14. In Start->Programs->Sun Microsystems->J2EE 1.4 SDK, do the following:
a. Click Start Application Server.
The initial domain is automatically created. After domain1 is created, you are prompted as follows:
Press any key to continue . . .
Can anybody guide me to other notes I may need to complete this installation process?
The log shows a few stack traces:
IntrospectionUtils: Unable to resolve host name:/0.0.0.0
<[SEVERE][j2eesdk1.4_beta2][][][10][org.apache.coyote.http11.Http11Protocol][01.July.2003 21:37:33:357 GMT-05:00][Error initializing endpoint
java.net.BindException: Address already in use: JVM_Bind:1043
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:280)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:155)
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1250)
at org.apache.catalina.startup.Embedded.start(Embedded.java:1005)
at com.sun.enterprise.web.WebContainer.start(WebContainer.java:490)
at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:253)
at com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:54)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.July.2003 21:37:33:367 GMT-05:00][Service com.sun.enterprise.web.PEWebContainerLifecycle@114382d cannot be started! : com.sun.appserv.server.ServerLifecycleException: WEB0105: An error occured while starting the web container]>
<[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.July.2003 21:37:33:367 GMT-05:00][CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: WEB0105: An error occured while starting the web container
at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:261)
at com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:54)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind:1043
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1252)
at org.apache.catalina.startup.Embedded.start(Embedded.java:1005)
at com.sun.enterprise.web.WebContainer.start(WebContainer.java:490)
at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:253)
<[WARNING][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.July.2003 21:37:33:427 GMT-05:00][CORE5049: Unexpected error occurred while shutting down applications
java.lang.NullPointerException
at com.sun.enterprise.server.AbstractMonitor.stop(AbstractMonitor.java:65)
at com.sun.enterprise.server.AbstractManager.shutdown(AbstractManager.java:307)
at com.sun.enterprise.server.ApplicationLifecycle.onShutdown(ApplicationLifecycle.java:339)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:409)
at com.sun.enterprise.server.PEMain.run(PEMain.java:184)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[WARNING][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.July.2003 21:41:29:036 GMT-05:00][CORE5049: Unexpected error occurred while shutting down applications
java.lang.NullPointerException
at com.sun.enterprise.server.AbstractMonitor.stop(AbstractMonitor.java:65)
at com.sun.enterprise.server.AbstractManager.shutdown(AbstractManager.java:307)
at com.sun.enterprise.server.ApplicationLifecycle.onShutdown(ApplicationLifecycle.java:339)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:409)
at com.sun.enterprise.server.PEMain.run(PEMain.java:184)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
There appear to be many other problems also but I hope this is sufficient.
Any ideas will be greatly appreciated.
Thank you.Please check if some process is occupying port 1043. The server
seems to be hitting this and hence cannot start. (BindException) -
Which better between Hibernate and EJB
Hello i am a new begginer in J2EE, i have some question
Which better between Hibernate and EJB ?
i still confuse when must using Hibernate or EJB, because as i know in EJB it can use datasource which can i map to Entity bean.
this function is same as Hibernate as i know.
if my concept is wrong please correct my concept
thx in advancedfbrayuki.darmanto wrote:
Hello i am a new begginer in J2EE, i have some question
Which better between Hibernate and EJB ?Just to clarify, you mean EJB3.x, not the earlier versions.
Define "better".
They're actually pretty similar.
If you use Hibernate instead of EJB3 you don't need a full-blown Java EE app server. You can deploy apps on a servlet/JSP engine or on the desktop.
i still confuse when must using Hibernate or EJB, because as i know in EJB it can use datasource which can i map to Entity bean.
this function is same as Hibernate as i know.
if my concept is wrong please correct my concept
thx in advanced% -
I am going to buy a macbook pro for grade 12, and I need to know wheather I should get a macbook pro or a macbook pro retina. If someone could tell me (in a very simple way) which one is,better for me and why, I would be ever so apprreciative.
Why do you need a expensive MacBook Pro?
Your attending high school and unless everyone else is rich also your likely going to be a target by the more poorer students for theft or damage to the machine.
You could keep it home, but if you need it for class then your exposed again.
Also at that age your not very careful yet, a MacBook Pro is a expensive and easily damaged machine.
Unless your made of money and so are others at your school, I would recommned a low profile, just does the job cheap Windows PC.
If it dies, gets lost, stolen or damaged because of your inexperince handling senstivie electronics then it's no big deal.
You can buy a Mac later on when your sure you have a need for it, currently there isn't much advantage of owning a Mac compared to a PC, they do just about the same things now, one just looks prettier than the other.
Since 95% of the world uses Windows PC's your going to have to install Windows on the Mac in order to keep your skills up there or be unemployed, so it's a extra headache and expense.
good luck -
Which is better of MANY_TO_ONE and ONE_TO_MANY
I am trying je.
A little confuse is , that suppose A has one_to_many relation to B, then B can have many_to_one relation to A. And both solution is acceptable to my application. Which should I choose?Hello Jie,
This is a very good question, since we do not describe in the documentation how to choose between MANY_TO_ONE and ONE_TO_MANY. As you point out, it can be done either way when a related entity is used.
For example, here is how MANY_TO_ONE can be used:
@Entity
class Person {
@PrimaryKey(sequence="ID")
long id;
@SecondaryKey(relate=MANY_TO_ONE, relatedEntity=Employer.class)
long employerId;
String name;
@Entity
class Employer {
@PrimaryKey(sequence="ID")
long id;
String description;
}Of course we will need primary indexes for both entities:
PrimaryIndex<Long,Person> personById = ...;
PrimaryIndex<Long,Employer> employerById = ...;To get the employer of a person, we simply pass the employerId to the primary index:
Person person = ...;
Employer employer = employerById.get(person.employerId);To get the employees for a given employer, we get a sub-index for the employerId secondary key:
long anEmployerId = ...;
SecondaryIndex<Long,Long,Person> personByEmployerId = ...;
EntityIndex<Long,Person> employees = personByEmployerId.subIndex(anEmployerId);
EntityCursor<Person> cursor = employees.entities();
try {
for (Person employee : cursor) {
// do something with employee
} finally {
cursor.close();
}And here is how ONE_TO_MANY can be used to provide the same functionality:
@Entity
class Person {
@PrimaryKey(sequence="ID")
long id;
String name;
@Entity
class Employer {
@PrimaryKey(sequence="ID")
long id;
@SecondaryKey(relate=ONE_TO_MANY, relatedEntity=Person.class)
Set<Long> employeeIds;
String description;
}To get the employer of a person, we simply pass the person id to the employer's secondary index:
Person person = ...;
SecondaryIndex<Long,Long,Employer> employerByEmployeeIds = ...;
Employer employer = employerByEmployeeIds.get(person.id);The primary difference is that with MANY_TO_ONE the collection of employee IDs is maintained by the secondary index, while with ONE_TO_MANY the collection of employee IDs is embedded in the Employer entity.
Therefore to get the employees for a given employer with ONE_TO_MANY, we get the Employer object from the employerById primary index and then get each person in the employeeIds set:
long anEmployerId = ...;
SecondaryIndex<Long,Long,Person> personByEmployerId = ...;
Employer employer = employerById.get(anEmployerId);
for (long employeeId : employer.employeeIds) {
Person employee = personById.get(employeeId);
// do something with employee
}There is a major difference in terms of performance and scalability. With ONE_TO_MANY, if the number of employees for a single employer is very large, then the Employer record will be large because the list of employee IDs is embedded in the Employer object. This means that it will be more expensive to load the employer, for example, if all you want is the employer description field. The list of employee IDs will always be loaded whenever you access an employer.
On the other hand, with MANY_TO_ONE, the set of employers is stored in the sub-index. The sub-index is a Btree. It is very scalable and can easily support large numbers of employees per employer, even millions. And when simply loading the Employer record, the set of employeeIds for that employer will not be loaded. The Employer record will be very small.
There are four factors in deciding whether to use MANY_TO_ONE or ONE_TO_MANY.
(1) As shown above, it is slightly easier to use ONE_TO_MANY, because you don't need to use a sub-index as you must do with MANY_TO_ONE.
(2) MANY_TO_ONE will scale to larger number of entities per relationship, since a sub-index Btree is used to store the related entities.
(3) With MANY_TO_ONE, the entity object will not grow to a large size as many related entities are added. Smaller records are always better for performance and resource consumption.
In general, I advise using MANY_TO_ONE because it does not have the potential performance problems of ONE_TO_MANY (items 2 and 3 above).
But if you know that the number of related entities per relationship will be small, then either technique works well, and you should choose whichever you prefer. You may find that ONE_TO_MANY is slightly easier to use (item 1 above). Or you may choose one technique over the other because you prefer to maintain the relationship via the Person.employerId field or the Employer.employeeIds set.
There is one additional factor. If you have a secondary key where there is no related entity, just related keys, then you have no choice. There is only one entity, and you choose the relationship type accordingly.
For example, a Person may have many email addresses, and you may choose not to have an EmailAddress entity. The email addresses are simply secondary keys, not the key of another related entity. If a user can only have one email address, you would use ONE_TO_ONE. If the user can have multiple email addresses, you would use ONE_TO_MANY as shown below.
@Entity
class Person {
@PrimaryKey(sequence="ID")
long id;
@SecondaryKey(relate=ONE_TO_MANY)
Set<String> emailAddresses;
String name;
}A gender (male or female) secondary key is an example of a MANY_TO_ONE relationship where no related entity is involved:
@Entity
class Person {
@PrimaryKey(sequence="ID")
long id;
@SecondaryKey(relate=MANY_TO_ONE)
char gender; // M or F
String name;
}In this last example, there is no choice about whether to use ONE_TO_MANY or MANY_TO_ONE because there is only one entity involved. So this last rule is:
(4) If there is no related entity, then because there is only one entity involved the relationship type is determined by the cardinality (number) of entities and keys in each relationship.
Mark -
Dear Friends, i did not update the latest public version of iOS6, but unfortuantely my beta 4 expired and messages displays like "Activation Required" and when i try to activate it says server is busy and unable to activate. I have installed latest version of iTunes and still unable to restore. What should i Do? Kindly help me to activate my iPhone 4s
You need to post this in the developer's forum.
-
What is difference bet call transaction and session method in BDC
hi
what is difference bet call transaction and session method in BDC
thanks.Hi,
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
Thanks,
Reward If Helpful. -
What is the Diff bet partner functions and business partner?
Hi friends
what is the Diff bet partner functions and business partner
Regards
AbirathHi,
In SRM there are different Partner functions like REQUESTER, GOODS RECIPIENT, VENDOR ,LOCATION.
All the org units or users in SRM will have a unique identification number called Business Partner Number maintained in table BUT000.
The users can have differnt partner functions in differnt documents and accordingly mainatained in table CRMD_PARTNER.
Hope this will give you some infomation.
Regards,
Sheetal. -
What is better to use and why?
Hi,
What is better to use and why?
We have written follwing statements to check the existence of interested record in table.
1).
select count(*) from emp where deptno = 20;
2).
select 'X'
from dual
where exists (
select 'X' from emp
where deptno = 20);
Thanks and Regards,
Rushang KansaraAssuming a large table, number two would be the fastest. If empno in unique, you can leave out the where exists part and just select x from emp where empno = 20. If empno is not unique, then using where exists can be faster. Assuming that empno is not unique, query 1 may elect to scan the whole table looking for that empno. Number 2 can use the index and return your result in, typically, three LIOs.
Again, it all depends on your indexing, size of tables, and uniqueness of key upon which you are searching. -
Revision: 15581
Revision: 15581
Author: [email protected]
Date: 2010-04-19 17:14:00 -0700 (Mon, 19 Apr 2010)
Log Message:
Better coding style and some comments for the previous code submission.
Modified Paths:
osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.asRevision: 15581
Revision: 15581
Author: [email protected]
Date: 2010-04-19 17:14:00 -0700 (Mon, 19 Apr 2010)
Log Message:
Better coding style and some comments for the previous code submission.
Modified Paths:
osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as -
What is the diff bet CCM catalog and MDM catalog?
Hi Friends
What is the diff bet CCM catalog and MDM catalog?
Thanks & Regards
KanniHello,
CCM & SRM-MDM are SAP Catalog Content Management solutions.
In basic terms, MDM is latest solution & will be replacing CCM. All new features like service hierarchies are included in MDM 3.0.
CCM: upload, manage, and search in procurement catalogs.
http://help.sap.com/saphelp_ccm20/helpdata/en/index.htm
MDM: Search, compare, and procure products from suppliers.
It provides:
Catalog content management functions, such as the import of catalog structures or data, the transfer of catalog items to a procurement application, and search functions
Procurement catalogs
Supplier catalogs in a Web-based environment
The SRM-MDM Catalog is based on functions provided by SAP NetWeaver Master Data Management (SAP NetWeaver MDM) and bundles together in one specific application those SAP NetWeaver MDM functions required for catalog content management.
http://help.sap.com/saphelp_srm70/helpdata/en/45/ddd04f8c6e2e97e10000000a155369/frameset.htm
Hope this helps.
Thanks
Ashutosh -
why did apple erase ichat? its so much better than messages and now I cant video chat with my ichat buddies!!!
HI,
Apple did not erase iChat.
Messages in Mountain Lion is iChat +
The plus bit is the fact you can iMessage iOS devices.
All the other features that were in iChat are still there.
If you upgraded Lion to get to Mountain Lion then in System Preferences > Mail, Contacts and Calendars you probably list all the iChat Accounts (Screen Names and IDs).
You may need to enable them for Messages.
They should also show up in Messages Menu > Preference > Accounts
Once those accounts (AIM and Jabber) are Enabled they can be viewed in a Combined Buddy List
Windows Menu > Buddies (Or using CMD + 1 Keystrokes)
In the General Section of the Preferences you can Unlink these Buddy lists.
The Green icons or highlight a Buddy and then using the Buddies Menu or the icons at the Bottom of the Buddy list can be used the same way to start Video or Audio Only chats.
The iMessage "Account" is only for texting iOS devices or other people using their Apple ID on a Mac in Messages.
It is an account "in addition to" rather than "taking over from" the services that iChat can join.
9:22 PM Thursday; December 6, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
G4/1GhzDual MDD (Leopard 10.5.8)
MacBookPro 2Gb (Snow Leopard 10.6.8)
Mac OS X (10.6.8),
Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images." No, Seriously -
I can't find my all PDF in new version and older version is better than new and fix this problem as soon as possible....!
Hi Manoj,
what exact problem are you facing? Are you unable to locate your pdf files?
Regards,
Rahul -
Diff bet Base Unit and Order Unit
Hi All,
I was going through the table MARA. I found tht there are two columns named 'Base Unit' n 'Order Unit'. I found interestingly that for couple of materials the units are diff in both coloumns (e.g: For a material Base Unit is EA but the Order unit is in KG). What is the diff bet Base unit and Order unit?
Please inform how is it possible to have two diff units for a single material??
Thanks in Adv.Base Unit of measure is generally the smallest unit that can be used for a material.
But a company may never issue orders in this base unit.
So in the material master, order unit can be configured which may be separate then Base unit.
As a result orders will always will be placed in this unit.
For ex:
Base unit is set an Inch but the company always issues material always in foot.
Therefore in the material master Base unit of measure is set to Inch and Order Unit of measure is set to Foot
Maybe you are looking for
-
i have an HP with mozilla 4 browser
-
Security update fixes ACL problems, almost
So far when running disk permissions, I've had one iMac C2D have no problems reported and the other iMac C2D only have ACL issues on /Library
-
Same Oracle Server, 2 schemas, one fast, one slow
We are in the process of updating a database at our company to co-exist with a more recent release of third-party software. Only a few tables are changing. We decided to create two schemas: PLVT and PLV2T respectively PLVT contains the original versi
-
Help! I could not upload roles from R/3 to EP60 -Stack13!!!
Hello! I could not upload roles from R/3 to EP60 (NW SR01 Stack 13). I Read "How to... Upload Roles from ABAP-based Systems" The error I am getting is: <b><b>Connection to SAP component system failed. Check the system settings.</b></b> I am able to r
-
Any way to set snooze time on the Alarm Clock
The default snooze time on the Alarm Clock is 10 minutes. Any way to set it to 5 minutes?