Re: The state of Geronimo --

[tb...@yahoo.com]

The unit test does not use the universal DB2 driver. I
think it really should since Geronimo is backed by
IBM. And that way people that use it would have an
example to go by. It uses org.hsqldb as a driver.

Anyways, I have a feeling that the way to get the
database connector as you, David, said below:
> DataSource ds = (DataSource)kernel.invoke(mcfName,
> "$getResource");

leads me to my next step of registering users and
adding them to the database. Now how would I get a
handle to the kernel from the SQLLoginModule? Is it
statically defined somewhere? What is mcfName supposed
to be, and what is $getResource supposed to be?

Also, can I create a form similar to the one provided
in the applications/demo/src/auth/login.html file
(just simple username and password registration) that
would call a class instead of the SQLLoginModule, get
the DataSource, connect to the database and insert the
new user? Can I do this using declarative J2EE as I am
with the deployment plan?

I assume I would just store this in the web-inf
directory and load/deploy it on Geronimo like I am the
security deployment plan, no?

Tyler


--- David Jencks <da...@yahoo.com> wrote:

> 
> On Oct 19, 2005, at 10:19 PM, <tb...@yahoo.com>
> wrote:
> 
> > I'm so determined I'm rebuilding M5 with print
> > statements in the SQLLoginModule file. Something's
> > clearly wrong with something (dunno what). I may
> be
> > narrowing it down. From then I guess I can build
> my
> > own modules that will connect to the database the
> way
> > I want, no?
> 
> That should work.  BTW, the SQLLoginModule is, umm,
> less than the most 
> sophisticated code ever seen, so if you want to
> improve it we would all 
> be appreciative.  See 
> http://issues.apache.org/jira/browse/GERONIMO-409. 
> I think some easy 
> improvements would be to use prepared statements
> with the user info as 
> parameters rather than fetching all the info each
> time.
> 
> Another, deeper, issue is that it makes a direct
> connection to the 
> database rather than getting one out of a connection
> pool.  I have 
> never thought this was a good idea.  However, jndi
> is not available to 
> look up datasources in a login module, so you would
> have to get the 
> datasource more directly from a
> ManagedConnectionFactoryWrapper gbean.  
> The call would be IIRC
> 
> DataSource ds = (DataSource)kernel.invoke(mcfName,
> "$getResource");
> 
> This would let you use pooled connections which
> ought to be faster for 
> most databases.
> 
> I do wonder what the cause of your problems might be
> because there is a 
> working unit test for this login module.
> >
> > If there's a quicker way to rebuild changes like
> this,
> > then please let me know.
> >
> > I rebuild security. Then I rebuild assembly, and
> use
> > the new server.jar in the
> > modules/assembly/target/geronimo-1.0-M5/bin
> directory.
> 
> This will definitely work.  I usually find it is
> more efficient to 
> debug the server in an IDE though.    I use IDEA and
> start the server 
> like this:
> 
> java -Xdebug -Xnoagent -Djava.compiler=NONE 
>
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
> -jar 
> bin/server.jar
> 
> and have a remote debugging configuration for that
> in IDEA.  I think 
> you can do essentially the same thing in eclipse.
> 
> thanks,
> david jencks
> 
> >
> > Thanks!
> > Tyler
> >
> >
> > --- Bruce Snyder <br...@gmail.com> wrote:
> >
> >> On 10/19/05, tbot55@yahoo.com <tb...@yahoo.com>
> >> wrote:
> >>> Lets have some discussion, maybe I'm totally
> >> missing
> >>> somethings.
> >>>
> >>> Currently I see all/most the applications I've
> >> looked
> >>> at as J2EE apps. This is the goal of Geronimo,
> but
> >>> they largly bypass the low-level purposes of
> >> Geronimo
> >>> by just sticking to J2EE and JSP. Though the
> >> GBeans
> >>> thing is cool. The goals are the same, but
> >>> accomplished in different ways.
> >>
> >> The reason the apps you see today running on
> >> Geronimo are J2EE apps of
> >> some type is because that was one of the first
> goals
> >> of Geronimo -
> >> J2EE 1.4 certification. In time, people will
> >> understand that they can
> >> construct their own application server by
> assembling
> >> different pieces
> >> of software using the Geronimo kernel and GBean
> >> architecture and only
> >> then will we see the true power of Geronimo begin
> to
> >> emerge.
> >>
> >> J2EE is simply one goal for Geronimo, it is
> >> certainly not *the* goal
> >> (after all, J2EE compliance is simply a set of
> >> configuration files).
> >> Another goal includes the result of the kernel
> and
> >> GBean architecture
> >> - the ability to easily plug in just about any
> piece
> >> of software to
> >> run in the Geronimo space. Still another goal
> (and a
> >> very important
> >> one) was to accomplish all of this work under the
> >> Apache License. I
> >> could go on and on, but I highly suggest reading
> >> through at least the
> >> wiki (http://wiki.apache.org/geronimo/) to
> >> understand Geronimo from
> >> your own perspective.
> >>
> >>> So why not use JBoss or some other server that
> >>> supports JSP and J2EE apps (even thought they
> may
> >>> require slight tweaks if they aren't fully J2EE
> >>> compliant). I'm sure they have much better
> support
> >> and
> >>> the built-in features (especially low level
> >> security
> >>> ones) are available? Why use Geronimo? It's all
> >> the
> >>> same until enough demo apps come built into the
> >>> distribution, demoing why someone should use
> >> Geronimo
> >>> instead of something else. It's the same stuff
> >> from my
> >>> viewpoint.
> >>
> >> JBoss uses the LGPL and this license is
> incompatible
> >> with the Apache
> >> License
> >>
> >
>
(http://www.apache.org/licenses/GPL-compatibility.html).
> >>
> >> Why use Geronimo? I think I'll let the rest of
> the
> >> community tackle
> >> this one ;-). What I will say is that the last
> two
> >> years of work has
> >> focused on J2EE 1.4 certification. Now that that
> >> goal has been
> >> accomplished, we can all begin to direct our
> focus
> >> on items that will
> >> distinguish Geronimo from the rest of the pack.
> The
> >> best is yet to
> >> come.
> >>
> >> One of the the most powerful features of Geronimo
> is
> >> the ability to
> >> assemble your own components to build your own
> >> application server. We
> >> call these custom assemblies. For example, if
> you're
> >> not developing
> >> EJBs, then don't run the EJB container.
> Geronimo's
> >> EJB container is
> >> not part of the core of the application server so
> it
> >> can be commented
> >> out or removed from the configuration. If you're
> >> only interested in
> >> running Tomcat and ActiveMQ, then run that. If
> you
> >> need an Enterprise
> >> Service Bus via a JBI container, then run
> >> ServiceMix, etc. The
> 
=== message truncated ===



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/