RE: [juddi-Developers] Problems with invalid XML on query results...

[Andy Cutright <An...@borland.com>]

hi ray, 
 
jUDDI is now an apache incubator project, and we've moved the email
lists. we are still using the bug software at sourceforge. can you
please create a bug and attach your proposed fixes so we can take a
look? or at least post your diffs to the list? 
 
cheers,
andy 

	-----Original Message-----
	From: Roberts, Ray [mailto:ray.roberts@lmco.com] 
	Sent: Wednesday, December 17, 2003 3:17 PM
	To: juddi-developers@lists.sourceforge.net
	Subject: [juddi-Developers] Problems with invalid XML on query
results...
	
	
	I'm trying to use JAXR with juddi and ran into some places where
juddi wasn't adhereing to the uddi spec.  Thought I'd relay my changes:
	 
	A serviceInfo element is required by the spec to have a
businessKey.  So, on line 3829 of JDBCDataStore.java I changed it to
read:
	
info.setServiceInfos(fetchServiceInfosByBusinessKey(businessKey,true));
	 
	This causes fetchServiceInfosByBusinessKey to include the
businessKey.  Since this was parameterized, I must assume that someone's
been mucking in this area before.  Which leads me to believe that I
might be missing something in the larger picture.  If so, could you
please let me know.
	 
	Also, a categoryBag is an optional element of a businessService,
but if it's included then it must have at least one keyedReference, as
per the spec.  The output was coming out with a <categoryBag/>, which is
invalid.  To fix this I modified some code around line 346 of
CategoryBagHandler to only output the categoryBag if it had
keyedReferences.
	 
	This seems to make the code that I've been working on work
better.  Please let me know if I'm missing something.
	 
	Thanks,
	-Ray