Menu
▾
▴
jboss-dev-forums — The jboss development forum posts
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
| 2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
| 2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
| 2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
| 2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
| 2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
| 2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
| 2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
| 2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
| 2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: mikezzz <nu...@jb...> - 2005-05-21 07:28:00
|
Patch applied. As for a POP listener chain, I think that SMTP is the only place that has a chain, although Andy recently decoupled the listener chain stuff such that it could be placed elsewhere. My preference would be to add a chain on the LocalDeliveryMBD (will require code change). Andy is the Mail Listener expert, hopefully he can offer a comment. Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878641#3878641 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878641 |
|
From: beyarecords <nu...@jb...> - 2005-05-21 01:19:08
|
Shawn, many thanks. beya View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878633#3878633 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878633 |
|
From: <cle...@jb...> - 2005-05-20 23:18:19
|
If you are using it inside JBoss, you could use the MBean instead.
I don't know if they have changed anything into JDK 1.5 for MacOS, but you could call Profiler JNI methods directly.
Take a look at <jboss-profiler-source-dir>/native/tests/Test1.java
| import java.text.SimpleDateFormat;
|
| public class Test1 {
| public static void rootCalling() {
| subMethod();
| }
|
| public static void subMethod() {
| System.out.println(new String("test"));
| subMethodCreate();
| }
|
| public static void subMethodCreate() {
| for (int i=0;i<100;i++) {
| SimpleDateFormat x = new SimpleDateFormat();
| System.out.println("IO Usage " + x.format(new java.util.Date()));
| }
| }
|
| public static void main(String arg[]) {
| org.jboss.profiler.threadcheck.StartupProfilerCheck.startProfiler();
| Test1 x = new Test1();
| for (int i=0;i<10;i++) {
| System.out.println("i = " + i);
| x.rootCalling();
| }
| org.jboss.profiler.threadcheck.StartupProfilerCheck.stopProfiler();
| System.out.println("End! (If profiler doesn't being terminate soon, wait few seconds and finish by using control-break/del");
| }
| }
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878632#3878632
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878632
|
|
From: gavinc <nu...@jb...> - 2005-05-20 23:02:49
|
We are using the MyFaces portlet bridge for our JSF based portlet and have been seeing some strange behaviour regarding HTTP sessions. I have added some debugging around the sessionCreated() and sessionDestroyed() methods to see what is happening. It seems that when the server starts sometimes the portlet has a "hidden" session i.e. I don't see any "session created" message. If the portlet is left idle for a short time this "hidden" session times out. The strange thing is the timeout is only a few minutes but we have the session timeout set to 30 minutes in our web.xml. I have also witnessed a couple of "session destroyed" messages from sessions that i don't see created!!? Does the portal create any sessions during startup that we are mistakenly getting assigned or could the MyFaces portal bridge be creating these "hidden" sessions? Anyone have any ideas what may be going on? By the way, if I run the application outside of JBoss/Portal i.e. in Tomcat, I see the session behaviour I would expect. Cheers, Gav View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878629#3878629 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878629 |
|
From: jboss05 <nu...@jb...> - 2005-05-20 22:51:28
|
Hi,
I was able to successfully run JBoss profiler on JDK 1.4.2 on OS X. But when i migrated to JDK 1.5, when i send the kill -3 signal, i'm getting the following dump. Could someone please let me know why i'm getting this dump?
Thanks for any input in advance!
Full thread dump Java HotSpot(TM) Client VM (1.5.0_02-36 mixed mode, sharing):
"DestroyJavaVM" prio=5 tid=0x00512be0 nid=0x1804600 waiting on condition [0x00000000..0xf0800210]
"Timer-0" daemon prio=5 tid=0x00523680 nid=0x1b2f600 in Object.wait() [0xf1091000..0xf1091ad0]
at java.lang.Object.wait(Native Method)
- waiting on <0x1c43a1f0> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0x1c43a1f0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"Thread-6" prio=5 tid=0x005221a0 nid=0x1ad2800 runnable [0xf0f8e000..0xf0f8fad0]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at oracle.net.ns.Packet.receive(Unknown Source)
at oracle.net.ns.DataPacket.receive(Unknown Source)
at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
at oracle.net.ns.NetInputStream.read(Unknown Source)
at oracle.net.ns.NetInputStream.read(Unknown Source)
at oracle.net.ns.NetInputStream.read(Unknown Source)
at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:375)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1894)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1094)
- locked <0x1c424b00> (a oracle.jdbc.ttc7.TTC7Protocol)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2132)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2015)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2877)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:608)
- locked <0x1a608f28> (a oracle.jdbc.driver.OracleCallableStatement)
- locked <0x1c424b78> (a oracle.jdbc.driver.OracleConnection)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:684)
- locked <0x1a608f28> (a oracle.jdbc.driver.OracleCallableStatement)
- locked <0x1c424b78> (a oracle.jdbc.driver.OracleConnection)
at com.apple.ist.espresso.monitor.EspressoEventMonitor.run(EspressoEventMonitor.java:251)
at java.lang.Thread.run(Thread.java:613)
"HManager" prio=5 tid=0x00520130 nid=0x1a7f800 in Object.wait() [0xf0f0e000..0xf0f0ead0]
at java.lang.Object.wait(Native Method)
- waiting on <0x1c3cf6e0> (a com.apple.ist.ruby.util.Queue)
at java.lang.Object.wait(Object.java:474)
at com.apple.ist.ruby.util.Queue.getNode(Queue.java:161)
- locked <0x1c3cf6e0> (a com.apple.ist.ruby.util.Queue)
at com.apple.ist.ruby.server.HandlerManager.run(HandlerManager.java:311)
"Listener" prio=5 tid=0x0051a370 nid=0x1a11200 runnable [0xf0e0c000..0xf0e0cad0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x1c3cef90> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at com.apple.ist.ruby.server.Connector.run(Connector.java:142)
"Admin" prio=5 tid=0x00519e20 nid=0x1a5b000 runnable [0xf0d8b000..0xf0d8bad0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x1c3cf098> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at com.apple.ist.ruby.server.Controller.run(Controller.java:160)
"Thread-0" daemon prio=5 tid=0x00517ae0 nid=0x19d1c00 waiting on condition [0xf0d0a000..0xf0d0aad0]
at java.lang.Thread.sleep(Native Method)
at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
"BAMPublisher-Thread-1" daemon prio=1 tid=0x005177e0 nid=0x1a18400 in Object.wait() [0xf0c89000..0xf0c89ad0]
at java.lang.Object.wait(Native Method)
- waiting on <0x1c380448> (a com.apple.ist.bam.util.BAMQueue)
at java.lang.Object.wait(Object.java:474)
at com.apple.ist.diagnostic.bam.BAMPublisher.run(BAMPublisher.java:122)
- locked <0x1c380448> (a com.apple.ist.bam.util.BAMQueue)
"Low Memory Detector" daemon prio=5 tid=0x0050ac00 nid=0x181fc00 runnable [0x00000000..0x00000000]
"CompilerThread0" daemon prio=10 tid=0x0050a1a0 nid=0x181da00 waiting on condition [0x00000000..0xf0b06378]
"Signal Dispatcher" daemon prio=10 tid=0x00509db0 nid=0x1818e00 waiting on condition [0x00000000..0x00000000]
"Finalizer" daemon prio=8 tid=0x005095c0 nid=0x1810400 in Object.wait() [0xf0a04000..0xf0a04ad0]
at java.lang.Object.wait(Native Method)
- waiting on <0x1c20ef50> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x1c20ef50> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x005091f0 nid=0x180f400 in Object.wait() [0xf0983000..0xf0983ad0]
at java.lang.Object.wait(Native Method)
- waiting on <0x1c20efd0> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x1c20efd0> (a java.lang.ref.Reference$Lock)
"VM Thread" prio=10 tid=0x00508a70 nid=0x1803c00 runnable
"VM Periodic Task Thread" prio=10 tid=0x0050c3a0 nid=0x1821600 waiting on condition
"Exception Catcher Thread" prio=10 tid=0x00501760 nid=0x1805600 runnable
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878628#3878628
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878628
|
|
From: gavinc <nu...@jb...> - 2005-05-20 22:46:38
|
Hi Stan, Sorry it's taken a while but I have added the issues and feature request to JIRA, the keys are as follows: 248 - Initialising twice error 249 - Re-deployment error 250 - Feature request for error page config option Cheers, Gav View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878626#3878626 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878626 |
|
From: garbett <nu...@jb...> - 2005-05-20 21:43:06
|
There are two other issues bouncing around about Hibernate3. The configuration as currently packaged ends up with two different copies of the Hibernate jar files. Delete one, and put the other in in the common lib directory. The other issue is more complicated and involves the fact the Hibernate opens the session with no auto flush. One has to flush explicitly. I'll reply in full tomorrow. Shawn View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878622#3878622 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878622 |
|
From: <ad...@jb...> - 2005-05-20 21:36:35
|
Thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878621#3878621 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878621 |
|
From: <ad...@jb...> - 2005-05-20 21:36:06
|
It can also be used to support other models, e.g. where Bill is dragging his heels deploying AOP metadata as BeanMetaData and instead using the POJO MC as a ServiceLocator. By removing the BeanMetaData requirement, this pattern can be more easily incorported without the cruft of wrapping things in BeanMetaData just to get the dependencies to work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878620#3878620 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878620 |
|
From: <ad...@jb...> - 2005-05-20 21:32:47
|
This has one major advantage in terms of backwards compatiblity. Which is that it will work equally as well with the current JMX kernel ServiceContext, where the ServiceContext can provide callbacks that just do what the ServiceCreator/Configurator/Controller do now. In other words, running older JMX code with new POJO code won't require complicated JMX introductions/AOP proxies that Bill is reluctant to support. The JMX introduction will of course still be required to actually manage POJOs, but it would mean I can make a start on the JBoss5 integration without waiting for it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878619#3878619 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878619 |
|
From: <ad...@jb...> - 2005-05-20 21:28:50
|
In more concrete terms, the Controller should have a
ControllerContext install(MetaData)
The MetaData gives a stateless callback for the lifecycle actions that are
currently hardwired towards BeanMetaData at the moment
| public interface ControllerAction
| {
| void install(ControllerState state, ControllerContext context) throws Throwable;
| void uninstall(ControllerState state, ControllerContext context);
| }
|
The BeanMetaData would just provide a callback that are the actions that
are currently in AbstractController.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878617#3878617
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878617
|
|
From: <ad...@jb...> - 2005-05-20 21:25:07
|
I've been looking at tidying up the dependency model used by the Microcontainer 1) So that is easier to follow (e.g. currently you have to look at both the metadata and dependency item to see how it works) 2) To make it more pluggable What I've actually been thinking about is that the dependency state machine should not by itself be tied to the bean model (BeanMetaData). The reason it is, was to follow the model used by the JMX microcontainer with translation MBean -> javabean Instead, the way I think it should it work is that the Controller should just allow an install of any MetaData object with the MetaData object interpreting what the lifecycle operations means. The only real requirement from the Controller is that the MetaData can "self describe" at which state dependencies are required, that those dependencies can be uniquely identified and that the "Instantiate" action gives a reference to some object. It is not even a requirement that the object go into the KernelRegistry. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878615#3878615 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878615 |
|
From: <ani...@jb...> - 2005-05-20 21:17:58
|
There will be additional attributes/elements within each of the 4 major elements - JavaToWSDL, JavaToXSD,..... I do not need feedback about those. :-) I am interested in knowing whether you think the above block is intuitive to users, when backed with good documentation in the JBossWS Tools document?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878614#3878614 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878614 |
|
From: wobbet <nu...@jb...> - 2005-05-20 20:59:06
|
How do I get jASEN into a POP listener chain? Right now the chain definition that is in jboss-service.xml is for the SMTP chain. That's nice in that whenever I send out a message it has a X-SpamScore header that other people can read but it doesn't help me evaluate if incoming mail is spam or not... Thanks! rjsjr View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878612#3878612 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878612 |
|
From: <ani...@jb...> - 2005-05-20 20:57:45
|
http://jira.jboss.com/jira/browse/JBWS-110 There are 4 tasks that can be done via jbossws, command line tool for JBossWS tools - JavaToWSDL, JavaToXSD, WSDLToJava and XSDToJava. I am thinking of the following structure for JavaToWSDL task in the configuration file. Similar elements can be created for the other tasks. | <!--This is the config file used by jbossws--> | <configuration> | <javatowsdl> | <service name="SomeService" | interface="org.jboss.myinterfaces.mySEI" | packagename="org.jboss.test" | wsdlstyle="rpc" | wsdldest="output/resources/tools/config"/> | <namespaces targetns="http://org.jboss/types" | typens="http://org.jboss/types" /> | <mapping directory="output/resources/tools/config" | filename="jaxrpc-mapping.xml" /> | </javatowsdl> | </configuration> | Please provide feedback. One thing I have decided is that there will be no command line options passed to jbossws. Everything that is needed is via this xml file. Do you think creating a Schema file for the configuration file is necessary? No surprise! A single xml configuration file can have multiple elements from the 4 tasks I mentioned above AND jbossws will generate the artifacts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878611#3878611 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878611 |
|
From: wobbet <nu...@jb...> - 2005-05-20 20:48:11
|
Is there a way to add and configure users other than editing the jboss-service.xml file? rjsjr View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878610#3878610 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878610 |
|
From: <sco...@jb...> - 2005-05-20 19:49:34
|
I would like to see a full release build working before cutting over to the sink or swim strategy ;) Bang on a standalone remoting, aop and small jbossas release to better flush out some of the current thirdparty/versioning/release usecases before taking the plunge. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878607#3878607 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878607 |
|
From: <ad...@jb...> - 2005-05-20 19:32:34
|
"sco...@jb..." wrote : That certainly should be part of the jbossbuild project tests to validate the implementation, but I don't see that it allows project developers to interact easily with the usecase driven design we are asking for. Yes, but that process is stuck in a deadlock where people request features without actually trying it. The continuous addition of new/changed features means it is not in a state where it is finished or being used. I'd be prepared to cutover jboss-head to the new build so that people can try it (leaving a deprecated-build.xml in place for people who need to get work done) But only, because this is likely to move things forward in terms of feedback and stabilization. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878605#3878605 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878605 |
|
From: <sco...@jb...> - 2005-05-20 19:06:41
|
That certainly should be part of the jbossbuild project tests to validate the implementation, but I don't see that it allows project developers to interact easily with the usecase driven design we are asking for. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878601#3878601 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878601 |
|
From: beyarecords <nu...@jb...> - 2005-05-20 19:05:37
|
Shawn, on a slightly different note, I saw an earlier post of yours where you changed the hbm.xml files DTD from 2 to 3. Can you please tell me how your hibernate.har and jboss-hibernate.deplayer is setup as I can't get my hibernate.har to deploy at all. I have changed all mapping files and class files to reflect the changes required for hibernate3 to work, but whe it comes to starting Jboss hibernate.har doesn't deploy at all. Any ideas? many thanks beya View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878600#3878600 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878600 |
|
From: garbett <nu...@jb...> - 2005-05-20 18:59:21
|
When writing an EJB that uses Hibernate I wrote the following:
| ...
| public class SomeEJB implements SomeEJBLocal, SomeEJBRemote
| {
| private static final String jndiName="java:hibernate/TestSessionFactory";
|
| public void doSomeHibernate()
| {
| Session session = HibernateContext.getSession(jndiName);
| ...
|
I cringe at the thought that if naming ever changed one would have to update all of these strings referenced. One could put the strings in a properties file, or a single file class in that project. If it's mispelled it also doesn't get checked at compile time. The code of EJB usage looks so much neater:
| InitialContext ctx = new InitialContext();
| SomeEJB service=(SomeEJB)ctx.lookup(SomeEJB.class.getName());
|
Is there someway to do something like this for Hibernate in JBoss so that it's a compile time check?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878599#3878599
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878599
|
|
From: garbett <nu...@jb...> - 2005-05-20 18:41:21
|
I posted my install/configuration script that gets JBoss 4.0.2 and Hibernate 3.0 up and running at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=64209 Also be sure to look at org.jboss.hibernate.session.HibernateContext and it's usage. There are some differences. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878597#3878597 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878597 |
|
From: <ad...@jb...> - 2005-05-20 17:28:35
|
I was thinking more of writing a regression testsuite for the new build. This could be based on a local cvs repository and binary repository inside the testsuite's output folder. The tests could be based on one of the oldest forms of regression tests where you start with an initial config and apply diffs/commands in steps/stages comparing the result with the expected output after each stage. test1/initial test1/step1/patch (the diffs) test1/step1/commands(ant build invocations) test1/step1/expected etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878583#3878583 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878583 |
|
From: <ben...@jb...> - 2005-05-20 17:16:51
|
Come to think of your singleton service, I don't understand how will that work though? If I need to upgrade, should I deploy to that specific farm directory? BTW, Adrian has a good thread on the farm service http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876152#3876152 for the future implementation on the new Pojo Server. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878582#3878582 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878582 |
|
From: <sco...@jb...> - 2005-05-20 17:14:36
|
Agreed. We need a real project to prototype the requirements and the interaction of components in both source and binary form, as well as getting to the release aspect of the build system. Matching artifacts on the legacy build was an ok start, but its not really getting us where we need to be. I would like to see the jbossas component used for this purpose. We can prototype this to point of building a release of the microkernel, ejb3, tomcat + dependencies to flesh out usecases and implementation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878580#3878580 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878580 |
1965 messages has been excluded from this view by a project administrator.
