[JBoss Seam] - Re: Seam cannot find component
by norman.richardsï¼ jboss.com
seam.properties does need to be at the root of the JAR file. I'm not an eclipse user, so I'm not really sure. I believe Seam 1.1 will allow you to not use seam.properties if you have a META-INF/components.xml, but for now you'll need your seam.properties in the right place.
To verify that Seam is finding your classes, you'll need to look at your server log when you deploy the application. You should see a message like this one that indicates seam is canning your JAR for components.
| 14:05:01,891 INFO [Scanner] scanning: /Users/orb/proj/jboss/jboss-4.0/build/output/jboss-4.0.5.GA-ejb3/server/default/tmp/deploy/tmp41693jboss-seam-pay.ear-contents/jboss-seam-pay.jar
You should also see component registration messages for your components. They will look like this:
14:05:02,503 INFO [Component] Component: paymentHome, scope: CONVERSATION, type: JAVA_BEAN, class: org.jboss.seam.example.seampay.PaymentController
If you aren't seeing those, you have packaging problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986312#3986312
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986312
19Â years, 7Â months
[JBoss Portal] - Re: JBoss Portal Stress Results (Repost)
by walbar
Hi,
I've performed the test on the new version from the trunk. I get:
With the CMS Portlet: 15 p/s
Without the CMS Portlet: 31p/s
Yesterday I was trying to find out where in your code there were the SQL queries logued by hibernate. I was suspecting that they were the bottleneck but the source code is quite big and I had not much success. Anyway I see you have worked on it and now only the cache is hit without actually reaching the DB.
I guess that another possible bottleneck are the JTA transactions that are continuously being opened and closed. I would like to try to remove them in order to perform more tests, would you point me to the config or code file where this could be done (if possible)?. I wouldn't mind to lack some functionality during the tests.
Regards,
Waldemar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986142#3986142
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986142
19Â years, 7Â months
[JBoss Eclipse IDE (users)] - NullPointerException JBoss Eclipse IDE 2.0
by chw
Hey folks,
I just installed Eclipse 3.2.1" and "JBoss Eclipse IDE 2.0". If I try to start an JBoss-Server (3.2) out of Eclipse I get a bunch of NullPointerExcpetions (see below). Can anybody help me with that? Greetings and thanks Chris
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.server.runtime.AbstractServerRuntimeDelegate.addDirectory(AbstractServerRuntimeDelegate.java:199)
at org.jboss.ide.eclipse.as.core.server.runtime.AbstractServerRuntimeDelegate.getRuntimeClasspath(AbstractServerRuntimeDelegate.java:146)
at org.jboss.ide.eclipse.as.core.server.JBossLaunchConfigurationDelegate.setupLaunchConfiguration(JBossLaunchConfigurationDelegate.java:227)
at org.jboss.ide.eclipse.as.core.server.JBossLaunchConfigurationDelegate.setupLaunchConfiguration(JBossLaunchConfigurationDelegate.java:94)
at org.jboss.ide.eclipse.as.core.client.TwiddleLauncher.createTwiddleLaunch(TwiddleLauncher.java:112)
at org.jboss.ide.eclipse.as.core.client.TwiddleLauncher.launchTwiddles(TwiddleLauncher.java:83)
at org.jboss.ide.eclipse.as.core.client.TwiddleLauncher.getTwiddleResults(TwiddleLauncher.java:150)
at org.jboss.ide.eclipse.as.core.client.TwiddleLauncher.getTwiddleResults(TwiddleLauncher.java:141)
at org.jboss.ide.eclipse.as.core.server.ServerStateChecker.getTwiddleResults(ServerStateChecker.java:284)
at org.jboss.ide.eclipse.as.core.server.ServerStateChecker.run(ServerStateChecker.java:107)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986304#3986304
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986304
19Â years, 7Â months
[JBoss Portal] - Re: JBoss Portal Stress Results
by julienï¼ jboss.com
removing JTA will not give you an extra performance boost as during the commit phase, every datasource (actually only the PortalDS) will say nothing has been changed and the TM will optmize. So the overhead is very minimal.
Yesterday I improved the way that portal objects and instances are looked up. They are lookup up by natural id, which has a significant cost in hibernate (and it should not). I have added a cache of natural-id to PK which eliminates the hibernate Query object in my profiler hotspot. It's in 2.4.1 branch and 2.6 trunk.
My advice : you should consider to implement PortalObjectContainer and InstanceContainer as read-only in-memory store (well just maps of maps). That will give a significant performance boost at the cost of no flexibility (since it's immutable.
"walbar" wrote : Anyway we don't need JTA in production since most of our portlets' logic would be read-only. We would use JTA during Staging, and in that phase we are not interested in performance yet.
|
| So, I'm still interested in knowing where I could remove JTA transactions. Would you help me?
|
| Thanks a lot,
|
| Waldemar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986303#3986303
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986303
19Â years, 7Â months