jUDDI tables dropped at server shutdown

[thomas.diesler]

http://jira.jboss.com/jira/browse/JBESB-1323

Kurt Stam [12/Nov/07 08:54 AM]
what do you think is causing the tables to be dropped? I have never seen this. How do I reproduce it? We have no code that does that, apart from code in the unittests that is.

Kevin Conner [12/Nov/07 11:14 AM]
This seems to be an issue with the SOA platform, there is a jUDDI configuration in juddi-service.sar. This configuration sets DropOnStop as true.

I don't think this is one for us. :)

Kevin Conner [12/Nov/07 11:17 AM]
Kurt, can you take a look at the SOA platform and advise Trevor on this? Is it safe for him just to remove this sar file?

Kurt Stam [12/Nov/07 11:30 AM]
Yes it should be removed. The juddi that comes with AS is much older then the one we use in ESB.

Mark Little [12/Nov/07 11:33 AM]
JBossWS uses jUDDI, so I assume it's coming from there. Someone needs to talk to Thomas Diesler first.

Kurt Stam [12/Nov/07 11:36 AM]
I guess we (ESB) should deploy the juddi.war by default, so we bring up the juddi WSs and then run whatever tests JBossAS has for this to make sure it all still works.

[marklittle]

What is the conclusion?

[kurtstam]

This is only a problem in the 'all' profile of JBossAS, where AS ships the juddi.sar. From an ESB perspective this should get removed, and we should deploy our juddi.war by default into the jbossesb.sar to bring up the juddi WSs. We *should* not break anything by doing that, but it would be nice if Thomas can tell us what to do to proof this out.

--Kurt

[kconner]

Just to clarify, this is also a problem in the 'production' profile of the SOA platform. This is why Trev needs to know how to tidy this up.

[thomas.diesler]

I don't really understand why there is a need for two juddi implementations. If juddi.sar is no good we should fix that

Specifically, I need to understand better why

we should deploy our juddi.war by default

[thomas.diesler]

The jboss jaxr project lives here

URL: https://svn.jboss.org/repos/jbossas/projects/jaxr/trunk
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 67503
Node Kind: directory
Schedule: normal
Last Changed Author: [e-mail]
Last Changed Rev: 60526
Last Changed Date: 2007-02-14 12:12:51 +0100 (Wed, 14 Feb 2007)

[mvecera]

I would prefer fixing EAP's juddi.

Supposing we deleted juddi-service.sar I can imagine the mess while applying patches for EAP and SOA to this (it must be possible to apply EAP patch to SOA-P)...

[thomas.diesler]

I would prefer fixing EAP's juddi.

Yes, and its not really a question of preference. The juddi-service needs to get updated and verified against the TCK.