Andy Dwelly <[EMAIL PROTECTED]> writes
>
>I've hacked together a prototype version of JAWSPersistenceManager that
>allows a user to interact directly with the database back end, and see
>what's in various tables and how jBoss is interacting with it. It also
>allows the user to drop tables and delete individual rows (non-compound PKs
>only right now). I find this useful during entity bean development because
>I'm stuck on an NT development environment and it has problems getting the
>correct date on files, causing difficulties for redeployment.  This visual
>JAWS class allows me to get the database into a sensible state for testing
>my clients and seeing what they make JAWS do.
>
>The prototype is extremely crude and wildly inefficient, I've absolutely no
>doubt that there are all sorts of of entity beans that will simply make it
>crash and burn.
>
>However, there may be the core of a useful plugin here although it needs
>considerable refactoring, it should probably be a separate component from
>JAWS or a subclass or something.
>
>I'd be happy to send out the code to anyone who's interested although I've
>badly mangled the original which was authored by Rickard berg.
>
>Mail me for screenshots or the source.

Andy

Thanks for emailing me the code. Putting a GUI in server code isn't
really the way we want to go, but at the same time we are very aware
that tool support is needed for ad-hoc DB queries, setting up tables,
etc.

There was some discussion of this back in April/May - see Bug #3 in
Bugzilla. Unfortunately, nothing has been implemented.

Some of the original discussion revolved around using a servlet to do
this. Personally, I think a stateless session bean would be the way to
go. You've already put a lot of work into the user interface - would you
be interested in having a go at turning it into a remote client of a
stateless session bean?

regards

   Justin

-- 
Justin Forder


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to