Configuring DataSource and Registering it with JNDI












1















I follow up the java doc java docfor datasource.



I am not understanding the below code snippt.



I create a connectionpooldatasource and register with jndi.



cpds.setServerName("creamer");

cpds.setDatabaseName("COFFEEBREAK");

cpds.setPortNumber(9040);

cpds.setDescription("Connection pooling for " + "COFFEEBREAK DBMS");



Context ctx = new InitialContext();

ctx.bind("jdbc/pool/fastCoffeeDB", cpds);


Now we can retrive this connection pool data source



Context ctx = new InitialContext();

ctx.lookup("jdbc/pool/fastCoffeeDB");


I create an another datasource and register it.



com.applogic.PooledDataSource ds = new 

com.applogic.PooledDataSource();

ds.setDescription("produces pooled connections to COFFEEBREAK");

ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



Context ctx = new InitialContext();

ctx.bind("jdbc/fastCoffeeDB", ds);


Now we can retrive this connection pool data source



ctx = new InitialContext();

ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


I am not clear about setDataSourceName.



We add ConnectionPoolDS into PoolDataSource.



when we retrive the datasource 



 ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


then the data soruce return from here is PoolDataSource type or ConnectionPoolDS type?.






java datasource jndi







share|improve this question



























    1















    I follow up the java doc java docfor datasource.



    I am not understanding the below code snippt.



    I create a connectionpooldatasource and register with jndi.



    cpds.setServerName("creamer");
    
cpds.setDatabaseName("COFFEEBREAK");
    
cpds.setPortNumber(9040);
    
cpds.setDescription("Connection pooling for " + "COFFEEBREAK DBMS");
    

    
Context ctx = new InitialContext();
    
ctx.bind("jdbc/pool/fastCoffeeDB", cpds);


    Now we can retrive this connection pool data source



    Context ctx = new InitialContext();
    
ctx.lookup("jdbc/pool/fastCoffeeDB");


    I create an another datasource and register it.



    com.applogic.PooledDataSource ds = new 
    
com.applogic.PooledDataSource();
    
ds.setDescription("produces pooled connections to COFFEEBREAK");
    
ds.setDataSourceName("jdbc/pool/fastCoffeeDB");
    

    
Context ctx = new InitialContext();
    
ctx.bind("jdbc/fastCoffeeDB", ds);


    Now we can retrive this connection pool data source



    ctx = new InitialContext();
    
ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


    I am not clear about setDataSourceName.



    We add ConnectionPoolDS into PoolDataSource.



    when we retrive the datasource 



     ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


    then the data soruce return from here is PoolDataSource type or ConnectionPoolDS type?.






    java datasource jndi







    share|improve this question

























      1












      1








      1








      I follow up the java doc java docfor datasource.



      I am not understanding the below code snippt.



      I create a connectionpooldatasource and register with jndi.



      cpds.setServerName("creamer");
      
cpds.setDatabaseName("COFFEEBREAK");
      
cpds.setPortNumber(9040);
      
cpds.setDescription("Connection pooling for " + "COFFEEBREAK DBMS");
      

      
Context ctx = new InitialContext();
      
ctx.bind("jdbc/pool/fastCoffeeDB", cpds);


      Now we can retrive this connection pool data source



      Context ctx = new InitialContext();
      
ctx.lookup("jdbc/pool/fastCoffeeDB");


      I create an another datasource and register it.



      com.applogic.PooledDataSource ds = new 
      
com.applogic.PooledDataSource();
      
ds.setDescription("produces pooled connections to COFFEEBREAK");
      
ds.setDataSourceName("jdbc/pool/fastCoffeeDB");
      

      
Context ctx = new InitialContext();
      
ctx.bind("jdbc/fastCoffeeDB", ds);


      Now we can retrive this connection pool data source



      ctx = new InitialContext();
      
ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


      I am not clear about setDataSourceName.



      We add ConnectionPoolDS into PoolDataSource.



      when we retrive the datasource 



       ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


      then the data soruce return from here is PoolDataSource type or ConnectionPoolDS type?.






      java datasource jndi







      share|improve this question














      I follow up the java doc java docfor datasource.



      I am not understanding the below code snippt.



      I create a connectionpooldatasource and register with jndi.



      cpds.setServerName("creamer");
      
cpds.setDatabaseName("COFFEEBREAK");
      
cpds.setPortNumber(9040);
      
cpds.setDescription("Connection pooling for " + "COFFEEBREAK DBMS");
      

      
Context ctx = new InitialContext();
      
ctx.bind("jdbc/pool/fastCoffeeDB", cpds);


      Now we can retrive this connection pool data source



      Context ctx = new InitialContext();
      
ctx.lookup("jdbc/pool/fastCoffeeDB");


      I create an another datasource and register it.



      com.applogic.PooledDataSource ds = new 
      
com.applogic.PooledDataSource();
      
ds.setDescription("produces pooled connections to COFFEEBREAK");
      
ds.setDataSourceName("jdbc/pool/fastCoffeeDB");
      

      
Context ctx = new InitialContext();
      
ctx.bind("jdbc/fastCoffeeDB", ds);


      Now we can retrive this connection pool data source



      ctx = new InitialContext();
      
ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


      I am not clear about setDataSourceName.



      We add ConnectionPoolDS into PoolDataSource.



      when we retrive the datasource 



       ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");


      then the data soruce return from here is PoolDataSource type or ConnectionPoolDS type?.






      java datasource jndi




      java datasource jndi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 1 at 6:19









      jogendrajogendra

      966




      966
























          1 Answer
          1






          active

          oldest

          votes


















          1














          using this




          jdbc/pool/fastCoffeeDB JNDI
          you are directly pointing to COFFEEBREAK database.




          in second JNDI




          jdbc/fastCoffeeDB




          you are using following statement



          ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



          In the above you are pointing old JNDI name, this means you are indirectly points to COFFEEBREAK database



          so from statement
          ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");
          you will get ConnectionPoolDS.






          share|improve this answer
























          • what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

            – jogendra
            Jan 1 at 11:42













          • @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

            – vivekdubey
            Jan 2 at 6:11













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53993424%2fconfiguring-datasource-and-registering-it-with-jndi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          using this




          jdbc/pool/fastCoffeeDB JNDI
          you are directly pointing to COFFEEBREAK database.




          in second JNDI




          jdbc/fastCoffeeDB




          you are using following statement



          ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



          In the above you are pointing old JNDI name, this means you are indirectly points to COFFEEBREAK database



          so from statement
          ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");
          you will get ConnectionPoolDS.






          share|improve this answer
























          • what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

            – jogendra
            Jan 1 at 11:42













          • @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

            – vivekdubey
            Jan 2 at 6:11


















          1














          using this




          jdbc/pool/fastCoffeeDB JNDI
          you are directly pointing to COFFEEBREAK database.




          in second JNDI




          jdbc/fastCoffeeDB




          you are using following statement



          ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



          In the above you are pointing old JNDI name, this means you are indirectly points to COFFEEBREAK database



          so from statement
          ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");
          you will get ConnectionPoolDS.






          share|improve this answer
























          • what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

            – jogendra
            Jan 1 at 11:42













          • @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

            – vivekdubey
            Jan 2 at 6:11
















          1












          1








          1







          using this




          jdbc/pool/fastCoffeeDB JNDI
          you are directly pointing to COFFEEBREAK database.




          in second JNDI




          jdbc/fastCoffeeDB




          you are using following statement



          ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



          In the above you are pointing old JNDI name, this means you are indirectly points to COFFEEBREAK database



          so from statement
          ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");
          you will get ConnectionPoolDS.






          share|improve this answer













          using this




          jdbc/pool/fastCoffeeDB JNDI
          you are directly pointing to COFFEEBREAK database.




          in second JNDI




          jdbc/fastCoffeeDB




          you are using following statement



          ds.setDataSourceName("jdbc/pool/fastCoffeeDB");



          In the above you are pointing old JNDI name, this means you are indirectly points to COFFEEBREAK database



          so from statement
          ds = (DataSource)ctx.lookup("jdbc/fastCoffeeDB");
          you will get ConnectionPoolDS.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 1 at 7:17









          vivekdubeyvivekdubey

          1495




          1495













          • what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

            – jogendra
            Jan 1 at 11:42













          • @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

            – vivekdubey
            Jan 2 at 6:11





















          • what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

            – jogendra
            Jan 1 at 11:42













          • @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

            – vivekdubey
            Jan 2 at 6:11



















          what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

          – jogendra
          Jan 1 at 11:42







          what is the reason of doing this.Why we create an extra PoolDataSource if we cant use it.By using jdbc/pool/fastCoffeeDB & jdbc/fastCoffeeDB if we get ConnectionPoolDS each time.

          – jogendra
          Jan 1 at 11:42















          @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

          – vivekdubey
          Jan 2 at 6:11







          @jogendra if you will read complete page answer is there A basic DataSource implementation produces standard Connection objects that are not pooled or used in a distributed transaction. A DataSource implementation that supports connection pooling produces Connection objects that participate in connection pooling, that is, connections that can be recycled.

          – vivekdubey
          Jan 2 at 6:11






















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53993424%2fconfiguring-datasource-and-registering-it-with-jndi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

          Image
          28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
          Read more

          Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

          Image
          up vote 13 down vote favorite 1 After the 2018 errata, the disintegrate spell description now reads: A creature targeted by this spell must make a Dexterity saving throw. On a failed save, the target takes 10d6 + 40 force damage. The target is disintegrated if this damage leaves it with 0 hit points. If you were to polymorph an enemy into a rat and then disintegrate it, would the enemy be disintegrated or would it just return to its original form? I know that for Druids, it’s not an instant kill anymore, but is this the case for polymorph as well? dnd-5e spells polymorph errata share | improve this question edited 18 hours ago
          Read more

          A Topological Invariant for $pi_3(U(n))$

          Image
          3 3 $begingroup$ Recently, I saw a construction of topological invariant for $pi_3(U(n))$ with $ngeq 2$ : $$ N=frac{1}{24pi^2}int_{S^3} d^3x epsilon^{ijk} Tr[(U^{-1}partial_{x_i}U)(U^{-1}partial_{x_j}U)(U^{-1}partial_{x_k}U)] , $$ where $Uin U(n)$ depends on $boldsymbol{x}=(x_1,x_2,x_3)in S^3$ , $epsilon^{ijk}$ is the Levi-Civita symbol, $i,j,k=1,2,3$ , and the duplicated indexes are summed over. It is claimed that $N$ is an integer, but why? Update 02/02/2019 I think I got an argument for $n=2$ . In this case, $U=e^{i varphi} q$ with $qin SU(2)$ . Due to the trace and the Levi-Civita symbol in $N$ , $varphi$ does not contribute to $N$ . As $Tr[q^{dagger}partial_i q]=0$ and $(q^{dagger}partial_i q)^{dagger}=-q^{dagger}partial_i q$ , $q^{dagger}partial_i q$ in geneeral has the form $q^{dagger}partia
          Read more