[JBoss-dev] [JBoss JIRA] Created: (JBAS-1664) Unloaded entities returned in low memory conditions
Unloaded entities returned in low memory conditions --- Key: JBAS-1664 URL: http://jira.jboss.com/jira/browse/JBAS-1664 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-3.2.6 Final Reporter: Arto Huusko In low memory conditions (that is, when OutOfMemoryExceptions are seen frequently all over the place), JBoss can behave wrong in a way that is critically wrong. I have seen on several occasions that a finder returns an entity with the correct identity, but where ejbLoad() has either not been called at all, or where ejbLoad() has failed at some point (I have no way of knowing which is the case). I have observed this behaviour only with BMP beans (and so there is a possibility that I am doing something wrong in the BMP code, but I doubt this). However, the fact that I haven't seen this with CMP beans may be just because CMP beans work differently, or just plain luck. When this occurs, the wrong behaviour can be seen because the instance variables of the entity bean contain what ever they had when the entity instance was previously attached to some other identity. For example, I may store the primary key of the entity in some instance variable. Let's say I can access the primary key via method "Long getMyPrimaryKey()". If the finder returns an entity with the correct identity (what I asked for in the finder call), but where ejbLoad() is not called or it fails, then entity.getMyPrimaryKey().equals(entity.getPrimaryKey()) is false. And this is exactly what I have seen. I have no idea where the problem is, and, as I said above, it may be a problem with my code. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1663) unsetEntityContext never called
unsetEntityContext never called
---
Key: JBAS-1663
URL: http://jira.jboss.com/jira/browse/JBAS-1663
Project: JBoss Application Server
Type: Bug
Components: EJBs
Versions: JBossAS-3.2.6 Final
Reporter: Arto Huusko
When entity instances are discarded, according to EJB 2.1 unsetEntityContext()
should be called (although, for some reason, this is not mentioned in Container
Provider Responsibilities, section 10.5.2 makes it quite clear that bean
providers may rely on unsetEntityContext() being called). As far as I can see
(and have tested slightly), unsetEntityContext() is never called in JBoss.
The problem can be seen in org.jboss.ejb.plugins.AbstractInstancePool.free():
if the pool is full, nothing spectacular is done; the entity instance is simply
left alone, which causes it to be GC at some time.
I believe, this code should be in the method:
// this already is there
if (pool.size() < maxSize)
{
pool.addFirst(ctx);
}
// add something like this
else
{
ctx.discard();
}
--
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
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.329 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050406011756Lbuild.329 BUILD COMPLETE - build.329Date of build: 04/06/2005 01:17:56Time to build: 20 minutes 56 secondsLast changed: 04/05/2005 23:59:11Last log entry: Remove the jdk1.4 exception initCause method usage Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.1.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/SecurityContextBean.javaRemove the jdk1.4 exception initCause method usage
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1662) Memory leak with SpecCompliant=true in transaction-service.xml
Memory leak with SpecCompliant=true in transaction-service.xml -- Key: JBAS-1662 URL: http://jira.jboss.com/jira/browse/JBAS-1662 Project: JBoss Application Server Type: Bug Components: Transaction Manager service Versions: JBossAS-3.2.6 Final Environment: jboss 3.2.6, linux 2.[46], DB2 7.[12] Reporter: Arto Huusko If SpecCompliant is set to true in transaction-service.xml, jboss begins to leak memory on a massive scale: all entity beans (both CMP and BMP) that become unused (that is: they are flushed from cache, and instance pool is full, so they are discarded) are never garbage collected. I don't pretend to understand the problem fully (I was in quite a rush to solve the memory leaks and it still took me over a week). I investigated the matter with a home-grown memory profiler, and found out that the leak ultimately occurs in org.jboss.resource.connectionmanager.CachedConnectionManager, which never releases the KeyConnectionAssociation objects (that are stored in a ThreadLocal LinkedList). And since KeyConnectionAssociation also holds a reference to the entity object, the entity objects leak once they are thrown out of the pool. And those KeyConnectionAssociation objects are of course created as a result of the entity beans opening connection to the database. I never found out why the KeyConnectionAssociation objects were never removed from the list (which would have resulted in garbage collection of the entity and all). I just saw somewhere in the code promising references to SpecCompliant, and thankfully it solved the problem for me. Note that leakage also occurs (immediately) if JBoss gets an entity from instance pool to run a finder, and the finder throws an exception. In that case, the entity used to run the finder is leaked immediately (the leakage happens in the same way as outlined above). I marked this problem for 3.2.6, but as far as I can see, the problem is the same in 3.2.7 and 4, too. Maybe priority should really be "minor", since I'm not sure that many people use SpecCompliant. Oh, and I also have Debug=true in transaction-service, if that makes any difference. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1649) Write OTS wrappers
[ http://jira.jboss.com/jira/browse/JBAS-1649?page=history ] Francisco Reverbel resolved JBAS-1649: -- Resolution: Done > Write OTS wrappers > -- > > Key: JBAS-1649 > URL: http://jira.jboss.com/jira/browse/JBAS-1649 > Project: JBoss Application Server > Type: Sub-task > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > Write some trivial OTS wrappers that implement the DTM interfaces by > delegating the work to OTS objects. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1648) Complete the existing implementation of the OTS interfaces
[ http://jira.jboss.com/jira/browse/JBAS-1648?page=history ] Francisco Reverbel resolved JBAS-1648: -- Resolution: Done > Complete the existing implementation of the OTS interfaces > -- > > Key: JBAS-1648 > URL: http://jira.jboss.com/jira/browse/JBAS-1648 > Project: JBoss Application Server > Type: Sub-task > Components: Transaction Manager service > Versions: JBossAS-5.0 Alpha > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > The existing OTS servant does not yet implements register_resource, recreate, > and replay_completion. The implementation of those methods will delegate the > actual work to the TransactionImpl instance the represents the transaction. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces
[ http://jira.jboss.com/jira/browse/JBAS-1647?page=history ] Francisco Reverbel resolved JBAS-1647: -- Resolution: Done > Provide JBoss remoting-based implementations of the DTM interfaces > -- > > Key: JBAS-1647 > URL: http://jira.jboss.com/jira/browse/JBAS-1647 > Project: JBoss Application Server > Type: Sub-task > Components: Transaction Manager service > Versions: JBossAS-5.0 Alpha > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > The implementations will delegate the actual work to TransactionImpl > instances. Besides the similarity in their interfaces, remoting-based DTM > objects (Resource, Coordinator, etc.) must be similar to OTS objects also in > that their references (proxies) are convertible to strings and vice-versa. > This will be needed for logging. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1646) Define OTS-like interfaces for the DTM
[ http://jira.jboss.com/jira/browse/JBAS-1646?page=history ] Francisco Reverbel resolved JBAS-1646: -- Resolution: Done > Define OTS-like interfaces for the DTM > -- > > Key: JBAS-1646 > URL: http://jira.jboss.com/jira/browse/JBAS-1646 > Project: JBoss Application Server > Type: Sub-task > Components: Transaction Manager service > Versions: JBossAS-5.0 Alpha > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > Define OTS-like interfaces for the following DTM objects associated with a > given transaction: Terminator, Coordinator, Resource, Synchronization, and > RecoveryCoordinator. These interfaces allow those objects to be manipulated > in a unified way, regardless of whether they are accessible via JBoss > remoting or via CORBA/IIOP. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1661) Test recovery
Test recovery - Key: JBAS-1661 URL: http://jira.jboss.com/jira/browse/JBAS-1661 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel This task will be split in several sub-tasks. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1660) Implement recovery for the distributed case
Implement recovery for the distributed case --- Key: JBAS-1660 URL: http://jira.jboss.com/jira/browse/JBAS-1660 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1659) Implement write-ahead logging for the distributed case
Implement write-ahead logging for the distributed case -- Key: JBAS-1659 URL: http://jira.jboss.com/jira/browse/JBAS-1659 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Resource and RecoveryCoordinator references must be logged. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1658) Change LocalId/GlobalId/Xid generation
Change LocalId/GlobalId/Xid generation -- Key: JBAS-1658 URL: http://jira.jboss.com/jira/browse/JBAS-1658 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Change the LocalId/GlobalId/Xid generation strategy so that the nextLocalId is not reset to 0 at server startup. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1657) Preliminary UserTransaction and 2PC tests
Preliminary UserTransaction and 2PC tests - Key: JBAS-1657 URL: http://jira.jboss.com/jira/browse/JBAS-1657 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Preliminary tests, still with no logging/recovery. Test UserTransaction over JBoss remoting. (UserTransaction over IIOP is already in place and has its own testcase.) Test 2PC across DTM Resources (either remoting-based and OTS-based) and XA resources. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1656) Implement UserTransaction over JBoss remoting
Implement UserTransaction over JBoss remoting - Key: JBAS-1656 URL: http://jira.jboss.com/jira/browse/JBAS-1656 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Profiler] - New DLL/SO release under CVS
I just compiled a new release for Linux and Windows. It's under CVS for now. If requested I can upload these version in some temporary place until we get a final release. Here is the release notes: Release Notes - JBoss Profiler - Version JBossProfiler-1.1 ** Feature Request * [JBPROFILER-2] - basic version of front-end plugin to Eclipse * [JBPROFILER-13] - Disable Object creation/releases by runtime parameter * [JBPROFILER-14] - Only open new thread files when capturing is activated ** Bug * [JBPROFILER-10] - Generate error messages for invalid initialization options View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872818#3872818 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872818 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1655) Add to TransactionImpl a method that enlists a DTM Resource...
Add to TransactionImpl a method that enlists a DTM Resource... -- Key: JBAS-1655 URL: http://jira.jboss.com/jira/browse/JBAS-1655 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Ensure that TransactionImpl has methods that do the actual work for all OTS/DTM objects and for XATerminator. Most of the needed methods already are in place, but some need to be added (e.g., a method to enlist a DTM Resource). -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1654) Extend TransactionImpl
Extend TransactionImpl -- Key: JBAS-1654 URL: http://jira.jboss.com/jira/browse/JBAS-1654 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Extend TransactionImpl so that it knows about the following DTM objects: Coordinator, Resource, and RecoveryCoordinator. Besides having a list of XA resources, a TransactionImpl instance will have a list of DTM Resources, each of which represents either a JBoss remoting-based resource or a (properly wrapped) OTS resource. It may also have a parent coordinator, which will be a DTM Coordinator (either a remoting-based coordinator or an OTS coordinator). If if has a parent coordinator, it must register itself as a Resource with that coordinator. The TransactionImpl must drive the 2PC across all XA resources and DTM resources. Logging and recovery are not included in this step. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ 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.90 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050406000633Lbuild.90 BUILD COMPLETE - build.90Date of build: 04/06/2005 00:06:33Time to build: 30 minutes 32 secondsLast changed: 04/05/2005 23:59:11Last log entry: Remove the jdk1.4 exception initCause method usage Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (81)1.1.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/SecurityContextBean.javaRemove the jdk1.4 exception initCause method usage1.24.2.9modifiedbwang00cache/src/main/org/jboss/cache/Node.javaFixed on 1.31.79.2.20modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaComptabile with 1.31.1.2.4modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/local/ConcurrentTransactionalUnitTestCase.javaBackporting from 1.2.21.3.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting from 1.2.21.12.2.7modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting from 1.2.21.10.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/NonBlockingWriterLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleLock.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/TimeoutException.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/lock/UpgradeException.javaBackporting from 1.2.21.3.2.8modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyNone.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadCommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting from 1.2.21.1.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/LockingException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting from 1.2.21.1.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategy.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/DeadlockException.javaBackporting from 1.2.21.2.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting from 1.2.21.13.4.3modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting from 1.2.21.4.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/SharedStoreCacheLoader.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoaderAop.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting from 1.2.21.11.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting from 1.2.21.13.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/JDBCCacheLoader.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting from 1.2.21.1.4.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/Interceptor.javaBackporting from 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/interceptors/LockInterceptor.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/OrderedSynchronizationHandler.javaBackporting from 1.2.21.6.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/ReplicationInterceptor.javaBackporting fro
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1653) Review TransactionImpl
Review TransactionImpl -- Key: JBAS-1653 URL: http://jira.jboss.com/jira/browse/JBAS-1653 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Review TransactionImpl with respect to LocalId/GlobalId association and transaction importing. An imported transaction should have a LocalId just like a non-imported one. (The local id is embedded into the CORBA references or into the JBoss remoting-based proxies for the transaction Coordinator, Terminator, etc.) -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1651) Make the TPC factory/importer/exporter configurable
[ http://jira.jboss.com/jira/browse/JBAS-1651?page=history ] Francisco Reverbel updated JBAS-1651: - Assign To: Francisco Reverbel Security Level: (was: Public) > Make the TPC factory/importer/exporter configurable > --- > > Key: JBAS-1651 > URL: http://jira.jboss.com/jira/browse/JBAS-1651 > Project: JBoss Application Server > Type: Sub-task > Components: Transaction Manager service > Versions: JBossAS-5.0 Alpha > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > Make the TPC factory/importer/exporter configurable so that the full context > (GlobalId + Coordinator reference) is propagated only if the DTM is actually > used (no additional overhead for DTMless server configs). -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1652) Propagate OTS context in IIOP invocations from the JBoss server
Propagate OTS context in IIOP invocations from the JBoss server --- Key: JBAS-1652 URL: http://jira.jboss.com/jira/browse/JBAS-1652 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Propagate the OTS context along with invocations issued by the JBoss server. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1651) Make the TPC factory/importer/exporter configurable
Make the TPC factory/importer/exporter configurable --- Key: JBAS-1651 URL: http://jira.jboss.com/jira/browse/JBAS-1651 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Make the TPC factory/importer/exporter configurable so that the full context (GlobalId + Coordinator reference) is propagated only if the DTM is actually used (no additional overhead for DTMless server configs). -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1650) Propagate full tx context along with JBoss remoting invocations
Propagate full tx context along with JBoss remoting invocations --- Key: JBAS-1650 URL: http://jira.jboss.com/jira/browse/JBAS-1650 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Enlarge the transaction context propagated along with JBoss remoting invocations. The current context has only a GlobalId/Xid, it must include also a Coordinator reference. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1649) Write OTS wrappers
[ http://jira.jboss.com/jira/browse/JBAS-1649?page=history ] Francisco Reverbel updated JBAS-1649: - Description: Write some trivial OTS wrappers that implement the DTM interfaces by delegating the work to OTS objects. Environment: Security Level: (was: Public) > Write OTS wrappers > -- > > Key: JBAS-1649 > URL: http://jira.jboss.com/jira/browse/JBAS-1649 > Project: JBoss Application Server > Type: Sub-task > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > Write some trivial OTS wrappers that implement the DTM interfaces by > delegating the work to OTS objects. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1649) Write OTS wrappers
Write OTS wrappers -- Key: JBAS-1649 URL: http://jira.jboss.com/jira/browse/JBAS-1649 Project: JBoss Application Server Type: Sub-task Reporter: Francisco Reverbel Assigned to: Francisco Reverbel -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1648) Complete the existing implementation of the OTS interfaces
Complete the existing implementation of the OTS interfaces -- Key: JBAS-1648 URL: http://jira.jboss.com/jira/browse/JBAS-1648 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel The existing OTS servant does not yet implements register_resource, recreate, and replay_completion. The implementation of those methods will delegate the actual work to the TransactionImpl instance the represents the transaction. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces
[ http://jira.jboss.com/jira/browse/JBAS-1647?page=history ] Francisco Reverbel updated JBAS-1647: - Assign To: Francisco Reverbel Security Level: (was: Public) > Provide JBoss remoting-based implementations of the DTM interfaces > -- > > Key: JBAS-1647 > URL: http://jira.jboss.com/jira/browse/JBAS-1647 > Project: JBoss Application Server > Type: Sub-task > Components: Transaction Manager service > Versions: JBossAS-5.0 Alpha > Reporter: Francisco Reverbel > Assignee: Francisco Reverbel > > > The implementations will delegate the actual work to TransactionImpl > instances. Besides the similarity in their interfaces, remoting-based DTM > objects (Resource, Coordinator, etc.) must be similar to OTS objects also in > that their references (proxies) are convertible to strings and vice-versa. > This will be needed for logging. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces
Provide JBoss remoting-based implementations of the DTM interfaces -- Key: JBAS-1647 URL: http://jira.jboss.com/jira/browse/JBAS-1647 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel The implementations will delegate the actual work to TransactionImpl instances. Besides the similarity in their interfaces, remoting-based DTM objects (Resource, Coordinator, etc.) must be similar to OTS objects also in that their references (proxies) are convertible to strings and vice-versa. This will be needed for logging. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1646) Define OTS-like interfaces for the DTM
Define OTS-like interfaces for the DTM -- Key: JBAS-1646 URL: http://jira.jboss.com/jira/browse/JBAS-1646 Project: JBoss Application Server Type: Sub-task Components: Transaction Manager service Versions: JBossAS-5.0 Alpha Reporter: Francisco Reverbel Assigned to: Francisco Reverbel Define OTS-like interfaces for the following DTM objects associated with a given transaction: Terminator, Coordinator, Resource, Synchronization, and RecoveryCoordinator. These interfaces allow those objects to be manipulated in a unified way, regardless of whether they are accessible via JBoss remoting or via CORBA/IIOP. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.476 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050405233458Lbuild.476 BUILD COMPLETE - build.476Date of build: 04/05/2005 23:34:58Time to build: 17 minutes 0 secondsLast changed: 04/05/2005 23:07:59Last log entry: Preserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-157 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (10)1.13.4.4modifiednihilitywebservice/src/resources/META-INF/jboss-service.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.18.2.13modifiednihilitywebservice/src/main/org/jboss/webservice/ServiceDeployer.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.19.4.4modifiednihilitywebservice/src/main/org/jboss/webservice/metadata/WebserviceDescriptionMetaData.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.2modifiednihilitytestsuite/src/resources/webservice/wsdlimport/absolute/WEB-INF/wsdl/Hello.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.1.1.4.3modifiednihilitytestsuite/src/resources/webservice/wsdlimport/simplefile/SimpleFile.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.35.4.12modifiednihilitywebservice/src/main/org/jboss/webservice/AxisService.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.2modifiednihilitytestsuite/src/resources/webservice/jbws153/WEB-INF/wsdl/OrderSOAP.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.1.1.4.2modifiednihilitytestsuite/src/resources/webservice/ws4eesimple/META-INF/wsdl/Hello.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.9.2.65modifiednihilitytestsuite/imports/test-jars.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.11modifiednihilitytestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaFix ws compare issues between platforms with different line endings
[JBoss-dev] jboss-3.2-testsuite build.103 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log2005040502Lbuild.103 BUILD COMPLETE - build.103Date of build: 04/05/2005 22:22:02Time to build: 64 minutes 31 secondsLast changed: 04/05/2005 15:24:24Last log entry: Fixed on 1.3 Unit Tests: (1967) Total Errors and Failures: (10)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestFederatedorg.jboss.test.jbossnet.external.ExternalUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestStatefulPassiviationExpirationorg.jboss.test.testbeancluster.test.BeanUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (2)1.24.2.9modifiedbwang00cache/src/main/org/jboss/cache/Node.javaFixed on 1.31.79.2.20modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaComptabile with 1.3
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1283) Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for Webapp
[ http://jira.jboss.com/jira/browse/JBAS-1283?page=comments#action_12316709 ] Scott M Stark commented on JBAS-1283: - Attach an example that illustrates your particular xml override scenario as I have tested being able to override the xml parser implementation in 4.0.2RC1 and it works as expected. There are some classes that cannot be overriden such as commons-logging currently, but the xml parser is not one of them. > Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for > Webapp > - > > Key: JBAS-1283 > URL: http://jira.jboss.com/jira/browse/JBAS-1283 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-3.2.6 Final > Environment: Stock JBoss 3.2.6 running on Linux (kernel 2.4.26), Sun JDK and > JRE version 1.4.2_04 > Reporter: Jeremy Brown > Assignee: Anil Saldhana > Priority: Minor > Attachments: test.war > > > See my initial forum post at > "http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861452#3861452";. > The dom4j libs provided by JBoss do not work correctly with my web > application, so I attempted to configure my webapp's "jboss-web.xml"--as per > the wiki page at > "http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration"--so that > my webapp would essentially be in a different classloader namspace and would > be able to override the server dom4j implementation with its own. Now, > Tomcat bails out during JSP compilation with a dom4j-related > ClassCastException, leading me to believe there might some problem with the > sort of setup I'm trying to attempt...for example, Tomcat's JSP compiler > might be trying to link with the dom4j in my application's namespace while > its classes have been loaded next to (and probably are already using) dom4j > in the server namespace. > I'll attach a .war file exhibiting this behavior to this bug report. > Here's the specific exception for this .war file: > java.lang.ClassCastException > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) > at > org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:91) > at > org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:70) > at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:188) > at > org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:240) > at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:160) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) > at > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:158) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
This is why the JBossXB framework needs to be adopted. Alexey already has the basis for this as one of the JBossXB testcases. The processing of the mbean deployment info could then be extracted out and even put into a xmbean interceptor that placed the deployment metadata into the DeploymentInfo context. The problem I had with the solution Dimtris came up with was with the LoginConfigInterceptor specifically, not the more general ability to add interceptors which was fine. A generalization which would improve the extensibility of the deployer configuration is described in this thread, but its not necessary to this discussion. http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864275#3864275 Maybe you could look at extracting out the xml processing using JBossXB and encapsulate this into a resulable xmbean interceptor Dimitris. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872812#3872812 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872812 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.931 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050405211911Lbuild.931 BUILD COMPLETE - build.931Date of build: 04/05/2005 21:19:11Time to build: 19 minutes 58 secondsLast changed: 04/05/2005 19:37:39Last log entry: Refactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (11)1.3modifiedejortj2se/src/main/javax/management/StandardMBean.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.3modifiedejortj2se/src/main/org/jboss/mx/server/ServerConfig.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.1addedejortj2se/src/main/org/jboss/mx/standardmbean/StandardMBeanDelegate.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.1addedejortj2se/src/main/org/jboss/mx/standardmbean/StandardMBeanDelegateFactory.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.1addedejortjmx/src/main/org/jboss/mx/standardmbean/StandardMBeanFactoryImpl.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.1addedejortjmx/src/main/org/jboss/mx/standardmbean/StandardMBeanImpl.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.6modifiedejortjmx/src/main/org/jboss/mx/metadata/AbstractBuilder.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.4modifiedejortjmx/src/main/org/jboss/mx/metadata/IllegalPropertyException.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.5modifiedejortjmx/src/main/org/jboss/mx/metadata/MetaDataBuilder.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.19modifiedejortjmx/src/main/org/jboss/mx/metadata/StandardMetaData.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction1.2modifiedejortjmx/src/main/org/jboss/mx/server/JBossMXServerConfig.javaRefactor the StandardMBean into a delegate pattern so we can1) change the implementation more easily2) not really on the jdk's implementation3) remove the metadata classes from the j2se abstraction
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: classloader question
Another question is why and how does a class have more than one UCL? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872803#3872803 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872803 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - classloader question
when is a UCL added to the repository? Does it happen when JBOSS starts for all the packages? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872802#3872802 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872802 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - JBossIDE 1.5M1 + Eclipse3.1M6
In case anyone was wondering it looks like 1.5M1 really is an M5a only version. It doesn't seem to work for me under M6. Maybe because they fixed the M5 bug that 1.5M1 is patched to work with. Anyway, here's looking forward to 1.5M2 and Eclipse M6 support. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872797#3872797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872797 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.930 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050405185234Lbuild.930 BUILD COMPLETE - build.930Date of build: 04/05/2005 18:52:34Time to build: 22 minutes 53 secondsLast changed: 04/05/2005 18:24:10Last log entry: Add the missing methods in the wscompile generated code for Nillable Typesso that the testcase passes. [JBWS-147] Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (19)1.2modifiedosdchicagowebservice/test/resources/tools/xsd-java-checker/wscompile/nillabletypes/NillableType.javaAdd the missing methods in the wscompile generated code for Nillable Typesso that the testcase passes. [JBWS-147]1.4modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/SchemaLocationRegistryTestCase.javaFix the testcase1.22modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDLDefinitions.javaAdd a method that gets all registered prefix1.22modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDL20Reader.javaMinor fix to do defensive programming against NPE1.15modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/JavaToWSDL20.javaMinor cleanup1.25modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/JavaToWSDL.javaAccessor for WSDLDefinitions added.1.11modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/Configuration.javaAdd some config for generation of jaxrpc mapping files1.19modifiedosdchicagowebservice/src/main/org/jboss/ws/Constants.javaAdd a prefix tns1.9modifiedosdchicagocommon/src/main/org/jboss/xml/binding/NamespaceRegistry.javaReturn a method getRegisteredPrefix that returns a list of prefix registered.1.18modifiedejortjmx/src/main/test/compliance/ComplianceSUITE.javaMove the serialization tests to j2se1.3modifiedejortjmx/src/main/test/compliance/FullComplianceSUITE.javaMove the serialization tests to j2se1.2deletedejortjmx/src/main/test/serialization/support/Trivial.javaMove the serialization tests to j2se1.2deletedejortjmx/src/main/test/serialization/support/TrivialMBean.javaMove the serialization tests to j2se1.2modifiedejortjmx/src/main/test/serialization/SerializationSUITE.javaMove the serialization tests to j2se1.8deletedejortjmx/src/main/test/serialization/SerializeTestCase.javaMove the serialization tests to j2se1.27modifiedejortserver/src/resources/dtd/jboss_4_0.dtdPort JBAS-1645 from JBoss41.69modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.javaPort JBAS-1645 from JBoss41.2modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvokerMBean.javaPort JBAS-1645 from JBoss41.95modifiedejortserver/src/etc/conf/default/standardjboss.xmlPort JBAS-1645 from JBoss4
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1283) Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for Webapp
[ http://jira.jboss.com/jira/browse/JBAS-1283?page=comments#action_12316704 ] Tomislav Bodor commented on JBAS-1283: -- This is quite a significant problem with farther reaching consequences than just JSP compilation. It affects all versions of JBoss from 3.2.6 onwards (possibly earlier). 3.2.3 is not affected, possibly due to use of Tomcat 4 or maybe due to a class loading bug that was fixed in 3.2.4 (I can find a reference if needed). But in 3.2.3 scoping is broken for other reasons and this overriding has no chance of working anyway. 4.0.2RC1 is affected as well. It does not only affect overriding dom4j but also any other package that makes use of the thread context class loader to locate classes (e.g. xerces). Basically, what is happening is that a worker thread starts of as having as thread context class loader the loader that is responsible for loading Tomcat sar. However, somewhere along the way (in ...catalina.core.StandardHostValve) Tomcat changes the context class loader to be the one responsible for loading classes from the deployed war file from which the JSP is loaded. After that point, any piece of code like: (DocumentBuilderFactory) DocumentBuilderFactory.newInstance() will cause a ClassCastException as the right hand side uses thread context class loader to load the DocumentBuilderFactory implementation from the war file (assuming it is overriden there and scoping is enabled), but the left hand side (the cast) specifies class loaded by the sar class loader (actually, by a parent of that loader - the class eventually comes from $(JBOSS_HOME}/lib/xercesImpl.jar in this example). Other similar scenarios fail, too - as long as Tomcat attempts to (say) parse an XML file between the StandardHostValve and the invocation of the servlet that is the target of the request. Basically, the context class loader is changed too early (though the fix may be more complicated). Finally, setting java2ParentDelegation to true does seem to fix the problem at the first glance, but in fact what it does is cause the DocumentBuilderFactory implementation in the above example to be also loaded from the JBoss's copy of xercesImpl.jar. So no ClassCastException, but also no overriding! Might as well turn off scoping and remove overriden libraries from the war file. Of course, if the application requires them, it stops working. Hardly what we want. So... Can I please ask you to raise the priority on this one? Perhaps even restructure the bug report so it doesn't appear as related to JSP only, but to scoping and class loading? I'm also happy to work with anyone there on fixing this as this is quite critical for us. Regards, Tomislav > Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for > Webapp > - > > Key: JBAS-1283 > URL: http://jira.jboss.com/jira/browse/JBAS-1283 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-3.2.6 Final > Environment: Stock JBoss 3.2.6 running on Linux (kernel 2.4.26), Sun JDK and > JRE version 1.4.2_04 > Reporter: Jeremy Brown > Assignee: Anil Saldhana > Priority: Minor > Attachments: test.war > > > See my initial forum post at > "http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861452#3861452";. > The dom4j libs provided by JBoss do not work correctly with my web > application, so I attempted to configure my webapp's "jboss-web.xml"--as per > the wiki page at > "http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration"--so that > my webapp would essentially be in a different classloader namspace and would > be able to override the server dom4j implementation with its own. Now, > Tomcat bails out during JSP compilation with a dom4j-related > ClassCastException, leading me to believe there might some problem with the > sort of setup I'm trying to attempt...for example, Tomcat's JSP compiler > might be trying to link with the dom4j in my application's namespace while > its classes have been loaded next to (and probably are already using) dom4j > in the server namespace. > I'll attach a .war file exhibiting this behavior to this bug report. > Here's the specific exception for this .war file: > java.lang.ClassCastException > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) > at > org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:91) > at > org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:70) > at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:188) > at > org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:240) > at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:160) > at org.apache.jasper.compi
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-44) Full POJO-based application use case (Order, Customer, LineItems) on TreeCacheAop
[ http://jira.jboss.com/jira/browse/JBCACHE-44?page=history ] Ben Wang updated JBCACHE-44: Summary: Full POJO-based application use case (Order, Customer, LineItems) on TreeCacheAop (was: Full POJO-based application (Order, Customer, LineItems) on TreeCacheAop) > Full POJO-based application use case (Order, Customer, LineItems) on > TreeCacheAop > - > > Key: JBCACHE-44 > URL: http://jira.jboss.com/jira/browse/JBCACHE-44 > Project: JBoss Cache > Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.3 > > Original Estimate: 6 weeks > Remaining: 6 weeks > > Full POJO based application to use TreeCacheAop > Goals: > - showcase POJO-based application > - test and detect bugs or performance problems in TreeCacheAop by using all > features available -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-44) Full POJO-based application (Order, Customer, LineItems) on TreeCacheAop
[ http://jira.jboss.com/jira/browse/JBCACHE-44?page=comments#action_12316703 ] Ben Wang commented on JBCACHE-44: - Maybe we can use something like Hibernate's Caveat Emptor for im-memory datastore version. > Full POJO-based application (Order, Customer, LineItems) on TreeCacheAop > > > Key: JBCACHE-44 > URL: http://jira.jboss.com/jira/browse/JBCACHE-44 > Project: JBoss Cache > Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.3 > > Original Estimate: 6 weeks > Remaining: 6 weeks > > Full POJO based application to use TreeCacheAop > Goals: > - showcase POJO-based application > - test and detect bugs or performance problems in TreeCacheAop by using all > features available -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-194) When using an IP that isn't localhost, the Admin CMS Portlet is empty due to incorrect portlet.xml entry
[ http://jira.jboss.com/jira/browse/JBPORTAL-194?page=history ] Julien Viet closed JBPORTAL-194: Resolution: Won't Fix it is not possible to detect the URL of the webdav server at deploy time, so that URL must manually be changed in web.xml > When using an IP that isn't localhost, the Admin CMS Portlet is empty due to > incorrect portlet.xml entry > > > Key: JBPORTAL-194 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-194 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 RC, 2.0 Final > Environment: RedHat 2.4.21-27.0.2.ELsmp , jdk 1.4.2_06, > Reporter: Damon Sicore > Assignee: Julien Viet > Fix For: 2.0 RC > > > Whenever a portal is deployed on an IP that doesn't resolve to localhost, the > Admin CMS Portlet is empty. A "Connection Refused" will appear in STDOUT as > an exception related to WebDAV. > It's not exactly clear that one needs to change the 'localhost' in > portlets.xml to the IP that you are binding to in your 'run.sh -b whateverip > -c standard'. > 16:30:17,402 INFO [STDOUT] /portal > 16:30:17,416 INFO [STDOUT] java.net.ConnectException: Connection refused > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.socketConnect(Native Method) > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) > 16:30:17,418 INFO [STDOUT] at > java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:452) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:402) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:309) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:124) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:105) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:683) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:661) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:529) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3457) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3423) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setNamedProp(WebdavResource.java:967) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setBasicProperties(WebdavResource.java:912) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setProperties(WebdavResource.java:1894) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1301) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setPath(WebdavResource.java:1469) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.WebDAVUtil.setCurrentPath(WebDAVUtil.java:103) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet$1.perform(AdminCMSPortlet.java:128) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.perform(AdminCMSPortlet.java:88) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.doView(AdminCMSPortlet.java:115) > 16:30:17,420 INFO [STDOUT] at > javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:51) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.render(AdminCMSPortlet.java:851) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeRequest(DispatcherInterceptor.java:143) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.portlet.invocation.DispatcherInterceptor.invoke(DispatcherInterceptor.java:171) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) > 16:30:17,421 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.CMSInterceptor.invoke(CMSInterceptor.java:78) > 16:30:17,421 INFO [STDOUT] at > org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) > 16
[JBoss-dev] [JBoss JIRA] Reopened: (JBPORTAL-194) When using an IP that isn't localhost, the Admin CMS Portlet is empty due to incorrect portlet.xml entry
[ http://jira.jboss.com/jira/browse/JBPORTAL-194?page=history ] Julien Viet reopened JBPORTAL-194: -- > When using an IP that isn't localhost, the Admin CMS Portlet is empty due to > incorrect portlet.xml entry > > > Key: JBPORTAL-194 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-194 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 RC, 2.0 Final > Environment: RedHat 2.4.21-27.0.2.ELsmp , jdk 1.4.2_06, > Reporter: Damon Sicore > Assignee: Julien Viet > Fix For: 2.0 RC > > > Whenever a portal is deployed on an IP that doesn't resolve to localhost, the > Admin CMS Portlet is empty. A "Connection Refused" will appear in STDOUT as > an exception related to WebDAV. > It's not exactly clear that one needs to change the 'localhost' in > portlets.xml to the IP that you are binding to in your 'run.sh -b whateverip > -c standard'. > 16:30:17,402 INFO [STDOUT] /portal > 16:30:17,416 INFO [STDOUT] java.net.ConnectException: Connection refused > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.socketConnect(Native Method) > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) > 16:30:17,417 INFO [STDOUT] at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) > 16:30:17,418 INFO [STDOUT] at > java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:452) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:402) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:309) > 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:124) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:105) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:683) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:661) > 16:30:17,418 INFO [STDOUT] at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:529) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3457) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3423) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setNamedProp(WebdavResource.java:967) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setBasicProperties(WebdavResource.java:912) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setProperties(WebdavResource.java:1894) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1301) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) > 16:30:17,419 INFO [STDOUT] at > org.apache.webdav.lib.WebdavResource.setPath(WebdavResource.java:1469) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.WebDAVUtil.setCurrentPath(WebDAVUtil.java:103) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet$1.perform(AdminCMSPortlet.java:128) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.perform(AdminCMSPortlet.java:88) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.doView(AdminCMSPortlet.java:115) > 16:30:17,420 INFO [STDOUT] at > javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:51) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.render(AdminCMSPortlet.java:851) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeRequest(DispatcherInterceptor.java:143) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.portlet.invocation.DispatcherInterceptor.invoke(DispatcherInterceptor.java:171) > 16:30:17,420 INFO [STDOUT] at > org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) > 16:30:17,421 INFO [STDOUT] at > org.jboss.portal.core.portlet.cms.CMSInterceptor.invoke(CMSInterceptor.java:78) > 16:30:17,421 INFO [STDOUT] at > org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) > 16:30:17,421 INFO [STDOUT] at > org.jboss.portal.portlet.invocation.PreferencesInterceptor.invoke(PreferencesInterceptor.java:93) > 16:30:17,4
[JBoss-dev] [Design of JBoss Portal] - Re: JBoss Portal and Google
Usually the parts we distinguish are : | * target : in that case window ID | * control parameters : in that case the PortletMode and the WindowState | * target parameters : in that case any parameter that the portlet URL carries | in the future it is possible it could change and use several namespace (instead of two today which are target and control) in order to have richer expressiveness in URLs. Nevertheless, it does not prevent up from having a defined mapping from URI to server URIs. Today we have such a mapping for portal and pages. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872792#3872792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872792 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.475 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050405164646Lbuild.475 BUILD COMPLETE - build.475Date of build: 04/05/2005 16:46:46Time to build: 38 minutes 55 secondsLast changed: 04/05/2005 15:16:18Last log entry: Fix the eclipse build Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (40)1.7.6.1modifiedejortmessaging/.classpathFix the eclipse build1.20.2.9modifiedejortserver/src/resources/dtd/jboss_4_0.dtd[JBAS-1645] - Allow the MDB's construction of JBossMQ Destinations to be turned off.1.64.2.12modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java[JBAS-1645] - Allow the MDB's construction of JBossMQ Destinations to be turned off.1.88.2.6modifiedejortserver/src/etc/conf/default/standardjboss.xml[JBAS-1645] - Allow the MDB's construction of JBossMQ Destinations to be turned off.1.8.4.2modifiedejorttomcat/.classpathFix the eclipse build1.18.2.16modifiedstarksmtools/etc/buildmagic/buildmagic.entChange the build.parsers directory name to gen-parsers1.5.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/ListenerRegistration.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/Management.javaCleanup the license header.1.5.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/ManagementHome.javaCleanup the license header.1.10.6.1modifiedstarksmmanagement/src/main/org/jboss/management/j2ee/LocalJBossServerDomain.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JDBCConnectionPoolStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JDBCConnectionStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JDBCStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSConnectionStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSConsumerStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSEndpointStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSProducerStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSSessionStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JMSStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JTAStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JVMStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JavaMailStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/MessageDrivenBeanStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/RangeStatistic.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/ServletStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/SessionBeanStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/StatefulSessionBeanStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/StatelessSessionBeanStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/Statistic.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/Stats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/TimeStatistic.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/URLStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/BoundedRangeStatistic.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/CountStatistic.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/EJBStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/EntityBeanStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee/statistics/JCAConnectionPoolStats.javaCleanup the license header.1.6.6.1modifiedstarksmmanagement/src/main/javax/management/j2ee
[JBoss-dev] [JBoss JIRA] Closed: (JBREM-97) Won't compile under JDK 1.5
[ http://jira.jboss.com/jira/browse/JBREM-97?page=history ] Tom Elrod closed JBREM-97: --- Resolution: Done Changed so not using enum keyword for variable names. Everything else is fine. > Won't compile under JDK 1.5 > --- > > Key: JBREM-97 > URL: http://jira.jboss.com/jira/browse/JBREM-97 > Project: JBoss Remoting > Type: Bug > Components: general > Versions: 1.0.2 final > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.2.0 beta > > > Need to change so will compile under JDK 1.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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-93) Callback handler returning a generic Object
[ http://jira.jboss.com/jira/browse/JBREM-93?page=comments#action_12316700 ] Tom Elrod commented on JBREM-93: - It just wraps any Throwable thrown when calling callBackClient.invoke(internalInvocation,callback.getRequestPayload()), so can just get original exception by calling getCause() on the HandleCallbackException thrown. Not sure I understand your request. Is it that you want the original exception throw from callBackClient.invoke() to be throw out of handleCallback() method, without wrapping it? Maybe you can explain use case? > Callback handler returning a generic Object > --- > > Key: JBREM-93 > URL: http://jira.jboss.com/jira/browse/JBREM-93 > Project: JBoss Remoting > Type: Feature Request > Components: callbacks > Reporter: Ovidiu Feodorov > Assignee: Tom Elrod > Priority: Optional > > > InvokerCallbackHandler.handleCallback() returns void. However, is is able to > throw a HandleCallbackException that ultimately reaches the calling party. > I was wondering if it is a big deal to have handleCallback() returning a > generic Object. This would make the handleCallback()'s semantics more > flexible. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ 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 - Standalone module - multiple builds
"[EMAIL PROTECTED]" wrote : | The other solution would be to use xml namespaces. I actually think namespace is technically a much better solution. However, I think will be more difficult for people to learn/use, so would not go with it because will lead to more build errors. So where does this leave things for JBossRemoting build? I obviously can't take the jbossbuild.xml from jboss-head/remoting/ directory and expect it to work as is. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872791#3872791 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872791 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: JBoss Portal and Google
So heres my take on it, and I may be oversimplifying it: Here is a standard portal url: http://localhost:8080/portal/auth/index.html?ctrl:id=window.default.PermissionPortletWindow&ctrl:type=windowstate&ctrl:windowstate=maximized On the admin screen with the PermissionPortlet maximized. URL Components: Context = portal PortletWindow = PermissionPortletWindow Action type = windowstate windowstate = maximized So, can we do something like this? http://localhost:8080/[context]/[portletwindow]/[actiontype]/[windowstate]/ Then we just parse things out like we have now and have the portal interpret this parameter-less url. The only thing that throws a wrench in the works is what to do about the cmsportlet: "/foo/bar/goo.html" Unless you append those at the end of the path, perhaps? Using this scheme, we already can figure out that $1 = context $2 = portletwindow $3 = actiontype $4 = windowstate $5 = cms item ? This is what I do on my personal sites with url-rewriting. I use regexes like this to parse things out and rebuild the url and pass it on a local script for execution. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872790#3872790 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872790 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ 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 - Standalone module - multiple builds
Yes, the split makes sense. 1) It clearly separates the external definition from the internal implementation 2) Nobody is likely to be interested in how a jar is constructed or which source is used, only the end product. So the duplicate | | should be irrelevent. 3) It means the repository is not being continually updated with minor internal tweaks to the module builds. The other solution would be to use xml namespaces. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872784#3872784 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872784 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.328 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050405154832Lbuild.328 BUILD COMPLETE - build.328Date of build: 04/05/2005 15:48:32Time to build: 31 minutes 46 secondsLast changed: 04/05/2005 15:24:24Last log entry: Fixed on 1.3 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.24.2.9modifiedbwang00cache/src/main/org/jboss/cache/Node.javaFixed on 1.31.79.2.20modifiedbwang00cache/src/main/org/jboss/cache/TreeCache.javaComptabile with 1.3
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
Yes, that is the one, but it doesn't include our convesation. Yes, I did test the parsing of the build.xml. The main problem I ran into was that of the ids of the various imported components conflicting. IE, every component has an source with an ID of "main", so trying to import a half dozen components is going to end up with Ant overriding the reference to main a half dozen times. The solution to this, I think, is to have two files in each component directory. One is the component-info.xml (better name?) which contains the external metadata (interface) of each component, as outlined in the issue you refer to. It would also include the "exports" that we talked about at the dev conference. The other would be the build.xml which includes the componentdefs as now. Do you see any problems with seperating them as I suggest? IE, instead of remoting importing common/build.xml, it would import common/component-info.xml instead? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872782#3872782 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872782 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - New Build - Standalone module - multiple builds
Hi Ryan, Is this the task for changing the build so it doesn't depend upon the top level build? http://jira.jboss.com/jira/browse/JBBUILD-16 i.e. the project "imports" the dependent projects (including binary projects downloaded from the repository into thirdparty). e.g. For Tom wants to create a standalone JBossRemoting project that will include other JBoss projects, but these projects reference the top level JBossAS for their artifact definitions. Did you test the ant parsing of other build.xml? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872779#3872779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872779 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
I think Adrian is correct in that a HARDeployer and a SARDeployer are conceptually very different "things". There is certainly a lot of overlap in functionality (the worst part being the xml parsing). After further thought on this, it seems a much better approach here is the simply better encapsulate this redundant logic into delegates. Especially if you think about the parsing of the service descriptors. Maybe even a JBoss XMBean "thingy". Then others can easily re-use that logic in custom deployers. I remember now what brought me to this situation now. Currently what the HARDeployer does is to essentially say that its 'hibernate-service.xml' file is a sub-deployment (i.e., SubDeployerSupport.isDeployable). The sole reason it does this is so that the SARDeployer can then pick it up and parse the xml descriptor, register mbeans... yuck! I was trying to clean that up so that the "nested deployment" concept was not needed. So I guess, in a way, a HAR deployment *is* is SAR :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872775#3872775 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872775 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - JBoss-IDE and custom tags
I've looked around the forums for a similar problem but didn't find any, so here's my post. I've got JBoss-IDE working, sorta. I know it's loading the .TLD files just fine but it doesn't seem to be finding the .JAR files. The error I get in the problem view is this: Failed to load or instantiate TagExtraInfo class: org.apache.struts.taglib.bean.CookieTei My package structure looks like this: WEBROOT/ WEBROOT/jsp/ WEBROOT/jsp/about.jsp WEBROOT/jsp/search.jsp WEBROOT/WEB-INF/ WEBROOT/WEB-INF/struts-config.xml WEBROOT/WEB-INF/web.xml WEBROOT/WEB-INF/lib/ WEBROOT/WEB-INF/lib/struts.jar WEBROOT/WEB-INF/taglib/ WEBROOT/WEB-INF/taglib/struts-html.tld WEBROOT/WEB-INF/taglib/struts-bean.tld WEBROOT/WEB-INF/taglib/struts-logic.tld And, yes, I do have JSP compilation turned on for the project. Is there some sort of other configuration file I might be missing? MANIFEST.MF perhaps? Or maybe a missing option in web.xml? How does JBoss-IDE know where the .JAR files are located? Any thoughts would be very appreciated! -Dan Watling View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872772#3872772 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872772 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - JBossRemoting project move
The JBossRemoting project has moved from being underneath the jboss-head module in CVS to its own module. For information, please see http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_CVS_move. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872771#3872771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872771 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1645) The MDB should not automatically create JBossMQ destinations
[ http://jira.jboss.com/jira/browse/JBAS-1645?page=history ] Adrian Brock closed JBAS-1645: -- Resolution: Done I have added true to the invoker proxy config so that this can be turned off. The default is true for backwards compatibility. > The MDB should not automatically create JBossMQ destinations > > > Key: JBAS-1645 > URL: http://jira.jboss.com/jira/browse/JBAS-1645 > Project: JBoss Application Server > Type: Feature Request > Components: JMS service > Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assignee: Adrian Brock > Fix For: JBossAS-4.0.2 Final > > > The MDB should not automatically create JBossMQ destinations: > 1) It is not portable > 2) It hides configuration mistakes made by the user (unless they pay > attention to warnings) -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: 2 Problems: 1. can't get into the AdminCMSPortlet 2. c
With respect to the AdminCMS Portlet, are you seeing a stack trace there? Once you are logged on as admin, go to "admin" and it should be there. If you see a stack trace there, post it here. The forums look like they're messed up from the DB, is my guess. Are you able to create new categories and forums? Try navigating to those. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872769#3872769 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872769 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-223) Edit a message
[ http://jira.jboss.com/jira/browse/JBPORTAL-223?page=history ] Roy Russo closed JBPORTAL-223: -- Resolution: Done done. > Edit a message > -- > > Key: JBPORTAL-223 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-223 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 Final, 2.0 RC > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC > > -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBREM-98) remove isDebugEnabled() within code as is now depricated
[ http://jira.jboss.com/jira/browse/JBREM-98?page=history ] Tom Elrod closed JBREM-98: --- Resolution: Done Either removed the isDebugEnabled() or changed to isTraceEnabled(). > remove isDebugEnabled() within code as is now depricated > > > Key: JBREM-98 > URL: http://jira.jboss.com/jira/browse/JBREM-98 > Project: JBoss Remoting > Type: Task > Components: general > Versions: 1.0.2 final > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.2.0 beta > > -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-98) remove isDebugEnabled() within code as is now depricated
remove isDebugEnabled() within code as is now depricated Key: JBREM-98 URL: http://jira.jboss.com/jira/browse/JBREM-98 Project: JBoss Remoting Type: Task Components: general Versions: 1.0.2 final Reporter: Tom Elrod Assigned to: Tom Elrod Fix For: 1.2.0 beta -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-97) Won't compile under JDK 1.5
Won't compile under JDK 1.5 --- Key: JBREM-97 URL: http://jira.jboss.com/jira/browse/JBREM-97 Project: JBoss Remoting Type: Bug Components: general Versions: 1.0.2 final Reporter: Tom Elrod Assigned to: Tom Elrod Fix For: 1.2.0 beta Need to change so will compile under JDK 1.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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJMX-90) inspectMBean.jsp throws AccessControlException
inspectMBean.jsp throws AccessControlException
--
Key: JBJMX-90
URL: http://jira.jboss.com/jira/browse/JBJMX-90
Project: JBoss JMX
Type: Bug
Versions: JBossAS-4.0.1
Environment: JBoss Version 4.0.2RC1
Reporter: Roland R?z
Priority: Minor
The inspectMBean.jsp page throws a AccessControlException
(javax.management.MBeanServerPermission is
missing) although the codesource from where the JSP servlet is loaded (I use
precompiled JSPs) has those
permission.
This is the code section where the AccessControlException is thrown
for(int a = 0; a < attributeInfo.length; a ++)
{
final MBeanAttributeInfo attrInfo = attributeInfo[a];
String attrName = attrInfo.getName();
String attrType = attrInfo.getType();
AttrResultInfo attrResult =
Server.getMBeanAttributeResultInfo(objectNameString, attrInfo);
...
You should use AccessController.doPrivileged to execute the code
AttrResultInfo attrResult =
Server.getMBeanAttributeResultInfo(objectNameString, attrInfo);
Regards
--
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
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1645) The MDB should not automatically create JBossMQ destinations
The MDB should not automatically create JBossMQ destinations Key: JBAS-1645 URL: http://jira.jboss.com/jira/browse/JBAS-1645 Project: JBoss Application Server Type: Feature Request Components: JMS service Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock Assigned to: Adrian Brock Fix For: JBossAS-4.0.2 Final The MDB should not automatically create JBossMQ destinations: 1) It is not portable 2) It hides configuration mistakes made by the user (unless they pay attention to warnings) -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.474 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050405104834Lbuild.474 BUILD COMPLETE - build.474Date of build: 04/05/2005 10:48:34Time to build: 38 minutes 31 secondsLast changed: 04/05/2005 06:28:29Last log entry: fixed QName construction that caused failures in xml tests Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (7)1.7.2.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/AbstractMarshaller.javafixed QName construction that caused failures in xml tests1.1.2.4modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/ws4eesimple/ClientStubTestCase.javaRemove dependencies on org.jboss.axis1.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/samples/OrganizationClientBean.javaRemove dependencies on org.jboss.axis1.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/samples/OrganizationClientServlet.javaRemove dependencies on org.jboss.axis1.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/jbws153/JBWS153TestCase.javaRemove dependencies on org.jboss.axis1.1.2.7modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentDIITestCase.javaRemove dependencies on org.jboss.axis1.1.2.10modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaRemove dependencies on org.jboss.axis
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Alexey Loubyansky updated JBAS-1523: Attachment: jboss_jar-patched.jar This is the patched jboss.jar that should replace jboss.jar in the lib. It also contains a readme file with the following contents: Support patch: JBAS-30 - txtimers created via Servlet init get duplicated Jira URL: http://jira.jboss.com/jira/browse/JBAS-1523 JBoss version: 4.0.0 final release Modified classes (server module): org.jboss.ejb.txtimer.TimerServiceImpl org.jboss.ejb.txtimer.PersistencePolicy org.jboss.ejb.txtimer.DatabasePersistencePolicy org.jboss.ejb.txtimer.DatabasePersistencePlugin org.jboss.ejb.txtimer.NoopPersistencePolicy org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin New configuration (in ejb-deployer.xml): jboss.jca:service=DataSourceBinding,name=DefaultDS org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin Notes: Existsing timer tables should be dropped. This issue is fixed in JBoss-4.0.1 final. Alexey Loubyansky ([EMAIL PROTECTED]) 05.04.2005 > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Alexey Loubyansky > Attachments: jboss_jar-patched.jar > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: 2 Problems: 1. can't get into the AdminCMSPortlet 2. c
Hello all, Hello Roy. I have created tables and relationsships in MSSQL-Server like in setup.dll(from jboss-portal-2.0-beta1-bin), filled the table from setup.sql. If you have some ideas to solve my problem tell me this please. regards vefkt View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872731#3872731 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872731 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-71) Last login date
[ http://jira.jboss.com/jira/browse/JBPORTAL-71?page=history ] Julien Viet updated JBPORTAL-71: Assign To: Julien Viet (was: Roy Russo) Description: Environment: Security Level: (was: Public) > Last login date > --- > > Key: JBPORTAL-71 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-71 > Project: JBoss Portal > Type: Sub-task > Components: Portal Core > Versions: 2.0 Alpha > Reporter: Thomas Heute > Assignee: Julien Viet > Fix For: 2.0 RC > > -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-194) When using an IP that isn't localhost, the Admin CMS Portlet is empty due to incorrect portlet.xml entry
[ http://jira.jboss.com/jira/browse/JBPORTAL-194?page=history ]
Julien Viet resolved JBPORTAL-194:
--
Resolution: Done
the URL configuration now uses the variable ${jboss.bind.address} to figure out
its own host. That does not prevent from changing the port whenever the slide
port changes
> When using an IP that isn't localhost, the Admin CMS Portlet is empty due to
> incorrect portlet.xml entry
>
>
> Key: JBPORTAL-194
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-194
> Project: JBoss Portal
> Type: Bug
> Components: Portal Core
> Versions: 2.0 RC, 2.0 Final
> Environment: RedHat 2.4.21-27.0.2.ELsmp , jdk 1.4.2_06,
> Reporter: Damon Sicore
> Assignee: Julien Viet
> Fix For: 2.0 RC
>
>
> Whenever a portal is deployed on an IP that doesn't resolve to localhost, the
> Admin CMS Portlet is empty. A "Connection Refused" will appear in STDOUT as
> an exception related to WebDAV.
> It's not exactly clear that one needs to change the 'localhost' in
> portlets.xml to the IP that you are binding to in your 'run.sh -b whateverip
> -c standard'.
> 16:30:17,402 INFO [STDOUT] /portal
> 16:30:17,416 INFO [STDOUT] java.net.ConnectException: Connection refused
> 16:30:17,417 INFO [STDOUT] at
> java.net.PlainSocketImpl.socketConnect(Native Method)
> 16:30:17,417 INFO [STDOUT] at
> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> 16:30:17,417 INFO [STDOUT] at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
> 16:30:17,418 INFO [STDOUT] at
> java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:452)
> 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:402)
> 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:309)
> 16:30:17,418 INFO [STDOUT] at java.net.Socket.(Socket.java:124)
> 16:30:17,418 INFO [STDOUT] at
> org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:105)
> 16:30:17,418 INFO [STDOUT] at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:683)
> 16:30:17,418 INFO [STDOUT] at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:661)
> 16:30:17,418 INFO [STDOUT] at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:529)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3457)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3423)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setNamedProp(WebdavResource.java:967)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setBasicProperties(WebdavResource.java:912)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setProperties(WebdavResource.java:1894)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1301)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408)
> 16:30:17,419 INFO [STDOUT] at
> org.apache.webdav.lib.WebdavResource.setPath(WebdavResource.java:1469)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.WebDAVUtil.setCurrentPath(WebDAVUtil.java:103)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet$1.perform(AdminCMSPortlet.java:128)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.perform(AdminCMSPortlet.java:88)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.doView(AdminCMSPortlet.java:115)
> 16:30:17,420 INFO [STDOUT] at
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:51)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.render(AdminCMSPortlet.java:851)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeRequest(DispatcherInterceptor.java:143)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.portlet.invocation.DispatcherInterceptor.invoke(DispatcherInterceptor.java:171)
> 16:30:17,420 INFO [STDOUT] at
> org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214)
> 16:30:17,421 INFO [STDOUT] at
> org.jboss.portal.core.portlet.cms.CMSInterceptor.invoke(CMSInterceptor.java:78)
> 16:30:17,421 INFO [STDOUT] at
> org.jboss.portal.server.impl.invocation.Invoca
[JBoss-dev] jboss-4.0-jdk-matrix build.121 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050405070050Lbuild.121 BUILD COMPLETE - build.121Date of build: 04/05/2005 07:00:50Time to build: 52 minutes 52 secondsLast changed: 04/05/2005 06:28:29Last log entry: fixed QName construction that caused failures in xml tests Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (98)1.7.2.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/AbstractMarshaller.javafixed QName construction that caused failures in xml tests1.1.2.4modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/ws4eesimple/ClientStubTestCase.javaRemove dependencies on org.jboss.axis1.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/samples/OrganizationClientBean.javaRemove dependencies on org.jboss.axis1.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/samples/OrganizationClientServlet.javaRemove dependencies on org.jboss.axis1.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/jbws153/JBWS153TestCase.javaRemove dependencies on org.jboss.axis1.1.2.7modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentDIITestCase.javaRemove dependencies on org.jboss.axis1.1.2.10modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaRemove dependencies on org.jboss.axis1.1.2.2modifiedtdieslertestsuite/src/resources/webservice/attachment/attach.txtRemove trailing whitespace1.4.6.1modifiedstarksmcommon/src/main/org/jboss/util/xml/DOMWriter.javaFix the license header.1.2.2.6modifiedstarksmthirdparty/licenses/thirdparty-licenses.xmlFor each license type, add the acceptable source code copyright headers for validation agains the codebase. This is used by the org.jboss.tools.copyright.ValidateCopyrightHeaders utility to determine which source files have invalid copyright headers.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/NavigationTag.javaFix the license header.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/Tab.javaFix the license header.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/TabTag.javaFix the license header.1.1.2.3modifiedstarksmcommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.javaFix the license header.1.10.2.5modifiedstarksmcache/src/main/org/jboss/cache/PropertyConfigurator.javaFix the license header.1.2.6.2modifiedstarksmcache/src/main/org/jboss/cache/lock/IsolationLevel.javaFix the license header.1.4.6.1modifiedstarksmvaria/src/main/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.javaFix the license header.1.1.2.2deletedstarksmcommon/src/main/javax/xml/XMLConstants.javaRemove the jdk5 files included by mistake.1.1.6.2deletedstarksmcommon/src/main/javax/xml/namespace/NamespaceContext.javaRemove the jdk5 files included by mistake.1.2.6.5modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaRollback the 4.0.1 version as we cannot have jdk source in our tree.1.9.2.64modifiedtdieslertestsuite/imports/test-jars.xmlSync up with HEAD1.2.2.9modifiedtdieslerjaxrpc/build.xmlSync up with HEAD1.1.2.1deletedbwang00cache/src/main/org/jboss/cache/tests/DelegatingCacheLoaderTest.javaBackorting from 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting 1.2.21.19.4.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting 1.2.21.12.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting 1.2.21.5.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CallbackTest.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/Client.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CopyOnWriteArrayTest.javaBackporting 1.2.21.16.2.3modifiedbwang00cache/src/main/org/jboss/cache/tests/FileCacheLoaderTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/InterceptorConfigurationTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/JDBCCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/LocalDelegatingCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReadWriteLockTest.javaBackporting 1.2.21.3.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReentrantWriterPreferenceReadWriteLockTest.javaBackporting 1.2.21.2.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/RestartTest.javaBackporting 1.2.21.3.2.1
[JBoss-dev] [JBoss JIRA] Closed: (JBPM-107) connection properties replacement
[ http://jira.jboss.com/jira/browse/JBPM-107?page=history ] Tom Baeyens closed JBPM-107: Resolution: Done the jbpm.db project was updated so that it replaces the jdbc connection properties as specified in jbpm.2/src/resources (the hypersonic in-memory properties) > connection properties replacement > - > > Key: JBPM-107 > URL: http://jira.jboss.com/jira/browse/JBPM-107 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 3.0 alpha 3 > > > in the resource directory, we should put the @@ markers such as in the > jbpm.db in the file src/resource/hibernate.cfg.xml > then in the unit tests, we should do the replacement of the jdbc connection > properties with the hypersonic in memory connection properties. > this is for the jbpm.db project so that it can use the resources directly > from the jbpm.3 project, making sure they are always in sync. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-232) Slide logging integration
[ http://jira.jboss.com/jira/browse/JBPORTAL-232?page=history ] Julien Viet resolved JBPORTAL-232: -- Resolution: Done > Slide logging integration > - > > Key: JBPORTAL-232 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-232 > Project: JBoss Portal > Type: Task > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Julien Viet > Fix For: 2.0 RC, 2.0 Final > > > Provide an implementation of org.apache.slide.util.logger.Logger that > delegates log4J logger -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-232) Slide logging integration
Slide logging integration - Key: JBPORTAL-232 URL: http://jira.jboss.com/jira/browse/JBPORTAL-232 Project: JBoss Portal Type: Task Versions: 2.0 RC, 2.0 Final Reporter: Julien Viet Assigned to: Julien Viet Fix For: 2.0 RC, 2.0 Final Provide an implementation of org.apache.slide.util.logger.Logger that delegates log4J logger -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: SecurityInterceptor and TransactionInterceptor
Steve? Are you still there? :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872717#3872717 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872717 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: setting up the portal sources for development
actually the file is created by the build and put in the output directory of the module, should be output/gen-src/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872716#3872716 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872716 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: ClosedInterceptor design approach
anonymous wrote : It's my understanding that, e.g. in ServerConnectionDelegate.createSession, the object returned is a dynamic proxy that (internally) references an instance of JMSInvocation handler that's been constructed in that method. This instance holds a reference to the interceptor stack and a few other things, and is serialized back to the client. | In JB4 it's this class (called Container in JB4) that maintains the hierarchy. That is correct. It's called JMSInvocationHandler because this is what it implements: java.lang.reflect.InvocationHandler. However, it is a container, since it "contains" the client-side interceptor stack. Since you mentioned this name several time, I am wondering whether we should rename it "JMSClientContainer". Anyway, it's a simple refactoring. If at least one more person starts refering to it as "container", I probably will :). anonymous wrote : Do I need to worry about server side close for MessageProducer and MessageConsumer? I.e is there any that needs to be done on close() for these objects in the server side delegates? ServerProducerDelegate itself does not need any clean-up on close() at this point. The Messaging Core destinations that receive messages from such endpoints do not care (do not have a reference to it). The only thing that is needed is to remove the producer delegate from the session's map. However, situation is different for Consumers. In a way, they are the equivalent of a ServerProducerDelegate, on the receiving side. They are not called ServerConsumerDelegate because they don't implement ConsumerDelegate, there is no need for that, all "ConsumerDelegate-ish" behavior is taking care of by interceptors: see ReceiverInterceptor on client-side and AsynchronousDeliveryInterceptor on the server-side. Here, there is need for clean-up: when a Consumer is closed, it must be de-registered from Messaging Core destination it is connected to. So far, I see ServerSessionDelegate doing this, in a method symmetrical to createConsumer(), that is called by a server-side CloseInterceptor. The current design is a little bit asymetrical and not exactly ellegant, but I would wait a little bit more to see if other needs arise, then maybe refactor. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872715#3872715 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872715 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: setting up the portal sources for development
Ah, I've found the reason for the missing "Analyzer" it's a flex file and wasn't shown by eclipse :) me View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872714#3872714 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872714 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPM-97) process deployer
[ http://jira.jboss.com/jira/browse/JBPM-97?page=history ] Tom Baeyens closed JBPM-97: --- Resolution: Done > process deployer > > > Key: JBPM-97 > URL: http://jira.jboss.com/jira/browse/JBPM-97 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 3.0 alpha 3 > > > implemented the process deployer, and added an ant task for it. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.473 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050405052326Lbuild.473 BUILD COMPLETE - build.473Date of build: 04/05/2005 05:23:26Time to build: 51 minutes 59 secondsLast changed: 04/05/2005 04:28:34Last log entry: Remove trailing whitespace Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (10)1.1.2.2modifiedtdieslertestsuite/src/resources/webservice/attachment/attach.txtRemove trailing whitespace1.4.6.1modifiedstarksmcommon/src/main/org/jboss/util/xml/DOMWriter.javaFix the license header.1.2.2.6modifiedstarksmthirdparty/licenses/thirdparty-licenses.xmlFor each license type, add the acceptable source code copyright headers for validation agains the codebase. This is used by the org.jboss.tools.copyright.ValidateCopyrightHeaders utility to determine which source files have invalid copyright headers.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/NavigationTag.javaFix the license header.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/Tab.javaFix the license header.1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/servlet/TabTag.javaFix the license header.1.1.2.3modifiedstarksmcommon/src/main/org/jboss/util/collection/WeakIdentityHashMap.javaFix the license header.1.10.2.5modifiedstarksmcache/src/main/org/jboss/cache/PropertyConfigurator.javaFix the license header.1.2.6.2modifiedstarksmcache/src/main/org/jboss/cache/lock/IsolationLevel.javaFix the license header.1.4.6.1modifiedstarksmvaria/src/main/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.javaFix the license header.
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Pls Help!!! HTTPInvoker Does not Work
Hi, i manage to solve the problem. I changed the port to something else... btw, i have enable all ports from the firewall setting but somehow it was block. is not a good number...for chinese :) Cheers, View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872710#3872710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872710 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - setting up the portal sources for development
hi, I'm currently trying to set up the portal sources for development. After adding some libraries to the projects I reached the point where I couldn't find a lib which I have to add... :( In the BBCodeParser.java on line 62 is Anaylzer needet but I can't figure out where to find the needed Anaylzer :( | private Anaylzer analyzer = new Analyzer(BBCodeParser.NULL_READER); I think someone has a good idea ;) Some points to mention: * It was really helpful that the sources contain the .project file but they are missing some libs. * The jregexp.jar is missing in the thirdparty directory * Some of the projects require the apache-ant and some the apache_ant directory. yours Marc View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872704#3872704 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872704 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Luc Texier reopened JBAS-1523: -- Not closed yet. The customer is requesting a patch for release 4.0.0 > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Alexey Loubyansky > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Alexey Loubyansky closed JBAS-1523: --- Fixed by Scott in 4.0.1 final. > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Alexey Loubyansky > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1391) Add support for datasource failover
[ http://jira.jboss.com/jira/browse/JBAS-1391?page=history ] Alexey Loubyansky closed JBAS-1391: --- Resolution: Done Done. The feature is documented here http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCADatabaseFailover > Add support for datasource failover > --- > > Key: JBAS-1391 > URL: http://jira.jboss.com/jira/browse/JBAS-1391 > Project: JBoss Application Server > Type: Feature Request > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Alexey Loubyansky > Fix For: JBossAS-4.0.2 Final > > > The change to > org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory > is easier than org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory > In LocalManagedConnectionFactory add a property "delimiter" > which when present will parse the connectionURL into multiple urls. > In XAManagedConnectionFactory you will also need a property to identify which > of the xaProps needs to be parsed for mulitple urls. > i.e. you need to identify which property contains the server to contact. > In both cases, if createManagedConnection fails for the first url, replace it > with the second url, and try again until all urls are exhausted. > Of course, you can get clever and remember which urls are currently failing > and try the non failing urls first, And also if the db is replicating, you > might want it to "load balance" > connections across the urls? > Also, this design does not allow for using different properties with > different db servers, e.g. user and password might change across the servers. > It also doesn't enforce that only connections from one connectionURL (db > server) are in the pool at the same time in the event the db is not > replicating. > If you are going to do this, I would suggest you subclass/replicate the > managed connection factories and create separate rars so we can mark them as > experimental. > > Adrian Brock > Director of Support > Back Office > JBoss Inc. > -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBIDE-135) creation wizard for process java projects
[ http://jira.jboss.com/jira/browse/JBIDE-135?page=history ] Koen Aers updated JBIDE-135: Fix Version: 1.5 Milestone 2 (was: 1.5 Milestone 3) > creation wizard for process java projects > - > > Key: JBIDE-135 > URL: http://jira.jboss.com/jira/browse/JBIDE-135 > Project: JBoss IDE > Type: Task > Components: jBPM Designer plugin > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 1.5 Milestone 2 > > Original Estimate: 2 days > Remaining: 2 days > > A wizard should create a new Java project, set the classpath right and > include the jBPM libraries into it so that users don't have to be bothered by > figuring this out again and again. Moreover database support can be added. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-170) Split the designer plugin in a jbpm.core and jbpm.ui plugin
Split the designer plugin in a jbpm.core and jbpm.ui plugin --- Key: JBIDE-170 URL: http://jira.jboss.com/jira/browse/JBIDE-170 Project: JBoss IDE Type: Task Components: jBPM Designer plugin Reporter: Koen Aers Assigned to: Koen Aers Fix For: 1.5 Milestone 2 -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBIDE-142) Configuration dialogs for node types
[ http://jira.jboss.com/jira/browse/JBIDE-142?page=history ] Koen Aers updated JBIDE-142: Fix Version: 1.5 Milestone 2 (was: 1.5 Milestone 3) > Configuration dialogs for node types > > > Key: JBIDE-142 > URL: http://jira.jboss.com/jira/browse/JBIDE-142 > Project: JBoss IDE > Type: Task > Components: jBPM Designer plugin > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 1.5 Milestone 2 > > Original Estimate: 1 week > Remaining: 1 week > > The different node types accept different configuration parameters. So each > of these should be supported by an appropriate dialog that enables users to > set these configuration parameters in a painless way. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBIDE-141) Configuration dialogs for action types
[ http://jira.jboss.com/jira/browse/JBIDE-141?page=history ] Koen Aers updated JBIDE-141: Fix Version: 1.5 Milestone 2 (was: 1.5 Milestone 3) > Configuration dialogs for action types > -- > > Key: JBIDE-141 > URL: http://jira.jboss.com/jira/browse/JBIDE-141 > Project: JBoss IDE > Type: Task > Components: jBPM Designer plugin > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 1.5 Milestone 2 > > Original Estimate: 1 week > Remaining: 1 week > > The different action types accept different configuration parameters. So each > of these should be supported by an appropriate dialog that enables users to > set these configuration parameters in a painless way. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-85) SequenceBlockIdGenerator produces duplicate keys
[ http://jira.jboss.com/jira/browse/JBPM-85?page=history ] Tom Baeyens updated JBPM-85: Component: Core Engine > SequenceBlockIdGenerator produces duplicate keys > > > Key: JBPM-85 > URL: http://jira.jboss.com/jira/browse/JBPM-85 > Project: JBoss jBPM > Type: Bug > Components: Core Engine > Versions: jBPM 2.0 > Environment: jbpm 2.0, jboss 4.01, jdk1.5 > Reporter: Armin Haaf > Assignee: Tom Baeyens > > > SequenceBlockIdGenerator produces duplicate keys, if the transaction in which > the hilo block is read from the database is rollbacked. This could occur in a > j2ee environment in a jta transaction. IÂm not sure if a hibernate session > using jta transactions creates a new jta transaction, if a transaction is > already registered, but it seems it uses the current transaction. So the > beginTransaction, commit code in SequenceBlockIdGenerator did not commit > immediatly and could be rollbacked later. -- 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
