You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jervis Liu (JIRA)" <ji...@apache.org> on 2006/09/30 05:54:19 UTC
[jira] Created: (CXF-134) Improve the demo xml message to make demo
more descriptiove
Improve the demo xml message to make demo more descriptiove
------------------------------------------------------------
Key: CXF-134
URL: http://issues.apache.org/jira/browse/CXF-134
Project: CeltiXfire
Issue Type: Sub-task
Affects Versions: 2.0-M1
Reporter: Jervis Liu
<Customers>
<Customer href="http://localhost/customerservice/customer?id=1234> <id>1234</id>
</Customer>
<!-- more customers -->
</Customers>
Just a minor comment here. I think it would be more descriptiove if some info more meaningful than an id (when available) can be returned to a client as part of collection queries, perhaps a name, or something similar. With ids you dont get anything interesting out of the collection, nothing to look at for a (human) user. If we have :
<Customers>
<Customer href="http://localhost/customerservice/customer?id=1234> <name>John</name>
</Customer>
<!-- more customers -->
</Customers>
Not a lot of interesting info, but still a client can use a name in order to choose which reference to follow, etc...Perhaps for this to work two annotations should be made, one for identifying a field which will be used as part of href, another one for identifying the ref value like 'John'.
Another thing is that it might be worth considering identifying reference-like elements as being references :
<CustomerRef href="http://localhost/customerservice/customer?id=1234> <name>John</name>
</CustomerRef>
It makes it easier to understand that a collection returns a bunch of references. The thing is is that most likely there'll be a schema out there which says how a Customer instance may look like and it may not permit Customer instances not to contain all elements or to contain an href attribute. Perhaps the convention should be <BeanName>+"Ref" for naming references. xml.com hosts a lot of interesting articles about it...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CXF-134) Improve the demo xml message to make demo
more descriptiove
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-134?page=all ]
maomaode closed CXF-134.
------------------------
Resolution: Fixed
> Improve the demo xml message to make demo more descriptiove
> ------------------------------------------------------------
>
> Key: CXF-134
> URL: http://issues.apache.org/jira/browse/CXF-134
> Project: CXF
> Issue Type: Sub-task
> Affects Versions: 2.0-M1
> Reporter: Jervis Liu
> Fix For: 2.0-M1
>
>
> <Customers>
> <Customer href="http://localhost/customerservice/customer?id=1234> <id>1234</id>
> </Customer>
> <!-- more customers -->
> </Customers>
> Just a minor comment here. I think it would be more descriptiove if some info more meaningful than an id (when available) can be returned to a client as part of collection queries, perhaps a name, or something similar. With ids you dont get anything interesting out of the collection, nothing to look at for a (human) user. If we have :
> <Customers>
> <Customer href="http://localhost/customerservice/customer?id=1234> <name>John</name>
> </Customer>
> <!-- more customers -->
> </Customers>
> Not a lot of interesting info, but still a client can use a name in order to choose which reference to follow, etc...Perhaps for this to work two annotations should be made, one for identifying a field which will be used as part of href, another one for identifying the ref value like 'John'.
> Another thing is that it might be worth considering identifying reference-like elements as being references :
> <CustomerRef href="http://localhost/customerservice/customer?id=1234> <name>John</name>
> </CustomerRef>
> It makes it easier to understand that a collection returns a bunch of references. The thing is is that most likely there'll be a schema out there which says how a Customer instance may look like and it may not permit Customer instances not to contain all elements or to contain an href attribute. Perhaps the convention should be <BeanName>+"Ref" for naming references. xml.com hosts a lot of interesting articles about it...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CXF-134) Improve the demo xml message to make demo
more descriptiove
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-134?page=all ]
maomaode updated CXF-134:
-------------------------
Fix Version/s: 2.0-M1
> Improve the demo xml message to make demo more descriptiove
> ------------------------------------------------------------
>
> Key: CXF-134
> URL: http://issues.apache.org/jira/browse/CXF-134
> Project: CXF
> Issue Type: Sub-task
> Affects Versions: 2.0-M1
> Reporter: Jervis Liu
> Fix For: 2.0-M1
>
>
> <Customers>
> <Customer href="http://localhost/customerservice/customer?id=1234> <id>1234</id>
> </Customer>
> <!-- more customers -->
> </Customers>
> Just a minor comment here. I think it would be more descriptiove if some info more meaningful than an id (when available) can be returned to a client as part of collection queries, perhaps a name, or something similar. With ids you dont get anything interesting out of the collection, nothing to look at for a (human) user. If we have :
> <Customers>
> <Customer href="http://localhost/customerservice/customer?id=1234> <name>John</name>
> </Customer>
> <!-- more customers -->
> </Customers>
> Not a lot of interesting info, but still a client can use a name in order to choose which reference to follow, etc...Perhaps for this to work two annotations should be made, one for identifying a field which will be used as part of href, another one for identifying the ref value like 'John'.
> Another thing is that it might be worth considering identifying reference-like elements as being references :
> <CustomerRef href="http://localhost/customerservice/customer?id=1234> <name>John</name>
> </CustomerRef>
> It makes it easier to understand that a collection returns a bunch of references. The thing is is that most likely there'll be a schema out there which says how a Customer instance may look like and it may not permit Customer instances not to contain all elements or to contain an href attribute. Perhaps the convention should be <BeanName>+"Ref" for naming references. xml.com hosts a lot of interesting articles about it...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira