Looks to be the fault of the trigger. Had some wild variation of sql. Sorry
for the claim.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947033#3947033
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947033
---
I have a Customer table with a relationship to an EyeColorCode table. The
eyeColorCode is maintained on inserts and updates through Sql Server triggers.
Both triggers do basically the same check.
Inserts behave as expected but updates aren't working.
However, if I remove the tU_Customer, the
Looks to be fixed at least I hope. The packaging needs to be broken down for
specific functions and these functions must be self contained. The cross
reference between the two ejb.jar files was mixing up the sfsb ejb reference.
View the original post :
http://www.jboss.com/index.html?module
Hi,
I have a stateful session bean which holds references to various ejb's and
performs queries against them. When I deploy the app several times one set of
ejb's stop working. The only way to get them to work again, randomly, is to
change the problem ejb's, so as, I guess, to give them a dif
Hi,
Is it possible to deploy an app without the archive being exploded?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927559#3927559
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927559
i know you guys are tired of the classloading woes, but, here's another one
which i'm sure it's just because i'm missing something.
began using hibernate3 with jboss4.0.2...
using the default settings for isolated classloading
created a hibernate.cfg.xml because i'm still not quite sure how to
Here's the story:
I have a Session bean which acts upon two different databases.
The session bean first updates db1 through an entity bean.
The session then calls upon a different SLSB which in turn updates
db2 through another entity bean.
However, do to some db constraints, the update to db2 c
thanks.
i just got it to work. and by the looks of it the structure really pays off.
402 rocks. the jsp initial deployment rules for testing.
thanks again
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881821#3881821
Reply to the post :
http://www.jboss.
now i'm really lost.
i have a web.war and an ejb.jar packaged in an ear. everything had been
working great until the switch to the latest class loaders.
i've been struggling with ClassCastException's and NoClassDefFoundError ever
since.
I understand that if there are two different classes fou
So, I've been patiently working through this and am getting closer to solving
the class loading issues, but, still have a few quirks to work out.
I have read the JBossClassLoadingUseCases and found
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration to be very
useful.
Based on t
Try adding transaction-control to the beans using Supports.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881628#3881628
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881628
-
I hope this doesn't come back to haunt me later, but, this article explains how
to get the classloading back to what it was doing in 4.0.1sp1:
http://jira.jboss.com/jira/browse/JBAS-1691
Could someone help me understand the difference between the two classloaders?
Why would one be favored over
Hey there,
The pattern works great and with a little modification you can get it to handle
your page display as well.
I started out using stateful session beans as well, but, found that they were
creating some Connection errors. I couldn't figure it out so I ended up
changing it back to HttpS
There's additional information in the server log after startup about MBeans
being the root cause:
=ERROR [main] (org.jboss.deployment.scanner.URLDeploymentScanner:527) -
Incomplete Deployment listing:
|
| --- Incompletely deployed packages ---
| [EMAIL PROTECTED] {
url=file:/C:/jboss-4.0
I recently upgraded to jboss-4.0.2 unsucessfully. The problem appears to be
during the context initialization.
| =DEBUG [main] (com.systemadmin.util.ContextListener:51) -
contextInitialized(ServletContextEvent() called!)
| =DEBUG [main] (com.systemadmin.util.ContextListener:58) - enterin
Hi all,
I get the same error trying to recreate a Stateful Session EJBObject from a
cached handle.
To re-read the object I use the following:
byte[] bytes = new String(id).getBytes();
java.io.ByteArrayInputStream io = new java.io.ByteArrayInputStream(bytes);
java.io.ObjectInputStream os =
16 matches
Mail list logo
