facebook

Access to WAS specific feature – DistributedMap

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #286400 Reply

    Hi

    With RAD, the WAS runtime seemed to be part of my build path, so it could resolve, for instance, a reference to a WAS-specific interface that comes bundled with the appserver. I want to make use of the WAS DistributedMap interface and dynamic cacheing features of WAS (com.ibm.websphere.cache.DistributedMap interface, specifically) but I can’t figure out how to get Blue to resolve this reference.

    Can anyone help out? I’m running WAS 6.1 locally on my Windows XP box.

    Dave

    #286611 Reply

    @dmacpher wrote:

    Hi

    With RAD, the WAS runtime seemed to be part of my build path, so it could resolve, for instance, a reference to a WAS-specific interface that comes bundled with the appserver. I want to make use of the WAS DistributedMap interface and dynamic cacheing features of WAS (com.ibm.websphere.cache.DistributedMap interface, specifically) but I can’t figure out how to get Blue to resolve this reference.

    Can anyone help out? I’m running WAS 6.1 locally on my Windows XP box.

    Just bumping this in the hopes that someone has been successful doing this. Has anyone been able to resolve references to WAS com.ibm.xxxxx interfaces such as DistributedMap in ME BLue?

    #287196 Reply

    I have a similar problem. I use RasHelper extensively during startup. Currently, I have to include the WAS .jar containing this class in my build path (or suffer reported errors in the proejct), and when I do that, the automated build includes said .jar, at 33MB, into my .ear. Of course, it’s already on the WAS system classpath, so I don’t need it in my deployment package.

    I finally solved the problem by:

    1. Add the WAS JRE as an “installed JRE”
    2. Within that JRE definition, you can define a library path. The default is the contents of {WAS install root}/java/jre/lib. I added com.ibm.jaxws.thinclient_6.1.0.jar from the “runtimes” directory in the WAS install (that, by the way, includes DistributedMap)
    3. In project properties/build path, add the WAS JRE system library (and drop the default library, whatever it is).

    #287230 Reply

    Riyad Kalla
    Member

    jandrews,
    Excellent solution to the problem, thank you for taking the time to post it. I am adding it to the FAQ with full credits.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Access to WAS specific feature – DistributedMap

This topic is marked as closed to new replies, however your posting capabilities still allow you to do so.

You must be logged in to post in the forum log in