I found the problem. It is in the configuration of JCA actually for MS SQL2000
driver.
The file mssql-ds.xml from the examples should have the following element set.
| connection-property name=SelectMethodcursor/connection-property
|
MS has a support article on this.
I have the same problem. Did anybody found a solution or root cause?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857937#3857937
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857937
I'm observing some strange behaviour with JBossMQ when JMS persistance is
configured to use MS SQL 2000 data source.
Looks like org.jboss.mq.pm.jdbc2.PersistenceManager creates its tables just
fine but org.jboss.mq.sm.jdbc.JDBCStateManager creates only JMS_USERS table. No
errors on creation of
Forgot to mention that data source is not an XA.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857802#3857802
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857802
---
Yes, but if there are bugs in the jaws you guys won't do anything about them
since it is not supported anymore :) ... well I guess we'll have to live with
it somehow.
Last question, right now jaws is still a part of JBoss 4.0.0, I mean it is in a
xx/lib/jboss.jar, will it be removed in release
[EMAIL PROTECTED] wrote : CMP1.1 is supported by JBossCMP engine. There is no
need to have two CMP engines for CMP1.1. So JAWS is removed.
|
First thig I found with new CMP engine that it doesn't handle correctly old
(jaws style) finders, e.g.
| finder
|
Can someone from JBoss team confirm (or not) that versio 4.x will drop support
of CMP 1.x via jaws?
It is working in 4.0.0 RC1 but there are a lot of rumors (even here) that jaws
won't (isn't) officially supported going forward in 4.x.
View the original post :
Is there any good documents for this? For example how to migrate jaws.xml to
jbosscp-jdbc.xml?
Especially what to do with elements?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857366#3857366
Reply to the post :
fbiaggi wrote : Not official,
| but on JBoss 4.0.0 all the jaws related classes are not here.
They still there at least in RC1, but as I could see from the prev. post they
will be removed...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857367#3857367
Dependencies that one can specify in jboss.xml didn't work (at least for me).
I was trying to make those like this
jboss.j2ee:jndiName=MyBeanName,service=EJB
To make the given EJB depend on one MyBean
The fix is rather trivial and I'm not sure if I should put it on sourceforge.net.
It's one
I have a servlet that launches, in its init() method, a bunch of threads (some
schedulers and background tasks).
When such a thread tries to lookup DataSource name via JNDI it fails with
NameNotFoundException but servlet itself can access DataSource just fine.
I think this points to the fact
please ignore this post, it was just missing java:/ in the thread's lookup code...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3844978#3844978
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3844978
Unfortunately this is not an option for me since I have to manage dependencies inside
one ear among multiple ejb jar files.
I had to modify JBoss code to make it work for me...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3844861#3844861
Reply to the post :
This question had been asked many time#1099; here (directly or indirectly) but so far
no answer was given.
So I've decided to try again.
Is there a way to specify an order in which EJB modules will be deployed?
Apparently JBoss (unlike WebSphere for example) ignores an order in which EJB
I'm migrating our application from WebSphere to JBoss 3.2.5.
During this migration I faced rather anoying problem.
Or EAR file has a lot of EJB jar files and many of them
reference each other via Class-Path entry in manifest.mf file.
manifest.mf for EJB X looks like this (excerpt):
Class-Path:
15 matches
Mail list logo