[
https://jira.jboss.org/browse/GTNWSRP-92?page=com.atlassian.jira.plugin.s...
]
Matt Wringe commented on GTNWSRP-92:
------------------------------------
A quick look through the v1 and v2 xsd shows that this should be the only real
compatibility issue with converting v1 over to v2. There are a few other minor issues with
things like CustomUserProfile, but these are optional
and we don't deal with them.
The code actually already handles the case where the namespacePrefix or the
PortletInstanceKey is null. If the NamespacePrefix if its null, it will use the
portletHandle. If the PortletInstanceKey is null, it will use the id of the PortletContext
(which is original set from the portletHandle). But the conversion methods will throw
errors before the defaults have a chance to be set.
It shouldn't be too hard to change how the conversion methods works so that it
doesn't throw an error. But, I don't know how often we run into v1 producers which
don't set these values, and I wonder if these defaults are the right ones to use.
Need to handle properly values that are now mandatory while they were
optional in v1
------------------------------------------------------------------------------------
Key: GTNWSRP-92
URL:
https://jira.jboss.org/browse/GTNWSRP-92
Project: GateIn WSRP
Issue Type: Task
Components: Specification Support
Affects Versions: 2.0.0-Alpha03
Reporter: Chris Laprun
Assignee: Chris Laprun
Fix For: 2.0.0-Beta
For example, RuntimeContext has mandatory namespacePrefix and portletInstanceKey in v2,
whereas these values were optional in v1.
Conversion methods need to be adapted so that we can provide appropriate values for
potentially missing fields.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira