pbaker01 wrote :
| btw - did you have any thoughts regarding the MDB binding issue and the
start/stopDelivery problem posted above? I would love to resolve this...
|
|
Honestly, i did not pay much attention to that thread. I saw the same thread in
multiple forum and someone had
btw - this previous posting was using JBoss 5.0.0. We would be happy to use
either version 4.2.3 or 5.0.0 as long as we can get the start/stopDeliver
methods exposed.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198276#4198276
Reply to the post :
Hi jaikiran,
Let me know if I can post any additional information.
Using the incorrect descriptor files below I get the following display from
JMX for jboss.j2ee.
When I select the first entry (message-driven-bean MDB), I get a display
with start/stopDelivery methods exposed.
This image
Okay, i now see what you are trying to do. I need some time to understand what
has changed and if it was intentional or if it just another configuration issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198280#4198280
Reply to the post :
Just going through the various issues that you reported in JBoss-5.0 GA. One of
them was :
anonymous wrote : Caused by: org.jboss.xb.binding.JBossXBException: Failed to
parse source: Element {http://www.jboss.
| com/xml/ns/javaee}jboss is not bound as a global element.
| at
Hi Jaikiran,
Thanks for that. I have added that tread to my watch list.
What about JBoss 4.2.3 and start/stopDelivery. Any ideas?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198318#4198318
Reply to the post :
anonymous wrote : Caused by: org.jboss.xb.binding.JBossXBException: Failed to
parse source: Element {http://java.sun.c
| om/xml/ns/javaee}jboss is not bound as a global element.
|
You have an incorrect xsd declaration in jboss.xml. Change it to:
| jboss
Hi,
Using the correct XSD corrected the problem. No more console errors!!!
The JBoss JNDI setting are like:
+- SsimEjbBean (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy74 implements interface
com.sita.wab.ejb.ssim.SsimEjbLocal,interface
Note: w.r.t. the above post, xsd only works with JBoss 4.2.3. I get a number
of errors when running JBoss 5.0.0 GA.
For the above question regarding binding... Assume JBoss 4.2.3
I start a new thread for the jboss.xml issue.
View the original post :
pbaker01 wrote : Note: w.r.t. the above post, xsd only works with JBoss
4.2.3. I get a number of errors when running JBoss 5.0.0 GA.
|
|
There should not be any errors with JBoss-5.0.0 GA too. Can you post more
details along with exception stacktrace, if available?
View the original
session
| ejb-nameAirlineEjb/ejb-name
| configuration-nameStandard Stateless
SessionBean/configuration-name
| jndi-nameAirlineEjb/jndi-name
| /session
Instead of the jndi-name, try the mapped-name instead. And please
I have a sneaking suspicion that jndi-name support is lacking.
Jaikiran, mind opening a JIRA w/ some simple integration test for it? I should
look when I'm back next week.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197835#4197835
Reply to the
ALRubinger wrote :
|
| Jaikiran, mind opening a JIRA w/ some simple integration test for it?
I could reproduce this issue. Created
https://jira.jboss.org/jira/browse/EJBTHREE-1649 with a testcase attached.
jaikiran wrote :
| Instead of the jndi-name, try the mapped-name instead. And
PB,
I reread the entire thread again:
anonymous wrote : During the initial development we did not use ejb-jar.xml or
jboss.xml config files. When the beans were deplyed the system created several
entries in the Global JNDI.
|
| We have now created jBoss.xml and ejb-jar files and now the
Hi Jaikiran,
Thanks so much for looking in to this!!!
I have changed both ejb-jar.xml and jboss.xml to use Version 3.0 xsds. See
below.
A number of errors are now generated in the console start-up.
What I am really after, at this point in development, is exposing the
start/stopDelivery
btw: JBoss 5.0.0 GA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197750#4197750
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4197750
___
jboss-user mailing list
One more thing Using the ejb-jar.xml and jboss.xml descriptor files has
solved the MDB problem wrt start/stopDelivery issue raised in:
http://www.jboss.com/index.html?module=bbop=viewtopict=147390
But this missing JNDI entries causes several new problems.
Also, when I change the version
17 matches
Mail list logo
