Check WSRP type definition to check for non-nillable values ----------------------------------------------------------- Key: JBPORTAL-808 URL: http://jira.jboss.com/jira/browse/JBPORTAL-808 Project: JBoss Portal Issue Type: Task Security Level: Public(Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Alpha1 Original Estimate: 2 hours Time Spent: 1 hour Remaining Estimate: 3 hours JBoss WS stack creates default value for nillable WSDL elements. If no valid value is provided for a non-nillable element, this will cause an error about elements being out of sequence. Example: From wsrp_v1_types.xsd, a valid markup request conforms to the getMarkup element: registrationContext (nillable), portletContext, runtimeContext, userContext (nillable), markupParams. runtimeContext is non-nillable. If no valid runtimeContext is provided when creating the getMarkup object, the WS stack will not emit an element for runtimeContext whereas one will be for userContext (which is nillable), resulting in the WS complaining about userContext not being in the right position in the sequence.