• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

why not a FQ classname in method-param

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
On page 579 of Head First EJB it says:

To distinguish overloaded methods in the DD (Security in EJB) you can use the method-param tag, but to my surprise the value of "String" is used; I would expect "java.lang.String". Why don't you have to use the fully qualified classname here? What if I have my own class as paramter, e.q. com.whatever.MyClass, what do I put in the method-param tag now?

Dick
 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
testMethod(char c int a,com.whatever.MyClass mc)


specified as:

<method>
<ejb-name>TestBean</ejb-name>
<method-name>testMethod</method-name>
<method-params>
<method-param>char</method-param>
<method-param>int</method-param>
<method-param> com.whatever.MyClass </method-param>
</method-params>
</method>
----

for string part it should be fully qualified java type
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic