You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by "Vinh Nguyen (vinguye2)" <vi...@cisco.com> on 2008/02/02 00:48:31 UTC
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:rleon@lpnhe.in2p3.fr]
Sent: Thursday, January 17, 2008 6:18 AM
To: muse-user@ws.apache.org
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: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Realworld Usage Of Muse
Posted by Ch...@swisscom.com.
Hi Rafael,
I am replying on a different subject so that more people may react to it. I am personally using Muse to provide advanced monitoring functionality for my applications. Its not productive yet, due in part to issue 270, but both the server and the client proxies are generated/enabled by Muse.
I am perhaps using some more advanced, and unplanned, functionality within Muse. I have adapted it to be able to:
- perform restarts at runtime
- adapt the soap client to be able to use jms or other transports (also requires a custom NotificationClient, but I have seen someone else on the list using this functionality as well)
- handle persisted subscriptions across planned stops and restarts (not just crashes)
- send notifications to "proxied" resource subscribers (not subscribers of the entire resource)
- have expected PullPoint functionality (only the messages subscribed to are notified)
- serialize dom elements without namespace prefixes (to handle XML Canonalization)
My only large complaints about Muse are the liberal use of "private" member data and some of the thread safety issues. The privates follow "good practice" but hamper being able to simply extend classes, often requiring complete copy+paste re-implementations. The thread issues of course affect everyone who intends to have serious load with Muse. These issues are more than fixable.
Having said that...
I have been using it now for half a year and everything else, from the tools to the internal architecture gives me a great developer experience, can't recommend it enough.
cheers,
Chris
-----Original Message-----
From: Rafael [mailto:rleon@lpnhe.in2p3.fr]
Sent: Tuesday, February 05, 2008 10:33 AM
To: muse-user@ws.apache.org
Subject: Re: HttpServer Example
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: HttpServer Example
Posted by Rafael <rl...@lpnhe.in2p3.fr>.
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
lenni.madsen@bt.com 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:vinguye2@cisco.com]
> Sent: 01 February 2008 23:49
> To: muse-user@ws.apache.org
> 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:rleon@lpnhe.in2p3.fr]
> Sent: Thursday, January 17, 2008 6:18 AM
> To: muse-user@ws.apache.org
> 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: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: HttpServer Example
Posted by le...@bt.com.
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:vinguye2@cisco.com]
Sent: 01 February 2008 23:49
To: muse-user@ws.apache.org
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:rleon@lpnhe.in2p3.fr]
Sent: Thursday, January 17, 2008 6:18 AM
To: muse-user@ws.apache.org
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: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org