cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graaf, Edgar de (fin)" <Edgar.de.Gr...@ordina.nl>
Subject RE: <datasources> <j2ee ....... ?!
Date Mon, 04 Mar 2002 08:35:04 GMT
The first thing I tried the second I didn't. But I will look into it. 
I choose to use Access because it was the only database around that was
easily accessible. You see I am a student and I have to test the
possibilities of cocoon, what is its performance, how extensible is it
etc... one thing I was trying to test is how easily can I change the
Hypersonic database to another one. 

In the future I am going to connect a MySql database, but that takes some
extra time finding out how it works. If all goes well my company will use
Cocoon in future projects. At the moment it performs just great.... And I
agree Access is a lousy database, if you can call it a database :-)

-----Oorspronkelijk bericht-----
Van: Berin Loritsch [mailto:bloritsch@apache.org]
Verzonden: vrijdag 1 maart 2002 18:35
Aan: cocoon-dev@xml.apache.org
Onderwerp: Re: <datasources> <j2ee ....... ?!


Graaf, Edgar de (fin) wrote:
> I am novice in the j2ee stuff. I added JNDI.properties to my
WEB-INF/classes
> directory of cocoon and I added the jndi.jar to the lib. 
> 
> My cocoon.xconf looks like this:
> 		.
> 		.
> 		.
> 	<j2ee name="tryout">
>     		<dbname>java:/MSAccess</dbname>
>     	</j2ee>
>   </datasources>

try this:

<j2ee name="tryout">
   <dbname>MSAccess</dbname>
</j2ee>

The lookup maps to:

java:comp/jdbc/MSAccess

as per the J2EE specs.  If JBoss maps it somewhere else, it is an error.


Unrealated to this, I guarantee you will run into problems developing
against Access and then moving to a real database.  That is a 100%
guaranteed occurance.  I don't care if you are using ColdFusion, Java,
PHP, ASP, JSP, XSP, or whatever.  If you develop against Access thinking
you can move to a real database later you are fooling yourself.

Access requires you to write non-standard SQL statements, and allows you
to use unusual join patterns that won't work on real databases.  Not to
mention when the Access database reaches a certain size, it implodes on
itself.

I have run into Access related problems more than I care to admit.
Therefore I tend to stay away from it.

> 
> I use JBoss. The datasource works with an EJB installed on JBoss and when
I
> use JDBC instead everything goes great to (very good by the way esql makes
> thinks very simple)
> 
> Please provide more information,
> 
> Regards,
> 
> Edgar
> 
> -----Oorspronkelijk bericht-----
> Van: Berin Loritsch [mailto:bloritsch@apache.org]
> Verzonden: vrijdag 1 maart 2002 14:32
> Aan: cocoon-dev@xml.apache.org
> Onderwerp: Re: <datasources> <j2ee ....... ?!
> 
> 
> Graaf, Edgar de (fin) wrote:
> 
>>People,
>>
>>I try to use <datasources> <j2ee ....... 
>>But what ever I do I keep on having the same problem. Please look at the
>>included exception. The only thing the Cocoon site says about the subject
>>
> is
> 
>>that it is as simple as filling <dbname>. Unfortunately nothing is simple.
>>Or is it?
>>
> 
> 
> The j2ee datasource component connects to your J2EE compliant
> application server.  If you are not using one, you should not use the
> j2ee datasource.
> 
> The place to look up datasource components is defined by the J2EE spec,
> so if JNDI cannot find "java:comp" then something is not set up
> correctly on your server.
> 
> 
> 



-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message