If I want to deploy Annotation based service ("@Service" rather than using
META-INF/jboss-service.xml", I have to name the extension .ejb3 for it to
deploy and work. It seems like if I name it .sar it never looks for @Service
annotated classes.
Now I need to deploy a service archieve which is supposed to configure client
and EJB 3.0 application security (using META-INF/jboss-service.xml). I need
access to "EJB" Session bean within this service module. When deploying as SAR,
the annotations @SessionContext and @EJB does not seem to work, whereas when I
deploy as ".ejb3", then META-INF/jboss-service.xml is not read. What solution
do you guys recommend.
1. If you can point me in the right direction/documentation, etc anything will
help.
2. Is there some documentation that I can get from JBoss that can explain this.
There are quite a fe details in 4.0.3 JBoss admin guide which seems to be out
of sync in several sections related to Services.
3. What is JBoss's direction/roadmap for EJB 3.0 support and JBoss extensions
for EJB 3.0. I read somewhere that the ".par", ".har", ".ejb3" extensions will
be deprecated. Where can I find more information.
N.B.: I have registered for JBoss Advanced traning in NYC this coming 6th.
regards
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919390#3919390
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919390
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
