axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "duglin" <dug...@yahoo.com>
Subject Re: Types of Deployment (Re: Thoughts about .jws deployment)
Date Mon, 28 May 2001 17:36:46 GMT
James,
  Just focussing on JWS for a moment - have you deployed a JWS
file yet?  From a newbie's point of view it can't get much easier - just
take their Java file and drop it in their webapp directory (with a new
extension - which BTW we might change back to just java).  No deployment
files, no XML no configuration, no compiling, or re-compiling when you
change the source.  Very easy.  Even if JWS file don't grow to have
any more functionality I still think it's a very usefully way of
demonstrating
to new SOAP users what SOAP is all about and how easy it can be.
(But they will grow  8-)
-Dug

----- Original Message -----
From: "James M Snell" <jasnell@us.ibm.com>
To: <axis-dev@xml.apache.org>
Sent: Monday, May 28, 2001 1:21 PM
Subject: Re: Types of Deployment (Re: Thoughts about .jws deployment)


> Yuhichi,
>
> The deployment methods that I am currently working on (during my rare
> spare moments of time) include:
>
> 1. WAR/EAR files that contain the compiled java code, and the
> WSDL/WSDD/SOAP 2.x Deployment Descriptor documents that provide the
> deployment metadata
> 2. WSDD +/- WSDL based deployment via Server-side command-line utility
> (DeploymentManager.java class)
> 3. SOAP 2.x Deployment Descriptor based deployment via Server-side
> command-line utility (DeploymentManager.java class)
> 4. WSDD +/- WSDL & SOAP 2.x Deployment Descriptor based deployment via
> Web-based administration console (disabled by default)
>
> I personally don't like the use of JWS files.  I don't see what advantage
> they give us over using something like BSF.  I'd like to see JWS removed
> completely before version 1.0 release.
>
> The preferred method of deploying services will be the WAR/EAR method.
>
> - James Snell
>      Software Engineer, Emerging Technologies, IBM
>      jasnell@us.ibm.com (online)
>      jsnell@lemoorenet.com (offline)
>
> Please respond to axis-dev@xml.apache.org
> To:     axis-dev@xml.apache.org
> cc:
> Subject:        Types of Deployment (Re: Thoughts about .jws deployment)
>
>
>
>
> Folks,
> I am wondering how many ways of deployments we should consider.
> 1. Use AdminClient + Java classes
> 2. Use AdminClient + jws files
> I am not sure if they are real deployments.  How Java classes and jws
> files
> are deployed?  I am also concerd with the jws approach in some case.
> It may compile jws on the file, so a permission should be given the user
> to
> write the class file on the server.  This would cause some security
> problem.
> I coudl imagine the following appoach:
> 3.Create a war (or ear) file which includes Java classes (and jws files)
> and
> deployment descriptor.
> I don't know why we do not have the third one.  This is most portable, and
> simplest.  1 and 2 are more advanced.
> Is there any other way for deployment?
> Best regards,
>
> Yuhichi Nakamura
> IBM Tokyo Research Laboratory
> Tel: +81-462-73-4668
>
>
> From: "Glen Daniels" <gdaniels@macromedia.com> on 2001/05/27 07:38
>
> Please respond to axis-dev@xml.apache.org
>
> To:   <axis-dev@xml.apache.org>
> cc:
> Subject:  Thoughts about .jws deployment
>
>
>
>
> The current system we have for dropping *.jws files into the web space to
> deploy services is very cool, but could be better.  One of the nice things
> that the .NET equivalent of this (*.asmx files) can do, because they
> control
> the compiler technology, is insert various deployment "hints" into the
> asmx
> file.  For instance, they can specify which methods are "WebMethods" and
> which ones are not exposed to the web service engine.
>
> I'd like to see the ability to "tweak" the deployment of a jws service in
> this way, and perhaps in other ways as well (for instance, custom
> typemappings).  I see two possible techniques for doing this:
>
> 1) Use a preprocessor to embed deployment hints directly in the java file,
> in comments.  This would be sweet, but would potentially be a bunch of
> work.
>
> 2) Have the server look for a companion "*.jwd" (java web deployment) file
> in the same directory as the .jws file.  This file, if it exists, would be
> an XML file containing some deployment config/options for the service.
>
> Example -
>
> Foo.jws:
> public class Foo {
>    public String method1()
>    { return "Hi, I'm method 1!"; }
>
>    public String method2(int seekrit_number)
>    { return "The seekrit number was " + seekrit_number; }
> }
>
> Foo.jwd:
> <deploy>
>  <method>method1</method>
> </deploy>
>
> This would only allow remote SOAP access to method1.
>
> Thoughts?
>
> --Glen
>
>
>
>
>
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


Mime
View raw message