[
http://jira.codehaus.org/browse/XFIRE-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145581#action_145581
]
Karl Palsson commented on XFIRE-765:
------------------------------------
Yuck. I know that xfire 1.X is not cool anymore, but seeing as there is a
proposed patch for this, can we get a bugfix release?
Is there any workaround besides changing the method signature?
public Map<String, String> blah() goes into anytype hell.
public List<StringPairObject> blah() works fine, if you want to monkey around
with a new class holding two strings.
I know that I should really have a better domain object, nicer, purer, cooler
XML than just key/value pairs, but that's how it goes. Is there any workaround
for this? I see in the spring-xfire jar, xfire.xml,
<bean id="xfire.typeMappingRegistry"
class="org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry"
init-method="createDefaultMappings" singleton="true">
</bean>
So I guess I'm using Aegis. Where do I put this .aegis.xml file and what
should it be called to work around this?
> Service interface generics map generates anyType2anyTypeMap WSDL
> ----------------------------------------------------------------
>
> Key: XFIRE-765
> URL: http://jira.codehaus.org/browse/XFIRE-765
> Project: XFire
> Issue Type: Bug
> Components: Aegis Module
> Affects Versions: 1.2.2
> Environment: xbean-spring-2.7-20061026.103714-1.jar
> Tomcat 5.5.17
> Java 1.5
> Reporter: Wesley Miaw
> Assignee: Dan Diephouse
> Priority: Minor
>
> I have the following two interface signatures:
> HashMap<Integer,Source> findMostRecentSources(int[] ids) throws SQLException;
> boolean createTask(ArrayList<Task> tasks) throws SQLException;
> The ArrayList<Task> is correctly turned into an ArrayOfTask, but for some
> reason the returned HashMap is turned into anyType2anyTypeMap from the WSDL.
> e.g.
> <xsd:complexType name="anyType2anyTypeMap">
> <xsd:sequence>
> <xsd:element maxOccurs="unbounded" minOccurs="0" name="entry">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="0" name="key"
> type="xsd:anyType"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="value"
> type="xsd:anyType"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> I was able to make it generate the correct int2TaskMap by treating it as a
> Java 1.4 collection and explicitly specifying the key and component types in
> the Interface.aegis.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email