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: <ale...@jb...> - 2005-04-29 12:29:45
|
Commenting on Scott's examples of binding info in XSD. This is my next step. I started to look into this this morning. First, I would like to address jaxb:class, jaxb:property, etc. Using actually jaxb namespace and as it is defined in the latest jaxb2.0 edr. And later (when needed), bindings in external file. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875901#3875901 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875901 |
From: <ale...@jb...> - 2005-04-29 12:25:06
|
"ad...@jb..." wrote : I suggested that these mappings be put in the xsd files themselves using | some kind of "processing instruction"??? | | But I think you rejected that idea! I have always being talking about bindings in XSD in the form of annotations. Processing instructions in XML are also an option. But XSD annotations are prefferable were possible. Also, I agree with Scott about the current namespace binding in his reply to you. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875900#3875900 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875900 |
From: <ale...@jb...> - 2005-04-29 12:20:35
|
"ad...@jb..." wrote : When I discussed this with Scott (on the pojoserver thread) | we decided we wanted to go down the road of allowing ANY inside the metadata. | | There is an xml test for this in the testsuite, but I don't see it getting tested? | http://cvs.sourceforge.net/viewcvs.py/jboss/jbosstest/src/resources/xml/pojoserver/test1-ejb-deployment.xml?rev=1.1&view=auto Right, I haven't looked at it yet. "ad...@jb..." wrote : What we are really looking for is the ability to provide some kind of registry or | self bootstrap of | schema public id -> SchemaBinding Yes, I know. There are just too many things to work on here. Before looking at "the ability to provide some kind of registry", I would like to have "good enough" binding working for at least one schema (this includes verious customizations). Once we have it, I think, some-kind-of-registry (or even runtime binding instead) should not be a big problem. However, if this is a priority right now, let me know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875899#3875899 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875899 |
From: rajdeep_dua <nu...@jb...> - 2005-04-29 10:56:40
|
Patch submitted in JIRA. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875887#3875887 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875887 |
From: rajdeep_dua <nu...@jb...> - 2005-04-29 08:29:34
|
Please see the issue # JBMESSAGING-56 in JIRA i have uploaded the clients to replicate the bug. Also uploaded windows batch files for running the clients View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875869#3875869 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875869 |
From: <rya...@jb...> - 2005-04-29 00:06:51
|
"tom...@jb..." wrote : The only problem I see with this, is there is no way that I know of to create another source element for this (because both would live under src/tests/ directory, both would have to be named 'tests'). For performance tests, you could add a seperate target which calls Junit directly. It would need JBBUILD-71 implemented to be able reference the classspath and other things you'll need. It is something we need in general, but will help with this particular case. anonymous wrote : Using the show target for the runtests.test, didn't work for me: Sorry, that should have been ant -f jbossbuild.xml show -Dshow=runtest.tests | | | | It is based on the ID of your source. target.id | | | | anonymous wrote : Am not sure how to find a solution to my particular problem of scoping the classes I want to include in test runs, but maybe a solution to the previous problem (performance vs functional tests) will present a solution to this as well. | | | | Honestly, all of this is making me wonder how much work we should put into making testing a core part of jbossbuild. I've already raised 2 JIRA issues for you to be able to run your tests, so this tells me we may need to rethink how we define tests for a project. I know aop has an extensive testsuite which seems like it would accept no generic solution. | | | | Perhaps projects should define their own test targets, at least until we get the build part of jbossbuild complete. | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875850#3875850 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875850 |
From: <ad...@jb...> - 2005-04-28 23:45:41
|
If there is agreement on the goals, I'll raise some JIRA tasks to complete this work. Also if anybody knows where Bill's feature request is located, let me know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875849#3875849 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875849 |
From: <ad...@jb...> - 2005-04-28 23:44:50
|
Commit message from jboss-head: anonymous wrote : | Make a start on factoring out the JBossTest support classes. | __There is a JIRA task for this somewhere raised by Bill, but I can't find it.__ | | These classes are at least already used in aspects which raises build circularity problems. | i.e. aspects needs testsuite which in turn needs aspects to compile | | Changes: | 1) Core JBossTest classes moved to test module where they can be used by other modules (and eventually released for others to use to run tests against JBoss - we should probably also add some skeleton tests for others to fill in when reporting bugs/problems that need reproducing) | 2) RMIAdaptor -> MBeanServerConnection | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875848#3875848 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875848 |
From: <rya...@jb...> - 2005-04-28 22:45:21
|
"ad...@jb..." wrote : Probably the most general solution is to allow any element to be added to a macro by making each type implement DynamicElement not just DynamicAttribute? | Yes, that's what I was thinking. I like the junit-elements idea. anonymous wrote : The downside is the loss of validation if you mistype and sub-element. Yes, I think is a serious flaw. I could add a in tasks.xml which would list the allowed dynamic elements to prevent silent errors such as the one above. | <dynamicElements> | <dynamicElement name="junit-element"/> | </dynamicElements> | I don't think I should add this at the targetdef/template level because a given targetdef won't necessarily know/care about all dynamic elements. http://jira.jboss.com/jira/browse/JBBUILD-70 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875847#3875847 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875847 |
From: grafpoo <nu...@jb...> - 2005-04-28 21:25:48
|
i am having trouble getting mixin functionality to work. what i am trying to do is to assign a unique ID to hibernate sessions so i can track them in a logging aspect i've created. the aspect works, but Session.toString() generates a big old verbose string that i don't really want to try to parse. so i created an interface: package foo.aop; public interface SessionIdentifier { public String getId(); } and my mixin class: package foo.aop; import java.io.UnsupportedEncodingException; import java.security.SecureRandom; import org.apache.commons.codec.binary.Base64; public class JbossSessionMixin implements SessionIdentifier { private String id; private static SecureRandom randy = new SecureRandom(); private static Base64 base64 = new Base64(); public JbossSessionMixin() { try { byte[] b = new byte[4]; randy.nextBytes(b); id = new String(base64.encode(b), "UTF-8"); } catch (UnsupportedEncodingException e) { id = "--ERROR--"; } } public String getId() { return id; } } and my jboss-aop.xml [?xml version="1.0" encoding="UTF-8"?] [aop] [introduction class="org.hibernate.impl.SessionImpl"] [mixin] [interfaces]foo.aop.SessionIdentifier[/interfaces] [class]foo.aop.JbossSessionMixin[/class] [/mixin] [/introduction] [/aop] i package this as a sarfile which contains my war file and a foo.aop, which has the the two class files above and the jboss-aop.xml - the two class files are also in a jar in the war's WEB-INF/lib when i try to deploy the sar, i get the following error: 2005-04-28 15:07:14,543 INFO [STDOUT] org.jboss.aop.instrument.TransformationException: Failed to aspectize class org.hibernate.impl.SessionImpl. Could not find class it references foo.aop.JbossSessionMixin It may not be in your classpath and you may not be getting field and constructor weaving for this class. 2005-04-28 15:07:14,543 INFO [STDOUT] at org.jboss.aop.instrument.Instrumentor.convertReferences(Instrumentor.java:543) 2005-04-28 15:07:14,543 INFO [STDOUT] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:579) just for grins, i added a jar file with the 'missing' class and interface in server/all/lib in jboss, but i still get the same error, so it doesn't seem to be a true classpath problem. if anyone can tell me what i am missing i will be very grateful. thanks. john View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875845#3875845 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875845 |
From: grafpoo <nu...@jb...> - 2005-04-28 21:20:12
|
yes, i got it working today, thanks to your help. i have a mixin problem i am going to search the archives for. if i can't find a solution, i'll be posting that as well. again, thanks. john View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875844#3875844 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875844 |
From: <ad...@jb...> - 2005-04-28 21:18:43
|
"tom...@jb..." wrote : | anonymous wrote : I've never liked the idea of passing arguments to tests this way. | | So given that my test example may not be a good example of why jvmarg is needed, I have another, more valid one. I have been working on SSL transport for remoting. This means that I'll need to be able to declare where the key store is located via a system property (i.e. -Djavax.net.ssl.keyStore=.keystore). This one is outside my control :) | | TestCase.setup() and System.setProperty() or docs/guide/security/jsse/JSSERefGuide.html#CustomizingStores For mocking something up that can be used in a testcase while still maintaining the ability for the test to be run with other tests that also want to do SSL with different trust configuration and/or checking failure conditions like expriing the certificate or removing one from the trusted chain. e.g. http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/invocation/http/interfaces/AnyhostVerifier.java?rev=1.6&view=markup View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875843#3875843 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875843 |
From: <tom...@jb...> - 2005-04-28 20:54:42
|
anonymous wrote : Yes, that's certainly a limitation. Is this an actual need at this point? If so, we could change that attribute to be an Ant patternset refid instead of the actual pattern. I really only need this to segment out the performance tests, which use the same XXXTestCase naming convention and is under the same org.jboss.test.remoting root package as the rest of the other functional remoting tests. This is because I don't always want to run the performance tests when running functional tests, as they takes a long time. I would not be opposed to just changing the package structure to be something like org.jboss.test.remoting.functional and org.jboss.test.remoting.performance so I can segment out the different tests. The only problem I see with this, is there is no way that I know of to create another source element for this (because both would live under src/tests/ directory, both would have to be named 'tests'). I could create a src/performance/ directory and put the tests there, but this does not seem appropriate. anonymous wrote : The pathElements tag is a special tag which resolves to the inputs of your source - and the jars in the Classpath of your inputs manfest. So if you have: Using the show target for the runtests.test, didn't work for me: C:\Projects\JBoss\JBossRemoting\remoting>ant -f jbossbuild.xml show -Dshow=runtests.test | Buildfile: jbossbuild.xml | | BUILD FAILED | Target `show' does not exist in this project. | | Total time: 0 seconds | C:\Projects\JBoss\JBossRemoting\remoting>ant -f release.xml show -Dshow=runtests.test | Buildfile: release.xml | | show: | | BUILD SUCCESSFUL | Total time: 0 seconds However, using ant -v shows that '..\remoting\output\classes\main' (which I would expect due to having ) and '..\remoting\output\classes\tests' is include in the JUnit classpath when running the tests. So trying to exclude certain test jars won't matter anyways. Am not sure how to find a solution to my particular problem of scoping the classes I want to include in test runs, but maybe a solution to the previous problem (performance vs functional tests) will present a solution to this as well. anonymous wrote : I've never liked the idea of passing arguments to tests this way. So given that my test example may not be a good example of why jvmarg is needed, I have another, more valid one. I have been working on SSL transport for remoting. This means that I'll need to be able to declare where the key store is located via a system property (i.e. -Djavax.net.ssl.keyStore=.keystore). This one is outside my control :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875842#3875842 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875842 |
From: <sco...@jb...> - 2005-04-28 18:10:11
|
Yes, that's what we want to do. This also helps test another compatibility issue with classes missing from client jars that has shown up from time to time due to the promiscuous use of the jboss module classes as the testuite classpath. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875827#3875827 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875827 |
From: <sco...@jb...> - 2005-04-28 18:03:57
|
Each unqiue namespace should have a binding for its associated xsd either coming from annotations in the xsd, or indirectly as an external binding instructions document referenced by the xsd. I'm pretty sure this is allowed in jaxb, but certainly can be supported by jbossxb. So I may not want to hard-code the binding instructions in the xsd: | <xs:complexType name="USAddress"> | <xs:annotation> | <xs:appinfo> | <jbossxb:binding-uri location="META-INF/jbossxb-info.xml" /> | </xs:appinfo> | </xs:annotation> | <xs:sequence>...</xs:sequence> | <xs:attribute name="country" type="xs:string"/> | </xs:complexType> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875825#3875825 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875825 |
From: <sco...@jb...> - 2005-04-28 17:58:57
|
An example of specifying binding info in the schema from the jaxb2.0 spec draft is: | <xs:complexType name="USAddress"> | <xs:annotation> | <xs:appinfo> | <jaxb:class name="MyAddress" /> | </xs:appinfo> | </xs:annotation> | <xs:sequence>...</xs:sequence> | <xs:attribute name="country" type="xs:string"/> | </xs:complexType> | The xs:annotation/xs:appinfo/jabx:class is specifying what class to use. We should be able to define similar jbossxb statements. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875824#3875824 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875824 |
From: <ad...@jb...> - 2005-04-28 17:57:20
|
"sco...@jb..." wrote : | all of the xsd to namespace mappings should be defined Do you mean this processing already exists or that it should exist? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875823#3875823 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875823 |
From: <ad...@jb...> - 2005-04-28 17:54:30
|
I've modified the SimpleCollection test to reproduce the Null problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875822#3875822 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875822 |
From: <cle...@jb...> - 2005-04-28 17:51:49
|
Ok! Just as a FYI (Let me know if you foresee any problem): I'm composing the classpath with: - build.classes = compiled classes from the testsuite - all the client libraries for a specific version - library.classpath - as some of the classes are make usage of these libraries: apache.avalon.classpath apache.commons.classpath apache.log4j.classpath apache.xerces.classpath apache.jaxme.classpath wutka.dtdparser.classpath dom4j.dom4j.classpath oswego.concurrent.classpath ibm.wsdl4j.classpath jacorb.jacorb.classpath jgroups.jgroups.classpath junit.junit.classpath junitejb.junitejb.classpath javassist.classpath sun.jaf.classpath sun.javamail.classpath sun.servlet.classpath trove.classpath gnu.regexp.classpath apache.bcel.classpath hsqldb.hsqldb.classpath hibernate2.classpath odmg.classpath cglib.classpath View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875821#3875821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875821 |
From: <sco...@jb...> - 2005-04-28 17:48:08
|
The only factory binding info you can put into the xsd schema is that for the current namespace. You can't specify the bindings for the extension points for which you don't know the schema or even the namespace. For a given hybrid document instance, all of the xsd to namespace mappings should be defined so I think the jbossxb layer should have all the info it needs to figure out the correct unmarshaller. In your example, the xsd for the urn:jboss:testejb-ns1 namespace should define this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875819#3875819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875819 |
From: <ad...@jb...> - 2005-04-28 17:19:27
|
I suggested that these mappings be put in the xsd files themselves using some kind of "processing instruction"??? But I think you rejected that idea! So I guess the alternative would be to have some registry of schemas that un/marshaller instances can use? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875817#3875817 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875817 |
From: <ad...@jb...> - 2005-04-28 17:16:54
|
Similarly, I actually want to simplify some of the urn:jboss:xml-deployer:bean configs with "use case" configs. They still produce BeanMetaDatas but the xml -> BeanMetaData is more hardwired (see the pojo server thread) | <beanfactory xmlns="urn:jboss:genericfactory" class="x.y.z"> | etc. | rather than the longwinded | <bean class="org.jboss.bean.plugins.GenericBeanFactory"> | <property name="Bean">x.y.z</property> | etc. | | or even something more simple like: | <queue xmlns="urn:jbossmq:queue" name="testQueue"/> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875816#3875816 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875816 |
From: <ad...@jb...> - 2005-04-28 17:14:33
|
When I discussed this with Scott (on the pojoserver thread) we decided we wanted to go down the road of allowing ANY inside the metadata. There is an xml test for this in the testsuite, but I don't see it getting tested? [url]http://cvs.sourceforge.net/viewcvs.py/jboss/jbosstest/src/resources/xml/pojoserver/test1-ejb-deployment.xml?rev=1.1&view=auto[url] What we are really looking for is the ability to provide some kind of registry or self bootstrap of schema public id -> SchemaBinding e.g. If I do | <?xml version="1.0" encoding="UTF-8"?> | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="urn:jboss:xml-deployer xml-deployer_1_0.xsd" | xmlns="urn:jboss:xml-deployer"> | i.e. I can shove the xml at an unmarshaller and expect it to work out that the urn:jboss:xml-deployer:deployment needs to go through org.jboss.kernel.plugins.deployment.xml.PojoSchemaBinding then when it hits | <bean name="EJBContainerConfig" class="org.jboss.ejb.Container"> | <property name="Config"> | <ejb:ejb-container xmlns="urn:jboss:testejb-ns1"> | it knows it needs to go a different mapping urn:jboss:xml-deployer:deployment -> org.jboss.ejb.metadata.EJBContainerSchemaBinding Since the number of these schema bindings is indeterminate (users could potentially write their own - certainly each JBoss module will) and "hot deployable" I don't want to hardwire these other namespaces into the pojo schemabinding. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875815#3875815 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875815 |
From: <sco...@jb...> - 2005-04-28 16:31:44
|
Posting to the mail services dev forum is not likely to help you out with this so you have been moved to the portal user forum. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875808#3875808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875808 |
From: <kab...@jb...> - 2005-04-28 15:59:12
|
Just to make sure I had a little play with the injboss example, it works when using the 'all' configuration, but not using 'default'. I'm not able to look into why right now, are you OK to use all for now? EnableTransformer is necessary if you're doing loadtime transformations. If you're precompiling you should not need to use it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875801#3875801 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875801 |