btw - i don't see the point with that xml parser issue. nowadays allmost everyone is using a jaxp compliant parser. that means that people could expect a specific functionally no matter what implementation they use.
if there will be really a demand, we could say that the user might distribute his own parser with his app and that this parser has precedence. that means the container's parser will be only used by the container and the user's parser for the user's app. that's the way tomcat treats different parsers in his classpath. regards daniel s. haischt -- > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im Auftrag von Cabrera, > Alan > Gesendet: Dienstag, 3. September 2002 17:54 > An: 'Partha Sarathi Bhakat' > Cc: [EMAIL PROTECTED] > Betreff: RE: RE: RE: [OpenEJB-user] CMP example > > > You're right, we could use the j2ee.jar. I was testing against the v1.3.1 > version; the v1.2.1 version works fine. However, there is a small hitch. > It contains the Sun reference implementation, which we are not allowed to > distribute. > > Given that David has put in code that renders our CLASSPATH issues moot, I > think that we won't need to include the j2ee.jar in the immediate future. > > We use Castor to read XML files. I would imagine that parser that works > with Castor would work for us. > > > Regards, > Alan > > -----Original Message----- > From: Partha Sarathi Bhakat [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 30, 2002 9:31 AM > To: Alan Cabrera > Cc: [EMAIL PROTECTED] > Subject: Re: RE: RE: [OpenEJB-user] CMP example > > > Hi Alan, > Now I have downloaded the 0.8.1 version. > I too got the same error as Zahid had regarding the > javax.sql.DataSource. I just added the j2ee.jar to the end of the > classpath in ejbserver.bat and test.bat. It "openejb test" worked > fine. I put j2ee.jar to end of te classpath so that only > DataSource is taken from the j2ee.jar > > But I'm still not clear on why we shouldn't be using j2ee.jar. > > Comming to xml parsing through j2ee.jar, since in this project we > are doing lot of xml parsing, different xml implementation like > xerces, crimson etc have different implementation. Suppose my > session bean needs to do some xml processing, I need to have some > xml implementation that implements jaxp. Some times XML > implementation that comes with the App server may not serve the > purpose. And may be that App Server works well with the xml > implementation that comes with the distribution. So we are stuck > with the functionality..... either this works or that works. > So my question is that is this openejb server specific to a > perticular implementation of xml? say either crimson or xerces or > that present in j2ee.jar? > > On Fri, 30 Aug 2002 Alan Cabrera wrote : > >Hey Partha, > > > > > -----Original Message----- > > > From: Partha Sarathi Bhakat [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, August 30, 2002 12:46 AM > > > > > > Hi All, > > > As LASKOWSKI,JACEK points out to use a xaDataSource, if I am > >not > > > wrong, can we not use j2ee.jar in the classpath to solve the > > > DataSource problem. > > > >If you look at the output that Zahid sent, you will see that the > >jar with > >that class is in the classpath. As I mentioned to Jacek, the > >j2ee.jar file > >will not work for us. > > > > > Here I have one small question to ask on the xml parsing that > >j2ee > > > does. As this project might be using different xml > >implementation > > > different from what j2ee.jar is having. Will it cause problem > >in > > > any way? I found that some app server don't even start if > > > different XML implementation is provided. > > > >Can you be more specific in regards to OpenEJB? > > > > > >Regards, > >Alan > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by: OSDN - Tired of that same > >old > >cell phone? Get a new here for FREE! > >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > >_______________________________________________ > >http://OpenEJB.sf.net > >OpenEJB-user mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/openejb-user > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > http://OpenEJB.sf.net > OpenEJB-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/openejb-user > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > http://OpenEJB.sf.net > OpenEJB-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/openejb-user > > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ http://OpenEJB.sf.net OpenEJB-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openejb-user
