SPONSORS:






User Tag List

Results 1 to 5 of 5
  1. #1
    Junior Member
    Join Date
    Jun 2002
    Posts
    12
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Using LaunchAnywhere\'s java launcher


    My application is started using
    LaunchAnywhere's java launcher. Should
    this exe be added to

    1. extensions enabler
    2. extensions

    of SilkTest before I start testing. I am
    using version 4.5 of the InstallAnywhere
    software.


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

  2. #2
    Senior Member
    Join Date
    Jul 1999
    Location
    Bellingham, WA USA
    Posts
    1,323
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Using LaunchAnywhere\'s java launcher

    Are you attempting to automate the install testing?

    Not familiar with "Launch Anywyere" but have automated installs with Install Anywhere and it was a bear-n-a-half to get it to work. What you may run into is the need to get the appropriate jar files in the classpath. There was an issue of Install Anywhere establishing a classpath AFTER the install had kicked off. It was an amazingly odd thing. What this did, in effect, was eliminate the Segue jar file from the classpath becuase Silk kicked off the install, and THEN the classpath was established by Install Anywhere. If Launch Anywhere works in the same manner, you will need to wrestle with that same issue.



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

  3. #3
    Junior Member
    Join Date
    Nov 2002
    Posts
    1
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Using LaunchAnywhere\'s java launcher

    DJ, you mentioned some of the headaches you have had trying to get around Install Anywhere testing. I am facing some of these same issues. I can't get the Window Decleration recorder to notice any of the controls in the Install Anywhere dialogs. What am I doing wrong? Any help would be appreciated.

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

  4. #4
    Senior Member
    Join Date
    Feb 2000
    Posts
    1,497
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Using LaunchAnywhere\'s java launcher

    Emma,

    The answer is no. Since Silk won't be be driving or interacting with the LaunchAnywhere process, it doesn't need to know about it (beyond knowing how to start it, that is).

    What must be configured in the extensions and extensions enabler is the name of the applications' executable if it differs from java.exe or javaw.exe. After you've started the app, look at the Task Manager Process tab to see what its name is.

    Also it matters where the silktest_java2.jar file is placed so that Silk can communicate with the application. You can either:

    1. copy it to the applications' java/lib/ex folder,

    OR optionally:

    2. Either insert Silk's jar file into the .lax entry for LAX.CLASS.PATH, or merely place the jar file in the same folder as the .lax. Talk to you developers to see which method they use in their code.

    Anymore, I always use #1. It's fast, simple, reliable and requires no periodic editing.


    John


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


    [This message has been edited by John J. Miller (edited 11-21-2002).]

  5. #5
    Senior Member
    Join Date
    Jul 1999
    Location
    Bellingham, WA USA
    Posts
    1,323
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Using LaunchAnywhere\'s java launcher

    Kevin,

    It's been a couple of years since I messed with this, but I would recommend John Miller's #1 suggestion. Find your Java install's ./lib/ext folder and copy the Silk_Java2.jar file into that folder. You may find this folder in more than one place on your drive; one in the JDK### folder and one in the Program Files folder. For safety sake I place it in each of them.

    When you have issues with Silk and Java testing, the issue is almost always that the Segue jar file is getting punted out of the classpath. At one point I got so irritated with it that I wrote a recursive routine to copy that file to every stinking folder on my hard drive. That way it HAD to be in the path, and sure enough everything started working!

    So, implement John's suggestion and try it again. If it really gets to be a problem, I recall at one point we actually compiled the segue jar right into the build to force those classes into the classpath. I can't recall all the specifics of that, but I remember doing it.

    Keep us posted on this. I know how frustrating it is. Just bear in mind that once you get it recognizing your InstallAnywhere java objects it works beautifully!

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

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 09:18 PM.

Copyright BetaSoft Inc.