[JBoss-dev] [JBoss JIRA] Created: (JGRP-15) Concurrent startup of initial members without merging
Concurrent startup of initial members without merging - Key: JGRP-15 URL: http://jira.jboss.com/jira/browse/JGRP-15 Project: JGroups Type: Feature Request Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 When multiple members are started simultaneously, and no other member is running yet, they form singleton groups, and merge after some time. GOAL: elect a coordinator out of all concurrent (client-)members and avoid a merge. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-5) Conversion of Externalizable to Streamable
[ http://jira.jboss.com/jira/browse/JGRP-5?page=history ] Bela Ban updated JGRP-5: type: Feature Request (was: Task) Description: Environment: Conversion of Externalizable to Streamable -- Key: JGRP-5 URL: http://jira.jboss.com/jira/browse/JGRP-5 Project: JGroups Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 Original Estimate: 3 weeks Remaining: 3 weeks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - webservices-context-root gone again?
Somewhere inbetween 4.0.0 and 4.0.1 there was a new element webservices-context-root in jboss_4_0.dtd to specify the (web context ) root of the webservice. I think this was a good element as override of the automatic calculation. In some environements, the names of the archives are fixed to silly values or values that let the webservices context root collide with the context root of a web-app. Heiko View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860706#3860706 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860706 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: NEW BUILD
And the developer should not only be able to check out a source tree, but also be able to *update* the tree without throwing things away and re-checking out some modules. This not only saves bandwidth, but also time. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860707#3860707 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860707 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of the JBoss Web Container] - Re: Clustered Sessions
Hello dfisher, I have exactly the same problem here. Same config: 2 Jboss 3.2.6 in cluster mode (both on solaris 8) if you found a solution or a possible fix, could you put it back here in the thread please ? thanks. Logs: 2005-01-05 00:05:48,790 ERROR [org.jboss.web.tomcat.tc5.session.JBossCacheManager] processExpires: failed with exception: java.lang.NullPointe rException 2005-01-05 00:05:48,791 INFO [STDOUT] java.lang.NullPointerException then it ends with a broken pipe io exception... 2005-01-04 23:58:47,592 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Exception destroying ManagedConnection [EMAIL PROTECTED] [EMAIL PROTECTED] handles=0 lastUse=1104878177872 permit=false trackByTx=false [EMAIL PROTECTED] [EMAIL PROTECTED] org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: Io exception: Broken pipe) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:572) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:276) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.java:539) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.removeTimedOut(InternalManagedConnectionPool.java:415) at org.jboss.resource.connectionmanager.IdleRemover$1.run(IdleRemover.java:70) at java.lang.Thread.run(Thread.java:534) Caused by: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:559) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:272) ... 4 more View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860709#3860709 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860709 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=comments#action_12314520 ] paveu commented on JBAS-68: --- I am so greatful for this fix as I need to use that page. But in the same time I am very sad because instead of mdbejb.jsp file attached to this fix I found ONLY a JPG. What a pity... :((( Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Minor Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-5.0 Alpha Attachments: screenshot-1.jpg added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=comments#action_12314521 ] Dimitris Andreadis commented on JBAS-68: The new jsp code is checked in, so just get it fro m CVS or find it in the new v4.0.1 Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Minor Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-5.0 Alpha Attachments: screenshot-1.jpg added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.50 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050105034002Lbuild.50 BUILD COMPLETE-build.50Date of build:01/05/2005 03:40:02Time to build:35 minutes 53 secondsLast changed:01/05/2005 02:56:26Last log entry:Add Date editor tests Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(105)1.7modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd Date editor tests1.5modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.25modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.1.22modifiedpatriot1burketransaction/src/main/org/jboss/tm/TxManager.javarecovery1.13modifiedpatriot1burketransaction/src/main/org/jboss/tm/XidFactory.javarecovery1.36modifiedpatriot1burketransaction/src/main/org/jboss/tm/TransactionImpl.javarecovery1.1addedchussenetaspects/src/jdk15/org/jboss/aspects/patterns/readwritelock/readLockOperation.javaSupport of JDK 1.5 annotations1.1addedchussenetaspects/src/jdk15/org/jboss/aspects/patterns/readwritelock/writeLockOperation.javaSupport of JDK 1.5 annotations1.434modifiedosdchicagotestsuite/build.xmlNew target tests-scout-jaxr1.1addedosdchicagotestsuite/src/main/org/jboss/test/jaxr/scout/query/JaxrBusinessQueryTestCase.javaSet of testcases that test the Jaxr Integration with Apache Scout/Apache jUDDI and JBoss.1.1addedosdchicagotestsuite/src/main/org/jboss/test/jaxr/scout/publish/JaxrSaveOrganizationTestCase.javaSet of testcases that test the Jaxr Integration with Apache Scout/Apache jUDDI and JBoss.1.1addedosdchicagotestsuite/src/main/org/jboss/test/jaxr/scout/publish/JaxrDeleteOrganizationTestCase.javaSet of testcases that test the Jaxr Integration with Apache Scout/Apache jUDDI and JBoss.1.1addedosdchicagotestsuite/src/main/org/jboss/test/jaxr/scout/JaxrBaseTestCase.javaSet of testcases that test the Jaxr Integration with Apache Scout/Apache jUDDI and JBoss.1.2modifiedosdchicagothirdparty/apache-scout/lib/scout.jarLatest version of Scout.1.373modifiedosdchicagobuild/build.xmlJaxr Integration: Build a juddi/jboss/axis library for the client.1.100modifiedosdchicagovaria/build.xmlBring in juddi/jaxr integration.1.210modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaPass log ref to MessageListenerAdaptor to work around with jdk1.31.3modifiedosdchicagovaria/src/resources/juddi/jboss-service.xmlForget isolation of axis jars.1.1addedosdchicagovaria/src/main/org/jboss/jaxr/juddi/axis/JBossJuddiAxisHandler.javaJaxr Integration: JBoss handlers for juddi that can work with Jboss's version of axis (ie axis-ws4ee.jar)1.1addedosdchicagovaria/src/main/org/jboss/jaxr/juddi/axis/JBossJuddiAxisProcessor.javaJaxr Integration: JBoss handlers for juddi that can work with Jboss's version of axis (ie axis-ws4ee.jar)1.1addedosdchicagovaria/src/main/org/jboss/jaxr/juddi/axis/JBossJuddiAxisTransport.javaJaxr Integration: JBoss handlers for juddi that can work with Jboss's version of axis (ie axis-ws4ee.jar)1.22modifiedtdieslerwebservice/test/build.xmlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/resources/header/config.xmlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/resources/header/WEB-INF/jaxrpc-mapping.xmlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/resources/header/WEB-INF/web.xmlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/resources/header/WEB-INF/webservices.xmlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/resources/header/WEB-INF/wsdl/TestService.wsdlAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestService.javaAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestServiceBean.javaAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/java/org/jboss/test/ws/header/ServerHandler.javaAdd support for headers on the Call objects1.1addedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestCase.javaAdd support for headers on the Call objects1.16modifiedtdieslerwebservice/test/java/org/jboss/test/ws/binding/SOAP12BindingTestCase.javaAdd support for headers on the Call
[JBoss-dev] [JBossWS] - Problem with EJB Web service Client
Hi,
I had successfully deployed my EJB web service.
Now i m trying to create a client to access the web service
the code i m using is
URL url =new
URL(http://192.10.10.58:8080/JoinBean/services/JoinServiceEJB?wsdl;);
| QName qname = new
QName(http://join.synxis.org,JoinEndpointService;);
| ServiceFactory factory = ServiceFactory.newInstance();
| Service service = factory.createService(url, qname);
|
| JoinEndpoint endpoint =
(JoinEndpoint)service.getPort(JoinEndpoint.class);
| JoinArray joinArray=new JoinArray();
| StatusArray statusArray=endpoint.addJoinDetails(joinArray);
| Status[] s=statusArray.getStatusArray();
|
|
| System.out.println(Join ID : + s[0].getJoinId());
| System.out.println(Status Desc : + s[0].getStatusDesc());
when i run this code i m getting this error in the client side
Exception in thread main AxisFault
| faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
| faultSubcode:
| faultString: org.xml.sax.SAXException: Deserializing parameter
'addJoinDetailsReturn': could not find deserializer for type
{http://join.synxis.org}StatusArray
| faultActor:
| faultNode:
| faultDetail:
| {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Deserializing parameter 'addJoinDetailsReturn': could not find deserializer
for type {http://join.synxis.org}StatusArray
| at
org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:273)
| at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1025)
| at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:159)
| at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:844)
| at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:198)
| at org.apache.axis.message.RPCElement.getParams(RPCElement.java:323)
| at org.apache.axis.client.Call.invoke(Call.java:2417)
| at org.apache.axis.client.Call.invoke(Call.java:2316)
| at org.apache.axis.client.Call.invoke(Call.java:1773)
| at
org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:159)
| at $Proxy0.addJoinDetails(Unknown Source)
| at org.synxis.join.JoinClient.main(JoinClient.java:37)
|
| {http://xml.apache.org/axis/}hostname:tapthi
How to solve this problem...
pls help me.
Thanks in Advance
Rgds
Gayathiri
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3860717#3860717
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860717
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-15) Concurrent startup of initial members without merging
[ http://jira.jboss.com/jira/browse/JGRP-15?page=history ] Bela Ban resolved JGRP-15: -- Resolution: Done Concurrent startup of initial members without merging - Key: JGRP-15 URL: http://jira.jboss.com/jira/browse/JGRP-15 Project: JGroups Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 Original Estimate: 2 days Remaining: 2 days When multiple members are started simultaneously, and no other member is running yet, they form singleton groups, and merge after some time. GOAL: elect a coordinator out of all concurrent (client-)members and avoid a merge. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.242 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050105045334Lbuild.242
BUILD COMPLETE-build.242Date of build:01/05/2005 04:53:34Time to build:23 minutes 6 secondsLast changed:01/05/2005 03:05:15Last log entry:Add date editor tests
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build:(7)1.2.2.8modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd date editor tests1.4.2.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.6.4.6modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.1.1.2.2modifiedstarksmcommon/src/main/org/jboss/util/StringPropertyReplacer.javaAdd support for property references of the form ${p:v}. This allows for a reference to system property 'p', and if there is no such property, then the default value v will be returned.1.79.2.18modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaAdded logger for inner class to support jdk1.31.1.4.2modifiedkabkhancommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.java*** empty log message ***1.1.4.1modifiedkabkhancommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.java*** empty log message ***
[JBoss-dev] jboss-4.0 build.306 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050105054154Lbuild.306 BUILD COMPLETE-build.306Date of build:01/05/2005 05:41:54Time to build:16 minutes 55 secondsLast changed:01/05/2005 03:01:20Last log entry:Add date editor tests Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(4)1.6.4.1modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd date editor tests1.4.18.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.24.2.2modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaFix the inner class FieldName serialVersionUID to the 4.0.0 value.1.24.2.1modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.
[JBoss-dev] [Design of JBoss/Tomcat Integration] - Re: session persistence config
Hi again! tinghe, you were completly right. It works just fine but only in JBoss 3.2.6 not any earlier version. Regards Pawel View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860725#3860725 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860725 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.662 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050105060601Lbuild.662 BUILD COMPLETE-build.662Date of build:01/05/2005 06:06:01Time to build:17 minutes 21 secondsLast changed:01/05/2005 02:56:26Last log entry:Add Date editor tests Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(24)1.7modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd Date editor tests1.5modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.25modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.1.1addedpatriot1burketestsuite/src/main/org/jboss/test/recover/interfaces/DummyRecoverable.javarecovery1.1addedpatriot1burketestsuite/src/main/org/jboss/test/recover/interfaces/DummyXAResource.javarecovery1.1addedpatriot1burketestsuite/src/main/org/jboss/test/recover/interfaces/MockLogger.javarecovery1.1addedpatriot1burketestsuite/src/main/org/jboss/test/recover/test/FileLogTestCase.javarecovery1.1addedpatriot1burketestsuite/src/main/org/jboss/test/recover/test/RecoverabilityTestCase.javarecovery1.22modifiedpatriot1burketransaction/src/main/org/jboss/tm/TxManager.javarecovery1.13modifiedpatriot1burketransaction/src/main/org/jboss/tm/XidFactory.javarecovery1.36modifiedpatriot1burketransaction/src/main/org/jboss/tm/TransactionImpl.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/FileRecoveryLogReader.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/FileRecoveryLogWriter.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/MultiFileRecoveryLogger.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/MultiFileRecoveryLoggerService.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/MultiFileRecoveryLoggerServiceMBean.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/Recoverable.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryLogReader.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryLogTerminator.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryLogger.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryLoggerInstance.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryManager.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryManagerService.javarecovery1.1addedpatriot1burketransaction/src/main/org/jboss/tm/recovery/RecoveryManagerServiceMBean.javarecovery
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-12) Analyze all occurences where up or down thread might block
[ http://jira.jboss.com/jira/browse/JGRP-12?page=comments#action_12314522 ] Bela Ban commented on JGRP-12: -- - MERGE(2,3) - PING, TCPPING, TCPGOSSIP, WANPING - FD, FD_SOCK - STABLE - NAKACK Analyze all occurences where up or down thread might block -- Key: JGRP-12 URL: http://jira.jboss.com/jira/browse/JGRP-12 Project: JGroups Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 Original Estimate: 2 days Remaining: 2 days disrupting regular traffic. One example is JGRP-11 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JGRP-16) GMS.getDigest() needs to be run in a separate thread
GMS.getDigest() needs to be run in a separate thread Key: JGRP-16 URL: http://jira.jboss.com/jira/browse/JGRP-16 Project: JGroups Type: Bug Reporter: Bela Ban Assigned to: Bela Ban Priority: Minor Fix For: 2.2.8 Not a bug, but results in slight performance imporvement -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: Define components and Generate JIRA Tasks
Isn't that the JBossPOJO Server is really JBossAS 5 (over the JBoss MicroContainer), where there will be more freedom in combing components. In this sense, why change name/version scheme? In which case a JBossPOJO server will be offered standalone and not be named JBossAS? If this is confusing to us, imagine how it'll be perceived by the users.. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860730#3860730 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860730 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite build.32 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050105064206Lbuild.32 BUILD COMPLETE-build.32Date of build:01/05/2005 06:42:06Time to build:90 minutes 14 secondsLast changed:01/05/2005 03:01:20Last log entry:Add date editor tests Unit Tests: (2300) Total Errors and Failures: (16)testAspectorg.jboss.test.aop.test.RemotingUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestEvictionorg.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCasetestEvictionReplicationorg.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCasetestStateTransferorg.jboss.test.cache.test.replicated.AsyncUnitTestCasetestSyncReplorg.jboss.test.cache.test.replicated.AsyncUnitTestCasetestSyncReplorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestASyncReplorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestPutorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestStateReplicationorg.jboss.test.cluster.test.DRMTestCasetestPoolingorg.jboss.test.cts.test.MDBUnitTestCasetestPoolingorg.jboss.test.securitymgr.test.MDBUnitTestCasetestStatelessBeanColocationorg.jboss.test.testbeancluster.test.BeanUnitTestCasetestMDBTimerorg.jboss.test.timer.test.BasicTimerUnitTestCasetestJBossEditorsorg.jboss.test.util.test.PropertyEditorsUnitTestCase Modifications since last build:(120)1.6.4.1modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd date editor tests1.4.18.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.24.2.2modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaFix the inner class FieldName serialVersionUID to the 4.0.0 value.1.24.2.1modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.1.17.2.1modifiedtelrodremoting/build.xmlJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.2.8.1modifiedtelrodremoting/build.shJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.2.8.1modifiedtelrodremoting/build.batJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.12.2.1modifiedtelrodremoting/.classpathJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.1.14.1deletedtelrodremoting/src/test/org/jboss/remoting/InvokerServerUnitTestCase.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.3.12.1deletedtelrodremoting/src/test/org/jboss/remoting/MockInvokerCallbackHandler.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.3.4.1deletedtelrodremoting/src/test/org/jboss/remoting/DistributedTest.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.6.10.1deletedtelrodremoting/src/test/org/jboss/remoting/InvokerClientUnitTestCase.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.1.14.1deletedtelrodremoting/src/test/org/jboss/remoting/AbstractInvokerTest.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.2.14.1deletedtelrodremoting/src/test/org/jboss/remoting/detection/multicast/MulticastUnitTestCase.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.1.14.1deletedtelrodremoting/src/main/test/MultipleTestRunner.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.3.10.1deletedtelrodremoting/src/main/test/OnewayInvokerClientTest.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.3.10.1deletedtelrodremoting/src/main/test/OnewayInvokerServerTest.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.1.10.1deletedtelrodremoting/src/main/test/OnewayInvokerTestCase.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.1.10.1deletedtelrodremoting/src/main/test/ShutdownListener.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0 branch.1.2.14.1deletedtelrodremoting/src/test/org/jboss/remoting/detection/jndi/JNDIDetectorUnitTestCase.javaJBREM-18: Backport of post alpha/pre beta release of remoting from HEAD to 4.0
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1269) toString called on EJB
toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assigned to: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314523 ] Alex Loubyansky commented on JBAS-1255: --- What does the following mean? In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long constant-memory-use period. If it's really CMP related, I assume I should see the leak if I remove all the MDB stuff and just create and delete entity instances. Is there a chance you can confirm this? Thanks. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alex Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-jdk-matrix build.23 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050105082334Lbuild.23
BUILD COMPLETE-build.23Date of build:01/05/2005 08:23:34Time to build:21 minutes 15 secondsLast changed:01/05/2005 05:56:35Last log entry:Add support for new option throw-runtime-exceptions in cmp defaults
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build:(14)1.1.2.10modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/AbstractQueryCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.1.2.25modifiednoelrocherserver/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_2.dtdAdd support for new option throw-runtime-exceptions in cmp defaults1.17.4.26modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/JDBCEntityMetaData.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.1.2.22modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractCreateCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.12.2.35modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractQueryCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.39.2.56modifiednoelrocherserver/src/etc/conf/default/standardjbosscmp-jdbc.xmlAdd support for new option throw-runtime-exceptions in cmp defaults1.2.2.8modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaAdd date editor tests1.4.2.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaExpand the date parsing to expand the formats it supports. It now tries the following SimpleDateFormat formats in order:* org.jboss.util.propertyeditor.DateEditor.format system property value (or MMM d, , if not specified),* EEE MMM d HH:mm:ss z * EEE, d MMM HH:mm:ss Z1.6.4.6modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCompletely validate the serializability of the descriptor field values in the writeObject method to ensure that non-serializable values do not prevent accessibility of the mbean in some form over connectors.1.1.2.2modifiedstarksmcommon/src/main/org/jboss/util/StringPropertyReplacer.javaAdd support for property references of the form ${p:v}. This allows for a reference to system property 'p', and if there is no such property, then the default value v will be returned.1.79.2.18modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaAdded logger for inner class to support jdk1.31.1.4.2modifiedkabkhancommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.java*** empty log message ***1.1.4.1modifiedkabkhancommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.java*** empty log message ***1.5.2.13modifiedschroufvaria/src/resources/services/binding/sample-bindings.xmlInclude explicit port assignment for some previously anonymous ports (needed for firewall ruleset definition) and removal of redundant tomcat port binding section
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - deployer.jar
I downloaded JBoss 4.0 but i don't have deployer.jar file .I want t have it. can you help me ?.Who can ?. Send for me deployer.jar file please. Thank you very much !. My email [EMAIL PROTECTED] View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860739#3860739 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860739 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JGRP-17) Common transport protocol
Common transport protocol - Key: JGRP-17 URL: http://jira.jboss.com/jira/browse/JGRP-17 Project: JGroups Type: Task Versions: 2.2.8 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.9 Create common TransportProtocol (subclass of Protocol): handles all message bundling, loopback etc, real transports (UDP, TCP, TUNNEL) have to extend this class and provide a send() and receive() method. Avoids code duplication -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.243 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050105085809Lbuild.243 BUILD COMPLETE-build.243Date of build:01/05/2005 08:58:09Time to build:14 minutes 31 secondsLast changed:01/05/2005 05:56:35Last log entry:Add support for new option throw-runtime-exceptions in cmp defaults Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(6)1.1.2.10modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/AbstractQueryCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.1.2.25modifiednoelrocherserver/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_2.dtdAdd support for new option throw-runtime-exceptions in cmp defaults1.17.4.26modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/JDBCEntityMetaData.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.1.2.22modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractCreateCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.12.2.35modifiednoelrocherserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractQueryCommand.javaAdd support for new option throw-runtime-exceptions in cmp defaults1.39.2.56modifiednoelrocherserver/src/etc/conf/default/standardjbosscmp-jdbc.xmlAdd support for new option throw-runtime-exceptions in cmp defaults
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-5) Conversion of Externalizable to Streamable
[ http://jira.jboss.com/jira/browse/JGRP-5?page=history ] Bela Ban resolved JGRP-5: - Resolution: Done Conversion of Externalizable to Streamable -- Key: JGRP-5 URL: http://jira.jboss.com/jira/browse/JGRP-5 Project: JGroups Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 Original Estimate: 3 weeks Remaining: 3 weeks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-5) Conversion of Externalizable to Streamable
[ http://jira.jboss.com/jira/browse/JGRP-5?page=comments#action_12314524 ] Bela Ban commented on JGRP-5: - Resulted in 40% speed improvement and 50% size reduction compared to Externalizable for marshalling and unmarshalling of Messages (not including transport and handling) Conversion of Externalizable to Streamable -- Key: JGRP-5 URL: http://jira.jboss.com/jira/browse/JGRP-5 Project: JGroups Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 Original Estimate: 3 weeks Remaining: 3 weeks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - problem with BeanSerializer
I've got object Order with an array of OrderOwner objects.
All objets are BeanPatterns.
I would like to send them beetwen Client and WebService useing
org.apache.axis.encoding.ser.BeanSerializer.
when I deploy WS in Tomcat with Axis everything is OK.
I can send Order with array od OrderOwners.
But when I trying deploy WS in JBoss-4.0.0 I've got errors during deserializing.
Could You help me?
-- error
call.invoke() throws: IllegalArgumentException: array element type mismatch
jboss console:
15:12:36,343 ERROR [BeanPropertyTarget] Could not convert
[Lcom.myapp.OrderOwner; to bean field 'owner[0]', type [Lcom.myapp.OrderOwner;
15:12:36,343 ERROR [RPCInvocation] java.lang.IllegalArgumentException: array
element type mismatch
java.lang.IllegalArgumentException: array element type mismatch
--- client: ---
...
Order order = new Order();
order.setCustomerName(Glen Daniels);
OrderOwner[] oo = {new OrderOwner()};
oo[0].setName(Mikey Mouse);
order.setOrderName(TESTTEST-2);
order.setOwner((OrderOwner[])oo);
...
Service service = new Service();
Call call= (Call) service.createCall();
QNameqn = new QName( urn:BeanService, Order );
QNameqn2 = new QName( urn:BeanService, OrderOwner );
call.registerTypeMapping(Order.class, qn,
new
org.apache.axis.encoding.ser.BeanSerializerFactory(Order.class, qn),
new
org.apache.axis.encoding.ser.BeanDeserializerFactory(Order.class, qn));
call.registerTypeMapping(OrderOwner.class, qn2,
new
org.apache.axis.encoding.ser.BeanSerializerFactory(OrderOwner.class, qn2 ),
new
org.apache.axis.encoding.ser.BeanDeserializerFactory(OrderOwner.class, qn2));
Order result = null;
String endpoint = http://localhost:8080/simple-ws4ee/exactpath/jse;;
try {
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName( new QName(OrderProcessor, processOrder)
);
call.addParameter( arg1, qn, ParameterMode.IN );
call.setReturnType( qn, Order.class);
result = (Order) call.invoke( new Object[] { new Order[] { order }
} );
} catch (AxisFault fault) {
//result = Error : + fault.toString();
System.out.println(er = +fault.toString());
}
classes
public class Order extends SimpleOrder
{
private String customerName;
private String shippingAddress;
private OrderOwner[] owner;
public Order() {}
public void setOwner(OrderOwner[] owner) {
this.owner = owner;
}
public OrderOwner[] getOwner() {
return this.owner;
}
public String getCustomerName() { return customerName; }
public void setCustomerName(String name) { customerName = name; }
public String getShippingAddress() { return shippingAddress; }
public void setShippingAddress(String address) { shippingAddress = address;
}
}
public class OrderOwner {
private String name = ;
public OrderOwner() {
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
public String toString() {
return this.name;
}
}
public class SimpleOrder {
private String orderName = ;
public SimpleOrder() {}
public void setOrderName(String orderName) {
this.orderName = orderName;
}
public String getOrderName() {
return this.orderName;
}
}
- WS implements interface (nothing special)
public interface BeanService extends java.rmi.Remote {
public Order processOrder(Order []orders) throws
java.rmi.RemoteException;
}
-jaxrpc-mapping.xml ---
?xml version='1.0' encoding='UTF-8' ?
java-wsdl-mapping
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd;
version=1.1
package-mapping
package-typecom.myapp/package-type
http://myapp.com
/package-mapping
/java-wsdl-mapping
-- ws4ee-deployment.xml
deployment
xmlns='http://xml.apache.org/axis/wsdd/'
xmlns:java='http://xml.apache.org/axis/wsdd/providers/java'
xmlns:soap='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
typeMapping
qname=myNS:Order
xmlns:myNS=urn:BeanService
serializer='org.apache.axis.encoding.ser.BeanSerializerFactory'
[JBoss-dev] [JBoss JIRA] Created: (JGRP-18) Fix RouterTest
Fix RouterTest -- Key: JGRP-18 URL: http://jira.jboss.com/jira/browse/JGRP-18 Project: JGroups Type: Bug Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 RouterTest still uses the old format, change it to the new one -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Problem with BeanSerializer
I've got object Order with an array of OrderOwner objects.
All objets are BeanPatterns.
I would like to send them beetwen Client and WebService useing
org.apache.axis.encoding.ser.BeanSerializer.
when I deploy WS in Tomcat with Axis everything is OK.
I can send Order with array od OrderOwners.
But when I trying deploy WS in JBoss-4.0.0 I've got errors during deserializing.
Could You help me?
-- error
call.invoke() throws: IllegalArgumentException: array element type mismatch
jboss console:
15:12:36,343 ERROR [BeanPropertyTarget] Could not convert
[Lcom.myapp.OrderOwner; to bean field 'owner[0]', type [Lcom.myapp.OrderOwner;
15:12:36,343 ERROR [RPCInvocation] java.lang.IllegalArgumentException: array
element type mismatch
java.lang.IllegalArgumentException: array element type mismatch
--- client: ---
...
Order order = new Order();
order.setCustomerName(Glen Daniels);
OrderOwner[] oo = {new OrderOwner()};
oo[0].setName(Mikey Mouse);
order.setOrderName(TESTTEST-2);
order.setOwner((OrderOwner[])oo);
...
Service service = new Service();
Call call= (Call) service.createCall();
QNameqn = new QName( urn:BeanService, Order );
QNameqn2 = new QName( urn:BeanService, OrderOwner );
call.registerTypeMapping(Order.class, qn,
new
org.apache.axis.encoding.ser.BeanSerializerFactory(Order.class, qn),
new
org.apache.axis.encoding.ser.BeanDeserializerFactory(Order.class, qn));
call.registerTypeMapping(OrderOwner.class, qn2,
new
org.apache.axis.encoding.ser.BeanSerializerFactory(OrderOwner.class, qn2 ),
new
org.apache.axis.encoding.ser.BeanDeserializerFactory(OrderOwner.class, qn2));
Order result = null;
String endpoint = http://localhost:8080/simple-ws4ee/exactpath/jse;;
try {
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName( new QName(OrderProcessor, processOrder)
);
call.addParameter( arg1, qn, ParameterMode.IN );
call.setReturnType( qn, Order.class);
result = (Order) call.invoke( new Object[] { new Order[] { order }
} );
} catch (AxisFault fault) {
//result = Error : + fault.toString();
System.out.println(er = +fault.toString());
}
classes
public class Order extends SimpleOrder
{
private String customerName;
private String shippingAddress;
private OrderOwner[] owner;
public Order() {}
public void setOwner(OrderOwner[] owner) {
this.owner = owner;
}
public OrderOwner[] getOwner() {
return this.owner;
}
public String getCustomerName() { return customerName; }
public void setCustomerName(String name) { customerName = name; }
public String getShippingAddress() { return shippingAddress; }
public void setShippingAddress(String address) { shippingAddress = address;
}
}
public class OrderOwner {
private String name = ;
public OrderOwner() {
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
public String toString() {
return this.name;
}
}
public class SimpleOrder {
private String orderName = ;
public SimpleOrder() {}
public void setOrderName(String orderName) {
this.orderName = orderName;
}
public String getOrderName() {
return this.orderName;
}
}
- WS implements interface (nothing special)
public interface BeanService extends java.rmi.Remote {
public Order processOrder(Order []orders) throws
java.rmi.RemoteException;
}
-jaxrpc-mapping.xml ---
?xml version='1.0' encoding='UTF-8' ?
java-wsdl-mapping
xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd;
version=1.1
package-mapping
package-typecom.myapp/package-type
http://myapp.com
/package-mapping
/java-wsdl-mapping
-- ws4ee-deployment.xml
deployment
xmlns='http://xml.apache.org/axis/wsdd/'
xmlns:java='http://xml.apache.org/axis/wsdd/providers/java'
xmlns:soap='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
typeMapping
qname=myNS:Order
xmlns:myNS=urn:BeanService
serializer='org.apache.axis.encoding.ser.BeanSerializerFactory'
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-14) TCP protocol stack won't merge view with initial hosts specified as IP addresses
[ http://jira.jboss.com/jira/browse/JGRP-14?page=history ] Bela Ban updated JGRP-14: - Summary: TCP protocol stack won't merge view with initial hosts specified as IP addresses (was: TCP protocol stack won't mergeview with initial hosts specified as IP addresses) TCP protocol stack won't merge view with initial hosts specified as IP addresses Key: JGRP-14 URL: http://jira.jboss.com/jira/browse/JGRP-14 Project: JGroups Type: Bug Versions: 2.2.8 Environment: Linux and JGroups 2.2.7 Reporter: Zac Hansen Assignee: Bela Ban Fix For: 2.2.8 Attachments: belacode.java When I use a TCP protocol stack with TCPPING having initial members as ip addresses: initial_members=192.168.1.200[4000], no merges will occur when 2 instances are started simultaneously. The same thing with initial_members=localhost[4000] merges fine when 2 instances are started simultaneously. The following code reproduces the problem when started with a command line parameter of 1, and works when run with a parameter of 0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: I18N logging messages
Anyone ever use the XDoclet @msg tags? Looks like they've already got the ability to create message bundles. Not sure what they mean when they say they generate translator classes, too. See: http://xdoclet.sourceforge.net/xdoclet/tags/xdoclet-tags.html[/url] View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860746#3860746 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860746 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Problem calling webservice from an EJB
Hello !
I try to access a webservice from an EJB (SLSB) that is deployed on JBoss 4.0.1
server (the EJB and the Webservices are located on the same server). The
service uses rpc/encoded format and returns arrays of user defined objects in
several of it's methods.
In my EJB create function I'm usinf this code to access the webservice:
URL url = new URL(http://localhost:8080/LvsWs/Item?wsdl;);
| QName qname = new QName(http://x.y.z;, LVSItemJSE);
| sfItemService = ServiceFactory.newInstance();
| svcItemService = sfItemService.createService(url, qname);
| itemService =
(LVSItemServicesEndpoint)svcItemService.getPort(LVSItemServicesEndpoint.class);
|
I can successfully call methods that return user defined objects; but if i call
a method that returns an array of user defined objects i get this message in
the log file:
anonymous wrote : 2005-01-05 14:24:55,333 DEBUG
[org.jboss.webservice.server.ServerEngine]
LvsWs.war#ItemService.getItemStockInfoArr
[trIn=0,glIn=0,invoke=47,glOut=0,trOut=0]
| 2005-01-05 14:24:55,380 DEBUG
[org.jboss.webservice.handler.HandlerChainBaseImpl] Enter: handleResponse
| 2005-01-05 14:24:55,380 DEBUG
[org.jboss.webservice.handler.HandlerChainBaseImpl] Exit: handleResponse with
status: true
| 2005-01-05 14:24:55,396 ERROR [org.apache.axis.client.Call] Exception:
| org.xml.sax.SAXException: No deserializer defined for array type
{http://lvsws.emediapark.de}LVSDoItemStockInfo
| at
org.apache.axis.encoding.ser.ArrayDeserializer.onStartElement(ArrayDeserializer.java:331)
| at
org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl.java:466)
| at
org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:1180)
| at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:244)
| ...
|
|
It looks like the axis client does not know the array.
Calling the webservice from a vb-client via pocketSOAP is successfull.
Can someone give me a hint/example.
I thought about using the stub generated by wscompile (jwsdp-1.5) but
havn't found any example yet.
TIA Gerhard
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3860747#3860747
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860747
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: Define components and Generate JIRA Tasks
Yes, there will be a non-JBossAS release of the POJO server that does not include the full j2ee related services. The confusion is not in the names, its in what the associated jira project is. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860749#3860749 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860749 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: webservices-context-root gone again?
This was rolled into the port-component-uri element:
{{{
!-- Absolute path starting with web context root to form fully qualified
endpoint address for a web service endpoint. The port component uri, if present
must contain at least two token seperated by '/'. The first token is the web
context root, which must be identical among all port component uris in a given
deployment.
If this element is not present, the web context root will be derived from the
deployment canonical name.
Used in: port-component
--
!ELEMENT port-component-uri (#PCDATA)
}}}
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3860752#3860752
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860752
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: problem with BeanSerializer
it is posible to have diferent version of axis in JBoss and client ?? How to check it ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860751#3860751 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860751 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314528 ] Scott M Stark commented on JBAS-1269: - This is not a practical solution. If an ejb is overriding toString to incorporate calls which are not universially accesible, then the toString method needs to guard against usage in context that may generate exceptions. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314529 ] Michael Lipp commented on JBAS-1269: I conceed that the EJB specification does not specify in what context(s) the toString method may be called. However, I don't understand why removing the call to toString in the AS is not a pratical solution. From the three application servers that I'm currently using (JBoss, WLS and JOnAS), JBoss is the only one that calls toString on the EJB. And I don't see the problem in removing this call (especially as the line in question serves only debug purposes). The AS cannot rely on a specific result of toString anyway. In my case, you currently find an application domain related message in the JBoss logs, not very useful in my point of view. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-92) Create admin interface for CMSPortlet.
[ http://jira.jboss.com/jira/browse/JBPORTAL-92?page=history ] Roy Russo resolved JBPORTAL-92: --- Resolution: Done Fix Version: 2.0 Alpha Code complete. Note: no ability for history previewing of files. Create admin interface for CMSPortlet. -- Key: JBPORTAL-92 URL: http://jira.jboss.com/jira/browse/JBPORTAL-92 Project: JBoss Portal Type: Sub-task Reporter: Roy Russo Assignee: Roy Russo Fix For: 2.0 Alpha Time Spent: 1 week, 3 days Remaining: 2 days -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBREM-26) Ability to use MBeans as handlers
[ http://jira.jboss.com/jira/browse/JBREM-26?page=history ] Tom Elrod updated JBREM-26: Environment: Fix Version: 1.0.1 beta Ability to use MBeans as handlers - Key: JBREM-26 URL: http://jira.jboss.com/jira/browse/JBREM-26 Project: JBoss Remoting Type: Feature Request Components: general Versions: 1.0.1 alpha Reporter: Tom Elrod Assignee: Tom Elrod Priority: Minor Fix For: 1.0.1 beta Would like ability to specify object name for the handler within the configuration xml instead of just the class name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPTL-59) Functional Spec
[ http://jira.jboss.com/jira/browse/JBPTL-59?page=history ] Roy Russo closed JBPTL-59: -- Resolution: Done Fix Version: 2.0 Alpha a bit late for this. Functional Spec --- Key: JBPTL-59 URL: http://jira.jboss.com/jira/browse/JBPTL-59 Project: JBoss Portal Type: Sub-task Reporter: Roy Russo Assignee: Roy Russo Fix For: 2.0 Alpha -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-92) Create admin interface for CMSPortlet.
[ http://jira.jboss.com/jira/browse/JBPORTAL-92?page=history ] Roy Russo closed JBPORTAL-92: - Create admin interface for CMSPortlet. -- Key: JBPORTAL-92 URL: http://jira.jboss.com/jira/browse/JBPORTAL-92 Project: JBoss Portal Type: Sub-task Reporter: Roy Russo Assignee: Roy Russo Fix For: 2.0 Alpha Time Spent: 1 week, 3 days Remaining: 2 days -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: CVS
Long term this work is going back to the head branch so I don't know what term you mean here. If its easiest to get the core micrkernel with jmx support, deployments, etc working on a branch, let's do it and then decide from there how to deal with migration of the existing services. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860762#3860762 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860762 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314533 ] Michael Lipp commented on JBAS-1269: This is easy: as far as the application server is concerned, the list is empty. I think the application server must never call toString on an EJB -- simply because the contract between the EJB container and the EJB developer (as defined in the specification) does not define any restrictions for the developer about what he can may do in toString. As there are no restrictions, he can do anything he likes. On the other hand side, there is no reason for the EJB container to assume that it may call toString -- in any context --, simply because the contract does not specify that toString must be callable (and as I mentioned before: what good is calling toString for the EJB container anyway: the result is controlled by the EJB developer and thus from the EJB container's point of view unspecified). There was a simalar issue in some JBoss version one or two years ago. My EJB caused problems because it overrode equals and hashCode (not the EJB as such, but the base class of my EJB which was a POJO). JBoss, at that time, used the instantiated EJBs as keys for lookup in a HashMap. This was absolutely fatal because JBoss assumed the default behaviour of Java object, i.e. no two objects are equal unless the are the same instance, while in my case different EJBs could be equal from a business point of view (and lucky for me, my patch was accepted, because I could not avoid the re-definition of equals and hashCode). I see a simalarity here because toString is, just like equals and hashCode, a method defined for Object. So the EJB container can of course assume that they are implemented and can call them. But as they may be overridden in an EJB (nothing in the EJB specification prevents me from doing this) the EJB container may not make any assumption about the results or even the callability of these methods. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314535 ] Scott M Stark commented on JBAS-1269: - An empty list means that there are no uses of the ejb object toString. The current context where the problem exists has no knowledge of ejbs. This problem is not like the previous equals/hashCode issue as the context in question is a debugging interface for use in determining connection leaks. If you want a meaningful view of the context interacting with the jca layer, your 'rawKey' (whatever that is) can implement a meaningful toString. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: CVS
That's what I mean by long term. Once is put back into HEAD, would leave ghost directories (system2 and jmx2), where as using a branch wouldn't. Is not a big deal, but just gets confusing when browsing repository and see a lot of meaningless directories. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860771#3860771 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860771 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-11) FIND_INITIAL_MBRS blocks entire traffic
[ http://jira.jboss.com/jira/browse/JGRP-11?page=comments#action_12314537 ] Bela Ban commented on JGRP-11: -- Here's Mark Kopec's example: TCPPING timeout=3000 initial_hosts=192.168.0.57[7800] port_range=3 num_initial_members=3/ My testdriver went as follows: 1) Client joins jgroups channel 2) Server joins jgroups channel Server sends packets to the client at short intervals of 100 ms. Client sends packets to the server at intervals of 2000 ms. (Packets are stuffed to be 10K) We were interested in measuring the response times from server to client. So Server put a timestamp send off packet to Client, client calculated the difference. The test was done on the same machine. (Client and server on same windows box) We found this pattern: This messages time for response is:62 This messages time for response is:47 This messages time for response is:78 This messages time for response is:47 This messages time for response is:79 This messages time for response is:94 This messages time for response is:46 This messages time for response is:94 This messages time for response is:47 This messages time for response is:94 This messages time for response is:31 This messages time for response is:0 This messages time for response is:0 This messages time for response is:47 This messages time for response is:31 This messages time for response is:47 This messages time for response is:31 This messages time for response is:94 This messages time for response is:3078 This messages time for response is:2969 This messages time for response is:2859 This messages time for response is:2750 This messages time for response is:2641 This messages time for response is:2547 This messages time for response is:2531 This messages time for response is:2438 This messages time for response is:2328 This messages time for response is:2235 This messages time for response is:2125 This messages time for response is:2031 This messages time for response is:1938 This messages time for response is:1844 This messages time for response is:1751 This messages time for response is:1641 This messages time for response is:1640 This messages time for response is:1531 This messages time for response is:1437 This messages time for response is:1375 This messages time for response is:1328 This messages time for response is:1203 This messages time for response is:1109 This messages time for response is:1000 This messages time for response is:906 This messages time for response is:797 This messages time for response is:703 This messages time for response is:594 This messages time for response is:516 This messages time for response is:407 This messages time for response is:297 This messages time for response is:265 This messages time for response is:172 This messages time for response is:93 This messages time for response is:78 This messages time for response is:62 This messages time for response is:31 This messages time for response is:47 This messages time for response is:0 This messages time for response is:0 This messages time for response is:0 This messages time for response is:47 This messages time for response is:47 This messages time for response is:16 This messages time for response is:46 This messages time for response is:78 This messages time for response is:32 This messages time for response is:47 This messages time for response is:47 This messages time for response is:47 This messages time for response is:16 This messages time for response is:0 This messages time for response is:31 This messages time for response is:47 This messages time for response is:3126 This messages time for response is:3047 This messages time for response is:2953 This messages time for response is:2844 This messages time for response is:2750 This messages time for response is:2703 This messages time for response is:2672 This messages time for response is:2578 This messages time for response is:2469 This messages time for response is:2438 This messages time for response is:2360 This messages time for response is:2266 This messages time for response is:2156 This messages time for response is:2063 This messages time for response is:1953 This messages time for response is:1860 This messages time for response is:1766 This messages time for response is:1656 This messages time for response is:1547 This messages time for response is:1453 This messages time for response is:1344 This messages time for response is:1250 This messages time for response is:1125 This messages time for response is:1031 This messages time for response is:937 This messages time for response is:812 This messages time for response is:718 This messages time for response is:609 This messages time for response is:500 This messages time for response is:359 This messages time for response is:250 This messages time for response is:78 This messages time for response is:31 This messages time for response is:79 This messages time for response is:47 This messages time for response
[JBoss-dev] [Design of JBoss Build System] - Re: NEW BUILD
pilhuhn wrote : And the developer should not only be able to check out a source tree, but also be able to *update* the tree without throwing things away and re-checking out some modules. This not only saves bandwidth, but also time. Yes, that is the purpose of the build definition. If you look at the synchronize method it actually does the following when executed at the top level. 1) Synchronize the main build project (from cvs) 2) Reinvoke ant to pick up any new build.xml downloaded from cvs 3) Do the same for each component (including checking out any new components that may have appeared in the build definition) With the current JBoss build, any new modules or thirdparty jars requires the developer to look at CVSROOT/modules then go to the relevent directory and do a cvs co or blow away the whole thing and check out from scratch. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860774#3860774 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860774 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: NEW BUILD
The synchronize also regenerates any ide project files from the build definition so all you have to do is refresh inside the ide (and maybe import new projects) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860776#3860776 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860776 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBPM-46) scheduler
[ http://jira.jboss.com/jira/browse/JBPM-46?page=comments#action_12314534 ] Ronald van Kuijk commented on JBPM-46: -- If the license permits it, I think we should look at Quartz again. It has clustering features. With a few classes that should be doable. How far is jbpm 3 on that part. Is the basic scheduler node there and only the backend not implemented? scheduler - Key: JBPM-46 URL: http://jira.jboss.com/jira/browse/JBPM-46 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens implement the scheduler functionality + a simple servlet that acts as a cron-task to check for due jobs on regular intervals. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBPM-51) add optional xml validation of process definitions
[ http://jira.jboss.com/jira/browse/JBPM-51?page=comments#action_12314538 ] Ronald van Kuijk commented on JBPM-51: -- Why suns MSV? What is the advantage? I've been playing a little with bpss now and I kind of like the usage of id's and refs. If you hava a node that has a transition and that transiton has a ref to a non existing id. The parser already notifies you of this. Even a simple xml editor in eclipse does this. add optional xml validation of process definitions -- Key: JBPM-51 URL: http://jira.jboss.com/jira/browse/JBPM-51 Project: JBoss jBPM Type: Sub-task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens along with this, a w3c schema should be created for process definition files. to be used : sun's msv multi schema validator. downside : +1.5 MB of libraries just for validation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: CVS
Actually, the ghost directories will be jmx and system jmx2 and system2 will become the new definitions. I am not branch phobic. I like branches, but I don't like the idea of continously merging lots of branches. If there was something like bitkeeper's pull in cvs where you can automatically merge change sets and it remembers how you resolved conflicts it wouldn't be such a problem. I'll go with the jmx2/system2 idea for now and only create a branch if it becomes unmanageable, i.e. we see a need to do major modifications to other projects. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860777#3860777 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860777 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-14) TCP protocol stack won't merge view with initial hosts specified as IP addresses
[ http://jira.jboss.com/jira/browse/JGRP-14?page=history ] Bela Ban updated JGRP-14: - Attachment: belacode.java TCP protocol stack won't merge view with initial hosts specified as IP addresses Key: JGRP-14 URL: http://jira.jboss.com/jira/browse/JGRP-14 Project: JGroups Type: Bug Versions: 2.2.8 Environment: Linux and JGroups 2.2.7 Reporter: Zac Hansen Assignee: Bela Ban Fix For: 2.2.8 Attachments: belacode.java, belacode.java When I use a TCP protocol stack with TCPPING having initial members as ip addresses: initial_members=192.168.1.200[4000], no merges will occur when 2 instances are started simultaneously. The same thing with initial_members=localhost[4000] merges fine when 2 instances are started simultaneously. The following code reproduces the problem when started with a command line parameter of 1, and works when run with a parameter of 0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-14) TCP protocol stack won't merge view with initial hosts specified as IP addresses
[ http://jira.jboss.com/jira/browse/JGRP-14?page=comments#action_12314536 ] Bela Ban commented on JGRP-14: -- Modified belacode.java a bit (removed unneeded code) and attached to this case as 2nd attachment. With this and the latest 2.2.8 from CVS, the bug has been fixed. TCP protocol stack won't merge view with initial hosts specified as IP addresses Key: JGRP-14 URL: http://jira.jboss.com/jira/browse/JGRP-14 Project: JGroups Type: Bug Versions: 2.2.8 Environment: Linux and JGroups 2.2.7 Reporter: Zac Hansen Assignee: Bela Ban Fix For: 2.2.8 Attachments: belacode.java, belacode.java When I use a TCP protocol stack with TCPPING having initial members as ip addresses: initial_members=192.168.1.200[4000], no merges will occur when 2 instances are started simultaneously. The same thing with initial_members=localhost[4000] merges fine when 2 instances are started simultaneously. The following code reproduces the problem when started with a command line parameter of 1, and works when run with a parameter of 0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314532 ] Scott M Stark commented on JBAS-1269: - Give me a list of every context in which an ejb toString method may be called and I think that attempting this will make it clear why this is not practical. Unless the spec dictates where toString cannot be called, its fair game in any context and usage of methods which have clearly excluded context should either not be used, or guarded against. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314539 ] Adrian Brock commented on JBAS-1269: There are two errors here: 1) The provider of the EJB must know that toString() should not throw an exception and that using getPrimaryKey() is not allowed in all contexts. e.g. the ejb instance may be being used on a home invocation. 2) The logging within JBoss should cause the operation to fail. It can be easily fixed in this case since all we are interested in is identifying the ejb instance so we can just use the default toString() implementation: -log.trace(new stack for key: + rawKey); +log.trace(new stack for key: + rawKey.getClass().getName() + @ + Integer.getAsHexString(System.identityHashCode(rawKey))); toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=history ] Adrian Brock updated JBAS-1269: --- Version: JBossAS-3.2.6 Final toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Adrian Brock Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=history ] Adrian Brock updated JBAS-1269: --- Assign To: Adrian Brock (was: Scott M Stark) toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Adrian Brock Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.663 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050105113919Lbuild.663 BUILD COMPLETE-build.663Date of build:01/05/2005 11:39:19Time to build:41 minutes 6 secondsLast changed:01/05/2005 11:11:12Last log entry:Add support for bound and unbound headers Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(15)1.23modifiedtdieslerwebservice/test/build.xmlAdd support for bound and unbound headers1.1addedtdieslerwebservice/src/main/org/jboss/ws/binding/UnboundHeader.javaAdd support for bound and unbound header elements1.2modifiedtdieslerwebservice/test/resources/header/WEB-INF/webservices.xmlAdd support for bound and unbound header elements1.17modifiedtdieslerwebservice/test/java/org/jboss/test/ws/binding/SOAP12BindingTestCase.javaAdd support for bound and unbound header elements1.2modifiedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestCase.javaAdd support for bound and unbound header elements1.1addedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestHandler.javaAdd support for bound and unbound header elements1.2modifiedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestService.javaAdd support for bound and unbound header elements1.2modifiedtdieslerwebservice/test/java/org/jboss/test/ws/header/HeaderTestServiceBean.javaAdd support for bound and unbound header elements1.2deletedtdieslerwebservice/test/java/org/jboss/test/ws/header/ServerHandler.javaAdd support for bound and unbound header elements1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/NameImpl.javaAdd support for bound and unbound header elements1.24modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/CallImpl.javaAdd support for bound and unbound header elements1.17modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/desc/ParameterDesc.javaAdd support for bound and unbound header elements1.17modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/desc/OperationDesc.javaAdd support for bound and unbound header elements1.7modifiedtdieslerwebservice/src/main/org/jboss/ws/binding/BindingProvider.javaAdd support for bound and unbound header elements1.20modifiedtdieslerwebservice/src/main/org/jboss/ws/binding/soap/SOAPBindingProvider.javaAdd support for bound and unbound header elements
[JBoss-dev] [Design of Mail Services] - Re: Any GUI guys? Swingers?
http://linuxintegrators.com/acoliver/code/2005/01/03/0206.html There is simply nothing that does everything that I want it to that is open source. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860783#3860783 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860783 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314540 ] Adrian Brock commented on JBAS-1269: - 2) The logging within JBoss should cause the operation to fail. + 2) The logging within JBoss should NOT cause the operation to fail. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Scott M Stark Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314541 ] Scott M Stark commented on JBAS-1269: - I assume that you mean the logging should NOT cause the operation to fail. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Adrian Brock Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=comments#action_12314542 ] Adrian Brock commented on JBAS-1269: I also believe you'll find that the other places in the ejb container that are interested in logging the ejb dump the ejb context to the log rather than the ejb instance. toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Adrian Brock Priority: Critical org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=history ] Adrian Brock updated JBMQ-17: - Attachment: JBossMQXid.java Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-3.2.6 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=history ] Adrian Brock updated JBMQ-17: - Attachment: TransactionRequest.java Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=history ] Adrian Brock updated JBMQ-17: - Description: A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. was: A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. Version: JBossAS-4.0.1 (was: JBossAS-3.2.6) Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Duplicate method names in mixins
Is there any way to support duplicate method names in mixin interfaces. I have
an introduction that has two mixins and I only seem to be able to get this to
work if none of the interfaces have methods of the same name.
Is this expected behaviour?
I was trying to extend a model so that I could both support a tree view and a
graphical workflow view, both interfaces having the method getChildren(). I'm
new to AOP so I'm not sure if this is an appropriate use of the technology,
just seemed like a good idea at the time.
Thanks,
John.
Example:
| ?xml version=1.0 encoding=UTF-8 standalone=yes?
| aop
| introduction class=test.HelloWorld
| mixin
| interfaces
| test.Test
| /interfaces
| classtest.HelloWorldImpl/class
| constructionnew test.HelloWorldImpl(this)/construction
| /mixin
| mixin
| interfaces
| test.Test1
| /interfaces
| classtest.HelloWorldImpl1/class
| constructionnew test.HelloWorldImpl1(this)/construction
| /mixin
|/introduction
|
| /aop
| public interface Test {
| String getWorldName();
| }
| public interface Test1 {
| String getWorldName();
| }
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3860791#3860791
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860791
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: CVS
Ok. In the end my only concern is that there is NOT a jmx2 and system2 (or any XXX2) directory for the jboss-head checkout This is just going to cause confusion for anyone who has not been keeping up with this thread. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860792#3860792 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860792 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss Portal Development] - Re: Build fails with JDK 5.0
I switched to jdk1.4.2_06 and it builds well. Just a minor deploy problem upon jboss starts, which is the Mail service. Oh almost forgot, in the wiki, it says the connector for mysql should be placed in | $JBOSS_HOME/server/standard/deploy, this caused me ClassNotFoundException. I tried putting the jar in $JBOSS_HOME/server/standard/lib, it resolves the issue. Now I am looking around the developer release and it looks good. Nothing will be better than a trivial example on getting started with building on jboss portal. I heard someone is working on the training module and hope such a module will bring interested ones in the development. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860795#3860795 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860795 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=comments#action_12314543 ] Adrian Brock commented on JBMQ-17: -- I've applied your fix for 3.2.7 with some modifications. I would appreciate it if you could test the attached source against WAS 5.0.2 Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.244 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050105142929Lbuild.244 BUILD COMPLETE-build.244Date of build:01/05/2005 14:29:29Time to build:35 minutes 1 secondLast changed:01/05/2005 13:38:03Last log entry:[JBMQ-17] - Fix for non serialize XID implementations Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(4)1.1.2.1modifiedejortmessaging/src/main/org/jboss/mq/JBossMQXid.java[JBMQ-17] - Fix for non serialize XID implementations1.2.8.2modifiedejortmessaging/src/main/org/jboss/mq/TransactionRequest.java[JBMQ-17] - Fix for non serialize XID implementations1.8.2.18modifiedejortconnector/src/main/org/jboss/resource/connectionmanager/CachedConnectionManager.java[JBAS-1269] Cached Connection Manager trace logging fails if the EJB's toString() throws an Exception1.4.2.8modifiedejortcommon/src/main/org/jboss/util/Strings.javaUtility method to get the default implementation of toString() for an object.
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1269) toString called on EJB
[ http://jira.jboss.com/jira/browse/JBAS-1269?page=history ] Adrian Brock closed JBAS-1269: -- Resolution: Done Fix Version: JBossAS-3.2.7 Final JBossAS-4.0.2RC1 toString called on EJB -- Key: JBAS-1269 URL: http://jira.jboss.com/jira/browse/JBAS-1269 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final Environment: Linux, J2SE 1.4.2_06 Reporter: Michael Lipp Assignee: Adrian Brock Priority: Critical Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1 org.jboss.resource.connectionmanager.CachedConnectionManager calls toString() on EJBs (e.g. line 250, where rawKey is an EJB. The toString() method of an EJB may, however, be overwritten, as is appropriate for the type of EJB. Such a toString() method may use getPrimaryKey() as it will usually be called from the business methods, i.e. from a context where this call is legal. CachedConnectionManager calls toString() during create, i.e. in a context where the call to getPrimaryKey is illegal, which results in an IllegalStateException. In order to avoid this kind of problem, the application server should never call toString() on EJBs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBMQ-102) SpyObjectMessage.setObject(null) throws an Exception
[ http://jira.jboss.com/jira/browse/JBMQ-102?page=history ] Adrian Brock closed JBMQ-102: - Resolution: Done Fix Version: JBossAS-3.2.7 JBossAS-4.0.2RC1 SpyObjectMessage.setObject(null) throws an Exception Key: JBMQ-102 URL: http://jira.jboss.com/jira/browse/JBMQ-102 Project: JBoss MQ Type: Bug Versions: JBossAS-4.0.0, JBossAS-3.2.6 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-3.2.7, JBossAS-4.0.2RC1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=history ] Adrian Brock closed JBMQ-17: Resolution: Done Fix Version: JBossAS-3.2.7 JBossAS-4.0.2RC1 5.0 Alpha Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Fix For: 5.0 Alpha, JBossAS-3.2.7, JBossAS-4.0.2RC1 Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBREM-26) Ability to use MBeans as handlers
[ http://jira.jboss.com/jira/browse/JBREM-26?page=history ] Tom Elrod closed JBREM-26: --- Resolution: Done See http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_configuration for info on handler change (bottom of page). Ability to use MBeans as handlers - Key: JBREM-26 URL: http://jira.jboss.com/jira/browse/JBREM-26 Project: JBoss Remoting Type: Feature Request Components: general Versions: 1.0.1 alpha Reporter: Tom Elrod Assignee: Tom Elrod Priority: Minor Fix For: 1.0.1 beta Would like ability to specify object name for the handler within the configuration xml instead of just the class name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-81) javax.management.monitor.Monitor.getObservedObjects() throws
[ http://jira.jboss.com/jira/browse/JBJMX-81?page=comments#action_12314547
]
Adrian Brock commented on JBJMX-81:
---
Didn't you already fix this Scott?
javax.management.monitor.Monitor.getObservedObjects() throws
Key: JBJMX-81
URL: http://jira.jboss.com/jira/browse/JBJMX-81
Project: JBoss JMX
Type: Bug
Reporter: SourceForge User
Assignee: Adrian Brock
SourceForge Submitter: ctday .
When I try to access a StringMonitor MBean through
jmx-console, I get a ClassCastException from
javax.management.monitor.Monitor.getObservedObjects
(). The code in the HEAD of CVS reads:
public ObjectName[] getObservedObjects()
{
Set set = new HashSet(observedObjects.keySet());
elementCount = set.size();
ObjectName[] result = new ObjectName[set.size()];
alreadyNotifieds = new int[set.size()];
int count = 0;
for (Iterator i = set.iterator(); i.hasNext();)
{
ObservedObject object = (ObservedObject) i.next
();
result[count] = object.getObjectName();
alreadyNotifieds[count++] =
object.getAlreadyNotified();
}
return result;
}
The Exception is raised from the (ObservedObject)
i.next, which is an ObjectName, not an ObservedObject.
The error appears to be in the initialization of set. The
keySet of the observedObjects HashMap is being used,
which is a set of ObjectNames, rather than the valueSet
of observedObjects, which is a set of ObservedObjects.
The code has been this way since at least 3.2.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1231) CachedConnectionManager - inUseConnections not correct
[ http://jira.jboss.com/jira/browse/JBAS-1231?page=history ] Adrian Brock closed JBAS-1231: -- Resolution: Done Fix Version: JBossAS-3.2.7 Final CachedConnectionManager - inUseConnections not correct -- Key: JBAS-1231 URL: http://jira.jboss.com/jira/browse/JBAS-1231 Project: JBoss Application Server Type: Bug Components: JCA service Versions: JBossAS-3.2.6 Final Reporter: SourceForge User Assignee: Adrian Brock Fix For: JBossAS-3.2.7 Final SourceForge Submitter: prudrakshala . Environment: Windows XP SP2, JDK 1.4.2_05, JBoss 3.2.6 For CachedConnectionManager service debug option is enabled to monitor connections. !-- Enable connection close debug monitoring -- attribute name=Debugtrue/attribute Using jmx-console, if we look at the inUseCount property. The number displayed is not consitent with the underlying connection pool. listInUseConnections shows stack traces for connections that have been closed long back. It take a long time for the inUseCount to drop down, but never drops to 0 even after the connection pools correctly show inUseCount as 0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBJMX-81) javax.management.monitor.Monitor.getObservedObjects() throws
[ http://jira.jboss.com/jira/browse/JBJMX-81?page=history ]
Scott M Stark resolved JBJMX-81:
Resolution: Done
Fix Version: JBossAS-3.2.7
JBossAS-4.0.1
Yes, this has been fixed in all branches.
javax.management.monitor.Monitor.getObservedObjects() throws
Key: JBJMX-81
URL: http://jira.jboss.com/jira/browse/JBJMX-81
Project: JBoss JMX
Type: Bug
Reporter: SourceForge User
Assignee: Adrian Brock
Fix For: JBossAS-3.2.7, JBossAS-4.0.1
SourceForge Submitter: ctday .
When I try to access a StringMonitor MBean through
jmx-console, I get a ClassCastException from
javax.management.monitor.Monitor.getObservedObjects
(). The code in the HEAD of CVS reads:
public ObjectName[] getObservedObjects()
{
Set set = new HashSet(observedObjects.keySet());
elementCount = set.size();
ObjectName[] result = new ObjectName[set.size()];
alreadyNotifieds = new int[set.size()];
int count = 0;
for (Iterator i = set.iterator(); i.hasNext();)
{
ObservedObject object = (ObservedObject) i.next
();
result[count] = object.getObjectName();
alreadyNotifieds[count++] =
object.getAlreadyNotified();
}
return result;
}
The Exception is raised from the (ObservedObject)
i.next, which is an ObjectName, not an ObservedObject.
The error appears to be in the initialization of set. The
keySet of the observedObjects HashMap is being used,
which is a set of ObjectNames, rather than the valueSet
of observedObjects, which is a set of ObservedObjects.
The code has been this way since at least 3.2.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMQ-102) SpyObjectMessage.setObject(null) throws an Exception
SpyObjectMessage.setObject(null) throws an Exception Key: JBMQ-102 URL: http://jira.jboss.com/jira/browse/JBMQ-102 Project: JBoss MQ Type: Bug Versions: JBossAS-4.0.0, JBossAS-3.2.6 Reporter: Adrian Brock Assigned to: Adrian Brock -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMQ-102) SpyObjectMessage.setObject(null) throws an Exception
[ http://jira.jboss.com/jira/browse/JBMQ-102?page=comments#action_12314545 ] Adrian Brock commented on JBMQ-102: --- It should allow null see JMS1.1 sec 3.1.2 SpyObjectMessage.setObject(null) throws an Exception Key: JBMQ-102 URL: http://jira.jboss.com/jira/browse/JBMQ-102 Project: JBoss MQ Type: Bug Versions: JBossAS-4.0.0, JBossAS-3.2.6 Reporter: Adrian Brock Assignee: Adrian Brock -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss Portal Development] - Re: Build Fails....
Im having similar issues - can i just confirm i understand what i should be doing:- 1) Install JBOSS 4.01 2) Obtain Head revision of Nukes-2 from CVS 3) JBOSS_HOME='D:\jboss-4.0.1' 4) SUN_JAVACC_LIB='D:\jboss_portal_src\thirdparty\sun\javacc' 4) build main I still get the following error ( $ ./build.bat main Executing d:\jboss_portal_src\nukes-2\build\..\tools\bin\ant.bat -logger org.apache.tools.ant.NoBannerLogger main Buildfile: build.xml _buildmagic:init: Trying to override old definition of task property configure-project: [echo] groups: default [echo] modules: format,common,portal,api,portlet,core _buildmagic:modules:most: == == == Executing 'most' in module 'format'... == == BUILD FAILED file:D:/jboss_portal_src/nukes-2/format/build.xml:109: JavaCC home must be a valid directory. obviously not doing something right View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860825#3860825 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860825 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Advanced Heap Protection (patch kinda...)
Hi, I have added a file (streamstore.zip) to the JBoss Mail Services patch page that contains a first whack at a stream store to support the advanced heap protection mechanism specfied on the Wiki. The file contains only new files (i.e. not actually a patch) and all of the additional libraries required to support the store implementations (mysql connector 3.1.5, sleepy cat db, apache commons db). The key interfaces are the Store and the StoreFactory which are stateless interfaces to provide access to the underlying store. InputStream and OutputStream implementations that utilise the store are also provided. There are currently 2 store implementations. One via a jdbc3 style blob, which has been tested with mysql (requires mysql connector 3.1.5 as 3.0 doesn't support in place blob updates). The other uses Sleepycat Berkley DB, which I preferred over a custom file based persistence mechanism. JUnits are supplied for both store implementations. The store is not yet integrated with the implementation of the SMTP Mail object. I will look into doing this after M2 is released. Comments, questions, etc. are welcome. Regards, Mike. P.S. Didn't submit the file as an actual patch as I can't get 'cvs diff' to handle new files. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860826#3860826 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860826 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.307 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050105151954Lbuild.307 BUILD COMPLETE-build.307Date of build:01/05/2005 15:19:54Time to build:19 minutes 7 secondsLast changed:01/05/2005 15:00:50Last log entry:[JBMQ-17] - SpyObjectMessage.setObject(null) should not throw an exception Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(5)1.17.6.1modifiedejortmessaging/src/main/org/jboss/mq/SpyObjectMessage.java[JBMQ-17] - SpyObjectMessage.setObject(null) should not throw an exception1.1.4.1modifiedejortmessaging/src/main/org/jboss/mq/JBossMQXid.java[JBMQ-17] Fix for non serializable XID1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/TransactionRequest.java[JBMQ-17] Fix for non serializable XID1.31.2.2modifiedejortconnector/src/main/org/jboss/resource/connectionmanager/CachedConnectionManager.java[JBAS-1269] - toString called on EJB1.12.2.1modifiedejortcommon/src/main/org/jboss/util/Strings.javaAdd default toString implementation helper
[JBoss-dev] [JBoss Portal Development] - Re: Build fails with JDK 5.0
liteuptoronto wrote : I switched to jdk1.4.2_06 and it builds well. | Just a minor deploy problem upon jboss starts, which is the Mail service. Oh almost forgot, in the wiki, it says the connector for mysql should be placed in | | $JBOSS_HOME/server/standard/deploy, this caused me ClassNotFoundException. I tried putting the jar in | $JBOSS_HOME/server/standard/lib, it resolves the issue. | Thanks for pointing that out. I fixed the wiki topic. The Alpha release should be public at the end of next week. We are working hard on it, documentation, and a featurelist - that will be public before the release. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860831#3860831 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860831 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJCA-12) CachedConnectionManager does not retain EJB context during transaction synchronizations
CachedConnectionManager does not retain EJB context during transaction synchronizations --- Key: JBJCA-12 URL: http://jira.jboss.com/jira/browse/JBJCA-12 Project: JBoss JCA Type: Bug Versions: JBossAS-4.0.1, JBossAS-3.2.6 Reporter: Adrian Brock Assigned to: Adrian Brock The CachedConnectionManager does not maintain the ejb context correctly for transaction synchronizations. If a connection is closed during afterCompletion(), it will use the caller's context to remove the connection from the list of unclosed connections. In fact, it is unsafe to be dealing the ejb context during the transaction interceptor since this is outside the lock interceptor for entity beans meaning it won't be thread safe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.245 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050105170350Lbuild.245 BUILD COMPLETE-build.245Date of build:01/05/2005 17:03:50Time to build:19 minutes 41 secondsLast changed:01/05/2005 15:20:05Last log entry:[JBMQ-102] - SpyObjectMessage.setObject(null) throws an exception Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.13.2.2modifiedejortmessaging/src/main/org/jboss/mq/SpyObjectMessage.java[JBMQ-102] - SpyObjectMessage.setObject(null) throws an exception
[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - In regards to Sun VM bugs 4670071 4699981
...as well as: http://jira.jboss.com/jira/browse/JBJMX-38 I hope you don't think this is a useless rant... ;^) Has there been any indications that Sun will *ever* try to address this bug? I see that these issues have been accepted as bugs, but that was over 2 years ago (and 2 major VM versions ago...) and it's unclear whether they have *any* intention of actually doing anything about it... (i.e. the number of votes it's gotten certainly has't moved them...) Also, in regards to the attempted workaround in JBoss 3.2.3. I don't believe the fix will work in all cases. For example: Suppose there are threads T1, T2 T3 and that T1 is using UCL1 and T2 and T3 are using UCL2. Now suppose T1 and T2 enter into loadClass(...) of UCL1 and UCL2 respectively (hence obtaining their locks). Now if T3 needs to load a class with UCL2 it will be blocked in the VM before even getting into UCL2 loadClass (or loadClassInternal for that matter because it seems the VM obtains the CL lock even before calling into loadClassInternal...). If UCL1 and UCL2 need to delegate to each other in T1 and T2, then it's possible for UCL2 to give up its lock thereby allowing T3 to acquire the lock and have the VM throw the ClassCircularityError (if T2 was in the middle of loading class Foo that T3 was also trying to load before it was blocked...). T3 is then an innocent bystander in this scenario. I believe the attempted fix assumes that the CCE occurs within the context of a UCL.loadClass(...) reentrant call. We have been plagued by random ClassCircularityErrors at startup of our server (we've used versions 3.0.8 and 3.2.3) and having evaluated the UCL code and the attempted workarounds to the VM bug, I believe the above scenario is a likely explaination. Do this assessment sound correct? If so, then I'm not sure that anything can be done about this at the UCL level as it seems there's always the possibility for an innocent bystander thread to get a CCE before the UCL has even been entered. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860837#3860837 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860837 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.664 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050105155716Lbuild.664 BUILD COMPLETE-build.664Date of build:01/05/2005 15:57:16Time to build:23 minutes 33 secondsLast changed:01/05/2005 15:30:09Last log entry:JBREM-26: Added ability to use MBeans as invocation handlers. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(15)1.1addedtelrodremoting/tests/src/org/jboss/remoting/handler/mbean/ClientTest.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.1addedtelrodremoting/tests/src/org/jboss/remoting/handler/mbean/MBeanHandler.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.1addedtelrodremoting/tests/src/org/jboss/remoting/handler/mbean/MBeanHandlerMBean.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.1addedtelrodremoting/tests/src/org/jboss/remoting/handler/mbean/MBeanHandlerTestCase.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.1addedtelrodremoting/tests/src/org/jboss/remoting/handler/mbean/ServerTest.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.18modifiedtelrodremoting/src/main/org/jboss/remoting/transport/Connector.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.3modifiedtelrodremoting/src/main/org/jboss/remoting/transport/http/HTTPServerInvoker.javaJBREM-26: Added ability to use MBeans as invocation handlers.1.2modifiedejortmessaging/src/main/org/jboss/mq/JBossMQXid.java[JBMQ-17] - Fix for non serializable XID implementations1.4modifiedejortmessaging/src/main/org/jboss/mq/TransactionRequest.java[JBMQ-17] - Fix for non serializable XID implementations1.18modifiedejortmessaging/src/main/org/jboss/mq/SpyObjectMessage.java[JBMQ-102] - SpyObjectMessage.setObject(null) throws Exception1.33modifiedejortconnector/src/main/org/jboss/resource/connectionmanager/CachedConnectionManager.java[JBAS-1269] - toString called on EJB1.14modifiedejortcommon/src/main/org/jboss/util/Strings.javaDefault toString() implementation helper1.1addedosdchicagowebservice/test/java/org/jboss/test/ws/tools/WSDL20ToJavaTestCase.javaTestcase to convert wsdl 2.0 to java1.3modifiedtdieslerwebservice/docs/project/en/master.xmlAdd JAXB integration1.1addedtdieslerwebservice/docs/project/en/modules/jaxb_integration.xmlAdd JAXB integration
[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - Re: In regards to Sun VM bugs 4670071 4699981
No, there has been no indication that this will be fixed. There was some additional simplification in 3.2.5 and 3.2.6 that further reduced the CCE problem, but there are still scenarios where it can occur. The workaround in that case is to simply preload the classes to avoid multiple threads trying to define the same classes. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860839#3860839 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860839 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBJCA-12) CachedConnectionManager does not retain EJB context during transaction synchronizations
[ http://jira.jboss.com/jira/browse/JBJCA-12?page=history ] Adrian Brock updated JBJCA-12: -- Description: The CachedConnectionManager does not maintain the ejb context correctly for transaction synchronizations. If a connection is closed during afterCompletion(), it will use the caller's context to remove the connection from the list of unclosed connections. In fact, it is unsafe to be dealing with the ejb context during the transaction interceptor since this is outside the lock interceptor for entity beans meaning it won't be thread safe. was: The CachedConnectionManager does not maintain the ejb context correctly for transaction synchronizations. If a connection is closed during afterCompletion(), it will use the caller's context to remove the connection from the list of unclosed connections. In fact, it is unsafe to be dealing the ejb context during the transaction interceptor since this is outside the lock interceptor for entity beans meaning it won't be thread safe. CachedConnectionManager does not retain EJB context during transaction synchronizations --- Key: JBJCA-12 URL: http://jira.jboss.com/jira/browse/JBJCA-12 Project: JBoss JCA Type: Bug Versions: JBossAS-4.0.1, JBossAS-3.2.6 Reporter: Adrian Brock Assignee: Adrian Brock The CachedConnectionManager does not maintain the ejb context correctly for transaction synchronizations. If a connection is closed during afterCompletion(), it will use the caller's context to remove the connection from the list of unclosed connections. In fact, it is unsafe to be dealing with the ejb context during the transaction interceptor since this is outside the lock interceptor for entity beans meaning it won't be thread safe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-41) jmx.test.SecureJMXInvokerUnitTestCase failure
[ http://jira.jboss.com/jira/browse/JBAS-41?page=history ] Scott M Stark resolved JBAS-41: --- Resolution: Done It was another NoSuchMethodError due to an inner class invoking sendNotification through InvokerTest.this. jmx.test.SecureJMXInvokerUnitTestCase failure - Key: JBAS-41 URL: http://jira.jboss.com/jira/browse/JBAS-41 Project: JBoss Application Server Type: Bug Components: JMX Versions: JBossAS-3.2.7 Final Environment: [EMAIL PROTECTED] case2471]$ $JAVA_HOME/bin/java -version java version 1.3.1_14 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_14-b03) Java HotSpot(TM) Client VM (build 1.3.1_14-b03, mixed mode) Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-3.2.7 Final Original Estimate: 2 hours Remaining: 2 hours There is a failure to receive remote notifications in the org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase when running under jdk 1.3.1_14. testcase classname=org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase name=testNotification time=15.062 failure message=Received 10 notifications, count=0 type=junit.framework.AssertionFailedErrorjunit.framework.AssertionFailedError: Received 10 notifications, count=0 at org.jboss.test.jmx.test.JMXInvokerUnitTestCase.testNotification(JMXInvokerUnitTestCase.java:123) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) /failure /testcase -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1260) Http session clustering throws NPE under load
[ http://jira.jboss.com/jira/browse/JBAS-1260?page=comments#action_12314552 ] Scott M Stark commented on JBAS-1260: - I don't see any checkin for this on the 3.2 branch. Is it still outstanding? Http session clustering throws NPE under load - Key: JBAS-1260 URL: http://jira.jboss.com/jira/browse/JBAS-1260 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-3.2.6 Final Reporter: Ben Wang Assignee: Ben Wang Priority: Minor Fix For: JBossAS-3.2.7 Final Original Estimate: 1 hour Remaining: 1 hour A customer reports (https://na1.salesforce.com/5003000ZG7i) Tomcat http session replication throws NPE under load. Here is the example trace: 15:59:10,424 ERROR [JBossCacheManager] processExpires: failed with exception: java.lang.NullPointerException 15:59:10,425 INFO [STDOUT] java.lang.NullPointerException 15:59:10,426 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossCacheManager.processExpires(JBossCacheManager.java:436) 15:59:10,426 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossManager.backgroundProcess(JBossManager.java:644) 15:59:10,427 INFO [STDOUT] at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:4647) 15:59:10,427 INFO [STDOUT] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1619) 15:59:10,427 INFO [STDOUT] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1628) 15:59:10,428 INFO [STDOUT] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1628) 15:59:10,428 INFO [STDOUT] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1608) 15:59:10,428 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=comments#action_12314553 ] Daniel Ramagem commented on JBMQ-17: I have verified that the attached source code works succesfully for IBM WebSphere Application Server 5.0.2. Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Fix For: 5.0 Alpha, JBossAS-3.2.7, JBossAS-4.0.2RC1 Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMQ-17) Fix for Use of Non-Serializable Xid Implementations
[ http://jira.jboss.com/jira/browse/JBMQ-17?page=comments#action_12314554 ] Adrian Brock commented on JBMQ-17: -- Thanks, Adrian Fix for Use of Non-Serializable Xid Implementations --- Key: JBMQ-17 URL: http://jira.jboss.com/jira/browse/JBMQ-17 Project: JBoss MQ Type: Patch Components: Transport, Persistence Versions: JBossAS-4.0.1 Environment: WebSphere Application Server 5.0.2 Reporter: Daniel Ramagem Assignee: Adrian Brock Fix For: 5.0 Alpha, JBossAS-3.2.7, JBossAS-4.0.2RC1 Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java, TransactionRequest.java.diff A java.io.NotSerializableException is thrown when using JBossMQ as a transactional Generic JMS Provider under IBM WebSphere Application Server 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes the SpyXAResourceManager.prepare(...) method to fail. The solution is to: 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid wrapper: JBossMQXid.java. 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be modified to perform the wrapping 3) The JBossMQXid class must now be available under both client and server. I think the packaging jboss-3.2.6-src product needs to be modified so that upon a build the JBossMQXid class gets made available in the jbossmq server (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: Advanced Heap Protection (patch kinda...)
Wow! I didn't expect this yet! Excellent. Sleepycat is a better idea. That's fine, in the case of new files directory preserving zips are preferred. Its still best if existing files are -u patches. Please don't be discouraged that these aren't being committed in real time. I'll branch CVS in the next few days. I'm very excited about your contributions and don't let me slow you down. -Andy View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860838#3860838 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860838 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1266) Create jboss-pojoserver module alias
[ http://jira.jboss.com/jira/browse/JBAS-1266?page=comments#action_12314555 ] Adrian Brock commented on JBAS-1266: The basics of this have been done. You can checkout jboss-pojo. This will checkout modules a subset of the modules from jboss-head with the following exceptions: 1) build comes from build/pojo in cvs 2) jmx comes from jmx2 in cvs 3) system comes from system2 in cvs TODO: 1) There is obviously a lot more that can be trimmed, but this would require some restructering of the project dependencies. 2) I have made no attempt to trim thirdparty. But I have created a separate alias jboss-pojo-thirdparty so this can be done or new jars added without affecting head. 3) I haven't updated the eclipse.psf 4) The build/build.xml only builds a subset of the checked out modules, e.g. ejb3 is not built (it was not built in jboss-head either) Create jboss-pojoserver module alias Key: JBAS-1266 URL: http://jira.jboss.com/jira/browse/JBAS-1266 Project: JBoss Application Server Type: Task Components: Build System Reporter: Scott M Stark Assignee: Adrian Brock Fix For: JBossPOJOServer-1.0 Alpha We need to create jboss-pojoserver module alias that allows us to work on the JBossPOJOServer release without impacting the existing jboss-head development. The associated forum reference contains background discussion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of POJO Server] - Re: CVS
The basics of this have been done, see the task for further work that can be done. Use cvs ... co jboss-pojo Be careful when modifying thirdparty and tools. They are shared with jboss-head for now. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860841#3860841 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860841 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Deployers overview
This is definition document so I don't have to repeat everything on the JIRA tasks DEPLOYER-OVERVIEW - The deployer architecture is made up of the following components: VDF - Virtual Deployment Framework The VDF works to abstract deployments meaning the deployers don't have to deal with the physical structure/protocol of the deployments. It is responsible for abstracting away: packed/unpacked deployments copying remote/nested deployments to a temp location supplying logical urls for users/config/codebase-protectiondomain/etc supplying physical urls for classloading/debugging/etc VDF Context A VDF context identifies a deployment/subdeployment holding the information that is identifed by the structural component deployers. Deployer A deployer is made up two components. 1) A structural component that says it recognises a particular deployment and deconstructs the deployment into its VDF contexts. 2) A deployment component that looks at the deployment and constructs the objects. MainDeployer Like the current main deployer it is reponsible for deploy(URL) and undeploy(URL). It also serves as a registry for the other deployers. MicroContainer Any bean that implements the Deployer interface will be registered/unregistered with the MainDeployer as it is instantiated. Since the structural components have no dependencies they can be instantiated early and the deployments identified. Deployment Chains Both the structural and deployment components of the deployers are stored inside the MainDeployer registry as a chain in a priority order. Structural Chain For the structural chain, the first deployer in priority order to recognise the deployer wins. All deployments/subdeployments must be structurally recognised before the deployment chain is processed. Deployment Chain Each deployer gets to process the deployment in the priority order. The chain is processed depth first, i.e. priority order over all deployments/subdeployments before moving to the next in the chain Structural Component More Detail To construct the VDF context the structural component must be able to identify: 1) The set of urls that make up the deployment classpath 2) The location of the metadata, e.g. META-INF, WEB-INF, etc. 3) The set of possible subdeployments Deployment Component More Detail This does the job of deployment for this VDF context (not subcontexts/deployments). We want to aim to use the deployment specific metadata to create microcontainer metadata that can be installed (instantiated/configured) according to dependencies. But there are thirdparty components where complete control of the construction/config is not under IOC/microcontainer control RAW Deployers Classloading JAR Bean Classloading Deployer This has no structural component. It forms the highest priority (first) deployment component since very little else can be done reliably until the classes are available. It takes it info from the urls identified by the structural deployments in the VDF contexts. JAR Deployer This is the lowest priority (last) structural component. It takes jars/zips and top level directories (not sub deployments) and adds the url to the VDF context for classloading. There is no deployment component. Bean Deployer The priority of this deployer is unimportant. Structural component It takes .bean with a (META-INF/jboss-bean.xml) or plain -bean.xml files that contain raw microcontainer config in xml format. It identifies the root of the .bean archive (or expanded deployment) as the classloader url. Any file in the root of the .bean is eligible as a subdeployment. Deployment component Parses the -bean.xml and installs it into the microcontainer Profile A profile serves as a collection of deployments. The simplest implementation is the current JBoss directory structure, i.e. a static config and a hot deploy config. A more useful implementation for production is a versioned/persistent list of deployments. The profile feeds URLs to the main deployer. Other Deployers SAR RAR EJB2 EJB3 EAR -ds.xml WAR BSH Hot Deployment Profile The hot deployment profile will need the mechanisms to order deployments like current JBoss View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860842#3860842 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860842 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-5) Main Deployer
Main Deployer - Key: JBMICROCONT-5 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-5 Project: JBoss MicroContainer Type: Task Components: Deployment Reporter: Adrian Brock Fix For: JBossMC_1_0_0M2 MainDeployer The primary methods of MainDeployer are (re/un)deploy(URL) other methods are (un)register/register(deployer, priority) which will be used by the microcontainer when a deployer is installed stats based methods that expose information from the VDF and config/constructors methods for things like the VDF and initial deployers. deploy(url) 1) create a skeleton VDF context for the top level deployment 2) ask the structural component chain who recognises it repeat recursively for identified subcontexts 3) invoke down the deployment component chain starting with the deepest subcontexts first redeploy(url) similar to deploy() but performing a reinstall on the microcontainer (i.e. suspend on valve for components being reinstalled) undeploy(url) invoke down the deployment chain in reverse order to remove the installed components Reverse order means both in terms of subcontexts and priority. (un)register/register(deployer) The deployer here identifies the structural and deployment components of the deployer and their respective priorities. This will be the name in the registry which might be instantiated later. Where present, the deployer is added to the relevent chain. ISSUE: Need to tighten up the semantics of the register/unregister(deployer) for when the deployment component has dependencies and cannot be instantiated immediately -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-10) Simple Profiles for testing purposes
Simple Profiles for testing purposes Key: JBMICROCONT-10 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-10 Project: JBoss MicroContainer Type: Task Components: Deployment Reporter: Adrian Brock Fix For: JBossMC_1_0_0M2 Simple Profile -- For initial testing we need a simple profile that takes identifies a list of deployments and passes them to the MainDeployer Backwards Compatibility Profile --- This will work like old jboss i.e. processing similar to statically deploying the conf folder, conf/jboss-service.xml and the deployment scanner farm and deploy-singleton are irrelvent since these will be handled by tags inside the microcontainer metadata IDE Profile --- TODO - Need to synch with JBoss IDE Versioned/Persistent Profile TODO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: Deployers overview
Add some tasks for the deployer framework: http://jira.jboss.com/jira/browse/JBMICROCONT-5 http://jira.jboss.com/jira/browse/JBMICROCONT-6 http://jira.jboss.com/jira/browse/JBMICROCONT-7 http://jira.jboss.com/jira/browse/JBMICROCONT-8 http://jira.jboss.com/jira/browse/JBMICROCONT-9 http://jira.jboss.com/jira/browse/JBMICROCONT-10 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860844#3860844 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860844 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
