Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Sun ONE Application Server 7 Deployment instruction for Advisor Example in Chapter 1

 
John Liang
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Okay, here we go, I finally got that working. However, I still don't know how to get a generated Stub-jar.
Any ways, for those that would like to play around with Sun ONE Application Server 7: Here we go:
0) Follow all the steps in HF EJB, so that you know your app is definitely working!!! You have the AdviceApp.ear from the RI.
1) unjar it

From now on you need one new Deployment Descriptor (DD) [sun-ejb-jar.xml] and modify an existing one [application.xml]
2) We need to have a new Sun ONE server-specific deployment descriptor:
Name: sun-ejb-jar.xml
Location: in the same directory as the normal DD ejb-jar.xml (META-INF)
Here:

3) We need to make sure that application.xml
Name: application.xml
Location: directory under META-INF in the ear file [application.xml] (META-INF)
Here:

4) Deploy it using the Administration Tool in the Browser. Default:
http://localhost:4848
However, I still don't know how to generate those Client stub. Well, I guess, stay tuned or may be somebody has an answer soon.
Thanks,
John
[ November 23, 2003: Message edited by: John Liang ]
 
Ron Havelock
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
go to the app deployed directory...you will see it. For windows, the default would be:
C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-apps
 
John Liang
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
Thanks, that's great help. I have found it, but:

javax.naming.CommunicationException: Can't find SerialContextProvider
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.jav
a:63)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120
)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at AdviceClient.go(AdviceClient.java:16)
at AdviceClient.main(AdviceClient.java:9)

So ... ... any idea? I have checked out the javasoft site, they said that's a problem with JDK ...
Thanks in advance,
John
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic