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: vickyk <do-...@jb...> - 2006-06-29 04:35:27
|
Please check the doStart() of the ServerImpl , here it goes http://fisheye.jboss.com/viewrep/JBoss/jboss-system/src/main/org/jboss/system/server/ServerImpl.java?r=1.69 Regards Vicky View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954233#3954233 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954233 |
|
From: <mcu...@jb...> - 2006-06-28 23:53:56
|
Well.. after some discussion on the dev list (starting to sound like an echo chamber in here ...) we've come full circle and decided the original release naming convention should stick, and that "Alpha" and "Beta" release conventions be relaxed to include development milestones. (In other words everything in the original post is good) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954214#3954214 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954214 |
|
From: <bst...@jb...> - 2006-06-28 22:12:26
|
"ben...@jb..." wrote : | Brian, I have thought about this issue while designing the new mapping scheme. While the scenario that you mentioned can happen, I think it is more unlikely. The reason being that buddy replication requires "sticky session" to operate in cases like http session repl. | | If it is http session repl, then every data structure will be stored under a sessionID. In this case, my undertanding is we will gravitate everything under sessionID in one shot during failover, am I correct. Therefore, shared reference between "joe" and "mary" will still work, for example. Yes, definitely. That's why this issue was not a big priority for me for 1.4.0 -- the session replication use case works even if this issue isn't resolved. Re: walking the object graph and gravitating aggressively vs. lazy gravitation, my instinct is that walking the object graph and gravitating aggressively would be more performant. Otherwise you end up doing a bunch of single node gravitations at random points. I could be wrong though. For example, gravitation now is a 2 step process: 1) Please give me everything under Fqn x -- return is a list of NodeData objects. 2) Please remove everything you had under Fqn x, as I now own it. This is a simple call, I just pass "x". Doing it in 2 steps is important as you avoid removing the data from the old backup node until the new owner acknowledges he's received it. With a flat heap it becomed more complex: 1) Please walk an object graph starting at x and give me all nodes. 2) Please rewalk that object graph, but now delete all nodes you have. I guess that's not that different, but it is different. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954200#3954200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954200 |
|
From: <ale...@jb...> - 2006-06-28 22:03:58
|
"Scott" wrote : but the datasouce can be deployment specific so we would have to rely on startup semantics other than dependencies for this to work. I think, a datasource should always be deployed before EJBs. EJBs may need a datasource to start but datasources don't need EJBs. "Scott" wrote : The PM should have its datasource injected via a dependency such that its not really started until the datasource is available. There are cyclic dependencies: EntityContainer cannot start until its PM is started while the PM is started from the EntityContainer.startService(). PM.start() should be called before EntityContainer.startService(). Maybe, EjbModule.createService() after the loop that creates all the containers, there should be another one that starts PMs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954199#3954199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954199 |
|
From: unibrew <do-...@jb...> - 2006-06-28 21:10:34
|
Hello Yeah, I wouldn't change a thing in the idea how projects' xml descriptors are parsed now. So, we would still use ResourceWatchers and Cache to update and keep the data gained from XMLs. The only improvement is that all this data would be served through SSB or MBeans. Information about projects will be available straight from drawed from cache objects and/or from Services(localy, remotely). "adamw" wrote : I guess we have to define more precisely what we mean by a "Labs Service". Please propose some definition. What else would you like to see? :-) Thanks in advance, Rysiek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954191#3954191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954191 |
|
From: <bst...@jb...> - 2006-06-28 20:41:05
|
Just an FYI to the community about a minor JBC/JBoss AS integration issue, as well as a follow up comment to Ben re: a phone discussion we had this AM. For JBC 1.4.0.CR2, we changed the internal workings of the CachedType class (see http://jira.jboss.com/jira/browse/JBCACHE-653 for why). This led to a change in the return type of CachedType.getFields from List{Field} to List{FieldPersistentReference}. This change prevents the use of 1.4.0.CR2 in AS 4.0.4 as it leads to a CCE in the HttpSession repl code. This has been fixed in Branch_JBossCache_1_4_0, so the integration will not be an issue in 1.4.0.GA. Ben, here's what I did: 1) CachedType.getFields() makes a defensive copy of the internal fields list. When making the copy it converts from FieldPersistentReference to Field. This fixes the issue for 4.0.4. 2) The above is inefficient for internal uses of getFields() as it makes an unnecessary copy. So, I added a new method CachedType.getFieldsIterator(). This returns a trivial custom iterator that wraps the iterator over the CachedType.fields member, overriding next() to translate from the FieldPersistentReference to Field. With this change, FieldPersistentReference is no longer exposed outside of CachedType. 3) Changed the internal PojoCache uses of CachedType.getFields() to use CachedTypes.getFieldsIterator(). Please let me know when it's OK to port this to JBC HEAD. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954186#3954186 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954186 |
|
From: tfennelly <do-...@jb...> - 2006-06-28 20:27:59
|
OK, so I've put something together on this.
So the solution I implemented revolves around a standard SAX Parser implementation called X12nToSaxEventParser. As its name is supposed to suggest, it parses an X12N stream and generates a set of SAX Events which it fires at a standard SAX ContentHandler implementation. It has 2 support class:
1. X12nStreamReader: Wraps the stream and makes the X12N segments easier to access.
2. X12nModel: Contains definitions to help the parser convert the X12N stream to a stream of SAX events.
Here's a sample of its output after parsing the sample X12N stream in Dave's above post - actually it's 2 blocks of the above sample X12N, hence the 2 blocks inside the root <x12n> element.
So, this parser could be used by any XML transformation tools that support SAX based processing and transformation. I had to make a very small mod to Smooks in order to make it easier to specify specific SAX parsers for specific message types - available in the v 0.7.2-SNAPSHOT build from the downloads.
See the JUnit test code. The x12n-config.cdrl config file illustrates how to configure the X12nToSaxEventParser to parse messages originating from X12N based message producers ("x12n-requester" - "x12n-producer" might have been a better profile name). See X12nToSaxEventParserTest for the units test code for executing a parse. Excuse the fact that this test has no assertions - it just runs the parse :-) This test doesn't perform any actual XML based transformations on the XMLified X12N stream. This would probably be required in a real life situation (different transformations for different consumers) and is easy enough using the standard Smooks mechanisms (see tutorials) - once we have it in XML, we can do whatever we want!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954185#3954185
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954185
|
|
From: <mar...@jb...> - 2006-06-28 20:16:39
|
Hold off on the maven stuff just now: there are a lot more important things we need to do that could use the cycles. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954179#3954179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954179 |
|
From: tfennelly <do-...@jb...> - 2006-06-28 19:45:06
|
Sure, I'll help out wherever you guys want - adding regression tests, switching to maven, or whatever :-) If ye're on for moving over to maven ( :-) ), I'll sort it out once I get my broadband connection sorted out at home - which should be soon. It's prob least disruptive to do this on a weekend i.e. when svn traffic is low. It will require moving files around a bit so... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954174#3954174 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954174 |
|
From: <sco...@jb...> - 2006-06-28 18:24:41
|
A related discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=64876 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954164#3954164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954164 |
|
From: <mcu...@jb...> - 2006-06-28 17:45:51
|
OK, Looks like we might do some back-pedalling here ;) If we use the new eclipse versioning scheme we should allow ourselves to stick with development milestones/previews and just tag our plugins & features with timestamps. So using this scheme we would revert to our original naming scheme from 1.5, i.e.: 2.0.0.Preview 2.0.0.M1-4 2.0.0.CR1-2 2.0.0.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954154#3954154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954154 |
|
From: <ale...@jb...> - 2006-06-28 17:42:31
|
The whole issue was about a message like this: "failed to start EJB1: query in EJB2 could not be compiled". The exception is thrown from the last entity (as a service) in the module. So the causing exception is wrapped. BTW, moving pm.start() to EntityContainer.createService() won't fix the exception message but only the dependency issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954152#3954152 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954152 |
|
From: <sco...@jb...> - 2006-06-28 17:16:28
|
head and 4.0. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954143#3954143 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954143 |
|
From: <sco...@jb...> - 2006-06-28 17:15:22
|
"ale...@jb..." wrote : | I was thinking about moving persistenceManager.start() to EntityContainer.createService() right after persistenceManager.create(). At this point all plugins are created and set, not started though. | The start() of the persistenceManager will use the DataSource and possibly the TransactionManager. Is this acceptable? It depends on how fine grained we want to be with dependencies. The ejb-deployer should have a dependency on the TM (and it does), but the datasouce can be deployment specific so we would have to rely on startup semantics other than dependencies for this to work. The PM should have its datasource injected via a dependency such that its not really started until the datasource is available. Back to the original JBAS-993, can't there just be better tracking of the ejbs causing the errors rather than having to start the PM differently? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954142#3954142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954142 |
|
From: sasi2103 <do-...@jb...> - 2006-06-28 17:06:39
|
Hi all, Where can I find list with all JBoos application server that support JDK 5.0? Thanks all View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954137#3954137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954137 |
|
From: <lon...@ho...> - 2006-06-28 17:06:19
|
I am using jboss 4.0.4. I need to set up a virtual directory in a web app (it has authentication which set up in web.xml). I added the following context in server.xml under jbossweb-tomcat55.sar directory. Since each context is a web app. The following URL http://hostname/doc does not prompt for login. I don't want to add WEB-INF/web.xml under c:/doc. I am looking for a way to set up
virtual directory in the same scope of the web app so the authentication
config in web.xml will be enforced to the virtual directory too.
thanks a lot.
<Context path="/doc"
| docBase="c:/doc"
| reloadable="false">
| </Context>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954136#3954136
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954136
|
|
From: <ale...@jb...> - 2006-06-28 16:40:55
|
That's true. However, for the next release I am just gonna do what the WS guys want... In fact that may help them too. But I'll let them to decide. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954126#3954126 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954126 |
|
From: <dan...@jb...> - 2006-06-28 16:33:28
|
We actually already had it migrated to Maven (1) before I left the company... Not sure why we didn't get that in the release we got. I would like to see us using Maven as well, but right now there's no cycles for it, unless someone volunteers and does it - hint hint... Cheers! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954122#3954122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954122 |
|
From: <bil...@jb...> - 2006-06-28 16:16:09
|
the biggest performance improvement would be the ability to serialize schema models to disk so that the XML wouldn't have to be parsed for the schema. A profiling run of E-EJB3 showed that schema parsing took 10% of boottime. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954117#3954117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954117 |
|
From: <kab...@jb...> - 2006-06-28 16:08:41
|
I've tried this out on linux and I don't get why it's not working. An
$ant -verbose precompiled-tests=20
yields:
| [aopc] The ' characters around the executable and arguments are
| [aopc] not part of the command.
| [aopc] Build Successful: 4494 ms
| Property ${aop.xml} has not been set
| Property ${exclude} has not been set
| [junit] Implicitly adding /home/kkhan/jboss-head/tools/lib/junit.ja=
r:/home/kkhan/jboss-head/tools/lib/ant-launcher.jar:/home/kkhan/jboss-head/=
tools/lib/ant.jar:/home/kkhan/jboss-head/tools/lib/ant-junit.jar to CLASSPA=
TH
| [junit] Running org.jboss.test.aop.basic.AOPTester
| [junit] Executing '/usr/java/j2sdk1.4.2_05/jre/bin/java' with argum=
ents:
| [junit] '-Djboss.aop.path=3D/home/kkhan/jboss-head/aop/src/resource=
s/test/basic/jboss-aop.xml'
| [junit] ''
| [junit] '-classpath'
| [junit] '/home/kkhan/jboss-head/thirdparty/qdox/lib/qdox.jar:/home/=
kkhan/jboss-head/thirdparty/javassist/lib/javassist.jar:/home/kkhan/jboss-h=
ead/thirdparty/trove/lib/trove.jar:/home/kkhan/jboss-head/thirdparty/xdocle=
t/lib/xdoclet-xjavadoc-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/li=
b/xdoclet-xdoclet-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/=
lib/xdoclet-web-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/li=
b/xdoclet-jdo-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/=
xdoclet-jboss-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/=
xdoclet-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-java-=
module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-ejb-mo=
dule-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-bea-modu=
le-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-jmx-module=
-jb4.jar:/home/kkhan/jboss-head/tools/lib/ant.jar:/home/kkhan/jboss-head/th=
irdparty/oswego-concurrent/lib/concurrent.jar:/home/kkhan/jboss-head/thirdp=
arty/junit/lib/junit.jar:/home/kkhan/jboss-head/thirdparty/jboss/profiler/j=
vmti/lib/jboss-profiler-jvmti.jar:/home/kkhan/jboss-head/thirdparty/jboss/m=
icrocontainer/lib/jboss-container.jar:/home/kkhan/jboss-head/thirdparty/jbo=
ss/microcontainer/lib/jboss-dependency.jar:/home/kkhan/jboss-head/thirdpart=
y/jboss/microcontainer/lib/jboss-microcontainer.jar:/home/kkhan/jboss-head/=
thirdparty/jboss/common/lib/namespace.jar:/home/kkhan/jboss-head/thirdparty=
/jboss/common/lib/jboss-common.jar:/home/kkhan/jboss-head/thirdparty/jboss/=
common/lib/jboss-archive-browsing.jar:/home/kkhan/jboss-head/aop/output/lib=
/jboss-aop.jar:/home/kkhan/jboss-head/aop/output/tests.classes:/home/kkhan/=
jboss-head/aop/docs:/home/kkhan/jboss-head/tools/lib/junit.jar:/home/kkhan/=
jboss-head/tools/lib/ant-launcher.jar:/home/kkhan/jboss-head/tools/lib/ant-=
junit.jar'
| [junit] 'org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunn=
er'
| [junit] 'org.jboss.test.aop.basic.AOPTester'
| [junit] 'filtertrace=3Dtrue'
| [junit] 'haltOnError=3Dfalse'
| [junit] 'haltOnFailure=3Dfalse'
| [junit] 'formatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.S=
ummaryJUnitResultFormatter'
| [junit] 'showoutput=3Dfalse'
| [junit] 'formatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.P=
lainJUnitResultFormatter,/home/kkhan/jboss-head/aop/output/reports/TEST-org=
.jboss.test.aop.basic.AOPTester-precompiled-tests.txt'
| [junit] 'formatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.X=
MLJUnitResultFormatter,/home/kkhan/jboss-head/aop/output/reports/TEST-org.j=
boss.test.aop.basic.AOPTester-precompiled-tests.xml'
| [junit] 'propsfile=3D/home/kkhan/jboss-head/aop/junit538469726.prop=
erties'
| [junit]=20
| [junit] The ' characters around the executable and arguments are
| [junit] not part of the command.
| [junit] Exception in thread "main" java.lang.NoClassDefFoundError:=
=20
| [junit] Test org.jboss.test.aop.basic.AOPTester FAILED
| [antcall] Exiting /home/kkhan/jboss-head/aop/build.xml.
|=20
Now taking this and executing the same directly from the command line works=
:
| [kkhan@dev02 aop]$ /usr/java/j2sdk1.4.2_05/jre/bin/java -Djboss.aop.pat=
h=3D/home/kkhan/jboss-head/aop/src/resources/test/basic/jboss-aop.xml -clas=
spath /home/kkhan/jboss-head/thirdparty/qdox/lib/qdox.jar:/home/kkhan/jboss=
-head/thirdparty/javassist/lib/javassist.jar:/home/kkhan/jboss-head/thirdpa=
rty/trove/lib/trove.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdocl=
et-xjavadoc-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-x=
doclet-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet=
-web-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-j=
do-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-jbo=
ss-module-jb4.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-jb4=
.jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-java-module-jb4.=
jar:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-ejb-module-jb4.ja=
r:/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-bea-module-jb4.jar:=
/home/kkhan/jboss-head/thirdparty/xdoclet/lib/xdoclet-jmx-module-jb4.jar:/h=
ome/kkhan/jboss-head/tools/lib/ant.jar:/home/kkhan/jboss-head/thirdparty/os=
wego-concurrent/lib/concurrent.jar:/home/kkhan/jboss-head/thirdparty/junit/=
lib/junit.jar:/home/kkhan/jboss-head/thirdparty/jboss/profiler/jvmti/lib/jb=
oss-profiler-jvmti.jar:/home/kkhan/jboss-head/thirdparty/jboss/microcontain=
er/lib/jboss-container.jar:/home/kkhan/jboss-head/thirdparty/jboss/microcon=
tainer/lib/jboss-dependency.jar:/home/kkhan/jboss-head/thirdparty/jboss/mic=
rocontainer/lib/jboss-microcontainer.jar:/home/kkhan/jboss-head/thirdparty/=
jboss/common/lib/namespace.jar:/home/kkhan/jboss-head/thirdparty/jboss/comm=
on/lib/jboss-common.jar:/home/kkhan/jboss-head/thirdparty/jboss/common/lib/=
jboss-archive-browsing.jar:/home/kkhan/jboss-head/aop/output/lib/jboss-aop.=
jar:/home/kkhan/jboss-head/aop/output/tests.classes:/home/kkhan/jboss-head/=
aop/docs:/home/kkhan/jboss-head/tools/lib/junit.jar:/home/kkhan/jboss-head/=
tools/lib/ant-launcher.jar:/home/kkhan/jboss-head/tools/lib/ant-junit.jar o=
rg.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner org.jboss.test.=
aop.basic.AOPTester filtertrace=3Dtrue haltOnError=3Dfalse haltOnFailure=3D=
false formatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.SummaryJUnit=
ResultFormatter showoutput=3Dfalse formatter=3Dorg.apache.tools.ant.taskde=
fs.optional.junit.PlainJUnitResultFormatter,/home/kkhan/jboss-head/aop/outp=
ut/reports/TEST-org.jboss.test.aop.basic.AOPTester-precompiled-tests.txt fo=
rmatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormat=
ter,/home/kkhan/jboss-head/aop/output/reports/TEST-org.jboss.test.aop.basic=
.AOPTester-precompiled-testsasnaknsknasnak.xml =
Tests run: 20, Failures: 0, Errors: 0, Time elapsed: 1.=
721 sec
|=20
View the original post : http://www.jboss.com/index.html?module=3Dbb&op=3Dv=
iewtopic&p=3D3954113#3954113
Reply to the post : http://www.jboss.com/index.html?module=3Dbb&op=3Dpostin=
g&mode=3Dreply&p=3D3954113
|
|
From: <ale...@jb...> - 2006-06-28 16:07:48
|
Probably, you are right. But before going that way let's make sure we are not leaving behind more critical performance issues that should be addressed first. Why don't we come up with a series of most common use-cases (probably, you already have them), run the tests and identify the bottlenecks and their severity? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954112#3954112 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954112 |
|
From: adamw <do-...@jb...> - 2006-06-28 16:05:38
|
Hello, of course we can access the data with SLSBs or anything else, what I meant (and wanted to achieve using the @Service annotation) is to have the XMLs and all other data parsed in the background (and only parsed when a descriptor changes) - like it is now using the cache. Of course, it's achievable with the SLSBs method too :). I guess we have to define more precisely what we mean by a "Labs Service". -- Cheers, Adam View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954111#3954111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954111 |
|
From: <hei...@jb...> - 2006-06-28 15:30:15
|
Previously (using XercesXSMarshaller) the reflection wrapper have been cached in the MappinObjectModelProvider. This could eagerly be populated and reused throughout several Marshaller invocations. Especially the WS usecases did benefit from this, because otherwise the same classes would have been introspected over and over again. When optimizing XB regarding the use of the reflection API, wouldn't it makes sense to extend the API that the callee could actually provide that mapping model, similar to what has been possible with the MappinObjectModelProvider? IMO usecases that work on the same object model /schema would greatly benefit in terms of performance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954087#3954087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954087 |
|
From: <ale...@jb...> - 2006-06-28 15:27:28
|
Right, I confused it with Branch_4_0_3_SP1 again. Containers are started in the same way, i.e. in the EjbModule.startService by invoking serviceController.start(con.getJmxName()). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954086#3954086 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954086 |
|
From: jc7442 <do-...@jb...> - 2006-06-28 15:18:04
|
Hi, I try to evaluate if JRunit can be usefull to test EJB3 based applications. For some unit test I use JBoss embedded EJB3. For integration test or load tests I'd like to use JBoss application server (wich is the targeted server). I have a look to the documentation. it uses a socket based server. With JBoss AS I also have to wait for starting tests that all components are deployed. Where can I find some examples and feedbacks about how to write server class to start the application server and client testcase ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954082#3954082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954082 |