9 Replies Latest reply on Dec 16, 2009 2:57 AM by amira manai

    unidirectional  and bidirectional  relationship

    amira manai Newbie

      Hi everybody,
      What's the difference between unidirectional relationship and
      bidirectional relationship!!
      Best Regards

        • 1. Re: unidirectional  and bidirectional  relationship
          Wolfgang Knauf Master

          Hi,

          assume that you have a relation "Person has many addresses" with two entities "Person" and "Address".

          If you declare a bidirectional relationship, your code can navigate from Person to Address, and from Adress to Person.

          With a unidirectional relationship, your code can navigate only from one side to the other. E.g. you can get the addresses of a person, but you cannot get the person of an address.

          The database representation of the relationship is not affected by your unidirectional/bidirectional decision. This defines only, how the code side looks like.

          Hope this helps

          Wolfgang

          • 2. Re: unidirectional  and bidirectional  relationship
            amira manai Newbie

             

            "Wolfgang Knauf" wrote:
            Hi,

            assume that you have a relation "Person has many addresses" with two entities "Person" and "Address".

            If you declare a bidirectional relationship, your code can navigate from Person to Address, and from Adress to Person.

            With a unidirectional relationship, your code can navigate only from one side to the other. E.g. you can get the addresses of a person, but you cannot get the person of an address.

            The database representation of the relationship is not affected by your unidirectional/bidirectional decision. This defines only, how the code side looks like.

            Hope this helps

            Wolfgang

            tHANK U so much sir ,
            Now i can see the difference but i have a new question another time, i'm developping an oaw project so after generating
            the code i have to build tables, That's why i used jboss ,but when i wanna add the oaw project in the server(add and remove option by right click on the sever ),i can not find the name of the oaw project ,So i created a new ejb3 project and i copy and paste the generated class into it finally i added
            the annotation and the relation ships into entities is it a good idea!!!
            Because My collegues add annotation (ejb3 code)in the Template!!
            That's why i'm wondering ,and I'm afraid if made a mistake!!
            What do you think Sir Knauf!!
            Viele Danke für Ihre Hilfe!!
            Thank you for ur help

            • 3. Re: unidirectional  and bidirectional  relationship
              Wolfgang Knauf Master

              Hi,

              what is an "oaw project" ;-)?

              I assume that this is a project type in eclipse which is provided by some plugin?

              The "add to server" works only for EJB projects, EAR projects and Dynamic Web Projects". Maybe you can convert the oaw project to one of those?

              Best regards

              Wolfgang

              • 4. Re: unidirectional  and bidirectional  relationship
                amira manai Newbie

                 

                "Wolfgang Knauf" wrote:
                Hi,

                what is an "oaw project" ;-)?

                I assume that this is a project type in eclipse which is provided by some plugin?

                The "add to server" works only for EJB projects, EAR projects and Dynamic Web Projects". Maybe you can convert the oaw project to one of those?

                Best regards

                Wolfgang

                Hi Sir ,
                An oaw project mean an open architecture ware project!!
                THaNK You for replying i really appreciate it!!
                You really my saver sir.



                • 5. Re: unidirectional  and bidirectional  relationship
                  amira manai Newbie

                  Hi Sir,

                  in my classes i have a manytomany relationshipm between 2 entities
                  (Student and course) so should i create an interface "Studentcourse" that contain the definition of functions , a class "StudentcourseUniBean" that implements this interface and also all functions and a client class " StudentcourseClient" that contain the main.

                  Or I can put this functions in one interface finally i'll have only one client. one interface and one class. and this interface contain all function that can i do for all entities(addStudentt(),deleteCourse(),addCourse()....)

                  or for each relationship and entity I have to create interface(contain functions ) ,class(implement the interface ),client(main class).Thank you for your help
                  Best Regards


                  • 6. Re: unidirectional  and bidirectional  relationship
                    Wolfgang Knauf Master

                    Hi,

                     

                    sorry, but I'm not sure whether I understand your question ;-). What do you mean with "Interface"? Probably you don't mean a remote/local interface, but the bussiness methods which are exposed by your session bean?

                     

                    In this case, there is no rule on how you combine them in your code. You can create a session bean for each entity, but you can also split your bussiness methods by use case.

                     

                    Best regards

                     

                    Wolfgang


                    • 7. Re: unidirectional  and bidirectional  relationship
                      amira manai Newbie

                      hi Sir Iresolved this error But I'm having another errors when i start my jboss server:

                      [Code]

                      02:16:02,242 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/ state=Not Installed mode=Manual requiredState=Parse

                      org.jboss.deployers.spi.DeploymentException

                       

                       

                      DeploymentException.java:49)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:337)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:297)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:269)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(

                      AbstractParsingDeployerWithOutput.java:230)

                      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(

                      DeployerWrapper.java:171)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(

                      DeployersImpl.java:1439)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(

                      DeployersImpl.java:1157)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(

                      DeployersImpl.java:1098)

                      at org.jboss.dependency.plugins.AbstractControllerContext.install(

                      AbstractControllerContext.java:348)

                      at org.jboss.dependency.plugins.AbstractController.install(

                      AbstractController.java:1598)

                      at org.jboss.dependency.plugins.AbstractController.incrementState(

                      AbstractController.java:934)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:1062)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:984)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:822)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:553)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(

                      DeployersImpl.java:781)

                      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(

                      MainDeployerImpl.java:698)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(

                      ProfileServiceBootstrap.java:304)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(

                      ProfileServiceBootstrap.java:205)

                      at org.jboss.bootstrap.AbstractServerImpl.start(

                      AbstractServerImpl.java:405)

                      at org.jboss.Main.boot(

                      Main.java:209)

                      at org.jboss.Main$1.run(

                      Main.java:547)

                      at java.lang.Thread.run(Unknown Source)

                      Caused by:

                      org.jboss.xb.binding.JBossXBException: Failed to parse source: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:203)

                      at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(

                      UnmarshallerImpl.java:168)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:199)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:170)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:132)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:118)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(

                      AbstractVFSParsingDeployer.java:256)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(

                      AbstractVFSParsingDeployer.java:188)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:323)

                      ... 22 more

                      Caused by:

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(

                      SaxJBossXBParser.java:432)

                      at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

                      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

                      at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:199)

                      ... 30 more

                      02:16:08,788 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector

                      02:16:09,085 INFO [MailService] Mail Service bound to java:/Mail

                      02:16:12,190 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

                      02:16:12,222 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent

                      02:16:12,503 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.

                      02:16:12,503 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer

                      02:16:13,158 INFO [TransactionManagerService] Initializing recovery manager

                      02:16:13,610 INFO [TransactionManagerService] Recovery manager configured

                      02:16:13,610 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

                      02:16:13,705 INFO [TransactionManagerService] Starting transaction recovery manager

                      02:16:14,984 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:14,984 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:14,984 INFO [StandardService] D�marrage du service jboss.web

                      02:16:14,984 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA

                      02:16:15,063 INFO [Catalina] Server startup in 710 ms

                      02:16:15,079 INFO [TomcatDeployment] deploy, ctxPath=/invoker

                      02:16:15,968 INFO [TomcatDeployment] deploy, ctxPath=/web-console

                      02:16:16,608 INFO [TomcatDeployment] deploy, ctxPath=/jbossws

                      02:16:16,796 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

                      02:16:16,827 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

                      02:16:16,858 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml

                      02:16:16,889 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml

                      02:16:16,936 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

                      02:16:17,186 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main

                      02:16:17,264 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

                      02:16:17,264 INFO [RAMJobStore] RAMJobStore initialized.

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2

                      02:16:17,264 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

                      02:16:19,027 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

                      02:16:19,917 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing

                      02:16:20,308 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,308 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@170cd42 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@8e4be2 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@b05ba4 started

                      02:16:20,542 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

                      02:16:20,557 INFO [TomcatDeployment] deploy, ctxPath=/

                      02:16:20,667 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console

                      02:16:20,776 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                       

                      DEPLOYMENTS IN ERROR:

                      Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/" is in error due to the following reason(s):

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                       

                      02:16:20,791 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:20,885 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:20,916 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 39s:739ms

                      02:16:02,242 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/ state=Not Installed mode=Manual requiredState=Parse

                      org.jboss.deployers.spi.DeploymentException

                       

                       

                      : Error creating managed object for vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/

                      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(

                      DeploymentException.java:49)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:337)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:297)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:269)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(

                      AbstractParsingDeployerWithOutput.java:230)

                      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(

                      DeployerWrapper.java:171)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(

                      DeployersImpl.java:1439)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(

                      DeployersImpl.java:1157)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(

                      DeployersImpl.java:1098)

                      at org.jboss.dependency.plugins.AbstractControllerContext.install(

                      AbstractControllerContext.java:348)

                      at org.jboss.dependency.plugins.AbstractController.install(

                      AbstractController.java:1598)

                      at org.jboss.dependency.plugins.AbstractController.incrementState(

                      AbstractController.java:934)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:1062)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:984)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:822)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:553)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(

                      DeployersImpl.java:781)

                      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(

                      MainDeployerImpl.java:698)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(

                      ProfileServiceBootstrap.java:304)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(

                      ProfileServiceBootstrap.java:205)

                      at org.jboss.bootstrap.AbstractServerImpl.start(

                      AbstractServerImpl.java:405)

                      at org.jboss.Main.boot(

                      Main.java:209)

                      at org.jboss.Main$1.run(

                      Main.java:547)

                      at java.lang.Thread.run(Unknown Source)

                      Caused by:

                      org.jboss.xb.binding.JBossXBException: Failed to parse source: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:203)

                      at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(

                      UnmarshallerImpl.java:168)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:199)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:170)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:132)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:118)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(

                      AbstractVFSParsingDeployer.java:256)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(

                      AbstractVFSParsingDeployer.java:188)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:323)

                      ... 22 more

                      Caused by:

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(

                      SaxJBossXBParser.java:432)

                      at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

                      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

                      at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:199)

                      ... 30 more

                      02:16:08,788 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector

                      02:16:09,085 INFO [MailService] Mail Service bound to java:/Mail

                      02:16:12,190 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

                      02:16:12,222 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent

                      02:16:12,503 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.

                      02:16:12,503 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer

                      02:16:13,158 INFO [TransactionManagerService] Initializing recovery manager

                      02:16:13,610 INFO [TransactionManagerService] Recovery manager configured

                      02:16:13,610 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

                      02:16:13,705 INFO [TransactionManagerService] Starting transaction recovery manager

                      02:16:14,984 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:14,984 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:14,984 INFO [StandardService] D�marrage du service jboss.web

                      02:16:14,984 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA

                      02:16:15,063 INFO [Catalina] Server startup in 710 ms

                      02:16:15,079 INFO [TomcatDeployment] deploy, ctxPath=/invoker

                      02:16:15,968 INFO [TomcatDeployment] deploy, ctxPath=/web-console

                      02:16:16,608 INFO [TomcatDeployment] deploy, ctxPath=/jbossws

                      02:16:16,796 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

                      02:16:16,827 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

                      02:16:16,858 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml

                      02:16:16,889 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml

                      02:16:16,936 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

                      02:16:17,186 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main

                      02:16:17,264 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

                      02:16:17,264 INFO [RAMJobStore] RAMJobStore initialized.

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2

                      02:16:17,264 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

                      02:16:19,027 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

                      02:16:19,917 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing

                      02:16:20,308 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,308 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@170cd42 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@8e4be2 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@b05ba4 started

                      02:16:20,542 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

                      02:16:20,557 INFO [TomcatDeployment] deploy, ctxPath=/

                      02:16:20,667 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console

                      02:16:20,776 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                       

                      DEPLOYMENTS IN ERROR:

                      Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/" is in error due to the following reason(s):

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                       

                      02:16:20,791 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:20,885 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:20,916 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 39s:739ms

                      02:16:02,242 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/ state=Not Installed mode=Manual requiredState=Parse

                      org.jboss.deployers.spi.DeploymentException

                       

                       

                      : Error creating managed object for vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/

                      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(

                      DeploymentException.java:49)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:337)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:297)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:269)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(

                      AbstractParsingDeployerWithOutput.java:230)

                      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(

                      DeployerWrapper.java:171)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(

                      DeployersImpl.java:1439)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(

                      DeployersImpl.java:1157)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(

                      DeployersImpl.java:1098)

                      at org.jboss.dependency.plugins.AbstractControllerContext.install(

                      AbstractControllerContext.java:348)

                      at org.jboss.dependency.plugins.AbstractController.install(

                      AbstractController.java:1598)

                      at org.jboss.dependency.plugins.AbstractController.incrementState(

                      AbstractController.java:934)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:1062)

                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(

                      AbstractController.java:984)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:822)

                      at org.jboss.dependency.plugins.AbstractController.change(

                      AbstractController.java:553)

                      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(

                      DeployersImpl.java:781)

                      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(

                      MainDeployerImpl.java:698)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(

                      ProfileServiceBootstrap.java:304)

                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(

                      ProfileServiceBootstrap.java:205)

                      at org.jboss.bootstrap.AbstractServerImpl.start(

                      AbstractServerImpl.java:405)

                      at org.jboss.Main.boot(

                      Main.java:209)

                      at org.jboss.Main$1.run(

                      Main.java:547)

                      at java.lang.Thread.run(Unknown Source)

                      Caused by:

                      org.jboss.xb.binding.JBossXBException: Failed to parse source: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:203)

                      at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(

                      UnmarshallerImpl.java:168)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:199)

                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(

                      JBossXBDeployerHelper.java:170)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:132)

                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(

                      SchemaResolverDeployer.java:118)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(

                      AbstractVFSParsingDeployer.java:256)

                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(

                      AbstractVFSParsingDeployer.java:188)

                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(

                      AbstractParsingDeployerWithOutput.java:323)

                      ... 22 more

                      Caused by:

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(

                      SaxJBossXBParser.java:432)

                      at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

                      at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

                      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

                      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

                      at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(

                      SaxJBossXBParser.java:199)

                      ... 30 more

                      02:16:08,788 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector

                      02:16:09,085 INFO [MailService] Mail Service bound to java:/Mail

                      02:16:12,190 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

                      02:16:12,222 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent

                      02:16:12,503 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.

                      02:16:12,503 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer

                      02:16:13,158 INFO [TransactionManagerService] Initializing recovery manager

                      02:16:13,610 INFO [TransactionManagerService] Recovery manager configured

                      02:16:13,610 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

                      02:16:13,705 INFO [TransactionManagerService] Starting transaction recovery manager

                      02:16:14,984 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:14,984 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:14,984 INFO [StandardService] D�marrage du service jboss.web

                      02:16:14,984 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA

                      02:16:15,063 INFO [Catalina] Server startup in 710 ms

                      02:16:15,079 INFO [TomcatDeployment] deploy, ctxPath=/invoker

                      02:16:15,968 INFO [TomcatDeployment] deploy, ctxPath=/web-console

                      02:16:16,608 INFO [TomcatDeployment] deploy, ctxPath=/jbossws

                      02:16:16,796 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

                      02:16:16,827 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

                      02:16:16,858 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml

                      02:16:16,889 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml

                      02:16:16,936 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

                      02:16:17,186 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main

                      02:16:17,264 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

                      02:16:17,264 INFO [RAMJobStore] RAMJobStore initialized.

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

                      02:16:17,264 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2

                      02:16:17,264 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

                      02:16:19,027 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

                      02:16:19,917 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover

                      02:16:20,151 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing

                      02:16:20,308 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,308 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@170cd42 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@8e4be2 started

                      02:16:20,355 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000

                      02:16:20,355 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds

                      02:16:20,355 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@b05ba4 started

                      02:16:20,542 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

                      02:16:20,557 INFO [TomcatDeployment] deploy, ctxPath=/

                      02:16:20,667 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console

                      02:16:20,776 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                       

                      DEPLOYMENTS IN ERROR:

                      Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/" is in error due to the following reason(s):

                      org.xml.sax.SAXException: Premature end of file. @ *unknown*[-1,-1]

                       

                      02:16:20,791 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080

                      02:16:20,885 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

                      02:16:20,916 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 39s:739ms

                      [/Code]

                       

                      Do you can tell me what's the cause of this errors!!

                       

                      Regards and THANK YOU FOR HELP

                      : Error creating managed object for vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/BancDataBase.jar/

                      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(

                      • 8. Re: unidirectional  and bidirectional  relationship
                        jaikiran pai Master

                        Amira,

                         

                        For new errors, please create new topics in appropriate forum.

                        • 9. Re: unidirectional  and bidirectional  relationship
                          amira manai Newbie
                          I'm So Sorry Sir I'll not do it any more But do you have an idea about it After a long research , I think it's related to an error in an xml file !!