• Post Reply Bookmark Topic Watch Topic
  • New Topic

deploytool - won't update files + whats JBoss like ?

 
Mikey Warren
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I've successfully written and deployed a couple of very simple session beans and a client, using the deploytool (1.3.1) that comes with Suns reference J2EE.
However when I make changes to the beans, and try to update the application from the deploytool I get the "nothing to update" message. I also get "the following files were not found on the disk" box showing the ear file and its contents. I've clicked on "edit the search paths" but these include the directory that I've put everything in as the search root.
... so I'm stuck. Any ideas ?
I could try getting v1.4, but the I'm using Sun's tutorial, and also SAM's "J2EE in 21 days" book which both use 1.3(.1? I think) - so I don't want to add complications of having a different version.
Also following various difficulties I've had, I'm thinking of trying JBoss for experimenting around with EJBs, and just using Sun's J2EE server for following the tutorials I've mentioned - although I don't want to have to learn too many things at once - is JBoss suitable for learning with, or am I better off sticking with Sun's J2EE reference implementation?
I like the idea of using something thats more likely to be used in the work place, rather than wasting time figuring how to use Sun's deploytool.
Any advice appreciated.
thanks Mike
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Now that you've got a handle on the deployment process (i.e. building JARs, writing deployment descriptors, etc) I'd take a look at JBoss. Sun's J2EE RI is great for getting to grips with these things, but you'll be amazed at what JBoss can do, and the speed at which it allows you to do it. For example, deployment simply involves copying a JAR/WAR/EAR file into a "deploy" directory.
Simon
 
Mikey Warren
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Simon,
I've now got the basic template example working for JBoss (had a couple of problems which I've covered in a post in the JBoss forum), and also managed to write and deploy a noddy bean of my own. The skies the limit ! , well perhaps Entity Beans are my limit at the moment.
Its good to feel that I'm actually working on a 'proper' J2EE app. server - I think I'd recommend it to others, although be prepared for a bit of time to learn about ant and XDoclet,(both usefull tools) as well as JBoss.
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's a completely different environment isn't it? I'm still learning about XDoclet myself but once set up in your build environment, writing EJBs is just so straightforward.
If you are considering getting the JBoss documentation ($30?) then I would recommend it - particularly if you can get your company to pay for it. There's some good stuff in there, especially when you start playing with clustering.
Glad to hear that you're having fun though.
Simon
 
jorge zapata
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JBoss is AWESOME!!!
 
Thomas Taeger
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by jorge zapata:
JBoss is AWESOME!!!

Hi Jorge,
some arguments would be fine.
Thomas.
 
Thomas Taeger
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mikey Warren:
... using the deploytool (1.3.1) that comes with Suns reference J2EE.
... I get the "nothing to update" message.

Hi Mikey,
besides all the hype for changing to JBoss, many people like
you and me start with J2EE Reference Implementation server.
I had exactly the same problem, it was a bug of Suns deploytool.
But it has been fixed in a later version in 1.3.x, not 1.4 only.
In my j2sdkee1.3.1 environment (NT4.0, SP5) it works today.
Thomas.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!