You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Mark Henning <md...@gldnrtvr.com> on 2008/03/05 21:02:10 UTC

Juddi application architecture question

I have a requirement to build an application framework which should 
be stand-alone (i.e. no tomcat server and no external database).

One possibility that I have come up with is to use juddi, hsqldb and 
jetty, all embedded in the application.
(please look at www dot gldnrtvr dot com/public/ServerComponents.png 
for a component diagram)

I have been having difficulty making juddi connect to the hsqldb 
embedded instance (though I was successful in
building the juddi repository by running the create_database.sql from 
the resources in the juddi jar file).

Is this architecture possible / practical?  If so I presume it is 
just a matter of supplying the juddi RepositoryEngine(Properties) 
constructor with the correct set of properties.

Any guidance you can supply would be helpful.

Thank you,

-Mark Henning


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-user-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-user-help@ws.apache.org


Re: Juddi application architecture question

Posted by Kurt T Stam <ku...@gmail.com>.
Hi Mark,

The easiest way is to scout, and configure it to use the LocalTransport. 
This will allow you to run jUDDI in embedded mode.
The scout unittests run that way using Derby (also embedded), but hsqldb 
works fine too. We run it that way (with hsqldb) in JBossESB.

So take a peek at Apache Scout, and JBossESB.

Hope that helps.

--Kurt

Mark Henning wrote:
> I have a requirement to build an application framework which should be 
> stand-alone (i.e. no tomcat server and no external database).
>
> One possibility that I have come up with is to use juddi, hsqldb and 
> jetty, all embedded in the application.
> (please look at www dot gldnrtvr dot com/public/ServerComponents.png 
> for a component diagram)
>
> I have been having difficulty making juddi connect to the hsqldb 
> embedded instance (though I was successful in
> building the juddi repository by running the create_database.sql from 
> the resources in the juddi jar file).
>
> Is this architecture possible / practical?  If so I presume it is just 
> a matter of supplying the juddi RepositoryEngine(Properties) 
> constructor with the correct set of properties.
>
> Any guidance you can supply would be helpful.
>
> Thank you,
>
> -Mark Henning
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: juddi-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: juddi-user-help@ws.apache.org
>
>


-- 
Kurt T Stam
kstam@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-user-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-user-help@ws.apache.org