Thanks! I appreciate you answer.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940232#3940232
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940232
---
Using Tomcat
Hello,
I'm wondering if JBoss supports EJB 2.1 timers (javax.ejb.TimerService...), and
if so, since which version. I know of other timer implamentations that JBoss
has (TimerService) but do not look the one J2EE spec but JBoss specific.
Thanks you for you help
grt.
View the original post :
Update: my bad, with commit option 'A' this is solved. My previous attempt
wasn't good and I was running still on the default 'B'.
GRT
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870692#3870692
Reply to the post :
http://www.jboss.org/index.html?module=b
Dear Adrian,
Do not let the words 'Chief' and 'Scientist' cloud your judgement. It is not by
posts like this that EJB has a bad reputation. It is by poor documentation
cumbersome configuration and contradictory advice in the forums.
Having done a good deal of searches on these forums, read wikis
Looks like JBoss will read for every column (propery of the entity bean) if the
entity is not part of a transaction. With the read-only element, the entity
doesn't participate on the transaciton.
GRT
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870461#3870
I am having pretty much the same problem. I even changed the commit option to
'A' and it didn't make any difference.
Seems to me that as long as the DB record is not involved in a transaction,
JBoss will go a make a read for every columnd (property). The commit option
doens't make any difference
Gogu, I believe that the throwing of RemoteException is part of the J2EE specs
on web services, therefore it has to stay there.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867287#3867287
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
I have to agree that this is quite an issue. We have to apologize to our
customers using C# clients becuase they have not to hack their code to force
HTTP 1.0 instead of 1.1.
JBoss web services should support HTTP 1.1.
GRT
View the original post :
http://www.jboss.org/index.html?module=bb&op=v
Hello,
Is it posible to have many session beans, but one singe web service that
exposes some methods of these beans? I need a single wsld generated. Otherwise,
I get the same types described in multiple wsdl which complicates a lot the
client side.
Thanks!
View the original post :
http://w
Right now, stick to Jboss.net .
Hope it helps.
GoldRimTang
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863763#3863763
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=postin
I just updated from 3.2.3 to 3.2.6 and had the same problem. I found the
jboss-net.jar fixed and everything worked well. I am surprised that they
released 3.2.6 with this bug, even though it was reported in the RC2.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic
Thank you Frank. I'm running on 1.4.2 so might as well go for JBoss 4 and
disable the services I won't be using.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860109#3860109
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply
anyone? please? :)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860062#3860062
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860062
---
SF email is sponsored by -
Hello,
We have been running our app on 3.2.3 for like a year without problems. Now
we have decided to upgrade. I wonder if we should go to 3.2.6 or jump to 4.0.1.
We are not interested in AOP, Hibernate or Clustering. Caching could be
good, but we are not having any performance issues a
14 matches
Mail list logo