You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@beehive.apache.org by Mike Pettypiece <Mi...@EMBARCADERO.COM> on 2006/02/24 21:48:16 UTC
WSDL generation
What's the easiest way to generate the WSDL for a JSR181-annotated Java
class in Beehive? I know I can deploy the web service and get the WSDL
by appending "?wsdl" to the URL, but I'm wondering if there is a way to
get it at build time. I could use the Axis Java2WSDL tool, but then I'm
no longer getting the benefit of the JSR181 annotations.
Cheers,
Mike
Re: Pageflow footprint compared to Struts..
Posted by James Allerton-Austin <ja...@bea.com>.
Sorry mispost.
Please ignore daft question.
JAA
On Thu, 2006-03-30 at 11:27 +0100, James Allerton-Austin wrote:
>
> Hi there,
>
> IHAC who wants to make the "best" decision for his MVC
> infrastructure.
>
> Currently, they are looking at Struts, Pageflow and Spring MVC. They
> are very focused on the memory footprint that pageflow has over
> struts.
>
> Does anyone have any experience of the relative footprint of pageflow
> vs struts and Spring MVC?
>
> cheers
>
> JAA
>
>
>
>
>
>
>
>
>
>
>
>
> James Allerton-Austin
> Senior SE
>
> Mobile: +44 (0) 77 80 69 30 60
> Yahoo: jaustinbea
> jaustin@bea.com
>
> BEA
> Systems, Ltd.
> Windsor Court
> Kingsmead Business Park
> Frederick Place, London Road
> High
> Wycombe
> Bucks, HP11 1JU
> England
>
> www.bea.com
>
>
>
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Pageflow footprint compared to Struts..
Posted by James Allerton-Austin <ja...@bea.com>.
Hi there,
IHAC who wants to make the "best" decision for his MVC infrastructure.
Currently, they are looking at Struts, Pageflow and Spring MVC. They are
very focused on the memory footprint that pageflow has over struts.
Does anyone have any experience of the relative footprint of pageflow vs
struts and Spring MVC?
cheers
JAA
James Allerton-Austin
Senior SE
Mobile: +44 (0) 77 80 69 30 60
Yahoo: jaustinbea
jaustin@bea.com
BEA
Systems, Ltd.
Windsor Court
Kingsmead Business Park
Frederick Place, London Road
High
Wycombe
Bucks, HP11 1JU
England
www.bea.com
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: WSDL generation
Posted by Eddie O'Neil <ek...@gmail.com>.
Mike--
Good question -- while the JSR-181 spec defines mappings for
annotations to WSDL, we don't have a tool to generate a WSDL file from
the annotated Java source. Certainly seems like such a thing would be
useful; could you add an enhancement request to JIRA?
I'm trying to eek out time to continue working on WSM for Axis 1.x /
2, and maybe this would be something that can be done along with that.
Thanks.
Eddie
On 2/24/06, Mike Pettypiece <Mi...@embarcadero.com> wrote:
> What's the easiest way to generate the WSDL for a JSR181-annotated Java
> class in Beehive? I know I can deploy the web service and get the WSDL
> by appending "?wsdl" to the URL, but I'm wondering if there is a way to
> get it at build time. I could use the Axis Java2WSDL tool, but then I'm
> no longer getting the benefit of the JSR181 annotations.
>
>
>
> Cheers,
>
>
>
> Mike
>
>
>