Sorry, EJB3_RC9_Patch_1_EJBTHREE1-1191
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133325#4133325
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133325
___
jboss-user maili
SVN tag is EJB3_RC9_Patch_1_EJBTHREE1-1091
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133324#4133324
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133324
___
jboss-user m
The problem is that the final version of the EJB3 API is dependent on Java 5
constructs. For example, javax.ejb.SessionContext.getBusinessObject() returns a
Generic. So we cannot compile some client classes using JDK1.4. The earlier
versions of the specification were not dependent on Java 5 cons
I've just checked in a fix for EJBTHREE-975 into Branch_4_2. The changes are
being reviewed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063144#4063144
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063144
_
Here is what looks like the latest problem - you can't load
src.FirstSessionBean. Do you have this class/bean loaded/deployed?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060681#4060681
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
Can you look at the whole log file and see what the original exception is? The
exception you posted indicates a problem with the EJB3 config, but if the SLSB
deploys on it's own, there must be another problem. What does your entity bean
and persistence.xml look like?
View the original post :
h
No, you should not have to modify that file unless you want to change the
default bean configuration or create a custom config. Are there any exceptions
when you start the app server?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060659#4060659
Reply to the
Make sure you have ejb3-interceptors-aop.xml in the deploy directory - that is
where the "Stateless Bean" container or domain configuration is defined.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060652#4060652
Reply to the post :
http://www.jboss.com/ind
Are there any benchmarks for JBossMessaging? Looking for comparisons to other
JMS providers.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056678#4056678
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056678
_
Are you running on an IBM machine? I've seen this exact problem before and it
was due to a bad IBM driver.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042230#4042230
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=404
Either annotation implementation is supported - you can annotate either the
interface or the bean.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036099#4036099
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036099
___
There aren't any known issues with @EJB injection in 4.0.5 w/EJB3 RC9 Patch 1.
Please post an example.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036095#4036095
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=403609
Interceptors are only triggered if the call goes through the ejb container. If
you make a call from within a bean to another of the bean's methods, it's a
simple java invocation - the call does not go through the container and is not
intercepted.
View the original post :
http://www.jboss.com/
That's correct - per the spec, SFSBs are not pooled. To manage the memory
footprint, SFSBs are passivated. SLSBs are pooled.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035421#4035421
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=postin
Make sure jboss-aop-jdk50-client.jar is in the client classpath
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035415#4035415
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035415
___
Stateful Session Beans are not pooled. If you need to control the number of
instances, I suggest that you either put a Stateless Session Bean in front of
the SFSB and limit the pool size of the SLSB to 2. Or you could limit the
number of threads that can access the SFSB, but this will limit acce
What is the local interface for SessionBeanB? I'm guessing you are injecting
into a field of the bean tye not the interface type (i.e. SessionBeanBLocal not
SessionBeanB). Are you seeing anything in the logs at deployment time?
The default JNDI bindings for an EJB3 are ejbName/remote and ejbNam
If you add the interceptor as a default for all beans of a certain type by
modifying ejb3-interceptors-aop.xml, then you need the interceptor class to be
globally loadable by all ejb3s (in server/XXX/lib as you did or in the
deployers/ejb3.deployer directory).
Can you paste the changes you have
JNDI bindings are not defined by the EJB specification. We use the bean name
prefixed by the deployment and suffixed by the type of interface.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035125#4035125
Reply to the post :
http://www.jboss.com/index.html?m
The default jndi bindings have probably changed
The default JNDI bindgs for an EJB3 are ejbName/remote and ejbName/local for
the remote and local business interfaces. If the EJB3 is deployed in an .ear,
the default jndi bindings are earName/ejbName/remote and earName/ejbName/local.
You can over
Entity beans are really a different animal in EJB3 - they're just pojos. There
is no container.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034793#4034793
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034793
__
See http://jira.jboss.com/jira/browse/EJBTHREE-825
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034748#4034748
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034748
___
jbos
What line is CountFasadeBean.update(CountFasadeBean.java:45)?? Is the injection
failing?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034730#4034730
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034730
_
XMBean support was added in 4.2.0.CR1
(http://jira.jboss.com/jira/browse/EJBTHREE-689).
There is now an xmbean parameter on @Service.
I have not explicitly tested XMBean persistence.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034247#4034247
Reply to th
Make sure you have jboss-ejb3x.jar in your classpath.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034150#4034150
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034150
___
j
4.0.5 is only compatible with EJB3 RC9 Patch 1. Our initial release of the
4.0.5 installer with the EJB3 option had problems. We then released a
corrected, non-installer version of EJB3 and shortly thereafter a corrected
installer version.
So if you want to run 4.0.5 with EJB3, you need to make
If you look at JNDIView from the jmx-console, you will be able to see the
interfaces that the Proxy implements. EJB3 Proxies implement the remote or
local business interfaces, so the bean bound to AddressFacade.RemoteJNDIName
must have AddressFacadeRemote as a remote business interface.
View th
You may want to deploy NamingAlias services that map a remote jndi binding to a
local binding - then your client code is always looking up local jndi bindings.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=NamingAliasMBean
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
Looks like you have the wrong classes in your client's classpath - you have a
different version running on the server vs the client.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033734#4033734
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
The default JNDI bindgs for an EJB3 are ejbName/remote and ejbName/local for
the remote and local business interfaces. If the EJB3 is deployed in an .ear,
the default jndi bindings are earName/ejbName/remote and earName/ejbName/local.
You can override the default with the @RemoteBinding and @Loc
Always a best practice to use jndi references.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033239#4033239
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033239
___
jboss-us
The only way I can think of is to examine the jmx jboss.j2ee domain to search
for deployments. Each bean will have an "ear=XXX" parameter. Take a look at the
jmx-console.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033211#4033211
Reply to the post :
http
How did you install 4.0.5? There is an installer option that will install 4.0.5
with ejb3 or clustered-ejb3. If you are installing ejb3 onto a pre-existing,
non-ejb3 4.0.5, download EJB3 RC9 Patch 1 from
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=132063
Follow the in
The default JNDI bindings for an EJB3 are ejbName/remote and ejbName/local for
the remote and local business interfaces. If the EJB3 is deployed in an .ear,
the default jndi bindings are earName/ejbName/remote and earName/ejbName/local.
You can override the default with the @RemoteBinding and @L
Yes, it's certainly possible. EJB3 supports home interfaces so they can
gradually replace EJB2.1 beans and continue to interact with EJB2.x style
beans. Take a look at the EJB3 reference21_30 tutorial that is distributed with
EJB3.
View the original post :
http://www.jboss.com/index.html?modul
|
|
|
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983946#3983946
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983946
___
Try this instead:
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983945#3983945
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983945
___
jboss-
The build script and source are in the docs/tutorial/stateless subdirectory of
the EJB3 RCX installation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972736#3972736
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972
4.0.4, 4.0.5, 5.0, 9.2, everything - just ask Burke. He might have backmerged
to 3.2 :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972018#3972018
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972018
_
JCA seems more like a pain in the ass that anything else. Why do we have to
learn this new technology?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961802#3961802
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961802
If you specify a home interface using either the @RemoteHome/@LocalHome
annotations or with the or elements in ejb-jar.xml, EJB3s will
behave as 2.x EJBs. Everytime you lookup an instance in the JNDI context, you
will acquire a new instance of an EJB - the jndi lookup behavior is identical
to
MsgConsumerBean is being deployed as a Stateless Session Bean because of the
@Stateless annotation. Remove the @Stateless annotation and you should be ok.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957127#3957127
Reply to the post :
http://www.jboss.com/
42 matches
Mail list logo