[JBoss Seam] - Re: A few issues.
by pete.muirï¼ jboss.org
"tzman" wrote : My apologies if these issues have already been fixed/mentioned.
|
| 1.) org.jboss.seam.mock.BaseSeamTest
http://jira.jboss.com/jira/browse/JBSEAM-1791
anonymous wrote :
| 2.) org.jboss.seam.framework.Identifier
|
| The equals method checks for an instance of the derived type org.jboss.seam.framework.EntityIdentifier
Please raise a JIRA issue for this.
anonymous wrote : 3.) It doesn't appear as though we can use injection in base classes. Am I mistaken? Is this a design decision?
| We have gotten around this by retrieving the components programatically, i.e. Component.getInstance( "entityManager" );
|
| This means that for testing I have to load the container, when I only need hibernate; or I have to do a check in by base class before retrieving the component to ensure the application context is active
I don't know what you mean by a base class. But Seam injection only occurs in classes annotated @Name.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073552#4073552
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073552
18Â years, 11Â months
[Installation, Configuration & DEPLOYMENT] - Not possible to deploy a Schedulable Implementation in an .e
by kyuss
Hi,
i'm trying to deploy an Implementation of the Schedulable-Interface in an .ear-file which contains my whole application. I've added the following lines to the scheduler-service.xml file:
| <mbean code="org.jboss.varia.scheduler.Scheduler"
| name=":service=Scheduler">
| <attribute name="StartAtStartup">true</attribute>
| <attribute name="SchedulableClass">com.offix.middleware.scheduler.CacheCleaner</attribute>
| <attribute name="InitialStartDate">1/1/07 0:00 p</attribute>
| <attribute name="SchedulePeriod">1800000</attribute>
| <attribute name="InitialRepetitions">-1</attribute>
| </mbean>
|
On jboss start, i get a ClassNotFoundException for my implementation-class, because the Scheduler-MBean starts, before the .ear gets deployed. This causes the Scheduler not to start at all.
Unfortunately, it's necessary to deploy the Schedulable-implementation with the application, cause we're using some variables, which are defined in there(i.e. JBossCache-parameters).
I've seen that there is a flag "startOnStartup", but how can i invoke the startSchedule operation of the mbean? It would be very convenient to do that automatically after the deployment of the .ear and not have to invoke the operation by hand, everytime we reboot the jboss. Is that possible?
Thanks in advance,
alex
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073550#4073550
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073550
18Â years, 11Â months
[EJB 3.0] - Re: need help for Transaction Attribute Types
by grdzeli_kaci
"ALRubinger" wrote : Looks like you'd just like an Extended Persistence Context, so that your EM isn't flushed to the DB automatically at JTA Commit.
|
| http://docs.jboss.org/ejb3/app-server/tutorial/extended_pc/extended.html
|
| S,
| ALR
Great Thanks for your posts,
i did what you say but problems is not resolved, my example now looks like :
| @Stateful
| @Remote(TestFasade.class)
| public class TestFasadeBean implements TestFasade {
|
| @PersistenceContext(type = PersistenceContextType.EXTENDED)
| EntityManager oracleManager;
|
| Test test;
|
| public Long create() {
| try {
| System.out.println("start persist");
| test = new Test();
| test.setAge(21L);
| test.setName("adsdasd");
| test.setSurname("asdasd");
| oracleManager.persist(test);
| System.out.println("end persist");
| Long ret = test.getId();
| return ret;
| } catch (Exception e) {
| e.printStackTrace();
| return 0L;
| }
| }
| public void comit() {
| try {
| System.out.println("start comit");
| oracleManager.flush();
| System.out.println("start end");
| } catch (Exception e) {
| e.printStackTrace();
| }
| }
| }
|
and after call create method information is flushed into database :( did i something incorrect ?
or maybe i have some bad versions of enviroment :
AS : JBoss AS 4.2.1.GA with ejb 3 included
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073548#4073548
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073548
18Â years, 11Â months