[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050207015742 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build:02/07/2005 01:57:42Time to build:49 minutes 55 secondsLast changed:02/07/2005 00:43:11Last log entry:Added comments Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(3)1.37modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaAdded comments1.10modifiedrecampbelltools/etc/jbossbuild/tasks.xmladded build.resources1.7modifiedrecampbelltools/lib/jbossbuild.jaradded resourcedef to jbossbuild
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1385) ClassCastException in execution of EJB-QL finder
ClassCastException in execution of EJB-QL finder Key: JBAS-1385 URL: http://jira.jboss.com/jira/browse/JBAS-1385 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final Reporter: nicolas cazottes Assigned to: Scott M Stark There is a ClassCastException at execution time on Jboss since version 3.2.6 (it worked on 3.2.5 but neither on 3.2.6 nor on 3.2.7) when calling an EJB finder query defined as follow with Xdoclet tags : @ejb.finder * view-type = local * signature=test.ProductLocal findByRefToAndToLicense(java.lang.String refTo, java.lang.String license) * result-type-mapping=Local * method-intf=LocalHome * query=SELECT DISTINCT pr.id FROM TourOperator to, IN ( to.products ) AS pr WHERE to.licenseNumber = ?2 AND pr.refTo = ?1 * The trace is given after when jboss is in trace log level. I also tested the same query with a return of type Collection and it worked well. So I think the Cast problem is that I declared the result as ProductLocal and not Collection but it should be working without using a Collection since I known by construction that the result of the search is either 0 or 1. Here is the trace : 16:03:09,690 TRACE [Registry] lookup 491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB 16:03:09,690 TRACE [StatelessSessionContainer] METHOD HOME INVOKE 491837535||create||[Ljava.lang.Object;@1900f17 16:03:09,690 TRACE [LogInterceptor] Start method=create 16:03:09,690 TRACE [TxInterceptorCMT] Current transaction in MI is null 16:03:09,690 TRACE [TxInterceptorCMT] TX_REQUIRED for create timeout=0 16:03:09,690 TRACE [TxInterceptorCMT] Thread came in with tx null 16:03:09,690 TRACE [TransactionImpl] Created new instance for tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [TxInterceptorCMT] Starting new tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [TxInterceptorCMT] TxInterceptorCMT: In finally 16:03:09,690 TRACE [TransactionImpl] Committing, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE 16:03:09,690 TRACE [TransactionImpl] Before completion done, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE 16:03:09,690 TRACE [TransactionImpl] Zero phase commit: No resources. 16:03:09,690 TRACE [TransactionImpl] Committed OK, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [LogInterceptor] End method=create 16:03:09,752 TRACE [Registry] lookup 491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB 16:03:09,752 TRACE [StatelessSessionContainer] METHOD REMOTE INVOKE 491837535||searchProductIDByRefToAndLicenseNumber|| 16:03:09,752 TRACE [LogInterceptor] Start method=searchProductIDByRefToAndLicenseNumber 16:03:09,752 TRACE [TxInterceptorCMT] Current transaction in MI is null 16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for searchProductIDByRefToAndLicenseNumber timeout=0 16:03:09,752 TRACE [TxInterceptorCMT] Thread came in with tx null 16:03:09,752 TRACE [TransactionImpl] Created new instance for tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [TxInterceptorCMT] Starting new tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [StatelessSessionInstancePool] Get instance [EMAIL PROTECTED] test.ProductSearchSession 16:03:09,752 TRACE [CachedConnectionManager] new stack for key: [EMAIL PROTECTED] 16:03:09,752 TRACE [ProxyFactoryFinderInterceptor] invokerBInding is null in ProxyFactoryFinder 16:03:09,752 TRACE [LogInterceptor] Start method=findByRefToAndToLicense 16:03:09,752 TRACE [TxInterceptorCMT] Current transaction in MI is TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for findByRefToAndToLicense timeout=0 16:03:09,752 TRACE [TxInterceptorCMT] Thread came in with tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [EntityInstancePool] Get instance [EMAIL PROTECTED] test.ProductCMP 16:03:09,752 TRACE [CachedConnectionManager] old stack for key: [EMAIL PROTECTED] 16:03:09,752 DEBUG [Product#findByRefToAndToLicense] Executing SQL: SELECT DISTINCT t0_pr.ID FROM tour_operator t1_to, product t0_pr WHERE ((t1_to.LICENSE = ? AND t0_pr.REF_TO = ?)) AND t1_to.ID=t0_pr.TO_ID 16:03:09,752 TRACE [TransactionImpl] enlistResource(): Entered, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] status=STATUS_ACTIVE 16:03:09,752 TRACE [TransactionImpl] startResource(XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=1]) entered: [EMAIL PROTECTED] flags=0 16:03:09,752 TRACE [TransactionImpl] startResource(XidImpl [FormatId=257,
[JBoss-dev] [Design of JBoss Portal] - Re: Help - wierd
I updated things related to hibernate, so you should do a fresh checkout from CVS. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865523#3865523 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865523 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1385) ClassCastException in execution of EJB-QL finder
[ http://jira.jboss.com/jira/browse/JBAS-1385?page=history ] Alexey Loubyansky closed JBAS-1385: --- Resolution: Rejected Finder's are not allowed to return field values. Use SELECT OBJECT(p)... ClassCastException in execution of EJB-QL finder Key: JBAS-1385 URL: http://jira.jboss.com/jira/browse/JBAS-1385 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final Reporter: nicolas cazottes Assignee: Scott M Stark There is a ClassCastException at execution time on Jboss since version 3.2.6 (it worked on 3.2.5 but neither on 3.2.6 nor on 3.2.7) when calling an EJB finder query defined as follow with Xdoclet tags : @ejb.finder * view-type = local * signature=test.ProductLocal findByRefToAndToLicense(java.lang.String refTo, java.lang.String license) * result-type-mapping=Local * method-intf=LocalHome * query=SELECT DISTINCT pr.id FROM TourOperator to, IN ( to.products ) AS pr WHERE to.licenseNumber = ?2 AND pr.refTo = ?1 * The trace is given after when jboss is in trace log level. I also tested the same query with a return of type Collection and it worked well. So I think the Cast problem is that I declared the result as ProductLocal and not Collection but it should be working without using a Collection since I known by construction that the result of the search is either 0 or 1. Here is the trace : 16:03:09,690 TRACE [Registry] lookup 491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB 16:03:09,690 TRACE [StatelessSessionContainer] METHOD HOME INVOKE 491837535||create||[Ljava.lang.Object;@1900f17 16:03:09,690 TRACE [LogInterceptor] Start method=create 16:03:09,690 TRACE [TxInterceptorCMT] Current transaction in MI is null 16:03:09,690 TRACE [TxInterceptorCMT] TX_REQUIRED for create timeout=0 16:03:09,690 TRACE [TxInterceptorCMT] Thread came in with tx null 16:03:09,690 TRACE [TransactionImpl] Created new instance for tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [TxInterceptorCMT] Starting new tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [TxInterceptorCMT] TxInterceptorCMT: In finally 16:03:09,690 TRACE [TransactionImpl] Committing, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE 16:03:09,690 TRACE [TransactionImpl] Before completion done, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE 16:03:09,690 TRACE [TransactionImpl] Zero phase commit: No resources. 16:03:09,690 TRACE [TransactionImpl] Committed OK, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//25, BranchQual=] 16:03:09,690 TRACE [LogInterceptor] End method=create 16:03:09,752 TRACE [Registry] lookup 491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB 16:03:09,752 TRACE [StatelessSessionContainer] METHOD REMOTE INVOKE 491837535||searchProductIDByRefToAndLicenseNumber|| 16:03:09,752 TRACE [LogInterceptor] Start method=searchProductIDByRefToAndLicenseNumber 16:03:09,752 TRACE [TxInterceptorCMT] Current transaction in MI is null 16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for searchProductIDByRefToAndLicenseNumber timeout=0 16:03:09,752 TRACE [TxInterceptorCMT] Thread came in with tx null 16:03:09,752 TRACE [TransactionImpl] Created new instance for tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [TxInterceptorCMT] Starting new tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [StatelessSessionInstancePool] Get instance [EMAIL PROTECTED] test.ProductSearchSession 16:03:09,752 TRACE [CachedConnectionManager] new stack for key: [EMAIL PROTECTED] 16:03:09,752 TRACE [ProxyFactoryFinderInterceptor] invokerBInding is null in ProxyFactoryFinder 16:03:09,752 TRACE [LogInterceptor] Start method=findByRefToAndToLicense 16:03:09,752 TRACE [TxInterceptorCMT] Current transaction in MI is TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for findByRefToAndToLicense timeout=0 16:03:09,752 TRACE [TxInterceptorCMT] Thread came in with tx TransactionImpl:XidImpl [FormatId=257, GlobalId=NICOLAS//26, BranchQual=] 16:03:09,752 TRACE [EntityInstancePool] Get instance [EMAIL PROTECTED] test.ProductCMP 16:03:09,752 TRACE [CachedConnectionManager] old stack for key: [EMAIL PROTECTED] 16:03:09,752 DEBUG [Product#findByRefToAndToLicense] Executing SQL: SELECT DISTINCT t0_pr.ID FROM tour_operator t1_to, product t0_pr WHERE ((t1_to.LICENSE = ? AND t0_pr.REF_TO = ?)) AND t1_to.ID=t0_pr.TO_ID 16:03:09,752 TRACE [TransactionImpl]
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
yes, you should work on that I think. This should be done as a an interceptor placed after the ViewInterceptor. It needs to iterate all the windows selected for this request and retain only those who can produce the selected content type. On the Window object you can get the Instance and on the Instance you can get the Component object. On that Component object you have a method getContentTypes() which returns a plugin of the component responsible for managing the associations between component and content types. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865525#3865525 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865525 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JGRP-32) UnicastTest too slow
UnicastTest too slow Key: JGRP-32 URL: http://jira.jboss.com/jira/browse/JGRP-32 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-31) Problem with MERGE2 when not using multicast
[ http://jira.jboss.com/jira/browse/JGRP-31?page=history ] Bela Ban updated JGRP-31: - Fix Version: 2.2.8 (was: 2.2.9) Problem with MERGE2 when not using multicast Key: JGRP-31 URL: http://jira.jboss.com/jira/browse/JGRP-31 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN Java 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Fix For: 2.2.8 Hi, There is one case in which MERGE2 will fail while using TCPPING/UDP(without mcast): The initial_hosts property is abc.com[7800];xyz.com[7801]. These 2 machines are permanent group members (if they are up, they will be members of the group). Now there are numerous other programs on different machines that may dynamically join and leave the group. These members are not known before hand and cannot be specified in the initial_hosts property. The members on abc.com and xyz.com are started and they join the same group. Now another member from mnop.com starts and joins the group. The co-ordinator will be abc.com A network problem occurs and mnop.com is separated from abc.com and xyz.com mnop.com forms its own single-member group with itself as the co-ordinator. Now suppose the network problem is fixed. The MERGE2 protocol on mnop.com periodically checks on the initial_hosts list to see if they are up. It now finds that abc.com is reachable and decides that abc.com is the leader (by lexical sorting) and will take care of the merging. So it does not go ahead with the merge. On the other hand, the MERGE2 protocol on both abc.com and xyz.com just check if they can find members on the initial_hosts with a different co-ordinator. Both of them never consider mnop.com as it is not in the initial_hosts list So mnop.com will never be merged with the group. Even the new MERGE3 MERGEFAST protocols don't seem to help here. I checked them out and found the following: MERGEFAST works only if multicast is used, which is not my case. MERGE3 just sends I am co-ordinator messages to a null destination. So in the case where multicast is enabled, it goes to all possible members. But in my case, with multicast disabled, the message will only be unicast to each member of the current group. So in the above example, the I am co-ordinator messages will never go to mnop.com after the network problem. So even MERGE3 does not work in this case. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-27) UNICAST: use cases that test window_size and min_threshold
[ http://jira.jboss.com/jira/browse/JGRP-27?page=history ] Bela Ban updated JGRP-27: - Fix Version: 2.2.8 (was: 2.2.9) UNICAST: use cases that test window_size and min_threshold -- Key: JGRP-27 URL: http://jira.jboss.com/jira/browse/JGRP-27 Project: JGroups Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.2.8 -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ 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)] - top-down entity modelling support
I've looked at the notes from the recent conference call. One extra thing I would like to see is top-down modelling support from diagrams, as well as middlegen-style bottom-up reverse engineering from existing databases. For 'clean-room' projects, top-down is an important ability, to let the requirements at one level drive the implementation at the next level. So I am just talking about UML class diagrams here. This is something we have implemented in our development processes using Andromda and Poseidon, but it this is very heavyweight, not 'nice', and it would be much better to have this integrated using EMF providing only the relevant functionality. Basically, model entities, their relationships, and documentation. I am actually quite keen to work on this myself, because I have experience of parsing UML 2.0 entity models and generating code. Components would be something like: UML class diagram editor, maintaining 2.0-compliant XMU | transformation to selected persistence technology (start with Hibernate, then EJB3, should EJB2 also be supported?), using e.g. velocity | | To begin with, support might not be bi-directional, e.g. just generate from the model. Integrating changes from the generated sources back to the model could come later. | | What do you think to this? Are some of the components available already, e.g. UML class-diagram editor based on EMF with compatible license? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865536#3865536 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865536 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ 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)] - Re: top-down entity modelling support
Bah! Clicked on Submit not Preview. Let me rewrite the latter part of that post: anonymous wrote : | Components would be something like: |UML class diagram editor, maintaining 2.0-compliant XMI |Transformation to selected persistence technology (start with Hibernate, then EJB3, should EJB2 also be supported?), using e.g. velocity | | To begin with, support might not be bi-directional, e.g. just generate from the model. Integrating changes from the generated sources back to the model could come later. | | What do you think to this? Are some of the components available already, e.g. UML class-diagram editor based on EMF with compatible license? | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865538#3865538 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865538 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
anonymous wrote : This should be done as a an interceptor placed after the ViewInterceptor. It needs to iterate all the windows selected for this request and retain only those who can produce the selected content type. | | On the Window object you can get the Instance and on the Instance you can get the Component object. | | On that Component object you have a method getContentTypes() which returns a plugin of the component responsible for managing the associations between component and content types. Questions: 1. Can we say window=page ? 2. How will we deal with composition of page ? I have suggested to dislplay links to portlets instead of portlets itself in those cases when we have WML, cHTML and xHTML. This meen that not only certain portlets are included into a page, but the page itself looks differently depending on user agent's prefered markup . 3. How about making a plugin or even portal's service which would provide WURFL's functionality to all parts (pages, portlets, etc.) of portal ? HAR? SAR ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865540#3865540 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865540 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: NullPointerException: TreeCache.put
Hi Ben,
Exception got fixed after anonymous wrote : cache usage=transactional/
tag in one of the hibernate class was removed from hibernate mapping file . and
after application was deploed in tomcat 5.0:
Also please not that, if
hibernate.cache.provider_class=net.sf.hibernate.cache.TreeCacheProvider
is replaced with following(coherence caching), everything works without need to
change mapping file. And I was able to see cache keys(coherence) on web
console(weblogic):
hibernate.cache.provider_class=net.sf.hibernate.cache.CoherenceCacheProvider
I am using hibernate 2.1.8 JBossCache 1.2.
Here are the files:
treecache.xml(don't know whether this correct at all):
?xml version=1.0 encoding=UTF-8?
| server
| classpath codebase=./lib archives=jboss-cache.jar, jgroups.jar/mbean
code=org.jboss.cache.TreeCache name=jboss.cache:service=TreeCache
| dependsjboss:service=Naming/depends
| dependsjboss:service=TransactionManager/depends
| !-- attribute
name=TransactionManagerLookupClassorg.jboss.cache.DummyTransactionManagerLookup/attribute--
|
| attribute name=IsolationLevelREPEATABLE_READ/attribute
| attribute name=ClusterNameTreeCache-Cluster/attribute
| attribute name=CacheModeREPL_SYNC/attribute
| attribute name=SyncReplTimeout1/attribute
| attribute name=LockAcquisitionTimeout15000/attribute
| attribute name=FetchStateOnStartuptrue/attribute
| attribute name=EvictionPolicyClass
| org.jboss.cache.eviction.LRUPolicy
| /attribute
| attribute name=EvictionPolicyConfig
| config
| attribute name=wakeUpIntervalSeconds5/attribute
|
| /config
| /attribute
| attribute name=ClusterConfig
| config
| UDP mcast_addr=224.10.10.10 mcast_port=45566
| ip_ttl=64 ip_mcast=true
| mcast_send_buf_size=15 mcast_recv_buf_size=8
| ucast_send_buf_size=15 ucast_recv_buf_size=8
| loopback=false bind_addr=127.0.0.1/
| PING timeout=2000 num_initial_members=3
| up_thread=false down_thread=false/
| MERGE2 min_interval=1 max_interval=2/
| FD_SOCK/
| VERIFY_SUSPECT timeout=1500
| up_thread=false down_thread=false/
| pbcast.NAKACK gc_lag=50
retransmit_timeout=600,1200,2400,4800
| max_xmit_size=8192 up_thread=false
down_thread=false/
| UNICAST timeout=600,1200,2400 window_size=100
min_threshold=10
| down_thread=false/
| pbcast.STABLE desired_avg_gossip=2
| up_thread=false down_thread=false/
| FRAG frag_size=8192
| down_thread=false up_thread=false/
| pbcast.GMS join_timeout=5000 join_retry_timeout=2000
| shun=true print_local_addr=true/
| pbcast.STATE_TRANSFER up_thread=true down_thread=true/
| /config
| /attribute
| /mbean
| /server
|
|
jdbc.properties which is used to initialize hibernate configuration with spring:
jdbc.driverClassName=org.hsqldb.jdbcDriver
| jdbc.url=jdbc:hsqldb:hsql://localhost:1476
| jdbc.username=sa
| jdbc.password=
| hibernate.show_sql=true
| hibernate.dialect=net.sf.hibernate.dialect.HSQLDialect
| hibernate.cache.provider_class=net.sf.hibernate.cache.TreeCacheProvider
|
#hibernate.cache.provider_class=net.sf.hibernate.cache.CoherenceCacheProvider
| hibernate.c3p0.minPoolSize=5
| hibernate.c3p0.maxPoolSize=20
| hibernate.c3p0.timeout=1800
| hibernate.c3p0.max_statement=50
|
applicationContext.xml of spring:
?xml version=1.0 encoding=UTF-8?
| !DOCTYPE beans PUBLIC -//SPRING//DTD BEAN//EN
http://www.springframework.org/dtd/spring-beans.dtd;
|
| !--
| - Application context definition for Petclinic on Apache OJB.
| --
| beans
|
|
| bean id=propertyConfigurer
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
| property
name=locationvalue/WEB-INF/jdbc.properties/value/property
| /bean
| bean id=dataSource
class=org.springframework.jdbc.datasource.DriverManagerDataSource
| property
name=driverClassNamevalue${jdbc.driverClassName}/value/property
| property name=urlvalue${jdbc.url}/value/property
| property
name=usernamevalue${jdbc.username}/value/property
| property
name=passwordvalue${jdbc.password}/value/property
| /bean
|
| bean id=sessionFactory
class=org.springframework.orm.hibernate.LocalSessionFactoryBean
| property name=dataSourceref local=dataSource//property
| property name=mappingResources
| valuevz/esm/vcm/core/vcm-core.hbm.xml/value
|
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
anonymous wrote : On that Component object you have a method getContentTypes() which returns a plugin of the component responsible for managing the associations between component and content types. In addition also I would like to set the preferred markup for the portal together with the MIME type. Pages and portlets will get it from the request. What do you think is the best way to set this attribute to the portal ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865545#3865545 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865545 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
[EMAIL PROTECTED] wrote : actually portlet has to use the request.getResponseContentType() to know which mime type has been decided for that request. | Truth, but markup!=MIME. For example: Markup MIME -- html text/html chtml text/html xhtml text/html wml text/vnd.wap.wml This meens, we have the same MIME for different markups. In fact, portlet would like to know what markup is expected by the current User Agent and it would form the corresponding content. We have the tag. It's rendered in different way in WML and cHTML/xHTML. There are more difference(, and so on), quite small but important . My idea is to provide portlets with all information which can be important when the content is rendered. So, I think we could provide this info in a header. What do you think about it ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865547#3865547 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865547 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
anonymous wrote : | This meens, we have the same MIME for different markups. In fact, portlet would like to know what markup is expected by the current User Agent and it would form the corresponding content. | We have the br tag. It's rendered in different way in WML and cHTML/xHTML. There are more difference(input, body and so on), quite small but important . My idea is to provide portlets with all information which can be important when the content is rendered. So, I think we could provide this info in a header. What do you think about it ? | Well, my example tags were taken into account by the forumin my previous post ;) . View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865549#3865549 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865549 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - TreeCache Security
Hello, we are using multiple tree cache instance which successfully connect to each other. If I want to prevent that I will use different cluster names. I've read the FAQ and the TreeCache HTML documentation and still have some questions unanswered: - TreeCaches use multicast to announce them to each other, right? - Do TreeCaches use multicast or unicast to replicate state? - Currently I didn't find any mechanism to define a common passphrase that is needed together with the cluster name so that only authorized caches can connect to each other. Are there any plans to do this? - How can I configure my cache so that it is only possible for to IP addresses to share information and they don't offer their content to malicious hosts? Thanks, Ralf View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865550#3865550 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865550 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Metadata not getting picked up for all invocations.
Hi, Sorry, but caller side metadata is not yet implemented. I have added it as a task to our JIRA: http://jira.jboss.com/jira/browse/JBAOP-74 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865552#3865552 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865552 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-74) Add metadata for caller invocations
Add metadata for caller invocations --- Key: JBAOP-74 URL: http://jira.jboss.com/jira/browse/JBAOP-74 Project: JBoss AOP Type: Feature Request Versions: 1.1 Reporter: Kabir Khan Assigned to: Bill Burke http://www.jboss.org/index.html?module=bbop=viewtopict=58139 -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1386) commit option B does not work with CMP 1.x
commit option B does not work with CMP 1.x
--
Key: JBAS-1386
URL: http://jira.jboss.com/jira/browse/JBAS-1386
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-4.0.1 Final
Environment: jdk 1.4.2 on linux
Reporter: Peter Doornbosch
Assigned to: Scott M Stark
When accessing a CMP 1.x entity bean with the commit option set to B, and the
bean is already loaded (by a previous invocation), the bean is not loaded again
from the database (as it should with commit option B). This can be easily
verified by deploying such a bean and enabling sql logging.
The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
public void resetPersistenceContext(EntityEnterpriseContext ctx)
{
if(isReadTimedOut(ctx))
{
JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
}
}
Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does nothing,
because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and the
EntityState is not affected by this call. Hence, after this method, the state
of the field is still loaded, and thus this field is not part of the
load-iterator created by JDBCEntityBridge.
I think the fix is rather easy: just reset the field flags explicitely (as it
is done in the cmp 2.x case), e.g.
jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1386) commit option B does not work with CMP 1.x
[ http://jira.jboss.com/jira/browse/JBAS-1386?page=history ]
Peter Doornbosch updated JBAS-1386:
---
Attachment: employee-ejb.jar
The jar file contains my test case: a very simple entity bean. It uses a
(non-standard) configuration named Standard CMP EntityBean Commit Option B,
which is just a copy of the standard Standard CMP EntityBean with the commit
option set to B.
I used the class ejbs.test.ViewEmployee in this jar to create an instance of
the bean and to reproduce the described behaviour.
commit option B does not work with CMP 1.x
--
Key: JBAS-1386
URL: http://jira.jboss.com/jira/browse/JBAS-1386
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-4.0.1 Final
Environment: jdk 1.4.2 on linux
Reporter: Peter Doornbosch
Assignee: Scott M Stark
Attachments: employee-ejb.jar
When accessing a CMP 1.x entity bean with the commit option set to B, and the
bean is already loaded (by a previous invocation), the bean is not loaded
again from the database (as it should with commit option B). This can be
easily verified by deploying such a bean and enabling sql logging.
The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
public void resetPersistenceContext(EntityEnterpriseContext ctx)
{
if(isReadTimedOut(ctx))
{
JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
}
}
Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does
nothing, because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and
the EntityState is not affected by this call. Hence, after this method, the
state of the field is still loaded, and thus this field is not part of the
load-iterator created by JDBCEntityBridge.
I think the fix is rather easy: just reset the field flags explicitely (as it
is done in the cmp 2.x case), e.g.
jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: TreeCache Security
ralf.siedow wrote : Hello, | | we are using multiple tree cache instance which successfully connect to each other. If I want to prevent that I will use different cluster names. | | I've read the FAQ and the TreeCache HTML documentation and still have some questions unanswered: | - TreeCaches use multicast to announce them to each other, right? | Not necessarily, this depends on the configuration of the JGroups reliable transport anonymous wrote : | - Do TreeCaches use multicast or unicast to replicate state? | 'Multi-point'. Multicast or multiple TCP connections, depending on the JGroups config anonymous wrote : | - Currently I didn't find any mechanism to define a common passphrase that is needed together with the cluster name so that only authorized caches can connect to each other. Are there any plans to do this? | This can be done on the JGroups level. Read JGroups/doc/ENCRYPT.html for an explanation of how to do this. anonymous wrote : | - How can I configure my cache so that it is only possible for to IP addresses to share information and they don't offer their content to malicious | Use a different 1: partition name 2: multicast address 3: multicast port you can and or or these together View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865561#3865561 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865561 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=history ] Ryan Campbell reassigned JBBUILD-8: --- Assign To: Ryan Campbell Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.781 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050207065007Lbuild.781 BUILD COMPLETE-build.781Date of build:02/07/2005 06:50:07Time to build:30 minutes 44 secondsLast changed:02/07/2005 05:43:45Last log entry:Remove trailing bracket Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(13)1.39modifiedtdieslercache/src/main/org/jboss/cache/aop/TreeCacheAop.javaRemove trailing bracket1.8modifiedkabkhanaop/docs/reference/reference/en/modules/compiling.xml*** empty log message ***1.38modifiedbelabancache/src/main/org/jboss/cache/aop/TreeCacheAop.javafixed compilation error1.37modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaAdded comments1.10modifiedrecampbelltools/etc/jbossbuild/tasks.xmladded build.resources1.7modifiedrecampbelltools/lib/jbossbuild.jaradded resourcedef to jbossbuild1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/commandlinetools.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/featurematrix.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/goals.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/java2wsdl.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/wsdl2java.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/build.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/master.xmlDocbook files for the JBossWS Tools project !
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1386) commit option B does not work with CMP 1.x
[
http://jira.jboss.com/jira/browse/JBAS-1386?page=comments#action_12315200 ]
Peter Doornbosch commented on JBAS-1386:
My previous remark that 'new FieldState(jdbcCtx)' effectively does nothing
should have been: does not reset the field flags. It does one thing: it
causes the original field value to be discarded. This is correct (and
necessary), but in combination with the fact that the instance is not reloaded
this causes the bean to be updated always, even when no field is modified.
commit option B does not work with CMP 1.x
--
Key: JBAS-1386
URL: http://jira.jboss.com/jira/browse/JBAS-1386
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-4.0.1 Final
Environment: jdk 1.4.2 on linux
Reporter: Peter Doornbosch
Assignee: Scott M Stark
Attachments: employee-ejb.jar
When accessing a CMP 1.x entity bean with the commit option set to B, and the
bean is already loaded (by a previous invocation), the bean is not loaded
again from the database (as it should with commit option B). This can be
easily verified by deploying such a bean and enabling sql logging.
The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
public void resetPersistenceContext(EntityEnterpriseContext ctx)
{
if(isReadTimedOut(ctx))
{
JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
}
}
Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does
nothing, because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and
the EntityState is not affected by this call. Hence, after this method, the
state of the field is still loaded, and thus this field is not part of the
load-iterator created by JDBCEntityBridge.
I think the fix is rather easy: just reset the field flags explicitely (as it
is done in the cmp 2.x case), e.g.
jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
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)] - VerifyError in JBossIDE-1.4.1's JSP editor
After updating to the 1.4.1 version, the Jsp editor no longer works. When I try to open a jsp file, I get a failure 'could not create part'. The eclipse .log file contains : java.lang.VerifyError: class org.jboss.ide.eclipse.jdt.j2ee.jsp.ui.assist.JSPResultCollector overrides final method . at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:308) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.defineClass(EclipseClassLoader.java:223) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClassImpl(DefaultClassLoader.java:291) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClass(DefaultClassLoader.java:172) at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.findLocalClass(AbstractClassLoader.java:221) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.basicFindLocalClass(EclipseClassLoader.java:135) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:59) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:328) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:354) at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:94) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.jboss.ide.eclipse.jdt.j2ee.jsp.ui.editors.JSPConfiguration.getContentAssistant(JSPConfiguration.java:192) [...] Setup: - Debian GNU/Linux (sid) - Java version 1.4.2_07 - eclipse-SDK-I20050202-0800-linux-gtk.tar.gz - JBossIDE-1.4.1-jre1.4-e31.zip View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865569#3865569 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865569 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ 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)] - Re: JBossIDE New Extension Wishlists
I would like to see good support for the web services client/server programming model. Server This involves adding annotations to the service endpoint interface (SEI) and generate the required WS4EE deployment artifacts. These are WSDL, XML Schema, jaxrpc-mapping.xml Client --- This involves pointing to a local/remote WSDL and generate the WS4EE required client artifacts. These are service interface (SI), SEI, complex user types, jaxrpc-mapping.xml. There should be a good integration between the jbossws tools project and JBossIDE. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865572#3865572 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865572 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
what are the differences between CHTML and others (HTML and XHTML) ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865574#3865574 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865574 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1386) commit option B does not work with CMP 1.x
[ http://jira.jboss.com/jira/browse/JBAS-1386?page=history ]
Alexey Loubyansky reassigned JBAS-1386:
---
Assign To: Alexey Loubyansky (was: Scott M Stark)
commit option B does not work with CMP 1.x
--
Key: JBAS-1386
URL: http://jira.jboss.com/jira/browse/JBAS-1386
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-4.0.1 Final
Environment: jdk 1.4.2 on linux
Reporter: Peter Doornbosch
Assignee: Alexey Loubyansky
Attachments: employee-ejb.jar
When accessing a CMP 1.x entity bean with the commit option set to B, and the
bean is already loaded (by a previous invocation), the bean is not loaded
again from the database (as it should with commit option B). This can be
easily verified by deploying such a bean and enabling sql logging.
The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
public void resetPersistenceContext(EntityEnterpriseContext ctx)
{
if(isReadTimedOut(ctx))
{
JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
}
}
Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does
nothing, because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and
the EntityState is not affected by this call. Hence, after this method, the
state of the field is still loaded, and thus this field is not part of the
load-iterator created by JDBCEntityBridge.
I think the fix is rather easy: just reset the field flags explicitely (as it
is done in the cmp 2.x case), e.g.
jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1386) commit option B does not work with CMP 1.x
[
http://jira.jboss.com/jira/browse/JBAS-1386?page=comments#action_12315202 ]
Alexey Loubyansky commented on JBAS-1386:
-
Not really. CMP1 has its own FieldState which has no connection to EntityState,
though, perhaps, it should.
commit option B does not work with CMP 1.x
--
Key: JBAS-1386
URL: http://jira.jboss.com/jira/browse/JBAS-1386
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-4.0.1 Final
Environment: jdk 1.4.2 on linux
Reporter: Peter Doornbosch
Assignee: Alexey Loubyansky
Attachments: employee-ejb.jar
When accessing a CMP 1.x entity bean with the commit option set to B, and the
bean is already loaded (by a previous invocation), the bean is not loaded
again from the database (as it should with commit option B). This can be
easily verified by deploying such a bean and enabling sql logging.
The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
public void resetPersistenceContext(EntityEnterpriseContext ctx)
{
if(isReadTimedOut(ctx))
{
JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
}
}
Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does
nothing, because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and
the EntityState is not affected by this call. Hence, after this method, the
state of the field is still loaded, and thus this field is not part of the
load-iterator created by JDBCEntityBridge.
I think the fix is rather easy: just reset the field flags explicitely (as it
is done in the cmp 2.x case), e.g.
jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
anonymous wrote : what are the differences between CHTML and others (HTML and XHTML) ? Most of those differences are related to markup tags and their attributes - it depends how device renders certain tag and it's attributes. Some devices simply ignores the rest part of content if unsupported combination is found. Please, take a look at this refference, here you'll find most of differences with markups: http://wurfl.sourceforge.net/java/refguide.php That's why I would like to provide portlets with additional info regarding markups preferred by certain User Agent. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865577#3865577 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865577 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
so the best place would be the request properties under a specific key View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865580#3865580 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865580 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - JBoss Portal and Applets
Are there any known limitations for JBoss Portal to work with applets? We having a problem - our web application uses applets and it works fine with other portals. It only fails on JBoss Portal. Any known issues? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865581#3865581 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865581 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assigned to: Bela Ban Priority: Critical I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM default (64M). The 10 programs join the same JGroup and the threads in the programs keep publishing a small hashmap at 5 second intervals. The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing OutOfMemory errors on all instances. I have run the program on unix and windows machines with 1G RAM. Not able to make much from an HProf output of one of the instances. This seems to be the cause for the JBossCache bug http://jira.jboss.com/jira/browse/JBCACHE-31; too. I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both cases. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Trouble - hadcoded MIME type and restrictions
anonymous wrote : so the best place would be the request properties under a specific key Where can I look for an example ? I mean, the existing portal's code. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865582#3865582 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865582 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=comments#action_12315203 ] B.S.Navin commented on JGRP-33: --- Have tried reproduced this issue with the JGroups 2.2.7 release as well as the latest JGroups HEAD. JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM default (64M). The 10 programs join the same JGroup and the threads in the programs keep publishing a small hashmap at 5 second intervals. The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing OutOfMemory errors on all instances. I have run the program on unix and windows machines with 1G RAM. Not able to make much from an HProf output of one of the instances. This seems to be the cause for the JBossCache bug http://jira.jboss.com/jira/browse/JBCACHE-31; too. I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both cases. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ] B.S.Navin updated JGRP-33: -- Attachment: PublishThread2.java JGroupsMemTest.java runj10.sh The sample programs execution script for the reproducing the issue JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Attachments: JGroupsMemTest.java, PublishThread2.java, runj10.sh I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM default (64M). The 10 programs join the same JGroup and the threads in the programs keep publishing a small hashmap at 5 second intervals. The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing OutOfMemory errors on all instances. I have run the program on unix and windows machines with 1G RAM. Not able to make much from an HProf output of one of the instances. This seems to be the cause for the JBossCache bug http://jira.jboss.com/jira/browse/JBCACHE-31; too. I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both cases. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ] B.S.Navin updated JGRP-33: -- Attachment: fc-fast-udp.xml fc-fast-udp-tcpping.xml Configuration files used for UDP/PING UDP/TCPPING JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, runj10.sh I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM default (64M). The 10 programs join the same JGroup and the threads in the programs keep publishing a small hashmap at 5 second intervals. The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing OutOfMemory errors on all instances. I have run the program on unix and windows machines with 1G RAM. Not able to make much from an HProf output of one of the instances. This seems to be the cause for the JBossCache bug http://jira.jboss.com/jira/browse/JBCACHE-31; too. I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both cases. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: javax.servlet.ServletException: no main
the context name doesn't seem to make the difference. I checked it over several times, tried to deploy as an EAR and as a WAR with no success. Looks like something's missing in the doc. Perhaps a web.xml entry (Servlet, listener)? I started to debug the issue, but haven't figured it out yet (too much new code and my head's spinning ;) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865584#3865584 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865584 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ] Bela Ban updated JGRP-33: - Fix Version: 2.2.8 JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, runj10.sh I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM default (64M). The 10 programs join the same JGroup and the threads in the programs keep publishing a small hashmap at 5 second intervals. The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing OutOfMemory errors on all instances. I have run the program on unix and windows machines with 1G RAM. Not able to make much from an HProf output of one of the instances. This seems to be the cause for the JBossCache bug http://jira.jboss.com/jira/browse/JBCACHE-31; too. I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both cases. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Invalidation / Lazy Replication
Hi, We are currently developing a client/server application. The server uses Hibernate for persistence, with TreeCache for the second-level cache. The clients need local data caches, and we were thinking that an easy way of implementing these local client caches might be to replicate the server cache to all the clients. However, we are hesitant to go this route due to the amount of data that could be involved. There are two cache features that would make the outlined implementation more palatable: - An invalidation model. When a node gets updated on the server, the clients receive notification that the specified node is no longer valid, but do not retrieve the data itself. - Lazy replication. When invalidated/uninitialized nodes are accessed on the clients, the data is retrieved transparently from the server cache. I have searched the forums and have found a couple of similar questions, some suggesting the use of a custom CacheLoader, or perhaps SharedStoreCacheLoader or DelegatingCacheLoader. However, neither of these can be configured via XML (no empty constructor), and even configuring them via code, it's not clear whether or not you can specify remote CacheLoader's/TreeCache's to delegate to. I'd be interested to hear what people think our options might be. Aside from switching to OSCache ;-) Regards, Daniel Gredler View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865588#3865588 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865588 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Caches being combined
How about just changing the ClusterName? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865592#3865592 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865592 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1115) bad path to included xsd gets built in WSDLFilePublisher
[ http://jira.jboss.com/jira/browse/JBAS-1115?page=comments#action_12315208 ] Thomas Diesler commented on JBAS-1115: -- Thanks for the good feedback bad path to included xsd gets built in WSDLFilePublisher Key: JBAS-1115 URL: http://jira.jboss.com/jira/browse/JBAS-1115 Project: JBoss Application Server Type: Bug Components: Web Services service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: mazzgolf . Problem when deploying a web service whose WSDL imports/includes other WSDL/schemas. See attached for a simple hello.war that illustrates this problem. To replicate, simply place the war file in the JBoss deploy directory and start. I don't think this has anything to do with platforms, but just in case - this is on JBoss 4.0, JDK 1.4.2, Windows XP SP1. Description: My web service WSDL imports another WSDL which in turn includes a schema (these are WSRF specification files). It looks like WSDLFilePublisher is not building the path correctly to that included schema. It's missing a / in one spot and has a double slash // in another spot. While debugging in WSDLFilePublisher, line 206 results in this as value for resourcePath: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd Note that there is a / missing between the last directory wsrf and the schema filename WS- ResourceProperties-1_1.xsd. There is also a double slash // in there as well. The double-slash is probably OK and most file systems will parse it fine, however, obviously the missing slash is going to cause problems (which it does on my box). The value of this.expLocation was WEB-INF/wsdl/ and the value of schemaLocation was WS- ResourceProperties-1_1.xsd. baseURI had a value of file:/C:/mazz/jboss/jboss- 4.0.0/server/default/data/wsdl/jboss- wsdm.war/services/../spec/wsrf/WS-ResourceProperties- 1_1.wsdl. this.di.shortName is jboss-wsdm.war. index is 57. All of those values are correct. The WSDL includes the .xsd like this: wsd:typesxsd:schema xsd:include schemaLocation=WS-ResourceProperties- 1_1.xsd/ ... The resulting exception is (which is actually thrown in line 210): 16:13:24,774 ERROR [ServiceDeployer] Cannot startup webservice for: jboss-wsdm.war org.jboss.deployment.DeploymentException: Cannot publish wsdl to: C:\mazz\jboss\jboss-4.0.0 \server\default\data\wsdl\jboss- wsdm.war\services\sensor.wsdl; - nested throwable: (java.lang.IllegalArgumentException: Cannot find schema import in deployment: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd) at org.jboss.webservice.WSDLFilePublisher.publishWsdlFile (WSDLFilePublisher.java:106) If, in my debugger, I fix the resourcePath evaluated on line 205 such that the path has the proper slashes, my web service deploys fine. In this example, its as if I made this fix on line 205 of WSDLFilePublisher.java from: resourcePath = resourcePath.substring(0, resourcePath.lastIndexOf(/)); to: resourcePath = resourcePath.substring(1, resourcePath.lastIndexOf(/) + 1); Obviously, it would be best if no assumptions were made about the location of / (that is to say, don't assume resourcePath has a leading / - I do above and hence the 1 in the first argument to substring). Probably would be better if we do something like this for the first parameter to that substring: resourcePath.charAt(0) == / ? 1 : 0 Same holds true with that second argument. We should not do the +1 if we know the schemaLocation is an absolute path. Otherwise, we'd introduce another double slash. So, perhaps, line 205 should be the following: resourcePath = resourcePath.substring (resourcePath.chatAt(0) == / ? 1 : 0, resourcePath.lastIndexOf(/) + (schemaLocation.charAt (0) == / ? 0 : 1)); I'll leave it up to the commiter to decide the best course of action. John Mazz -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1381) Clustering with CrossContext Enabled generates exception
[ http://jira.jboss.com/jira/browse/JBAS-1381?page=comments#action_12315209 ] Scott M Stark commented on JBAS-1381: - A testcase for this needs to be added to the existing clustering unit tests. Clustering with CrossContext Enabled generates exception Key: JBAS-1381 URL: http://jira.jboss.com/jira/browse/JBAS-1381 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-4.0.1 Final Reporter: Ben Wang Assignee: Ben Wang Fix For: JBossAS-4.0.1 SP1 Original Estimate: 2 hours Remaining: 2 hours Excerpt from sf case: https://na1.salesforce.com/5003000bw4l We have a Big Application that are deployed as multiple WebApplications and they make crosscontext calls, When we enabled Clustering Seems like FirstCrossContext Failes on this Method. JBOSSCacheManager.createEmptySession(). We would appreciate if you can help us resolve this issue. Note: If i deploy this App on Default Server Configuration and it works fine Basically, the problem is createEmptySession is treated as a un-implemented method since it is also called by passivation and activation. But we will simply return this method call now with a new ClusteredSession instance (depending on the granularity, of course). -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1387) Config of jboss.deployment mbean does not work as specified
Config of jboss.deployment mbean does not work as specified --- Key: JBAS-1387 URL: http://jira.jboss.com/jira/browse/JBAS-1387 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.6 Final Environment: WindowsXP, Java1.5 Reporter: Yevgeny Shakhnovich Assigned to: Scott M Stark Priority: Minor I already reported this issue on the forum but did not get any response. This is why I repeat it here as a bug report. I have a problem with deploying of Tomcat in jboss 3.2.6 under JVM1.5 (I did not try another JVM) First time, I did not modify anything in the downloaded installation. I ran run.bat and everything looked fine. Then, I modified URLs attribute in jboss.deployment mbean in default/conf/jboss-service.xml. Namely, instead of referring to the entire directory by deploy/, I listed all files in the deploy directory, like Code: deploy/http-invoker.sar/, deploy/jboss-jca.sar deploy/jbossweb-tomcat50.sar/, deploy/jmx-invoker-adaptor-server.sar/, deploy/uuid-key-generator.sar, deploy/mail-service.xml, deploy/cache-invalidation-service.xml, deploy/client-deployer-service.xml, deploy/hibernate-deployer-service.xml, deploy/monitoring-service.xml, deploy/properties-service.xml, deploy/schedule-manager-service.xml, deploy/scheduler-service.xml, deploy/sqlexception-service.xml, deploy/transaction-service.xml, deploy/user-service.xml, deploy/jboss-local-jdbc.rar, deploy/jboss-xa-jdbc.rar, deploy/jmx-console.war/, deploy/jms/, deploy/management/, deploy/jsql-ds All services were deployed except Tomcat. The latter gave exception: Code: 2005-01-20 14:05:06,391 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-3.2.6/server/default/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:139) at org.jboss.system.ServiceController.install(ServiceController.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentSc anner.java:201) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja va:274) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271) at
[JBoss-dev] [Design of JBoss Portal] - Re: Theme development
My idea could be implemented on top of the 'theme' idea you are grappling with. I think for now, I'll plan on implementing it as a 'Skinnable' theme after we sort out the more general theme idea. So I guess my first thought is can we separate the UI (the 'Theme') into a separately deployable web application and establish an API into the server? (Still trying to get my head around the overall architecture, so let me know if I'm making invalid assumptions.) Is the API already there? Do we just need the tag libs? What kinds of things have potential to break the themes? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865600#3865600 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865600 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1388) Create property for deployment directory
Create property for deployment directory
Key: JBAS-1388
URL: http://jira.jboss.com/jira/browse/JBAS-1388
Project: JBoss Application Server
Type: Feature Request
Reporter: Yevgeny Shakhnovich
Assigned to: Scott M Stark
Priority: Trivial
It is not always convenient to put files for deployment into deploy
directory. JBoss provides the way to modify such default behavior through
attribute URLs of jboss.deployment mbean but it requires modification of
jboss-service.xml which is also inconvenient, especially taking in account the
frequency of jboss upgrades. I would prefer if in jboss-service.xml the URLs
attribute looked like
attribute name=URLs
${jboss.server.deploy.list}
/attribute
where the property jboss.server.deploy.list had the default value deploy/.
In that case, I could specify my components for deployment in the runtime in a
different directory without changing the jboss installation just by setting the
right value for the property. It would simplify upgrades to new jboss versions.
Thanks,
Yevgeny
--
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
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
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)] - Packaging configurations option not available in JBOSS IDE 1
Hi I am trying JBossIDE-1.5-Preview-jre1.5 for EJB3.0 features I got a HelloWorld session bean done, and I am looking to package and deploy. I saw there was package configuations option in the project properties (shown in JBoss Webinar for JBoss IDE 1.5), but that doesn't seem to be available in the above build I am using. Is the option shown in the demo not available in this build ? or do I need to install and extra plug-in ? thanks cmpuser View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865603#3865603 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865603 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.76 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050207105542Lbuild.76 BUILD COMPLETE-build.76Date of build:02/07/2005 10:55:42Time to build:57 minutes 13 secondsLast changed:02/07/2005 10:44:18Last log entry:javadoc update Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(115)1.16modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javajavadoc update1.16modifiedbelabancache/src/main/org/jboss/cache/interceptors/LockInterceptor.javastill working on it...1.3modifiedbelabantestsuite/src/main/org/jboss/test/cache/perf/basic/ReplicatedSyncPerfTestCase.javatrying to fix the failures1.1addedrecampbelljmx/jbossbuild.xmlinitial checkin for jmx module; demonstrates use of resource node1.11modifiedtdieslertools/etc/buildmagic/modules.xmlReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.30modifiedtdieslertools/etc/buildmagic/modules.entReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.387modifiedtdieslerbuild/build.xmlReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.11modifiedrecampbelljbossas/jbossbuild.xmlcomponents needed for jboss-jmx1.39modifiedtdieslercache/src/main/org/jboss/cache/aop/TreeCacheAop.javaRemove trailing bracket1.8modifiedkabkhanaop/docs/reference/reference/en/modules/compiling.xml*** empty log message ***1.38modifiedbelabancache/src/main/org/jboss/cache/aop/TreeCacheAop.javafixed compilation error1.37modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaAdded comments1.10modifiedrecampbelltools/etc/jbossbuild/tasks.xmladded build.resources1.7modifiedrecampbelltools/lib/jbossbuild.jaradded resourcedef to jbossbuild1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/commandlinetools.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/featurematrix.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/goals.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/java2wsdl.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/modules/wsdl2java.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/build.xmlDocbook files for the JBossWS Tools project !1.1addedosdchicagowebservice/docs/tools-docs/project/en/master.xmlDocbook files for the JBossWS Tools project !1.2modifiedccrouchadmin-console/src/resources/admin-console.war/WEB-INF/classes/messages/applicationmessages.propertiesview and controller layer code and tests for listing different types of datasources1.2modifiedccrouchadmin-console/src/resources/admin-console.war/WEB-INF/jsp/common/secondaryMenu.jspview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/console/web/struts/datasource/BaseDataSourceAction.javaview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/console/web/struts/datasource/ListDataSourcesAction.javaview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/test/org/jboss/admin/console/web/struts/datasource/ListDataSourcesActionTest.javaview and controller layer code and tests for listing different types of datasources1.2modifiedccrouchadmin-console/.classpathview and controller layer code and tests for listing different types of datasources1.2modifiedccrouchadmin-console/README.txtview and controller layer code and tests for listing different types of datasources1.6modifiedccrouchadmin-console/build.xmlview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/console/web/struts/BaseAction.javaview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/model/datasource/DataSource.javaview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/model/datasource/LocalTxDatasource.javaview and controller layer code and tests for listing different types of datasources1.1addedccrouchadmin-console/src/main/org/jboss/admin/model/datasource/NoTxDatasource.javaview and controller layer code and tests for listing different types of
[JBoss-dev] [JBoss JIRA] Resolved: (JBREM-61) Possible RMI exception semantic regression
[ http://jira.jboss.com/jira/browse/JBREM-61?page=history ] Tom Elrod resolved JBREM-61: - Resolution: Done Fix Version: 1.0.1 final Changed UnifiedInvokerProxy to catch AccessException and rethrow wrapped as ServerException. org.jboss.test.security.test.EJBSpecUnitTestCase is now passing. Possible RMI exception semantic regression -- Key: JBREM-61 URL: http://jira.jboss.com/jira/browse/JBREM-61 Project: JBoss Remoting Type: Bug Components: transport Reporter: Scott M Stark Assignee: Tom Elrod Fix For: 1.0.1 final The org.jboss.test.security.test.EJBSpecUnitTestCase.testDeepRunAs method is currently failing in head after the switch of the default invoker to the remoting based unified invoker due to a subtle difference in how exceptions are handled by the jrmp invoker. The test is expecting that the java.rmi.AccessException thrown by the ejb contaner be wrapped in a java.rmi.ServerException. This is a wrapping exception used by the jrmp implementation. The java.rmi.ServerException javadoc: A ServerException is thrown as a result of a remote method invocation when a RemoteException is thrown while processing the invocation on the server, either while unmarshalling the arguments, executing the remote method itself, or marshalling the return value. A ServerException instance contains the original RemoteException that occurred as its cause. The unified invoker is simply throwing back the java.rmi.AccessException. Although this looks like what the JRMPInvoker is doing, this ignores the fact that the jrmp implementation sits between the network and the client. We probably need a strictRMIException mode that allows for the same behavior. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-75) @Service
@Service Key: JBAOP-75 URL: http://jira.jboss.com/jira/browse/JBAOP-75 Project: JBoss AOP Type: Feature Request Components: Aspect Library Versions: 2.0 Reporter: Bill Burke Assigned to: Kabir Khan Fix For: 2.0 As stated in Aspect LIbrary Docuemnt -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-76) @Local/@Remote with deployment
@Local/@Remote with deployment -- Key: JBAOP-76 URL: http://jira.jboss.com/jira/browse/JBAOP-76 Project: JBoss AOP Type: Sub-task Versions: 2.0 Reporter: Bill Burke Assigned to: Kabir Khan Fix For: 2.0 Get the service component working with local/remote interfaces and deployable through the EJB3 container. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-77) @Management interface support
@Management interface support - Key: JBAOP-77 URL: http://jira.jboss.com/jira/browse/JBAOP-77 Project: JBoss AOP Type: Sub-task Components: Aspect Library Versions: 2.0 Reporter: Bill Burke Assigned to: Kabir Khan Fix For: 2.0 @Management defines a JMX management interface for the component. Create a Model MBean with the metadata defined by the @Management interfaces of the @Service bean. There should be some helper classes within the JMX CVS module that will help you to create the MBeanInfo metadata from the interface classes. For 1st iteration, just allow one management interface. Open up a future task for multiple management interfaces. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (EJBTHREE-63) @Local/@Remote with deployment
[ http://jira.jboss.com/jira/browse/EJBTHREE-63?page=history ] Bill Burke moved JBAOP-76 to EJBTHREE-63: - Project: EJB 3.0 (was: JBoss AOP) Key: EJBTHREE-63 (was: JBAOP-76) Version: (was: 2.0) Fix Version: (was: 2.0) @Local/@Remote with deployment -- Key: EJBTHREE-63 URL: http://jira.jboss.com/jira/browse/EJBTHREE-63 Project: EJB 3.0 Type: Sub-task Reporter: Bill Burke Assignee: Kabir Khan Get the service component working with local/remote interfaces and deployable through the EJB3 container. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (EJBTHREE-62) @Service
[ http://jira.jboss.com/jira/browse/EJBTHREE-62?page=history ] Bill Burke moved JBAOP-75 to EJBTHREE-62: - Project: EJB 3.0 (was: JBoss AOP) Key: EJBTHREE-62 (was: JBAOP-75) Issue Type: Task (was: Feature Request) Component: EJB3 Extensions (was: Aspect Library) Version: Preview 4 (was: 2.0) Fix Version: Preview 4 (was: 2.0) @Service Key: EJBTHREE-62 URL: http://jira.jboss.com/jira/browse/EJBTHREE-62 Project: EJB 3.0 Type: Task Components: EJB3 Extensions Versions: Preview 4 Reporter: Bill Burke Assignee: Kabir Khan Fix For: Preview 4 As stated in Aspect LIbrary Docuemnt -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (EJBTHREE-64) @Management interface support
[ http://jira.jboss.com/jira/browse/EJBTHREE-64?page=history ] Bill Burke moved JBAOP-77 to EJBTHREE-64: - Project: EJB 3.0 (was: JBoss AOP) Key: EJBTHREE-64 (was: JBAOP-77) Component: (was: Aspect Library) Version: (was: 2.0) Fix Version: (was: 2.0) @Management interface support - Key: EJBTHREE-64 URL: http://jira.jboss.com/jira/browse/EJBTHREE-64 Project: EJB 3.0 Type: Sub-task Reporter: Bill Burke Assignee: Kabir Khan @Management defines a JMX management interface for the component. Create a Model MBean with the metadata defined by the @Management interfaces of the @Service bean. There should be some helper classes within the JMX CVS module that will help you to create the MBeanInfo metadata from the interface classes. For 1st iteration, just allow one management interface. Open up a future task for multiple management interfaces. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-65) @Management interface support
@Management interface support - Key: EJBTHREE-65 URL: http://jira.jboss.com/jira/browse/EJBTHREE-65 Project: EJB 3.0 Type: Sub-task Components: EJB3 Extensions Versions: Preview 4 Reporter: Bill Burke Assigned to: Kabir Khan Fix For: Preview 4 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-65) @Management interface support
[ http://jira.jboss.com/jira/browse/EJBTHREE-65?page=history ] Bill Burke updated EJBTHREE-65: --- Description: @Management defines a JMX management interface for the component. Create a Model MBean with the metadata defined by the @Management interfaces of the @Service bean. There should be some helper classes within the JMX CVS module that will help you to create the MBeanInfo metadata from the interface classes. For 1st iteration, just allow one management interface. Open up a future task for multiple management interfaces. Environment: Version: Preview 4 Component: EJB3 Extensions Fix Version: Preview 4 @Management interface support - Key: EJBTHREE-65 URL: http://jira.jboss.com/jira/browse/EJBTHREE-65 Project: EJB 3.0 Type: Sub-task Components: EJB3 Extensions Versions: Preview 4 Reporter: Bill Burke Assignee: Kabir Khan Fix For: Preview 4 @Management defines a JMX management interface for the component. Create a Model MBean with the metadata defined by the @Management interfaces of the @Service bean. There should be some helper classes within the JMX CVS module that will help you to create the MBeanInfo metadata from the interface classes. For 1st iteration, just allow one management interface. Open up a future task for multiple management interfaces. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (EJBTHREE-64) @Management interface support
[ http://jira.jboss.com/jira/browse/EJBTHREE-64?page=history ] Bill Burke deleted EJBTHREE-64: --- @Management interface support - Key: EJBTHREE-64 URL: http://jira.jboss.com/jira/browse/EJBTHREE-64 Project: EJB 3.0 Type: Sub-task Reporter: Bill Burke Assignee: Kabir Khan @Management defines a JMX management interface for the component. Create a Model MBean with the metadata defined by the @Management interfaces of the @Service bean. There should be some helper classes within the JMX CVS module that will help you to create the MBeanInfo metadata from the interface classes. For 1st iteration, just allow one management interface. Open up a future task for multiple management interfaces. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-66) Asynchronous interface for all EJB types
Asynchronous interface for all EJB types Key: EJBTHREE-66 URL: http://jira.jboss.com/jira/browse/EJBTHREE-66 Project: EJB 3.0 Type: Feature Request Components: EJB3 Extensions Versions: Preview 4 Reporter: Bill Burke Assigned to: Kabir Khan Fix For: Preview 4 Allow asynchronous interface that uses the Asynchronous aspect from the aspect library. This should be usable from all EJB types except entities. Look at Aspect Library Document for more information. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1389) run-as-principal only propogates one level
run-as-principal only propogates one level -- Key: JBAS-1389 URL: http://jira.jboss.com/jira/browse/JBAS-1389 Project: JBoss Application Server Type: Bug Components: JMS service, Security, EJBs Versions: JBossAS-4.0.1 Final Environment: Windows XP, JBoss 4.0.1 Reporter: Randy Ott Assigned to: Scott M Stark The JBoss run-as-principal identity only works if calling a single EJB. Example: MDB with run-as-principal set calls SB which calls EB The SB will contain the correct principal name as specified in the jboss.xml file, but when the EB is called, the principal becomes null (or anonymous if using the UsersRolesPassword login module). This is currenlty holding up a port from WLS to JBoss. I have an example to attach. Randy Ott Capstone Consulting [EMAIL PROTECTED] 402.597.3664 x225 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1389) run-as-principal only propogates one level
[ http://jira.jboss.com/jira/browse/JBAS-1389?page=history ] Randy Ott updated JBAS-1389: Attachment: JBossTest.zip Example attached. run-as-principal only propogates one level -- Key: JBAS-1389 URL: http://jira.jboss.com/jira/browse/JBAS-1389 Project: JBoss Application Server Type: Bug Components: JMS service, Security, EJBs Versions: JBossAS-4.0.1 Final Environment: Windows XP, JBoss 4.0.1 Reporter: Randy Ott Assignee: Scott M Stark Attachments: JBossTest.zip The JBoss run-as-principal identity only works if calling a single EJB. Example: MDB with run-as-principal set calls SB which calls EB The SB will contain the correct principal name as specified in the jboss.xml file, but when the EB is called, the principal becomes null (or anonymous if using the UsersRolesPassword login module). This is currenlty holding up a port from WLS to JBoss. I have an example to attach. Randy Ott Capstone Consulting [EMAIL PROTECTED] 402.597.3664 x225 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.360 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050207130338Lbuild.360 BUILD COMPLETE-build.360Date of build:02/07/2005 13:03:38Time to build:133 minutes 34 secondsLast changed:02/07/2005 12:00:12Last log entry:Re-added as binary Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(12)1.1.2.3modifiedkabkhanaspects/dist/jboss-aspect-library-jdk50.jarRe-added as binary1.1.2.3modifiedkabkhanaspects/dist/jboss-aspect-library.jarRe-added as binary1.1.2.3modifiedkabkhanaspects/dist/jboss-aop.deployerRe-added as binary1.1.2.3modifiedkabkhanaspects/dist/jboss-aop-jdk50.deployerRe-added as binary1.1.2.3modifiedkabkhanaop/dist/jboss-aop.jarRe-added as binary1.1.2.3modifiedkabkhanaop/dist/jboss-aop-jdk50.jarRe-added as binary1.1.2.2deletedkabkhanaop/dist/jboss-aop.jarNot added as binary1.1.2.2deletedkabkhanaop/dist/jboss-aop-jdk50.jarNot added as binary1.1.2.2deletedkabkhanaspects/dist/jboss-aspect-library-jdk50.jarNot added as binary1.1.2.2deletedkabkhanaspects/dist/jboss-aspect-library.jarNot added as binary1.1.2.2deletedkabkhanaspects/dist/jboss-aop.deployerNot added as binary1.1.2.2deletedkabkhanaspects/dist/jboss-aop-jdk50.deployerNot added as binary
[JBoss-dev] [Design of JBoss Portal] - default views on login/logout
When a user logs in or out of a portal, how do I let the portlets know that this has happened and trigger them to update their views with default views. Currently in my portal if I log out, the portlet's views are still in the state they were in. For example if I am logged in and click the edit button and get an edit view and then logout, the portal page refreshes showing that I've logged out in the Login portlet but everything else stays the same. Thanks Mike View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865617#3865617 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865617 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-61) Possible RMI exception semantic regression
[ http://jira.jboss.com/jira/browse/JBREM-61?page=comments#action_12315213 ] Scott M Stark commented on JBREM-61: It should either be rethrowing all java.rmi.RemoteExceptions in a ServerException or only conditionally wrapping all java.rmi.RemoteExceptions based on some setting. I did not mean that java.rmi.AccessException should be treated specially. Possible RMI exception semantic regression -- Key: JBREM-61 URL: http://jira.jboss.com/jira/browse/JBREM-61 Project: JBoss Remoting Type: Bug Components: transport Reporter: Scott M Stark Assignee: Tom Elrod Fix For: 1.0.1 final The org.jboss.test.security.test.EJBSpecUnitTestCase.testDeepRunAs method is currently failing in head after the switch of the default invoker to the remoting based unified invoker due to a subtle difference in how exceptions are handled by the jrmp invoker. The test is expecting that the java.rmi.AccessException thrown by the ejb contaner be wrapped in a java.rmi.ServerException. This is a wrapping exception used by the jrmp implementation. The java.rmi.ServerException javadoc: A ServerException is thrown as a result of a remote method invocation when a RemoteException is thrown while processing the invocation on the server, either while unmarshalling the arguments, executing the remote method itself, or marshalling the return value. A ServerException instance contains the original RemoteException that occurred as its cause. The unified invoker is simply throwing back the java.rmi.AccessException. Although this looks like what the JRMPInvoker is doing, this ignores the fact that the jrmp implementation sits between the network and the client. We probably need a strictRMIException mode that allows for the same behavior. -- 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=6595alloc_id=14396op=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: Adding Resources To Artifacts
Ok. It is only used internally anyway so we don't need to worry about whether it is relative to a source or binary build. In general, it would probably be an idea to fix these such that we know what the resources relate to, i.e. those files would be better moved to src/resources/jboss-jmx It also makes it easier for somebody to come along later and add resources that do not relate to that jar. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865620#3865620 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865620 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1387) Config of jboss.deployment mbean does not work as specified
[ http://jira.jboss.com/jira/browse/JBAS-1387?page=history ] Adrian Brock closed JBAS-1387: -- Resolution: Rejected deploy/http-invoker.sar/ means to deploy all the files in that directory when what you really want todo is deploy that directory as a single deployment, i.e. deploy/http-invoker.sar Config of jboss.deployment mbean does not work as specified --- Key: JBAS-1387 URL: http://jira.jboss.com/jira/browse/JBAS-1387 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.6 Final Environment: WindowsXP, Java1.5 Reporter: Yevgeny Shakhnovich Assignee: Scott M Stark Priority: Minor I already reported this issue on the forum but did not get any response. This is why I repeat it here as a bug report. I have a problem with deploying of Tomcat in jboss 3.2.6 under JVM1.5 (I did not try another JVM) First time, I did not modify anything in the downloaded installation. I ran run.bat and everything looked fine. Then, I modified URLs attribute in jboss.deployment mbean in default/conf/jboss-service.xml. Namely, instead of referring to the entire directory by deploy/, I listed all files in the deploy directory, like Code: deploy/http-invoker.sar/, deploy/jboss-jca.sar deploy/jbossweb-tomcat50.sar/, deploy/jmx-invoker-adaptor-server.sar/, deploy/uuid-key-generator.sar, deploy/mail-service.xml, deploy/cache-invalidation-service.xml, deploy/client-deployer-service.xml, deploy/hibernate-deployer-service.xml, deploy/monitoring-service.xml, deploy/properties-service.xml, deploy/schedule-manager-service.xml, deploy/scheduler-service.xml, deploy/sqlexception-service.xml, deploy/transaction-service.xml, deploy/user-service.xml, deploy/jboss-local-jdbc.rar, deploy/jboss-xa-jdbc.rar, deploy/jmx-console.war/, deploy/jms/, deploy/management/, deploy/jsql-ds All services were deployed except Tomcat. The latter gave exception: Code: 2005-01-20 14:05:06,391 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-3.2.6/server/default/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:139) at org.jboss.system.ServiceController.install(ServiceController.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478) at
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1387) Config of jboss.deployment mbean does not work as specified
[ http://jira.jboss.com/jira/browse/JBAS-1387?page=comments#action_12315215 ] Adrian Brock commented on JBAS-1387: The most likely reason why you don't get answers in the forums is because it is an FAQ that people are bored of answering. Config of jboss.deployment mbean does not work as specified --- Key: JBAS-1387 URL: http://jira.jboss.com/jira/browse/JBAS-1387 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.6 Final Environment: WindowsXP, Java1.5 Reporter: Yevgeny Shakhnovich Assignee: Scott M Stark Priority: Minor I already reported this issue on the forum but did not get any response. This is why I repeat it here as a bug report. I have a problem with deploying of Tomcat in jboss 3.2.6 under JVM1.5 (I did not try another JVM) First time, I did not modify anything in the downloaded installation. I ran run.bat and everything looked fine. Then, I modified URLs attribute in jboss.deployment mbean in default/conf/jboss-service.xml. Namely, instead of referring to the entire directory by deploy/, I listed all files in the deploy directory, like Code: deploy/http-invoker.sar/, deploy/jboss-jca.sar deploy/jbossweb-tomcat50.sar/, deploy/jmx-invoker-adaptor-server.sar/, deploy/uuid-key-generator.sar, deploy/mail-service.xml, deploy/cache-invalidation-service.xml, deploy/client-deployer-service.xml, deploy/hibernate-deployer-service.xml, deploy/monitoring-service.xml, deploy/properties-service.xml, deploy/schedule-manager-service.xml, deploy/scheduler-service.xml, deploy/sqlexception-service.xml, deploy/transaction-service.xml, deploy/user-service.xml, deploy/jboss-local-jdbc.rar, deploy/jboss-xa-jdbc.rar, deploy/jmx-console.war/, deploy/jms/, deploy/management/, deploy/jsql-ds All services were deployed except Tomcat. The latter gave exception: Code: 2005-01-20 14:05:06,391 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-3.2.6/server/default/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:139) at org.jboss.system.ServiceController.install(ServiceController.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478) at
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1387) Config of jboss.deployment mbean does not work as specified
[ http://jira.jboss.com/jira/browse/JBAS-1387?page=comments#action_12315216 ] Adrian Brock commented on JBAS-1387: AND you should always test the latest version (3.2.7 at time of writing) before reporting bugs. Although in this case it is irrelevent since it is a user error. Config of jboss.deployment mbean does not work as specified --- Key: JBAS-1387 URL: http://jira.jboss.com/jira/browse/JBAS-1387 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.6 Final Environment: WindowsXP, Java1.5 Reporter: Yevgeny Shakhnovich Assignee: Scott M Stark Priority: Minor I already reported this issue on the forum but did not get any response. This is why I repeat it here as a bug report. I have a problem with deploying of Tomcat in jboss 3.2.6 under JVM1.5 (I did not try another JVM) First time, I did not modify anything in the downloaded installation. I ran run.bat and everything looked fine. Then, I modified URLs attribute in jboss.deployment mbean in default/conf/jboss-service.xml. Namely, instead of referring to the entire directory by deploy/, I listed all files in the deploy directory, like Code: deploy/http-invoker.sar/, deploy/jboss-jca.sar deploy/jbossweb-tomcat50.sar/, deploy/jmx-invoker-adaptor-server.sar/, deploy/uuid-key-generator.sar, deploy/mail-service.xml, deploy/cache-invalidation-service.xml, deploy/client-deployer-service.xml, deploy/hibernate-deployer-service.xml, deploy/monitoring-service.xml, deploy/properties-service.xml, deploy/schedule-manager-service.xml, deploy/scheduler-service.xml, deploy/sqlexception-service.xml, deploy/transaction-service.xml, deploy/user-service.xml, deploy/jboss-local-jdbc.rar, deploy/jboss-xa-jdbc.rar, deploy/jmx-console.war/, deploy/jms/, deploy/management/, deploy/jsql-ds All services were deployed except Tomcat. The latter gave exception: Code: 2005-01-20 14:05:06,391 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-3.2.6/server/default/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:139) at org.jboss.system.ServiceController.install(ServiceController.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478) at
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1363) JACC DelegatingPolicy will not work with a SecurityManager installed
[ http://jira.jboss.com/jira/browse/JBAS-1363?page=history ] Scott M Stark updated JBAS-1363: Fix Version: JBossAS-4.0.1 SP1 JBossAS-4.0.2 Final JBossAS-5.0 Alpha JACC DelegatingPolicy will not work with a SecurityManager installed Key: JBAS-1363 URL: http://jira.jboss.com/jira/browse/JBAS-1363 Project: JBoss Application Server Type: Bug Components: Security Versions: JBossAS-4.0.1 Final, JBossAS-5.0 Alpha Reporter: Scott M Stark Assignee: Scott M Stark Priority: Blocker Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-4.0.1 SP1 If one runs with the JACC policy provided enabled, and also specify that a security manager is intalled, the service fails to start with an exception like: 16:01:48,985 WARN [ServiceController] Problem starting service jboss.security:service=JACCSecurityService java.lang.ClassCircularityError: javax/security/jacc/EJBMethodPermission at org.jboss.security.jacc.DelegatingPolicy.implies(DelegatingPolicy.java:72) at java.security.ProtectionDomain.implies(ProtectionDomain.java:195) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:249) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at sun.misc.URLClassPath.check(URLClassPath.java:398) at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:601) at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:673) at sun.misc.URLClassPath$JarLoader.findResource(URLClassPath.java:660) at sun.misc.URLClassPath.findResource(URLClassPath.java:139) at java.net.URLClassLoader$2.run(URLClassLoader.java:362) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findResource(URLClassLoader.java:359) at java.lang.ClassLoader.getResource(ClassLoader.java:977) at org.jboss.mx.loading.RepositoryClassLoader.getResourceLocally(RepositoryClassLoader.java:200) at org.jboss.mx.loading.LoadMgr3$ResourceAction.run(LoadMgr3.java:95) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:247) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:464) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:374) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.jboss.security.jacc.DelegatingPolicy.implies(DelegatingPolicy.java:72) at java.security.ProtectionDomain.implies(ProtectionDomain.java:195) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:249) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.Thread.setContextClassLoader(Thread.java:1306) at org.jboss.mx.server.TCLAction$5.run(TCLAction.java:102) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.mx.server.TCLAction$2.setContextClassLoader(TCLAction.java:97) at org.jboss.mx.server.TCLAction$UTIL.setContextClassLoader(TCLAction.java:37) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:288) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:908) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) The problem is the interaction between the class loading layer attempting to locate the class in question as a resource and the lazy loading of the JACC permission classes from within the Policy.implies override which results in recursion into a ClassCircularityError: Thread main@336 in group jboss status: RUNNING init():32, java.lang.ClassCircularityError implies():72, org.jboss.security.jacc.DelegatingPolicy implies():189, java.security.ProtectionDomain checkPermission():254, java.security.AccessControlContext checkPermission():401, java.security.AccessController checkPermission():524, java.lang.SecurityManager check():397, sun.misc.URLClassPath getResource():884, sun.misc.URLClassPath$FileLoader getResource():157, sun.misc.URLClassPath getResource():209, sun.misc.URLClassPath getBootstrapResource():950, java.lang.ClassLoader getResource():811, java.lang.ClassLoader getResource():809, java.lang.ClassLoader getResource():809, java.lang.ClassLoader getResource():809, java.lang.ClassLoader getResourceLocally():205, org.jboss.mx.loading.RepositoryClassLoader run():95, org.jboss.mx.loading.LoadMgr3$ResourceAction doPrivileged():-1, java.security.AccessController beginLoadTask():247,
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315217 ] ericeberry commented on JBIDE-116: -- I just downloaded 1.4.1 and it has the same problem. From reading other bug entries, it looks like this is a problem with multiple source control plugins. Please fix this ASAP! Conflict between JBoss-IDE plugin and Rational ClearCase SCM Key: JBIDE-116 URL: http://jira.jboss.com/jira/browse/JBIDE-116 Project: JBoss IDE Type: Bug Reporter: SourceForge User Assignee: Marshall Culpepper SourceForge Submitter: ericeberry . I have been getting this exception when trying to Run XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 09:07:29.742 !MESSAGE An internal error occurred during: XDoclet Generation. !STACK 0 java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/bnc1.5 at org.eclipse.core.internal.runtime.Assert.isLegal (Assert.java:58) at org.eclipse.core.internal.jobs.ThreadJob.illegalPush (ThreadJob.java:106) at org.eclipse.core.internal.jobs.ThreadJob.push (ThreadJob.java:200) at org.eclipse.core.internal.jobs.ImplicitJobs.begin (ImplicitJobs.java:80) at org.eclipse.core.internal.jobs.JobManager.beginRule (JobManager.java:170) at org.eclipse.core.internal.resources.WorkManager.checkIn (WorkManager.java:95) at org.eclipse.core.internal.resources.Workspace.prepareOp eration(Workspace.java:1628) at org.eclipse.core.internal.resources.Resource.refreshLocal (Resource.java:1224) at org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct ion$1.run(XDocletRunAction.java:191) at org.eclipse.core.internal.jobs.Worker.run (Worker.java:66) It turns out there is a conflict between the JBoss-IDE plugin and the Rational ClearCase SCM Adapter 6.0.24 plugin. Becuase this plugin is always on, we can't turn the plugin off. We have to disable the plugin to turn it off. I disabled the plugin and I was able to run xdoclet every time. As soon as I re-enabled the plugin. Run XDoclet stopped working. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1389) run-as-principal only propogates one level
[ http://jira.jboss.com/jira/browse/JBAS-1389?page=history ] Scott M Stark resolved JBAS-1389: - Resolution: Cannot Reproduce Bug This appears to be the same as JBAS-1113 which was fixed in 4.0.1: http://jira.jboss.com/jira/browse/JBAS-1113 Runn the testcase shows that the expected run-as identity is seen at the session and entity bean levels: 14:30:28,437 INFO [Server] JBoss (MX MicroKernel) [4.0.1 (build: CVSTag=JBoss_4_0_1 date=200412230944)] Started in 28s:125ms 14:31:09,828 INFO [STDOUT] TestSessionEJB.test, principal = [roles=[TestRole],principal=TestPrincipal] 14:31:09,843 INFO [STDOUT] TestEntity.test, principal = [roles=[TestRole],principal=TestPrincipal] Make sure you are on the 4.0.1 final as evidenced by a version line that matches that shown above. run-as-principal only propogates one level -- Key: JBAS-1389 URL: http://jira.jboss.com/jira/browse/JBAS-1389 Project: JBoss Application Server Type: Bug Components: JMS service, Security, EJBs Versions: JBossAS-4.0.1 Final Environment: Windows XP, JBoss 4.0.1 Reporter: Randy Ott Assignee: Scott M Stark Attachments: JBossTest.zip The JBoss run-as-principal identity only works if calling a single EJB. Example: MDB with run-as-principal set calls SB which calls EB The SB will contain the correct principal name as specified in the jboss.xml file, but when the EB is called, the principal becomes null (or anonymous if using the UsersRolesPassword login module). This is currenlty holding up a port from WLS to JBoss. I have an example to attach. Randy Ott Capstone Consulting [EMAIL PROTECTED] 402.597.3664 x225 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-61) Possible RMI exception semantic regression
[ http://jira.jboss.com/jira/browse/JBREM-61?page=comments#action_12315220 ] Tom Elrod commented on JBREM-61: - Have changed from AccessException to java.rmi.RemoteException. Don't see any need to make this conditional, as is doing this only within UnifiedInvokerProxy, which is specific to EJB call processing. Remoting will remain unaffected. Possible RMI exception semantic regression -- Key: JBREM-61 URL: http://jira.jboss.com/jira/browse/JBREM-61 Project: JBoss Remoting Type: Bug Components: transport Reporter: Scott M Stark Assignee: Tom Elrod Fix For: 1.0.1 final The org.jboss.test.security.test.EJBSpecUnitTestCase.testDeepRunAs method is currently failing in head after the switch of the default invoker to the remoting based unified invoker due to a subtle difference in how exceptions are handled by the jrmp invoker. The test is expecting that the java.rmi.AccessException thrown by the ejb contaner be wrapped in a java.rmi.ServerException. This is a wrapping exception used by the jrmp implementation. The java.rmi.ServerException javadoc: A ServerException is thrown as a result of a remote method invocation when a RemoteException is thrown while processing the invocation on the server, either while unmarshalling the arguments, executing the remote method itself, or marshalling the return value. A ServerException instance contains the original RemoteException that occurred as its cause. The unified invoker is simply throwing back the java.rmi.AccessException. Although this looks like what the JRMPInvoker is doing, this ignores the fact that the jrmp implementation sits between the network and the client. We probably need a strictRMIException mode that allows for the same behavior. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1388) Create property for deployment directory
[ http://jira.jboss.com/jira/browse/JBAS-1388?page=history ]
Scott M Stark resolved JBAS-1388:
-
Resolution: Done
Fix Version: JBossAS-4.0.1 Final
JBossAS-3.2.7 Final
This is already supported. If you set the URLs attribute to the following:
attribute name=URLs
${jboss.server.deploy.list:deploy/}
/attribute
then if the jboss.server.deploy.list property is set it will be used, else the
default of deploy/ is used.
Create property for deployment directory
Key: JBAS-1388
URL: http://jira.jboss.com/jira/browse/JBAS-1388
Project: JBoss Application Server
Type: Feature Request
Reporter: Yevgeny Shakhnovich
Assignee: Scott M Stark
Priority: Trivial
Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
It is not always convenient to put files for deployment into deploy
directory. JBoss provides the way to modify such default behavior through
attribute URLs of jboss.deployment mbean but it requires modification of
jboss-service.xml which is also inconvenient, especially taking in account
the frequency of jboss upgrades. I would prefer if in jboss-service.xml the
URLs attribute looked like
attribute name=URLs
${jboss.server.deploy.list}
/attribute
where the property jboss.server.deploy.list had the default value deploy/.
In that case, I could specify my components for deployment in the runtime in
a different directory without changing the jboss installation just by setting
the right value for the property. It would simplify upgrades to new jboss
versions.
Thanks,
Yevgeny
--
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=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.782 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050207163618Lbuild.782 BUILD COMPLETE-build.782Date of build:02/07/2005 16:36:18Time to build:31 minutes 15 secondsLast changed:02/07/2005 14:50:48Last log entry:Feature Matrix between jbosswstool and wscompile [Provided by Sun's JWSDP] Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(13)1.2modifiedosdchicagowebservice/docs/tools-docs/project/en/modules/featurematrix.xmlFeature Matrix between jbosswstool and wscompile [Provided by Sun's JWSDP]1.2modifiedosdchicagowebservice/docs/tools-docs/project/en/master.xmlFeature Matrix between jbosswstool and wscompile [Provided by Sun's JWSDP]1.2modifiedtelrodserver/src/main/org/jboss/invocation/unified/interfaces/UnifiedInvokerProxy.javaJBREM-61 Will not catch AcessException and rethrow wrapped inside ServerException.1.2modifiedbwang00testsuite/src/main/org/jboss/test/cache/bean/CacheObjectMeanTesterBean.javaUpdated with right service name1.6modifiedtelrodremoting/tests/src/org/jboss/samples/callback/CallbackServer.javaAdded catch for HandleCallbackException when calling handleCallback() on InvocationCallbackHandler to better show this is what will be thrown if exception handling callback.1.16modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javajavadoc update1.16modifiedbelabancache/src/main/org/jboss/cache/interceptors/LockInterceptor.javastill working on it...1.3modifiedbelabantestsuite/src/main/org/jboss/test/cache/perf/basic/ReplicatedSyncPerfTestCase.javatrying to fix the failures1.1addedrecampbelljmx/jbossbuild.xmlinitial checkin for jmx module; demonstrates use of resource node1.11modifiedtdieslertools/etc/buildmagic/modules.xmlReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.30modifiedtdieslertools/etc/buildmagic/modules.entReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.387modifiedtdieslerbuild/build.xmlReinstall jboss-ws4ee.sar as the default. It's probably better to keep it defaultuntill jbossws passes the ws4ee tests in the main testsuite.1.11modifiedrecampbelljbossas/jbossbuild.xmlcomponents needed for jboss-jmx
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=history ] Ryan Campbell updated JBAS-1294: Fix Version: JBossAS-4.0.2RC1 commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Minor Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-12) ClassData spi
ClassData spi - Key: JBMICROCONT-12 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-12 Project: JBoss MicroContainer Type: Task Components: BeanInfo Reporter: Adrian Brock Assigned to: Bill Burke Define the ClassData spi. This is a concrete implementation of class metadata that can be used to analyse classes. It is similar to javassist's data and can be used by both jboss-aop and the microcontainer (and other modules if required). This replaces the BeanInfo spi currently in the container module. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-13) Create Joinpoint spi
Create Joinpoint spi Key: JBMICROCONT-13 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-13 Project: JBoss MicroContainer Type: Task Components: Container Reporter: Adrian Brock Assigned to: Bill Burke This is a set of interfaces that model different types of invocations. It is a set of interfaces that can be used to construct invocations that target either javabeans or the jboss aop advisors. The joinpoints are obtained through a JoinPointFactory that serves as the joinpoint model in effect, i.e. reflection or jboss-aop -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-14) Create ClassAdaptor spi
Create ClassAdaptor spi --- Key: JBMICROCONT-14 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-14 Project: JBoss MicroContainer Type: Task Reporter: Adrian Brock Assigned to: Bill Burke The ClassAdaptor spi is a set of interfaces that defines how to aspectize a POJO class. This maybe a null operation. The ClassAdaptor allows different policies to be used, currently two are anticapted, javabean and jboss-aop. It performs the following functions: * Integration point for retrieving ClassData * Annotation processing (both retrieval and overriding) * Dependency resolution * JoinPointFactory resolution (dependency upon custom configuration by annotation overrides and how the class is instrumented - if at all) -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-78) javassist implementation of ClassData spi
javassist implementation of ClassData spi - Key: JBAOP-78 URL: http://jira.jboss.com/jira/browse/JBAOP-78 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke Write a javassist implementation of the ClassData spi -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-79) pointcut expressions should use the ClassData spi
pointcut expressions should use the ClassData spi - Key: JBAOP-79 URL: http://jira.jboss.com/jira/browse/JBAOP-79 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke The pointcut expression matcher should use the ClassData spi implemeneted on top of javassist -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-80) AOP JoinPointFactory
AOP JoinPointFactory Key: JBAOP-80 URL: http://jira.jboss.com/jira/browse/JBAOP-80 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke AOP should expose itself through the JoinPointFactory in particular the invocations should implement the JoinPoint interfaces. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-81) InstanceAdvisor needs all the features of the ClassAdvisor
InstanceAdvisor needs all the features of the ClassAdvisor -- Key: JBAOP-81 URL: http://jira.jboss.com/jira/browse/JBAOP-81 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke The instance advisor needs to be a complete replacement for the ClassAdvisor -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAOP-78) javassist implementation of ClassData spi
[ http://jira.jboss.com/jira/browse/JBAOP-78?page=comments#action_12315223 ] Adrian Brock commented on JBAOP-78: --- Load time aop should store the ClassData structures and dump the javassist internal structures that consume a lot of memory. javassist implementation of ClassData spi - Key: JBAOP-78 URL: http://jira.jboss.com/jira/browse/JBAOP-78 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assignee: Bill Burke Write a javassist implementation of the ClassData spi -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-82) Generic ProxyAdvisor
Generic ProxyAdvisor Key: JBAOP-82 URL: http://jira.jboss.com/jira/browse/JBAOP-82 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke There should be a Generic ProxyAdvisor like the EJB3 Container implementation. This can be used when a class is not instrumented. Obviously it won't have all the features of the ClasAdvisor. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-83) Serialization issues
Serialization issues Key: JBAOP-83 URL: http://jira.jboss.com/jira/browse/JBAOP-83 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke Need changes to properly support serialization/proxying of generated classes on the client. In particular when the client is a limited environment (e.g. a security manager is installed) -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-84) Layered aspects
Layered aspects --- Key: JBAOP-84 URL: http://jira.jboss.com/jira/browse/JBAOP-84 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke AOP should support layered aspects where an advice can directly implement the methods it is aspectizing. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.361 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050207213856Lbuild.361 BUILD COMPLETE-build.361Date of build:02/07/2005 21:38:56Time to build:29 minutes 56 secondsLast changed:02/07/2005 21:04:49Last log entry:When run with a security manager the act of class loading can trigger security checks which in turn causes this classes implies method to be called as soon as the this class is installed as the Policy implementation. The implies method cannot cause class loading to occur before there is the delegation to the non-JACC Policy provider or else an infinite recursion scenario arises where entrance into implies triggers class loading which recurses into implies. Resolves [JBAS-1363] JACC DelegatingPolicy will not work with a SecurityManager installed. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(8)1.5.4.2modifiedstarksmsecurity/src/main/org/jboss/security/jacc/DelegatingPolicy.javaWhen run with a security manager the act of class loading can trigger security checks which in turn causes this classes implies method to be called as soon as the this class is installed as the Policy implementation. The implies method cannot cause class loading to occur before there is the delegation to the non-JACC Policy provider or else an infinite recursion scenario arises where entrance into implies triggers class loading which recurses into implies. Resolves [JBAS-1363] JACC DelegatingPolicy will not work with a SecurityManager installed.1.1.4.2modifiedstarksmserver/src/main/org/jboss/ejb/plugins/JaccAuthorizationInterceptor.javaUse a PrivilegedExceptionAction for accessing the "javax.security.auth.Subject.container" JACC PolicyContext.getContext() value.1.5.2.4modifiedstarksmserver/src/main/org/jboss/ejb/plugins/SecurityActions.javaAdd a PrivilegedExceptionAction for accessing the "javax.security.auth.Subject.container" JACC PolicyContext.getContext() value.1.406.2.39modifiedstarksmtestsuite/build.xmlUpdate for the tomcat55 sar and run the jacc tests under a security manager1.3.2.1deletedstarksmtestsuite/src/resources/test-configs/tomcat-ssl/deploy/jbossweb-tomcat50.sar/server.xmlUpdate for the tomcat55 sar1.2.2.1deletedstarksmtestsuite/src/resources/test-configs/tomcat-ssl/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xmlUpdate for the tomcat55 sar1.1.2.1deletedstarksmtestsuite/src/resources/test-configs/jacc/deploy/jbossweb-tomcat50.sar/server.xmlUpdate for the tomcat55 sar1.1.2.1deletedstarksmtestsuite/src/resources/test-configs/jacc/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xmlUpdate for the tomcat55 sar
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-85) Annotation compiler should support imports
Annotation compiler should support imports -- Key: JBAOP-85 URL: http://jira.jboss.com/jira/browse/JBAOP-85 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assigned to: Bill Burke The annotation should process imports, i.e. import org.jboss.security.Security; /** * @@Security */ instead of /** * @@org.jboss.security.Security */ -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-15) Reflection based implementation of classdata spi
Reflection based implementation of classdata spi Key: JBMICROCONT-15 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-15 Project: JBoss MicroContainer Type: Task Components: BeanInfo Reporter: Adrian Brock There needs to be a reflection based implementation of the ClassData spi for when javassist/aop is not 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-17) BeanJoinPointFactory
BeanJoinPointFactory Key: JBMICROCONT-17 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-17 Project: JBoss MicroContainer Type: Task Reporter: Adrian Brock Create a BeanJoinPointFactory, a reflection based JoinPointFactory for when aop is not available or not required. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-16) BeanInfo model
BeanInfo model -- Key: JBMICROCONT-16 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-16 Project: JBoss MicroContainer Type: Task Reporter: Adrian Brock The BeanInfo model needs moving back into MicroContainer module. It provides javabean semantics on top of the ClassData model. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-17) BeanJoinPointFactory
[ http://jira.jboss.com/jira/browse/JBMICROCONT-17?page=comments#action_12315224 ] Adrian Brock commented on JBMICROCONT-17: - Also, implement the rest of the ClassAdaptor spi for the same reason. BeanJoinPointFactory Key: JBMICROCONT-17 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-17 Project: JBoss MicroContainer Type: Task Reporter: Adrian Brock Create a BeanJoinPointFactory, a reflection based JoinPointFactory for when aop is not available or not required. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMICROCONT-17) BeanJoinPointFactory
[ http://jira.jboss.com/jira/browse/JBMICROCONT-17?page=history ] Adrian Brock updated JBMICROCONT-17: Component: Container BeanJoinPointFactory Key: JBMICROCONT-17 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-17 Project: JBoss MicroContainer Type: Task Components: Container Reporter: Adrian Brock Create a BeanJoinPointFactory, a reflection based JoinPointFactory for when aop is not available or not required. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-18) Annotation metadata
Annotation metadata --- Key: JBMICROCONT-18 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-18 Project: JBoss MicroContainer Type: Task Reporter: Adrian Brock Add annotation metadata to the BeanMetaData classes for overriding class values at the instance level. This replaces the getValue(...) stuff in FeatureMetaData. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-19) Controller should use the ClassAdaptor
Controller should use the ClassAdaptor -- Key: JBMICROCONT-19 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-19 Project: JBoss MicroContainer Type: Task Components: Dependency Reporter: Adrian Brock Modify the controller's describe() and instantiate() processing to use the ClassAdaptor. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMICROCONT-18) Annotation metadata
[ http://jira.jboss.com/jira/browse/JBMICROCONT-18?page=history ] Adrian Brock updated JBMICROCONT-18: Component: MetaData Annotation metadata --- Key: JBMICROCONT-18 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-18 Project: JBoss MicroContainer Type: Task Components: MetaData Reporter: Adrian Brock Add annotation metadata to the BeanMetaData classes for overriding class values at the instance level. This replaces the getValue(...) stuff in FeatureMetaData. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite build.66 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050207184523Lbuild.66 BUILD COMPLETE-build.66Date of build:02/07/2005 18:45:23Time to build:81 minutes 47 seconds Unit Tests: (1936) Total Errors and Failures: (23)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestQueueMessageOrderorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestRequestReplyQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryQueueDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryTopicDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueSendorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueBrowseorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationTopicPublishorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestErrorsTopicSubscribeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestCreateQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestMessageListenerorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestApplicationServerStufforg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicsorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalBounceorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorChangeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorNullOrEmptyorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveExpiredorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendListenOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build:(0)
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-21) GenericBeanFactory
GenericBeanFactory -- Key: JBMICROCONT-21 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-21 Project: JBoss MicroContainer Type: Task Components: Deployment Reporter: Adrian Brock Implement a GenericBeanFactory that provides for an indirection/lazy instantiation of bean instances from dependency configuration. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBMICROCONT-21) GenericBeanFactory
[ http://jira.jboss.com/jira/browse/JBMICROCONT-21?page=history ] Adrian Brock updated JBMICROCONT-21: Component: Deployment GenericBeanFactory -- Key: JBMICROCONT-21 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-21 Project: JBoss MicroContainer Type: Task Components: Deployment Reporter: Adrian Brock Implement a GenericBeanFactory that provides for an indirection/lazy instantiation of bean instances from dependency configuration. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-20) Collections MetaData
Collections MetaData Key: JBMICROCONT-20 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-20 Project: JBoss MicroContainer Type: Task Components: MetaData Reporter: Adrian Brock Add support for collections (arrays[], collection, set, list, map, etc.) to the BeanMetaData. Including initialization the collection values from dependencies. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
