This is for JBoss EJB 3 integration code, so we can use JBoss interfaces, not
just EJB standard interfaces.
Inside an interceptor instance, I need access to the ejbName of the EJB being
intercepted (so I can use this as a unique key to look up other info on the
EJB). Currently I am doing this
I would also expect that MC will implement JSR-330 natively?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4246065#4246065
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4246065
Whilst the 299 spec requires that we provide 299 style injection into an Java
EE component, I would propose that we also provide it for MC aware bean (MC
beans, MBeans etc.). I would also like to support an 299 MCBean type of Bean
for JBoss, so that any MCBean can be injected into your 299
epbernard wrote : If WB does check for @Entities and orm.xml it also needs to
read the right META-INF/persistence.xml or a representation of it because:
| - classes might not be scanned
| - some non annotated class can be explicitly listed
I would have to do a generic solution here I
I mean, is there some code I can take :-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224051#4224051
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4224051
___
jboss-user
I agree with Carlo, whilst for the narrow scope of making WB spec compliant, I
only need @Entity/orm.xml (i.e. spec'd entities) it would be much more user
friendly to also extend this to provider specific entities (case in point is
hbm.xml).
If necessary for EE6/AS6 we can do a simple impl:
*
Another integration issue for Web Beans/JSR299 - this time around JPA.
The JSR299 spec says that any entities (either specified using @Entity or
orm.xml) should not be simple beans (i.e. have injection/interception
facilities). As per the other integrations with the container, I would like to
I would prefer to wait until there is a release, so that we can update the EJB3
impl in JBoss to the correct version using the plugin updater.
Thanks :-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4218088#4218088
Reply to the post :
This works well - thanks Carlo for pointing out the obvious :-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4218032#4218032
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4218032
I added
http://anonsvn.jboss.org/repos/webbeans/ri/trunk/spi/src/main/java/org/jboss/webbeans/ejb/api/EjbReference.java
which also adds the create() method for instantiating the EJB. This also
includes Ken's recomendation of using the reference to obtain the correct proxy
which implements the
BTW https://jira.jboss.org/jira/browse/WBINT-7
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4218034#4218034
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4218034
___
jboss-user
ALRubinger wrote : I'll implement remove() for us. It'll be dependent upon
the new EJB3 release (due out this week).
I thought so. We're starting to have other deps on newer revs of JBoss AS (bug
in Javassist proxies) so we'll bounce our minimum up to JBoss AS 5.1.0.CR1 once
it's out.
Sorry guys, I was being super confusing here ;-)
First of all, I'm working on the Web Beans interceptor not Seam.
Second, I was just representing the way we add the interceptor as XML, actually
we add it programatically in a deployer by manipulating the metadata:
public class
I talked to ALR about this a bit, here is a precis:
Andrew Rubinger wrote : So maybe you can explain a couple things then I'll
weigh in? This needs to be in a portable way
The standard WB requirement - that WB must operate on other AS than JBoss - we
can't have JBoss code in WB itself - if we
Ok, by default default interceptors are invoked in the order they are defined
in ejb-jar.xml, and before any class level interceptors. I guess we just go
with inserting our interceptor at the top of chain for now. We can also check
the order the user defines, and WARN if ours isn't first I
Hmm, this won't work, as I need this to be serializable. So, I guess we need
some serializable identifier for a session bean instance. Perhaps we change to
an EjbResolver for getting instances of SFSB that can return something like:
interface EJBInstanceT {
|
|Serializable getId();
|
wolfc wrote : What's the problem you're trying to resolve? If it's
'configuration errors', then adding complexity to relieve that is not an option.
That we perform JSR-299 injection and interceptor binding into an EJB using a
default interceptor. This should be called before any user
wolfc wrote : Why doesn't the @PreDestroy on the SeamInterceptor work?
It probably does, I hadn't thought of this. I'll check it out.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4216252#4216252
Reply to the post :
I guess again it comes down to needing a way to uniquely identify an SFSB
instance. I guess I can squirrel away the reference to the actual bean obtained
from @PostConstruct and pass that through? Would that be good way to identify
it from the EJB3.0
View the original post :
I need to have a callback from the EJB container when an EJB is removed for
some reason. The JSR-299 spec requires us to ignore any EJBs that have been
removed, so I need to mark an instance ignored.
https://jira.jboss.org/jira/browse/WBRI-165
Again, not sure of the best API for this, so open
ALRubinger wrote : Just for SFSB I'd imagine?
Oops, yes :-)
anonymous wrote : Our standard M.O. applies I guess; make some SPI to register
a callback listener in wb-as-int and we'll invoke upon it via some EJB3
optional add-on component.
|
| What contextual information do you need?
N.B. This is effectively the inverse of
http://www.jboss.org/index.html?module=bbop=viewtopict=151896, where, rather
than wanting to be notified that an EJB was removed by someone other than Web
Beans, we want to request an EJB be removed.
View the original post :
For the purposes of JSR-299, the specified @Remove method of removing instances
isn't sufficient (as we have no way to supply the parameters or know which
method to call if there are multiple). Therefore, JSR-299 specifies that we
should ask the container to remove the EJB instance in a
Given
ejb-jar xmlns=http://java.sun.com/xml/ns/javaee;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd;
| version=3.0
|
|
wolfc wrote : The underlying problem is that we don't have a (JTA) data
source deployer in E-EJB3.
|
| jta-profile needs to move down the food chain. jpa-profile needs to be
created and we need a simple jca-profile for the above. Then ejb3-embedded
should be based on profile3_1 and your
I'd like to start a discussion on this.
First, we'll need an EEJB release that contains these MC beans:
* PersistenceUnitDependencyResolver
* EjbReferenceResolver
and the second issue to address is that to run the EJB discovery, we need to
set the deployment unit in use onto the discovery
I'm attempting to port the Web Beans EJB integration to the EJB3.1 embedded
container. I've identified two potential issues:
1) Do the org.jboss.ejb3.EjbReferenceResolver and the
PersistenceUnitDependencyResolver beans exist in embedded EJB3.1?
2) How can I get hold of the deployment unit and
It's my understanding from the spec that it should, however the JNDI lookup
fails. A lookup for java:/TransactionManager succeeds, so I suspect it's not a
problem with my environment.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201446#4201446
Reply to the
I have a field/method annotated @PersistenceContext (not on an EJB) that I need
to inject. I have full access to the field/method (declared type, annotation),
and need a way to get the correct persistence unit from JBoss EJB3. This could
be directly (return the correct object) or a JNDI
Also, I have full access to MC at this point, so what I'm doing for @EJB
injection is to lookup the EjbReferenceResolver MC bean and use it to get the
JNDI name for the injection point.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200151#4200151
Reply to
https://jira.jboss.org/jira/browse/EJBTHREE-1611
I went ahead and committed these changes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4194555#4194555
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4194555
Another problem with the build - if I include the artifact using:
dependency
|groupIdorg.jboss.ejb3/groupId
|artifactIdjboss-ejb3-embedded/artifactId
|scopetest/scope
| /dependency
Then I get a problem resolving some artifacts:
Downloading:
32 matches
Mail list logo
