2 Replies Latest reply on Apr 29, 2008 10:40 PM by fab52

    own portlet's table is not build in oracle

    fab52

      Hi, I used jboss portal 2.6.3 and Jboss AS 4.2. Running on windows XP sp2 and using Oracle10g XE as my db.

      I don't use SYSTEM for the db instead my portal ds looks like this:

      <datasources>
       <local-tx-datasource>
       <jndi-name>PortalDS</jndi-name>
       <connection-url>jdbc:oracle:thin:fab/password@localhost:1521:XE</connection-url>
       <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
       <user-name>fab</user-name>
       <password>password</password>
       </local-tx-datasource>
      </datasources>
      


      in the logfile, hibernates always look for tables from SYSTEM
      like:
      SYSTEM.jbp_table1
      instead of:
      FAB.jbp_table1

      this problem occurs for portlets that I made. inside the FAB's db are all JBoss tables.

        • 1. Re: own portlet's table is not build in oracle
          fab52

          I hope, my explanation is good enough.

          • 2. Re: own portlet's table is not build in oracle
            fab52

            I've been looking into this matter. It seems that Hibernates looks for the previous schema.

            Let say you use System for the first run. Hibernate will create the schema in the System schema.

            on the second run you use A schema instead , hibernate will create schema in A Schema.

            on the third run, you use B schema, hibernate will create schema just like A.

            unfortunately, Schema in A and B is not as complete as in System schema.

            Schema A and B is lacking the custom portlet. Therefore when JBoss portal come to look for these portlet. it will look at the previous schema for the respective tables. therefore it found these tables at the System schema.

            Still I haven't come up with a solution for this.