I think I figured it out.
For the problem:
A bean has a method with an output "foo 1"
I load the client and the call to that bean's method returns "foo 1"
Then I go into the bean and change "foo 1" to "bar 34"
I redeploy the bean.
Reload the client and the call to the method returns "foo 1", b
hmmm interesting. touch -a filename.jar or something else? I'm with the
'verycool' guy on the subject.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854525#3854525
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply
it acts more or less like hot deployment is not on. Hopefully that's a better
explanation.
I only use 'caching' as an adjitive...I don't mean that's exactly what's goin'
on :)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854519#3854519
Reply to the post
I'm sorry if I wasn't clear...
I don't want it to cache anything right now. This is just our development
server so quick little "let's see if this bean works now" deployments are all
we are after. I would like it to 'refresh' after I deploy a new EJB.
View the original post :
http://www.jbos
Hi,
Question for all of ya'll smart people roaming the forums.
Two days ago, our server needed to be shut down but all was well. JBoss worked
flawlessly. But, after the shutdown, a few little quirks emerged for some odd
reason. The biggest and foremost is the hot deploy. When I put a newer
Hi,
Been browsing for a nice idea of what we need for hardware to run our EJB's through
JBoss and couldn't really find anything, so I'll just ask.
The goal is to give JBoss its own server that would connect to a PostgreSQL database
server and allow a web server to connect to the JBoss server. W
Just giving this a bump after almost a week. Any one out there with any ideas?
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848323#3848323
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848323
Hi, been searching around and never could find the answer to this. Is it better to
have a whole bunch of little EJB's with only 1 or 2 methods or a couple of large EJB's
with many methods? We're wondering performance wise, and ease of maintenance.
The goal of the application is to write most/all
