Thanks you for all the response to my email.
I have a new question, in this case is a practical question.
In this moment I'm develop a few examples for demonstrate in my
laboratory that Apache Muse is a good Framework for use here. A few days
ago, I showed that Muse is very good tool for a rapid development, but
at this meeting a developer made me a question, Who is using Apache Muse
Framework at this moment ?.
My question is: Do you know some enterprise or laboratory that use Muse
in a real problem ?
Thanks
Rafael León Zamorano
[EMAIL PROTECTED] escribió:
Hi Rafael
Just a fair bit of warning and help, the xsd:integer variable value is to the
best of my knowledge only useful within the scope of Java. At least for the
integration work I've done so far with WSRF .Net and Muse, the generation of
proxies for a Muse resource with a xsd:integer value in the wsdl fails, however
using xsd:int is fine for both Java and WSRF .Net.
Just in case you want to make your resource have more integration abilities
later down the road.
And guys I suggest this small alteration to the Muse example to show good
practice in terms of integration further down the road.
/Lenni
-----Original Message-----
From: Vinh Nguyen (vinguye2) [mailto:[EMAIL PROTECTED]
Sent: 01 February 2008 23:49
To: [email protected]
Subject: RE: HttpServer Example
Hi Rafael,
Normally, the client application will also have references to the WSDL/XSDs implemented
by the server. These files define the server's operational and object model interface.
If the client doesn't have these files, it won't know what operations it can call or what
data structures are required. With these files, the client should easily know that
"Port" contains an integer, even though the actual XML stores the value as a
plain string.
If you use a Java data binding tool (i.e. XmlBeans), the tool should be smart enough to generate
methods to access "Port" as an integer. So if you client app uses the artifacts
generated from your data binding tool (i.e. Java classes from XmlBeans representing the XSD types),
it should be able to access "Port" as an integer without needing to look directly as the
WSDL/XSD to know its type.
-Vinh
-----Original Message-----
From: Rafael [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 6:18 AM
To: [email protected]
Subject: HttpServer Example
Hello everyone,
I'm working over the example "HttpServer". This example has 2 element:
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Port" type="xsd:integer"/>
Exists some method for to know the type of the element from a client
application ?
For example, I want to know the type of the element "Port" to present this type
to the client application.
Thank you.
Rafael León Z.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
