Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316758

Summary:	Type model: Can no longer specify a defaultValue which is an empty string
Product:	[Technology] OSEE	Reporter:	Mark D-B <mark.db>
Component:	OSEE Application Framework	Assignee:	Project Inbox <osee.framework-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.9.4
Target Milestone:	0.9.5
Hardware:	All
OS:	All
Whiteboard:

Description Mark D-B

2010-06-14 09:42:55 EDT

In versions prior to 0.9.4, one could specify a min of 1 and then a defaultValue of "" to cause a string attribute to always appear for an artifact but be highlighted as an error (with the little red cross). This was very useful for artifacts where an attribute contains essential data but has no meaningful default.

On 0.9.4, attempting to import a type model with such an attribute definition in yields:

SEVERE   org.eclipse.osee.framework.manager.servlet.OseeModelServlet   handleError (59)
Osee Cache request error: [org.eclipse.equinox.http.servlet.internal.HttpServletRequestAdaptor@fdb3e9]
org.eclipse.osee.framework.core.exception.OseeWrappedException: Import Osee Types: OSEE Text Model to OSEE: DefaultValue must be set
 for attribute [<name of attribute>] with minOccurrences

Changing the min to 0 (which is not what we want) or defaultValue to "Fred" (which is also not what we want) allows the import to proceed.

Is the check for an empty string really a necessary change? If so, what's the workaround to get the error markers to appear please?