× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Using the wizard for creating a service from a Java Bean also asks you for the Service Deploy Scope. Or you could modify the generated xml file manually.



----- Original Message ----
From: Mike Burdette <Mike.Burdette@xxxxxxxxxxxxx>
To: java400-l@xxxxxxxxxxxx
Sent: Monday, 17 November, 2008 22:34:07
Subject: Re: JAVA400-L Digest, Vol 6, Issue 234

    Hi Michael:

    Thanks for your reply.

    We are not creating our service from a wsdl, but rather from a Java
    class. So we choose the "Java Bean Web Service" as our Web Service type.

    Is there an option that would work for creating a webservice from an
    existing Java class?

    Thanks again!

    message: 2
    date: Mon, 17 Nov 2008 05:58:38 -0800 (PST)
    from: Michael Hawes <mihawes@xxxxxxxxx>
    subject: Re: Object creation as pertains to Web Services in
        Websphere...

    Did you use the wizard to craete a Java Bean skeleton? On the "Web
    Service Skeleton Java Bean Configuration" page, for "Service deploy
    Scope" specify "Application" rather than the default value of "default".

    The resulting entry in the generated file "ibm-webservices-bnd.xmi" for
    the scopt attribute might look similar to the following:

    <wsdescBindings xmi:id="WSDescBinding_1219844169757"
    wsDescNameLink="myDescName">? <pcBindings
    xmi:id="PCBinding_1219844169757" pcNameLink="myLinkName"
    scope="Application"/></wsdescBindings>

    This should use a singleton (Application scoped)?rather than a request
    scoped bean. Hope that helps.

    Mike

    ?
    ----- Original Message ----
    From: Mike Burdette <Mike.Burdette@xxxxxxxxxxxxx>
    To: java400-l@xxxxxxxxxxxx
    Sent: Monday, 17 November, 2008 13:30:36
    Subject: Object creation as pertains to Web Services in Websphere...

    Hi:

    We are developing a Java based web service in Rational 6.0.1 to be
    deployed in WAS 6.0. The web service is being used by a .Net front end
    to
    fetch as well as update data on the iSeries.

    We notice that when deployed to WAS 6.0 on the iSeries, the constructor
    for the Java object that provides the Web Service is called each time
    the
    web service is called. We would like to provide some initialization
    instructions that would persist between calls to the web service, but it
    slows our response when the object is created for each request. (The
    object is created only once when using the Websphere Test Environment.)

    Any thoughts on how to do this?

    Thanks
    --
    This is the Java Programming on and around the iSeries / AS400
    (JAVA400-L) mailing list
    To post a message email: JAVA400-L@xxxxxxxxxxxx
    To subscribe, unsubscribe, or change list options,
    visit: http://lists.midrange.com/mailman/listinfo/java400-l
    or email: JAVA400-L-request@xxxxxxxxxxxx
    Before posting, please take a moment to review the archives
    at http://archive.midrange.com/java400-l.

    ------------------------------

    --
    This is the Java Programming on and around the iSeries / AS400
    (JAVA400-L) digest list
    To post a message email: JAVA400-L@xxxxxxxxxxxx
    To subscribe, unsubscribe, or change list options,
    visit: http://lists.midrange.com/mailman/listinfo/java400-l
    or email: JAVA400-L-request@xxxxxxxxxxxx
    Before posting, please take a moment to review the archives
    at http://archive.midrange.com/java400-l.

    End of JAVA400-L Digest, Vol 6, Issue 234
    *****************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.