Win a copy of Succeeding with AI this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Junilu Lacar
Sheriffs:
  • Tim Cooke
  • Jeanne Boyarsky
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • fred rosenberger
  • Frits Walraven

Howard Kushner's book question

 
Ranch Hand
Posts: 247
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I actually prepare for test 287 and read howard's book.
I'm currently in the chapter J2EE container clients and something is not clear for me.
on p.417, it is stated that

typival resources definitions in client-resource.xmi are used by Websphere Application Client to resolve resource manager connection factory references for J2EE Application Client components.



Where is located this file client-resource.xmi? In my client projet, under META/INF, I just have application_client.xml and ibm-application-client-bnd.xmi.

I have well understood the following words p.417

JMS clients declaring access to JMS with resource manager connection factory references must have all references resolved locally. J2EE web components and J2EE Enterprise components have their resource manager connection factory references resolved by administering the J2EE Application Server in which they run



we don't declare the references to resource manager connection factory references the same way, depending if we deal with Application Clients or other J2EE components.

I know the second way - simply by fulling the box websphere binding in the tab reference of the Web component or EJB component - but I have no idea about the first.
Filling manually the client-resource.xmi (if one can find it...) with factories element as suggested p.417?

i would be very grateful for any assistance on this subject.
Regards,
Cyril.
[ December 15, 2004: Message edited by: cyril vidal ]
 
cyril vidal
Ranch Hand
Posts: 247
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK. Just have found a kind of solution for my problem by reading further the Howard's book, p.419:

JMS clients declaring access to JMS with resource environment references must have all references resolved using bindings to administrated components, such as those shown for EJB clients in Figures 12.7 and 12.8



So this time, used the following configuration in my application-client.xml:



and used a websphere binding also, and it works fine!!!

BUT: as the only types proposed by websphere wizard consist in Topic and Queue, you have still to edit your deployment descriptor manually.
traditionnaly, it seems we don't use resource-env-ref element to reference a JMS Queue or Topic connection factory.

Regards,
Cyril.
 
cyril vidal
Ranch Hand
Posts: 247
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
two month later, the response is simply that reource-ref declared in application clients don't work in WSAD.
You have to open the Application client resource configuration tool in <wsadhome>/runtimes/base_v5/bin and run the clientConfig.bat, then navigate to your exported ear and double click the jar of your client application.

For more details on this, please refer to the exellent red book EJB2.0 development with WSAD p.632.

Regards,
Cyril.
 
Could you hold this puppy for a sec? I need to adjust this tiny ad:
ScroogeXHTML 8.7 - RTF to HTML5 and XHTML converter
https://coderanch.com/t/730700/ScroogeXHTML-RTF-HTML-XHTML-converter
    Bookmark Topic Watch Topic
  • New Topic