[JBoss-dev] [Design of JBoss Portal] - Re: Own servlet mapping
"mholzner" wrote : the same way as you would do it in any other war. add a servlet-mapping element in the web.xml Have you tried to to like that? I have try to map my servlets like in common web-application, but when I've tried to call my servlet I got 404 error in portal! So, I think this doesnt works!! I guess it's something with PortalURL class.. You can take dispatcher as jsp with extending PortalJsp class, but in servlet? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871851#3871851 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871851 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1626) ClientReconnectInterceptor doesn't work
ClientReconnectInterceptor doesn't work --- Key: JBAS-1626 URL: http://jira.jboss.com/jira/browse/JBAS-1626 Project: JBoss Application Server Type: Bug Components: JMS service Versions: JBossAS-4.0.1 SP1 Environment: SuSE Linux Enterprise Server 8, JBoss-4.0.1SP1 Reporter: jens.schanz Priority: Minor File: jbossmq-service.xml org.jboss.mq.server.ClientReconnectInterceptor jboss.mq:service=DestinationManager I have uncommented this feature, because our application has a bug with unregistering and disconnecting. Until this bug is solved I want to enable this feature in JBoss, but it doesn't work. I allready get the message "reconnect failed : javax.jms.InvalidClientIDException: This client id 'system1' is already registered!". Maybee it's a bug. Could someone please check this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step
anonymous wrote : Remoting is just a mechanism for making remote invocations (including callbacks). It has no concept of contextual processing. There has to be a ServerInvocationHandler on the server side to process invocation requests, including adding and removing of callback listeners. The ServerInvocationHandler is also responsible for generating the callbacks (remoting itself has not idea of when a callback should be generated or what it contains, it only knows how to get the callback sent to the original listener). I agree. You definitely need a ServerInvocationHandler on the target server, otherwise the target server is useless. However, you don't need a ServerInvocationHandler on the callback server, assuming that you created the callback server to only handle callbacks. This paragraph from the wiki document you've posted seems to confirm that: anonymous wrote : | It is important to note that sub-system associated with the callback server is not directly involved in the dispatching of callbacks to the client callback handler; this is all handled within the JBoss Remoting layer. ... and this is a logical inference based on the above paragraph: (I create a callback server to only handle callbacks) + (the subsystems associated with the callback server are not involved in the dispatching of callbacks) => (I don't need server invocation handlers on my callback server) Do we agree up this point? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871848#3871848 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871848 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: How do I get rollback to occur with remote cache access?
I suggest debug the remote TreeCache MBean, set a breakpoint into
TreeCache.put():
public Object put(Fqn fqn, Object key, Object value) throws CacheException {
GlobalTransaction tx=getCurrentTransaction();
MethodCall m=new MethodCall(putKeyValMethodLocal, new Object[]{tx, fqn, key,
value, Boolean.TRUE});
return invokeMethod(m);
}
Step into getCurrentTransaction(), you'll see that if getLocalTransaction() is
null, then you don't have a TX.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871846#3871846
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871846
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1580) Problem when Submitting Massive Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBAS-1580?page=history ] Ben Wang resolved JBAS-1580: Resolution: Done > Problem when Submitting Massive Load into HttpSession > - > > Key: JBAS-1580 > URL: http://jira.jboss.com/jira/browse/JBAS-1580 > Project: JBoss Application Server > Type: Bug > Components: JBoss Cache service > Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-5.0 Alpha, > JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Clebert Suconic > Assignee: Ben Wang > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > > Description available at: > http://jira.jboss.com/jira/browse/JBCACHE-102 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1580) Problem when Submitting Massive Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBAS-1580?page=history ] Ben Wang reopened JBAS-1580: > Problem when Submitting Massive Load into HttpSession > - > > Key: JBAS-1580 > URL: http://jira.jboss.com/jira/browse/JBAS-1580 > Project: JBoss Application Server > Type: Bug > Components: JBoss Cache service > Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-5.0 Alpha, > JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Clebert Suconic > Assignee: Ben Wang > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > > Description available at: > http://jira.jboss.com/jira/browse/JBCACHE-102 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1580) Problem when Submitting Massive Load into HttpSession
[
http://jira.jboss.com/jira/browse/JBAS-1580?page=comments#action_12316464 ]
Ben Wang commented on JBAS-1580:
Now the load test against the all three releases 3.2.8, 4.0.2 and head all
succeed after using the latest jboss-head (post 1.2.1 release).
Here is the client load on two nodes:
java -jar testClient.jar http:${MYTESTIP_1}:8080 2 4 0
java -jar testClient.jar http:${MYTESTIP_2}:8080 2 4 0
Above that sometimes, it will exceed the 512 heap and cause OOM.
> Problem when Submitting Massive Load into HttpSession
> -
>
> Key: JBAS-1580
> URL: http://jira.jboss.com/jira/browse/JBAS-1580
> Project: JBoss Application Server
> Type: Bug
> Components: JBoss Cache service
> Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-5.0 Alpha,
> JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Clebert Suconic
> Assignee: Ben Wang
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
>
> Description available at:
> http://jira.jboss.com/jira/browse/JBCACHE-102
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1580) Problem when Submitting Massive Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBAS-1580?page=history ] Ben Wang resolved JBAS-1580: Resolution: Rejected > Problem when Submitting Massive Load into HttpSession > - > > Key: JBAS-1580 > URL: http://jira.jboss.com/jira/browse/JBAS-1580 > Project: JBoss Application Server > Type: Bug > Components: JBoss Cache service > Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-5.0 Alpha, > JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Clebert Suconic > Assignee: Ben Wang > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > > Description available at: > http://jira.jboss.com/jira/browse/JBCACHE-102 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.905 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050329011517Lbuild.905 BUILD COMPLETE - build.905Date of build: 03/29/2005 01:15:17Time to build: 18 minutes 12 secondsLast changed: 03/28/2005 21:58:38Last log entry: JBAS-1622 findSessions api is not correct Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (87)1.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api is not correct1.18modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api is not correct1.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.4modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivation.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.4modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivationSpec.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.5modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDriven.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.3modifiedejorttestsuite/src/resources/messagedriven/jar/META-INF/ejb-jar.xmlTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.2modifiedejorttestsuite/src/resources/messagedriven/jar/META-INF/jboss.xmlTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.4modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/mbeans/TestMessageDrivenManagement.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.5modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicMessageDrivenUnitTest.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.3modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckJMSDestinationOperation.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.6modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/SimpleMessageDrivenUnitTest.javaTests and fixes for the DLQ handling/XA connection setupplus some more logging.1.57modifiedpatriot1burketools/etc/buildmagic/libraries.entwhoops! forgot to commit changes for HB3 annotation project1.10modifiedejortserver/src/main/org/jboss/ejb/plugins/inflow/JBossMessageEndpointFactory.javaLog whether delivery is transacted1.2modifiedejortserver/src/main/org/jboss/ejb/plugins/inflow/JBossJMSMessageEndpointFactory.javaFix a TYPO1.2deletedpatriot1burkethirdparty/hibernate/lib/hibernate-metadata.jarupdate docs1.3modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupdate docs1.40modifiedejorttransaction/src/main/org/jboss/tm/TransactionImpl.javaImprove the logging of commit/rollback/etc requests of theresources in a transaction.1.6modifiedpatriot1burkeejb3/INSTALL.htmlupdate docs1.10modifiedpatriot1burkeejb3/docs/tutorial/index.htmlupdate docs1.9modifiedpatriot1burkeejb3/docs/tutorial/index.wikiupdate docs1.7modifiedpatriot1burkeejb3/docs/tutorial/installing.htmlupdate docs1.5modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.htmlupdate docs1.4modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.wikiupdate docs1.1addedpatriot1burkeejb3/docs/tutorial/ear/build.xmlear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/calculator.jspear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/ear.htmlear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/ear.wikiear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/src/org/jboss/tutorial/ear/servlet/CalculatorActionServlet.javaear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/src/org/jboss/tutorial/ear/bean/Calculator.javaear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/src/org/jboss/tutorial/ear/bean/CalculatorBean.javaear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/src/org/jboss/tutorial/ear/bean/CalculatorLocal.javaear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/src/org/jboss/tutorial/ear/bean/CalculatorRemote.javaear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/resources/application.xmlear tutorial1.1addedpatriot1burkeejb3/docs/tutorial/ear/resources/web.xmlear tutorial1.1addedosdchicagowebservice/docs/tools-docs/wscompileIssues.txtJust a text file that stores the issues seen while using wscompile tool for xsd-> java conversion.1.9modifiedejortserver/src/main/org/jboss/ejb/plugins/inflow/JBossMessageEndpointFactory.javaLog the endpoint construction.1.21modifiedrecampbelljbossas/jbossbuild.xmlJBBUILD-57 support bin artifacts1.2modifiedrecampbellserver/jbossbuild.xmlJBBUILD-57 support bin artifacts1.18modifiedrecampbell
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1502) IllegalStateException with http sessionr repl under load
[ http://jira.jboss.com/jira/browse/JBAS-1502?page=history ] Ben Wang resolved JBAS-1502: Resolution: Rejected Again this is a problem due to the http client setup. Need to create a new session after it is invalidated. > IllegalStateException with http sessionr repl under load > > > Key: JBAS-1502 > URL: http://jira.jboss.com/jira/browse/JBAS-1502 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-5.0 Beta > Reporter: Ben Wang > Assignee: Ben Wang > Priority: Minor > Fix For: JBossAS-5.0 Final > > Original Estimate: 3 hours > Remaining: 3 hours > > The following exception gets generated with http session replication under > load. It's a minor issue of defining the local property string. > 01:42:34,589 ERROR [StandardWrapper[/jbossHttpTest:HttpStressTest]] > Servlet.serv > ice() for servlet HttpStressTest threw exception > java.lang.IllegalStateException: standardSession.setAttribute.ise > at > org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(Cluste > redSession.java:185) > at > org.apache.catalina.session.StandardSessionFacade.setAttribute(Standa > rdSessionFacade.java:129) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1622) findSessions doesn't find all sessions in http session replication
[ http://jira.jboss.com/jira/browse/JBAS-1622?page=history ] Ben Wang resolved JBAS-1622: Resolution: Done Fix Version: JBossAS-3.2.8 Final Fixed in all cvs branches. > findSessions doesn't find all sessions in http session replication > -- > > Key: JBAS-1622 > URL: http://jira.jboss.com/jira/browse/JBAS-1622 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.2RC1 > Reporter: Ben Wang > Assignee: Ben Wang > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 days > Remaining: 2 days > > Current implementation of http session replication does not return > findSessions correctly. It is correct when called the first time. But when it > is active-active clustering when node is concurrently updated, the api is not > correct. This was discovered when load testing on both nodes simultaneously. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-102) Exception when Submitting Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBCACHE-102?page=history ] Ben Wang resolved JBCACHE-102: -- Resolution: Rejected These two errors are mostly due to in-proper setup of the http client program. The original one that Clebert has used the same session for the http client over and over again (before it gets invlidated). When I create a new http client after the session is invalidated, the error goes away. > Exception when Submitting Load into HttpSession > --- > > Key: JBCACHE-102 > URL: http://jira.jboss.com/jira/browse/JBCACHE-102 > Project: JBoss Cache > Type: Bug > Environment: jboss-4.0 Branch_4_0 > Reporter: Clebert Suconic > Assignee: Ben Wang > > > When submitting load using ou HttpStressTest application, using 10 threads in > the client and 1 session hold per thread, we have thrown these exceptions: > java.lang.IllegalStateException: standardSession.setAttribute.ise > at > org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(ClusteredSession.java:185) > at > org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:129) > at > org.jboss.test.weblayer.HttpStressTest.doGet(HttpStressTest.java:24) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:147) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:81) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:534) > And: > java.lang.IllegalArgumentException: You can only add ClusteredSessions to > this Manager > at > org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:228) > at > org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:38) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:534) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jb
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1270) UserTransaction with non default ProviderURL
[
http://jira.jboss.com/jira/browse/JBAS-1270?page=comments#action_12316460 ]
Dirk Niemeier commented on JBAS-1270:
-
Dear Scott,
don't you solve the problem in the 3.x versions ?
Regards,
Dirk
> UserTransaction with non default ProviderURL
>
>
> Key: JBAS-1270
> URL: http://jira.jboss.com/jira/browse/JBAS-1270
> Project: JBoss Application Server
> Type: Bug
> Components: Transaction Manager service
> Versions: JBossAS-3.2.6 Final
> Environment: WinXP Client SP 2, java version 1.4.2_04-b05, jboss-3.2.6
> Reporter: Dirk Niemeier
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
>
> Problem to initiate an UserTransaction from client with non default
> providerURL.
> java.util.Hashtable env = new java.util.Hashtable();
> env.put( Context.PROVIDER_URL, "myserver:1199");
> InitialContext ctx = new InitialContext(env);
> javax.transaction.UserTransaction tx = (UserTransaction)
> ctx.lookup("UserTransaction");
> The lookup cause an stacktrace like this :
> 08:36:54,531 DEBUG [AWT-EventQueue-0] (NamingContext.java:1192) - Failed to
> connect to 172.30.1.22:1099
> javax.naming.CommunicationException: Failed to connect to server
> 172.30.1.22:1099 [Root exception is javax.naming.ServiceUnavailableException:
> Failed to connect to server 172.30.1.22:1099 [Root exception is
> java.net.ConnectException: Connection timed out: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:213)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1187)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
> The provider "172.30.1.22:1099" is the default provider in my jndi properties
> file which is not online at this time.
> I think the problem is in
> org.jboss.tm.usertx.client.ClientUserTransactionObjectFactory, which will be
> called in lookup handling.
> The getUserTransaction() tries to create an new InitialContext with default
> parameters. It should use the context available by getObjectInstance(..).
> An additional problem to this is in class
> org.jboss.tm.usertx.client.ClientUserTransaction :
> private synchronized void createSession()
>{
> // Destroy any old session.
> if (session != null)
> destroySession();
> try {
> // Get a reference to the UT session factory.
> UserTransactionSessionFactory factory;
> factory = (UserTransactionSessionFactory)new
> InitialContext().lookup("UserTransactionSessionFactory");
> // Call factory to get a UT session.
> session = factory.newInstance();
> } catch (Exception ex) {
> throw new RuntimeException("UT factory lookup failed: " + ex);
> }
>}
> This occurs when begin() is invoked. Same problem with new InitialContext().
> In class ServerVMClientUserTransaction the same problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Support for SSO
There should be a lot to say about this. And so far I haven't found any documentation If you are going to deliver a intranet-portal to an organisation, you simply can't drag a propritary userdatabase along with the product. Doing that will force the organisation to maintain more than one userdatabase, and duplicating all userinformation. I think we passed this way of thinking years ago. How does JBoss Portal integrate with LDAP? Is it enough to switch from HibernateLoginModule to LDAPLoginModule (shipped with JBoss AS) to achive authenication of users.from an LDAP server? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871845#3871845 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871845 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-86) setAttribute does not find correct method
[ http://jira.jboss.com/jira/browse/JBJMX-86?page=comments#action_12316459
]
Michael Kopp commented on JBJMX-86:
---
Well, I have an mbean that extends StandardMBean. The only attribute it has to
be set from the -service.xml is an xml element. This worked well all the time.
I now had to step back from java 1.5 to 1.4 and thus use the jboss
implementation of jmx instead of the jdk one.
The problem is that the actual object to be set is of course a subclass of
org.w3c.Element and thus the method with that specific subclass as a parameter
is not found by the StandardMBean.
I think this problem will occur every time the attribute type is an interface
and one tries to set it.
e.g. The attribute is of type java.lang.Map. Now if code of mine is calling the
setAttribute for this attribute it will give it an actual implementation of the
Map like java.util.HashMap.
The setAttribute of StandardMBean will then try to find a setter for this
attribute that has a parameter HashMap, and this will not find the correct
setter which of course has a parameter of type Map.
Pls check out the setAttribute method of StandardMBean and you'll see what I
mean.
> setAttribute does not find correct method
> -
>
> Key: JBJMX-86
> URL: http://jira.jboss.com/jira/browse/JBJMX-86
> Project: JBoss JMX
> Type: Bug
> Versions: JBossAS-4.0.1
> Reporter: Michael Kopp
>
>
> The setAttribute searches for a method:
> Class[] clArr = null;
> if (attribute.getValue() != null)
> {
>clArr = new Class[]{attribute.getValue().getClass()};
> }
> Method method = implementation.getClass().getMethod("set" +
> attribute.getName(), clArr);
> This means that if the value is DomElement, the class would be a
> org.apache.xerces.dom.DeferredElementImpl. But the Setter would normally
> reference org.w3c.dom.Element.
> The feature of jboss to support Element in a -service.xml is pretty useless
> this way.
> I think this should be done in the same way as Java5 does it. search for a
> method with the right name and the right number of parameters. for the found
> ones, check if the paramters are assignable. This way subclass and
> implementations of interfaces can be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.319 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050329001709Lbuild.319 BUILD COMPLETE - build.319Date of build: 03/29/2005 00:17:09Time to build: 23 minutes 9 secondsLast changed: 03/28/2005 12:33:36Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.9.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.
[JBoss-dev] [JBossCache] - Isolation Level of NONE Works In JBC 1.2.1?
As mentioned in a previous post, I am using the cache in an asychronously replicated manner, and with the default isolation level of REPEATABLE_READ I get lock errors when there is moderate to heavy use of the cache. As suggested, I set the isolation level to NONE, and I received the following error from lots of the threads accessing the cache (even with mild to moderate use of the cache). | java.lang.IllegalStateException: addWriter(): owner already existed | at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112) | at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:175) | at org.jboss.cache.Node.acquireWriteLock(Node.java:483) | at org.jboss.cache.Node.acquire(Node.java:440) | at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:240) | at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:156) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) | at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) | at org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:217) | at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682) | 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:324) | at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) | at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220) | at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) | at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) | at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554) | at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) | at java.lang.Thread.run(Thread.java:534) | Is this an issue or expected? Would a test case that presents this behavior help (it seems easy to produce in our application anyway)? I set the isolation level to READ_UNCOMMITTED while running the same tests that produced the above issue, and it seems promising, but I am not done testing with it yet. Is this a valid workaround for this issue? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871843#3871843 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871843 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-jdk-matrix build.86 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050328225510Lbuild.86 BUILD COMPLETE - build.86Date of build: 03/28/2005 22:55:10Time to build: 40 minutes 3 secondsLast changed: 03/28/2005 12:33:36Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.9.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.
[JBoss-dev] jboss-3.2-testsuite build.98 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050328204559Lbuild.98 BUILD COMPLETE - build.98Date of build: 03/28/2005 20:45:59Time to build: 84 minutes 55 secondsLast changed: 03/28/2005 12:33:36Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. Unit Tests: (1967) Total Errors and Failures: (10)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestStatefulPassiviationExpirationorg.jboss.test.testbeancluster.test.BeanUnitTestCasetestThreadedAccess_SimpleLockorg.jboss.test.cache.test.generic.IdentityLockUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (2)1.9.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.4.4.2modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.
[JBoss-dev] jboss-4.0-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050328192936 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: 03/28/2005 19:29:36Time to build: 46 minutes 28 secondsLast changed: 03/28/2005 18:10:20Last log entry: Add the personsAge field Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (52)1.15.4.3modifiedstarksmtestsuite/src/resources/cts/META-INF/ejb-jar.xmlAdd the personsAge field1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/ejb/CtsCmpBean.javaAdd the personsAge field1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/Ge
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Can we start writing jms test clients to check complianc
An observation related to naming: org.jboss.test.messaging.util is intendend to contain tests for Messaging utility classes, not utilities. Please use org.jboss.test.messaging.tools for that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871830#3871830 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871830 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Run-Time Page Definition
I need this as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871827#3871827 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871827 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050328160349 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: 03/28/2005 16:03:49Time to build: 57 minutes 17 secondsLast changed: 03/28/2005 12:34:04Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (76)1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject constructi
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: CacheInterceptor not intercepting
* Are you precompiling using AOPC? * Are you using Loadtime transformation? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871825#3871825 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871825 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - CacheInterceptor not intercepting
I may cross-post this on the JBoss Cache forum too... I have a class which is "prepared" in the aop.xml file. The TreeCacheAop implementation then calls this: | | InstanceAdvisor advisor = ((Advised) obj)._getInstanceAdvisor(); | advisor.appendInterceptor(new CacheInterceptor(this, fqn, type)); where obj is the prepared object. Then I call fieldX = val inside my class where fieldX is a member of my class. The interceptor's "invoke" never gets called, so the change never gets committed to the cache. Could someone help me try to figure this out? There is another class that extends this class, and field accesses on that class are intercepted. Could this be a problem with intercepting field accesses in a superclass? Let me know what more info I can provide. This is completely preventing me from using the jboss cache since many of my field updates are not being committed. Jboss AS 4.0.1.sp1 jboss-aop_1.1.1 (jboss-aop-jdk50.deployer) jbossCache-1.2.1 java (build 1.5.0_02-b09) -andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871824#3871824 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871824 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-219) See new posts
[ http://jira.jboss.com/jira/browse/JBPORTAL-219?page=history ] Roy Russo closed JBPORTAL-219: -- > See new posts > - > > Key: JBPORTAL-219 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-219 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 Final, 2.0 Beta 2 > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Beta 2 > > > Works with last login date, user should differenciate the newest posts from > the others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-219) See new posts
[ http://jira.jboss.com/jira/browse/JBPORTAL-219?page=history ] Roy Russo resolved JBPORTAL-219: Resolution: Done Fix Version: 2.0 Beta 2 This appears to already be done. New posts are marked with a different icon than the rest. > See new posts > - > > Key: JBPORTAL-219 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-219 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 Final, 2.0 Beta 2 > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Beta 2 > > > Works with last login date, user should differenciate the newest posts from > the others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: How do I get rollback to occur with remote cache access?
Thanks for the reply. I think I discovered for myself that the scenario I tried where there was a session bean running on the jboss instance with the cache wouldn't work because the JBoss transaction manager doesn't extend transactions across JVM's. However, from your reply, I assume it should work if the cache is looked up and accessed directly from the other instance. I apologize for my ignorance, but could you give me a little more guidance with your suggestions? I'm no expert on transactions, I've mostly just used container managed transactions without any direct manipulation. What exactly do I need to do to verify whether the cache was enrolled in the transaction? Also, I tried a sessionContext.setRollbackOnly() in my session bean, but that made no difference, the cache still didn't roll back. I was also going to try setting that on the transaction at the cache level, in case that's what you meant, so I tried to get the Transaction Manager for the cache using getTransactionManager() on the TreeCacheMBean instance, but that resulted in this error... Caused by: java.io.NotSerializableException: org.jboss.tm.TxManager at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at java.rmi.MarshalledObject.(MarshalledObject.java:92) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:364) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871823#3871823 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871823 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-222) Announcements and sticky posts
[ http://jira.jboss.com/jira/browse/JBPORTAL-222?page=history ] Roy Russo closed JBPORTAL-222: -- > Announcements and sticky posts > -- > > Key: JBPORTAL-222 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-222 > Project: JBoss Portal > Type: Task > Components: Forums > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Beta 2 > > > Very few to do, just to add the checkbox for it, the forums already check for > this flag in the database and displays announcements or sticky posts as it > should -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-222) Announcements and sticky posts
[ http://jira.jboss.com/jira/browse/JBPORTAL-222?page=history ] Roy Russo resolved JBPORTAL-222: Resolution: Done Fix Version: 2.0 Beta 2 fin. > Announcements and sticky posts > -- > > Key: JBPORTAL-222 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-222 > Project: JBoss Portal > Type: Task > Components: Forums > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Beta 2 > > > Very few to do, just to add the checkbox for it, the forums already check for > this flag in the database and displays announcements or sticky posts as it > should -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-21) MDB, Session Bean XML support
[ http://jira.jboss.com/jira/browse/EJBTHREE-21?page=history ] Bill Burke updated EJBTHREE-21: --- Fix Version: Preview 6 (was: EJB 3.0 Beta 1) > MDB, Session Bean XML support > - > > Key: EJBTHREE-21 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-21 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 5 > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 6 > > Original Estimate: 1 week > Remaining: 1 week > > Support EJB 3 spec mandated XML deployment descriptors. This has yet to be > defined in the EJB 3 specification though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-112) Support integration with Hibernate Query caches.
[ http://jira.jboss.com/jira/browse/EJBTHREE-112?page=history ] Bill Burke closed EJBTHREE-112: --- Resolution: Done Should be doable now that Hibernate Session/Query are exposed and hibernate.cfg.xml is available. > Support integration with Hibernate Query caches. > > > Key: EJBTHREE-112 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-112 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > > Not sure what is involved here, but make sure this is in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-55) EAR/WAR integration tutorial
[ http://jira.jboss.com/jira/browse/EJBTHREE-55?page=history ] Bill Burke closed EJBTHREE-55: -- Resolution: Done > EAR/WAR integration tutorial > > > Key: EJBTHREE-55 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-55 > Project: EJB 3.0 > Type: Task > Versions: Preview 4 > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > > Show how ejb3 jars can be packaged within an EAR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
[ http://jira.jboss.com/jira/browse/HIBERNATE-11?page=history ] youngm updated HIBERNATE-11: Attachment: hibernate-cache.diff Here is a patch that appears to fix the problem. It replaces all instances of TreeCache with TreeCacheMBean. > DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1 > - > > Key: HIBERNATE-11 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-11 > Project: Hibernate > Type: Bug > Reporter: youngm > Assignee: Gavin King > Attachments: hibernate-cache.diff > > > When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the > returned instance to org.jboss.cache.TreeCacheMBean not > org.jboss.cache.TreeCache. > Mike > See stacktrace below: > 13:25:29,883 ERROR [Hibernate] Starting failed > jboss.har:service=am_data/HibernateFactory > net.sf.hibernate.HibernateException: Could not instantiate Cache > at > net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138) > at > net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795) > at > org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583) > at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > 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.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at > org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at > org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy7.deploy(Unknown Source) > at > org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) > at > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483) > at > org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanne
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=history ] Ryan Campbell resolved JBBUILD-8: - Resolution: Done Ok, resources can now be artifacts. See sqlexception-service.xml in jboss/jbossbuild.xml for an example. > 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 > Fix For: milestone-1 > > > Allow resources to be defined like source. A component should be able to > declare a resource where: > > includes the source under src/resources/jbossmq-httputil which could be > included in an artifact: > > > > > > 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 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-57) Support script (bin) artifacts
[ http://jira.jboss.com/jira/browse/JBBUILD-57?page=history ] Ryan Campbell resolved JBBUILD-57: -- Resolution: Done This is complete, see server/jbossbuild.xml for an example. > Support script (bin) artifacts > -- > > Key: JBBUILD-57 > URL: http://jira.jboss.com/jira/browse/JBBUILD-57 > Project: JBoss Build System > Type: Feature Request > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Fix For: milestone-1 > > > Allow an artifact like: > > Which would come from component/output/bin. These bin artifacts will depend > on the new build.bin target which copies them from src/bin, calls chmod and > crlf as appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050328132632 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: 03/28/2005 13:26:32Time to build: 55 minutes 48 secondsLast changed: 03/28/2005 12:34:04Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (54)1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2
[JBoss-dev] [JBossCache] - Re: IdentityLock write lock
we try to release every 2-3 months, but the next release is going to be 1.2.2 (hopefully end of April). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871819#3871819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871819 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-57) Support script (bin) artifacts
Support script (bin) artifacts -- Key: JBBUILD-57 URL: http://jira.jboss.com/jira/browse/JBBUILD-57 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: milestone-1 Allow an artifact like: Which would come from component/output/bin. These bin artifacts will depend on the new build.bin target which copies them from src/bin, calls chmod and crlf as appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
-
Key: HIBERNATE-11
URL: http://jira.jboss.com/jira/browse/HIBERNATE-11
Project: Hibernate
Type: Bug
Reporter: youngm
Assigned to: Gavin King
When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the
returned instance to org.jboss.cache.TreeCacheMBean not
org.jboss.cache.TreeCache.
Mike
See stacktrace below:
13:25:29,883 ERROR [Hibernate] Starting failed
jboss.har:service=am_data/HibernateFactory
net.sf.hibernate.HibernateException: Could not instantiate Cache
at
net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138)
at
net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795)
at
org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583)
at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
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.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy7.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
Caused by: net.sf.hibernate.cache.CacheException: java.lang.ClassCastException:
Object at 'cache/am_data' in context
{java.naming.fa
[JBoss-dev] [JBoss JIRA] Created: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+ Key: HIBERNATE-10 URL: http://jira.jboss.com/jira/browse/HIBERNATE-10 Project: Hibernate Type: Bug Reporter: youngm Assigned to: Gavin King DeployedTreeCacheProvider must be updated to support interface changes made to net.sf.hibernate.cache.CacheProvider in 2.1.8. http://forum.hibernate.org/viewtopic.php?t=940501 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - install nukes problems
How I must to install nukes in Jboss portal betta That verion compatible with Jboss portal betta View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871813#3871813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871813 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: IdentityLock write lock
When is the 1.3 or 1.4 JBossCache to be released? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871812#3871812 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871812 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Can we start writing jms test clients to check complianc
Looks fine. Go ahead. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871809#3871809 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871809 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Own servlet mapping
the same way as you would do it in any other war. add a servlet-mapping element in the web.xml View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871808#3871808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871808 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Head build broken
On Mon, 2005-03-28 at 14:27, Adrian Brock wrote: > On Mon, 2005-03-28 at 14:09, Dave Smith wrote: > > Ok .. > > > > cvs co j2se > > cvs server: cannot find module `j2se' - ignored > > cvs [checkout aborted]: cannot expand modules > > > > Try .. > > cvs co -d j2se jboss-j2se > > > > Correct. > > > This seems to work. Looks like the module is not defined in head. > > > > Yes it is. > cvs does not look at CVSROOT/modules for an update/get, > it only looks at your local repository. > > You have to do a cvs co, either partial (like above) or a full > clean checkout. > > I'm going to add this to the FAQ, even though it is really a CVS > question/limitation. > Well actually, I won't because it will be redundant when the new build is online: cd jbossas ant synchronize > > On Mon, 2005-03-28 at 13:57, Adrian Brock wrote: > > > cd jboss-head > > > cvs co j2se > > > > > > On Mon, 2005-03-28 at 13:45, Dave Smith wrote: > > > > When trying to build, latest head CVS with jdk 1.5 the jmx module does > > > > not compile. It has been like this since the jmx refactoring that > > > > happened last week. > > > > > > > > An example .. > > > > > > > > jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: > > > > cannot find symbol > > > > symbol : class ServerConstants > > > > location: package org.jboss.mx.server > > > > import org.jboss.mx.server.ServerConstants; > > > > > > > > jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: > > > > cannot find symbol > > > > symbol : class ModelMBeanConstants > > > > location: package org.jboss.mx.modelmbean > > > > import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Adrian Brock Chief Scientist JBoss Inc. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Head build broken
On Mon, 2005-03-28 at 14:09, Dave Smith wrote: > Ok .. > > cvs co j2se > cvs server: cannot find module `j2se' - ignored > cvs [checkout aborted]: cannot expand modules > > Try .. > cvs co -d j2se jboss-j2se > Correct. > This seems to work. Looks like the module is not defined in head. > Yes it is. cvs does not look at CVSROOT/modules for an update/get, it only looks at your local repository. You have to do a cvs co, either partial (like above) or a full clean checkout. I'm going to add this to the FAQ, even though it is really a CVS question/limitation. > On Mon, 2005-03-28 at 13:57, Adrian Brock wrote: > > cd jboss-head > > cvs co j2se > > > > On Mon, 2005-03-28 at 13:45, Dave Smith wrote: > > > When trying to build, latest head CVS with jdk 1.5 the jmx module does > > > not compile. It has been like this since the jmx refactoring that > > > happened last week. > > > > > > An example .. > > > > > > jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: > > > cannot find symbol > > > symbol : class ServerConstants > > > location: package org.jboss.mx.server > > > import org.jboss.mx.server.ServerConstants; > > > > > > jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: > > > cannot find symbol > > > symbol : class ModelMBeanConstants > > > location: package org.jboss.mx.modelmbean > > > import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Adrian Brock Chief Scientist JBoss Inc. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Head build broken
I think this one is for Bill ... ejb3 head build is broken .. in tools/etc/buildmagic/libraries.ent the needs to include On Mon, 2005-03-28 at 14:09, Dave Smith wrote: > Ok .. > > cvs co j2se > cvs server: cannot find module `j2se' - ignored > cvs [checkout aborted]: cannot expand modules > > Try .. > cvs co -d j2se jboss-j2se > > This seems to work. Looks like the module is not defined in head. > > On Mon, 2005-03-28 at 13:57, Adrian Brock wrote: > > cd jboss-head > > cvs co j2se > > > > On Mon, 2005-03-28 at 13:45, Dave Smith wrote: > > > When trying to build, latest head CVS with jdk 1.5 the jmx module does > > > not compile. It has been like this since the jmx refactoring that > > > happened last week. > > > > > > An example .. > > > > > > jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: > > > cannot find symbol > > > symbol : class ServerConstants > > > location: package org.jboss.mx.server > > > import org.jboss.mx.server.ServerConstants; > > > > > > jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: > > > cannot find symbol > > > symbol : class ModelMBeanConstants > > > location: package org.jboss.mx.modelmbean > > > import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Dave Smith http://www.theappman.com --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Head build broken
Ok .. cvs co j2se cvs server: cannot find module `j2se' - ignored cvs [checkout aborted]: cannot expand modules Try .. cvs co -d j2se jboss-j2se This seems to work. Looks like the module is not defined in head. On Mon, 2005-03-28 at 13:57, Adrian Brock wrote: > cd jboss-head > cvs co j2se > > On Mon, 2005-03-28 at 13:45, Dave Smith wrote: > > When trying to build, latest head CVS with jdk 1.5 the jmx module does > > not compile. It has been like this since the jmx refactoring that > > happened last week. > > > > An example .. > > > > jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: > > cannot find symbol > > symbol : class ServerConstants > > location: package org.jboss.mx.server > > import org.jboss.mx.server.ServerConstants; > > > > jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: > > cannot find symbol > > symbol : class ModelMBeanConstants > > location: package org.jboss.mx.modelmbean > > import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Dave Smith http://www.theappman.com --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Head build broken
cd jboss-head cvs co j2se On Mon, 2005-03-28 at 13:45, Dave Smith wrote: > When trying to build, latest head CVS with jdk 1.5 the jmx module does > not compile. It has been like this since the jmx refactoring that > happened last week. > > An example .. > > jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: > cannot find symbol > symbol : class ServerConstants > location: package org.jboss.mx.server > import org.jboss.mx.server.ServerConstants; > > jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: > cannot find symbol > symbol : class ModelMBeanConstants > location: package org.jboss.mx.modelmbean > import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Adrian Brock Chief Scientist JBoss Inc. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Head build broken
When trying to build, latest head CVS with jdk 1.5 the jmx module does not compile. It has been like this since the jmx refactoring that happened last week. An example .. jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:13: cannot find symbol symbol : class ServerConstants location: package org.jboss.mx.server import org.jboss.mx.server.ServerConstants; jboss/jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java:47: cannot find symbol symbol : class ModelMBeanConstants location: package org.jboss.mx.modelmbean import org.jboss.mx.modelmbean.ModelMBeanConstants; -- Dave Smith Candata Systems Ltd 416-493-9020 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Security Context
an addition to the previous: and the reason for that is because I'm doing auditing of ejb methods in my aspect class (writing which ejb method was called into the log file) and I need to know which user called the ejb method that I'm auditing. Thanks Michael. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871793#3871793 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871793 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-166) exception during refactoring
[ http://jira.jboss.com/jira/browse/JBIDE-166?page=comments#action_12316452 ] Marshall Culpepper commented on JBIDE-166: -- We do not support eclipse 3.1M5a in any release other than 1.5 Milestone 1.. unfortunately some changes were made to distribution that required a last minute fix that is incompatible with previous releases (including 3.0) > exception during refactoring > > > Key: JBIDE-166 > URL: http://jira.jboss.com/jira/browse/JBIDE-166 > Project: JBoss IDE > Type: Bug > Environment: eclipse ide 3.1M5a > Reporter: mike andrews > Assignee: Marshall Culpepper > > > got a null pointer exception during refactoring. was not using any > functionality of jboss plugin. > see original eclipse bug report, which was redirected to jboss: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=89201 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Security Context
Hi, I'm sorry I meant inside of my Aspect class. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871790#3871790 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871790 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: IdentityLock write lock
I tired to grab the TreeCache and TreeCacheProvider classes from Hibernate3 and using them with 2.1.8 but this produced the following exception when I try to commit the JTA transaction: | java.lang.ArrayIndexOutOfBoundsException: 1 | at net.sf.hibernate.impl.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:57) | at net.sf.hibernate.impl.BatcherImpl.executeBatch(BatcherImpl.java:128) | at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2438) | at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2392) | at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2261) | at net.sf.hibernate.transaction.JTATransaction.commit(JTATransaction.java:52) | Apparently there is more to this change than just these classes. Any ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871787#3871787 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871787 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Security Context
yes. 1) org.jboss.aspects.security.SecurityContext.getCallerPrincipal 2) getCurrentPrincipal() isCallerInRole isCurrentInRole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871786#3871786 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871786 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - AOP Security Context
If I intercept calls to ejb methods, is there a way to get access to a principal object to get user name or user role that called the ejb? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871785#3871785 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871785 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=history ] Dimitris Andreadis closed JBAS-1448: Resolution: Done (actually the output looks a little better :) ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=comments#action_12316449 ] Dimitris Andreadis commented on JBAS-1448: -- Example output when running under jdk5+: Total Threads: 54Total Thread Groups: 7Thread Group: system : max priority:10, demon:falseThread: Reference Handler : priority:10, demon:true, threadId:2, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.Object.wait(Object.java:474)java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)Thread: Finalizer : priority:8, demon:true, threadId:3, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)Thread: Signal Dispatcher : priority:10, demon:true, threadId:4, threadState:RUNNABLE, threadLockName:nullThread: RMI TCP Accept-1098 : priority:5, demon:true, threadId:14, threadState:RUNNABLE, threadLockName:nulljava.net.PlainSocketImpl.socketAccept(Native Method)java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)java.net.ServerSocket.implAccept(ServerSocket.java:450)java.net.ServerSocket.accept(ServerSocket.java:421)sun.rmi.transport.tcp.TCPTransport.run(TCPTransport.java:334)java.lang.Thread.run(Thread.java:595)Thread: RMI Reaper : priority:5, demon:false, threadId:16, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:336)java.lang.Thread.run(Thread.java:595)Thread: GC Daemon : priority:2, demon:true, threadId:17, threadState:TIMED_WAITING, threadLockName:[EMAIL PROTECTED](Native Method)sun.misc.GC$Daemon.run(GC.java:100)Thread: RMI TCP Accept- : priority:5, demon:true, threadId:20, threadState:RUNNABLE, threadLockName:nulljava.net.PlainSocketImpl.socketAccept(Native Method)java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)java.net.ServerSocket.implAccept(ServerSocket.java:450)java.net.ServerSocket.accept(ServerSocket.java:421)sun.rmi.transport.tcp.TCPTransport.run(TCPTransport.java:334)java.lang.Thread.run(Thread.java:595) ... ... ... > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=comments#action_12316448 ] Dimitris Andreadis commented on JBAS-1448: -- Example output when running under jdk1.3/1.4 (same as before): Total Threads: 55Total Thread Groups: 7Thread Group: system : max priority:10, demon:falseThread: Reference Handler : priority:10, demon:trueThread: Finalizer : priority:8, demon:trueThread: Signal Dispatcher : priority:10, demon:trueThread: CompilerThread0 : priority:10, demon:trueThread: RMI TCP Accept-1098 : priority:5, demon:trueThread: RMI Reaper : priority:5, demon:falseThread: GC Daemon : priority:2, demon:trueThread: RMI TCP Accept- : priority:5, demon:trueThread Group: main : max priority:10, demon:falseThread: DestroyJavaVM : priority:5, demon:falseThread Group: jboss : max priority:10, demon:falseThread: Thread-0 : priority:5, demon:trueThread: ScannerThread : priority:5, demon:trueThread: Thread-2 : priority:5, demon:trueThread: PooledInvokerAcceptor#0-4445 : priority:5, demon:falseThread: ContainerBackgroundProcessor[StandardEngine[jboss.web]] : priority:5, demon:trueThread: HSQLDB Timer @1d532ae : priority:5, demon:trueThread: JBossMQ Cache Reference Softner : priority:5, demon:trueThread: Thread-4 : priority:5, demon:trueThread: TimeoutFactory : priority:5, demon:trueThread: IdleRemover : priority:5, demon:falseThread: JCA PoolFiller : priority:5, demon:falseThread: JBossLifeThread : priority:5, demon:falseThread: http-0.0.0.0-8080-Processor1 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor2 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor3 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor4 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor5 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor6 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor7 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor8 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor9 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor10 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor11 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor12 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor13 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor14 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor15 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor16 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor17 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor18 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor19 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor20 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor21 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor22 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor23 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor24 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor25 : priority:5, demon:trueThread: http-0.0.0.0-8080-Monitor : priority:5, demon:falseThread: TP-Processor1 : priority:5, demon:trueThread: TP-Processor2 : priority:5, demon:trueThread: TP-Processor3 : priority:5, demon:trueThread: TP-Processor4 : priority:5, demon:trueThread: TP-Monitor : priority:5, demon:trueThread Group: JBoss Pooled Threads : max priority:10, demon:falseThread: ClassLoadingPool(2)-1 : priority:5, demon:trueThread Group: System Threads : max priority:10, demon:falseThread: JBoss System Threads(1)-1 : priority:5, demon:trueThread Group: JBossMQ Server Threads : max priority:10, demon:falseThread: UILServerILService Accept Thread : priority:5, demon:falseThread Group: RMI Runtime : max priority:10, demon:false > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- 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.c
[JBoss-dev] jboss-head build.904 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050328104639Lbuild.904 BUILD COMPLETE - build.904Date of build: 03/28/2005 10:46:39Time to build: 54 minutes 32 secondsLast changed: 03/28/2005 10:32:58Last log entry: add support for hibernate.cfg.xml fileDo not scope EntityManager to entire EAR. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (16)1.40modifiedpatriot1burkeejb3/build-test.xmladd support for hibernate.cfg.xml fileDo not scope EntityManager to entire EAR.1.29modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/Ejb3Module.javaadd support for hibernate.cfg.xml fileDo not scope EntityManager to entire EAR.1.8modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/entity/HibernateSessionFactory.javaadd support for hibernate.cfg.xml fileDo not scope EntityManager to entire EAR.1.12modifiedejorttransaction/.classpathFix the eclipse build1.2modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupdate1.1addedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/lob/BlobEntity2.javaadd additional @Lob tests1.2modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/lob/LobTester.javaadd additional @Lob tests1.4modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/lob/LobTesterBean.javaadd additional @Lob tests1.2modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/lob/unit/BlobUnitTestCase.javaadd additional @Lob tests1.2modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/composite2/Composite.javafix composite bug1.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.13modifiedreverbelthirdparty/jacorb-jacorb/lib/jacorb_g.jarJacORB libs updated to a patched version of JacORB 2.2.1, which identifiesitself as "JacORB V 2.2.1 (JBoss patch 2)". This version fixes thefollowing JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574,#584, #585, and #586. It also includes the exception reporting improvementscommitted to JacORB's CVS repository in 2004/11/18 and 2004/12/11.1.8modifiedreverbelthirdparty/jacorb-jacorb/lib/idl_g.jarJacORB libs updated to a patched version of JacORB 2.2.1, which identifiesitself as "JacORB V 2.2.1 (JBoss patch 2)". This version fixes thefollowing JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574,#584, #585, and #586. It also includes the exception reporting improvementscommitted to JacORB's CVS repository in 2004/11/18 and 2004/12/11.1.33modifiedreverbelthirdparty/jacorb-jacorb/lib/jacorb.jarJacORB libs updated to a patched version of JacORB 2.2.1, which identifiesitself as "JacORB V 2.2.1 (JBoss patch 2)". This version fixes thefollowing JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574,#584, #585, and #586. It also includes the exception reporting improvementscommitted to JacORB's CVS repository in 2004/11/18 and 2004/12/11.1.29modifiedreverbelthirdparty/jacorb-jacorb/lib/READMEJacORB libs updated to a patched version of JacORB 2.2.1, which identifiesitself as "JacORB V 2.2.1 (JBoss patch 2)". This version fixes thefollowing JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574,#584, #585, and #586. It also includes the exception reporting improvementscommitted to JacORB's CVS repository in 2004/11/18 and 2004/12/11.1.11modifiedreverbelthirdparty/jacorb-jacorb/lib/idl.jarJacORB libs updated to a patched version of JacORB 2.2.1, which identifiesitself as "JacORB V 2.2.1 (JBoss patch 2)". This version fixes thefollowing JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574,#584, #585, and #586. It also includes the exception reporting improvementscommitted to JacORB's CVS repository in 2004/11/18 and 2004/12/11.
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1625) JBossQL ORDER BY does not work on string valued mapped types
JBossQL ORDER BY does not work on string valued mapped types Key: JBAS-1625 URL: http://jira.jboss.com/jira/browse/JBAS-1625 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.1 Final Environment: Windows XP Pro SP2, JBoss 4.0.1, Sun JDK 1.5.0_02 Reporter: cgs 09:59:09,147 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/Contact,service=EJB org.jboss.deployment.DeploymentException: Error compiling JBossQL statement 'SELECT DISTINCT OBJECT(c) FROM organization o, IN (o.contactList) AS c WHERE o = ?1 ORDER BY c.currentContactInfo.lastName ASC, c.currentContactInfo.firstName ASC, c.currentContactInfo.emailAddress ASC OFFSET ?2 LIMIT ?3'; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "c.currentContactInfo.emailAddress" at line 1, column 186. Was expecting one of: ... ... ... ) at org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.(JDBCJBossQLQuery.java:52) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createJBossQLQuery(JDBCCommandFactory.java:72) at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:260) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:490) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:381) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157) at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy304.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:394) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-105) DS: add hibernate.dialect metadata
[ http://jira.jboss.com/jira/browse/EJBTHREE-105?page=history ] Bill Burke closed EJBTHREE-105: --- Resolution: Rejected Too many dependencies. JCA would have to know about hibernate, Hibernate would have to know about JBoss JCA. > DS: add hibernate.dialect metadata > -- > > Key: EJBTHREE-105 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-105 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 4 > Environment: Linux, JDK 1.5; Jboss 4.0.1sp1 > Reporter: Jens Elkner > Priority: Critical > > > Actually IMHO it is not possible, to deploy an EJB3 application to jboss in a > relayable way. E.g. an application may ask a user to create a datasource with > a certain name, however, it should not care/dictate, what a database the user > chooses (IMHO thats one of the biggest advantage of an J2EE server). > However, since the hibernate.dialect property depends direct on the type of > database, an application can't be shipped with a > META-INF/hibernate.properties, where the hibernate.dialect is set. E.g. if so > oracle.jdbc.driver.OracleDriver and > hibernate.dialect=hibernate.dialect=org.hibernate.dialect.MySQLMyISAMDialect > simply would produce garbage. > Editing the META-INF/hibernate.properties is not an option, since if the > archive is signed, this would destroy the inegrity of the archive (besides > the fact, that it would be unaceppably to ask the user/admin to that). > To solve this problem, IMHO it is neccessary, that a new optional metadata > tag should be allowed in . E.g.: > >... > > ... > ... > > > Now, if the EBJ3 deployer starts deploying an ejb3 archive, > it may have a look at the DS metadata and add/overwrite the hibernate.dialect > property. > Digging around, I guess, that > org.jboss.ejb3.entity.HibernateSessionFactory:createSessionFactory(java.util.Collection > classes, Properties props) right before > "if (props != null) cfg.setProperties(props);" > would be anappropriate place, doing that. > Unfortunately, I do not know, whether/how it is possible and allowed to > access the metadata of the datasource at this point. > If you can give me a hint, I would try to implement/test this... > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - DO NOT POST USER QUESTIONS HERE!
User questions will be deleted. If you are asking for help, you are asking a "user question". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871780#3871780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871780 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: failure in building testsuite
Your question does not relate to the "Design of the Build System". Use the *user* forums. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871779#3871779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871779 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-103) @NamedQuery for method and package level
[ http://jira.jboss.com/jira/browse/EJBTHREE-103?page=history ] Bill Burke closed EJBTHREE-103: --- Resolution: Rejected will/is handled in Hibernate annotations project > @NamedQuery for method and package level > > > Key: EJBTHREE-103 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-103 > Project: EJB 3.0 > Type: Feature Request > Reporter: Kabir Khan > > > Implement once spec makes more sense -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-88) EJB doc - missing quotes
[ http://jira.jboss.com/jira/browse/EJBTHREE-88?page=history ] Bill Burke closed EJBTHREE-88: -- Resolution: Done > EJB doc - missing quotes > > > Key: EJBTHREE-88 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-88 > Project: EJB 3.0 > Type: Bug > Components: Documentation > Versions: Preview 4 > Environment: Linux, Mozilla 1.7.3, Apache/2.0.52 (Unix) > Reporter: Jens Elkner > Priority: Trivial > > Original Estimate: 5 minutes > Remaining: 5 minutes > > ejb3/docs/index.html: quotes are missing for the first two hrefs and thus one > gets e.g. "http://localhost/develop/jboss40/ejb3/EJB3-edr2.pdf%22"; from > mozilla pointing to a non-existent object ... > --- patch --- > --- index.html.orig Tue Feb 8 22:52:22 2005 > +++ index.htmlWed Mar 2 00:12:44 2005 > @@ -6,8 +6,8 @@ > > > > - EJB 3.0 Specification (non-persistence > stuff) > - EJB 3.0 Persistence Specification > + EJB 3.0 Specification (non-persistence > stuff) > + EJB 3.0 Persistence > Specification > Tutorial Walks you through EJB 3.0 > with real examples that you can build and run. > Configuring Describes how you > configure datasources and Hibernate 3.0. Hibernate 3.0 drives our entity > bean implementation. > JNDI Bindings JNDI , interceptor, and > transport bindings for your session beans. > --- eo patch -- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-89) docs included twice
[ http://jira.jboss.com/jira/browse/EJBTHREE-89?page=history ] Bill Burke closed EJBTHREE-89: -- Resolution: Done will be fixed in preview 5 > docs included twice > --- > > Key: EJBTHREE-89 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-89 > Project: EJB 3.0 > Type: Feature Request > Components: Documentation > Versions: Preview 4 > Environment: All > Reporter: Jens Elkner > Priority: Trivial > > Original Estimate: 5 minutes > Remaining: 5 minutes > > jboss-EJB-3.0_Preview_4.zip contains documentation twice: > 1) unpacked in jboss-EJB-3.0_Preview_4/docs/ and > 2) as zip: jboss-EJB-3.0_Preview_4/docs/ejb3-preview4-docs.zip > One of both should be removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-115) Doco on Hibernate integration
[ http://jira.jboss.com/jira/browse/EJBTHREE-115?page=history ] Bill Burke reassigned EJBTHREE-115: --- Assign To: Bill Burke > Doco on Hibernate integration > - > > Key: EJBTHREE-115 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-115 > Project: EJB 3.0 > Type: Task > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > > * mix of .hbm.xml and @Entity > * tutorial on .hbm.xml > * Exposing Session/Query > * Query cache tutorial and doco -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-98) Use latest Hibernate distribution
[ http://jira.jboss.com/jira/browse/EJBTHREE-98?page=history ] Bill Burke reassigned EJBTHREE-98: -- Assign To: Bill Burke > Use latest Hibernate distribution > - > > Key: EJBTHREE-98 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-98 > Project: EJB 3.0 > Type: Task > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-112) Support integration with Hibernate Query caches.
[ http://jira.jboss.com/jira/browse/EJBTHREE-112?page=history ] Bill Burke reassigned EJBTHREE-112: --- Assign To: Bill Burke > Support integration with Hibernate Query caches. > > > Key: EJBTHREE-112 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-112 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > > Not sure what is involved here, but make sure this is in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-116) EntityManager should not be scoped to entire EAR
[ http://jira.jboss.com/jira/browse/EJBTHREE-116?page=history ] Bill Burke closed EJBTHREE-116: --- Resolution: Done > EntityManager should not be scoped to entire EAR > > > Key: EJBTHREE-116 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-116 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 4 > Reporter: Bill Burke > Fix For: Preview 5 > > > For one EAR in Preview 4 and lower, there is one EntityManager instance > scoped to the entire EAR. THis is not good because 1 ear may want to > interact with multiple data sources. So, EntityManager is scoped to the EJB > jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-116) EntityManager should not be scoped to entire EAR
EntityManager should not be scoped to entire EAR Key: EJBTHREE-116 URL: http://jira.jboss.com/jira/browse/EJBTHREE-116 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Fix For: Preview 5 For one EAR in Preview 4 and lower, there is one EntityManager instance scoped to the entire EAR. THis is not good because 1 ear may want to interact with multiple data sources. So, EntityManager is scoped to the EJB jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-111) Support hibernate.cfg.xml file
[ http://jira.jboss.com/jira/browse/EJBTHREE-111?page=history ] Bill Burke closed EJBTHREE-111: --- Resolution: Done > Support hibernate.cfg.xml file > -- > > Key: EJBTHREE-111 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-111 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Fix For: Preview 5 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (EJBTHREE-111) Support hibernate.cfg.xml file
[ http://jira.jboss.com/jira/browse/EJBTHREE-111?page=comments#action_12316444 ] Bill Burke commented on EJBTHREE-111: - You can now use a META-INF/hibernate.cfg.xml file instead of a hibernate.properties file > Support hibernate.cfg.xml file > -- > > Key: EJBTHREE-111 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-111 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Fix For: Preview 5 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-114) EntityManager Identity
[ http://jira.jboss.com/jira/browse/EJBTHREE-114?page=history ] Bill Burke updated EJBTHREE-114: Fix Version: EJB 3.0 Beta 1 (was: Preview 5) > EntityManager Identity > -- > > Key: EJBTHREE-114 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-114 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: EJB 3.0 Beta 1 > > > EntityManager's are scoped per EJB-JAR. We want to give them identity so > that they can be injected into a WAR or another SessionBean outside the scope. > The default EntityManager name is the empty string "". > Provide a ejb3-jboss.xml file that allows you to specify the EntityManager > name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Will JBossCache support non read/write mode?
This is the original message that I posted to the Hibernate JBoss forum. We have multiple applications that uses a metadata cache. Currently each application needs to refresh itself from the database using Hibernate. To minimize database hits, we would like to implement a clustered, replicated cache. But without the overhead of a J2EE app server. A couple of the applications are medium size RMI servers that would only become bloated with JBoss. One application already runs Tomcat as a lightweight web container. I've checked out SwarmCache and OSCache. Neither supports replication. Cache invalidation really is only marginally better than the refreshing action we have now. Changed objects will be immediately updated but new objects will still have to be periodically refreshed. As I understand it, if JBossCache supported r/w and/or nonrestrict r/w, it wouldn't be necessary to have the app server overhead. As of now, I am leaning towards using OSCache with the patched CacheProvider code that handles clustering. I'll see if perhaps I can modify the code to handle newly created objects. Does anyone have anything to say on this approach? In addition, is it possible to have a server with read-only cache (sans transaction manager) and another server with transactional cache in the same cluster? We could get away with installing JBoss with our tomcat app. Any help is greatly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871773#3871773 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871773 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: ordered (re) delivery etc.. / ebMS
"kukeltje" wrote : Hi, | | I've been working with Hermes, the freebXML ebMS server. They have developed lots of things that are already in J2EE (like transactions, a connectionpool) for resons beyond *my* comprehension. Users say they just want to be able to run it in a simple servlet engine, so anything other than a j2ee server (it was even mentioned that the would build their own servlet engine or plain http server). Since Tomcat as well as Jetty already have transaction and connectionpool support, to me it is like reinventing the wheel, but that is their choice. | This is an FAQ (of sorts): http://www.jboss.org/wiki/Wiki.jsp?page=I+want+to+plugin+a+custom%2Fthirdparty+DataSource anonymous wrote : | One other issue is that ebMS has something called ordered delivery, redelivery delay and redelivey count. Hermes also implemented this themselves, but It would be realy great if JMS would support something like this. Not just by the order in which messages are put in the queue, but based on jms headers (sequence comes into mind, ) in combination with redelivery delay and redelivery count. Not only for ebMS, but for WS-Reliability* as well. | JBossMQ already has redelivery delay/count There is currently no mechanism to override the spec defined order of priority/arrival sequence, but I would accept a patch that allowed a Comparator to be defined per Queue/Topic. anonymous wrote : | Is there any change JBoss will extend JMS with this functionality or even participate in the JCP to enhance JMS with this functionality. The thing is that parts of this are already in JMS, but a full functioning combination is (to my knowledge) not. | I would doubt this would make it into JMS spec. JMS is a lowest common demonitor spec designed to plug disparate messaging systems. It is a "quality of implementation" issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871771#3871771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871771 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-55) EAR/WAR integration tutorial
[ http://jira.jboss.com/jira/browse/EJBTHREE-55?page=history ] Bill Burke updated EJBTHREE-55: --- Assign To: Bill Burke (was: Kabir Khan) > EAR/WAR integration tutorial > > > Key: EJBTHREE-55 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-55 > Project: EJB 3.0 > Type: Task > Versions: Preview 4 > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > > Show how ejb3 jars can be packaged within an EAR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - ordered (re) delivery etc.. / ebMS
Hi, I've been working with Hermes, the freebXML ebMS server. They have developed lots of things that are already in J2EE (like transactions, a connectionpool) for resons beyond *my* comprehension. Users say they just want to be able to run it in a simple servlet engine, so anything other than a j2ee server (it was even mentioned that the would build their own servlet engine or plain http server). Since Tomcat as well as Jetty already have transaction and connectionpool support, to me it is like reinventing the wheel, but that is their choice. One other issue is that ebMS has something called ordered delivery, redelivery delay and redelivey count. Hermes also implemented this themselves, but It would be realy great if JMS would support something like this. Not just by the order in which messages are put in the queue, but based on jms headers (sequence comes into mind, ) in combination with redelivery delay and redelivery count. Not only for ebMS, but for WS-Reliability* as well. Is there any change JBoss will extend JMS with this functionality or even participate in the JCP to enhance JMS with this functionality. The thing is that parts of this are already in JMS, but a full functioning combination is (to my knowledge) not. If someone could point me in the right direction of a designpattern to implement this, that would be great. Ronald View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871769#3871769 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871769 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1624) Hibernate deployment failed on JBossAS 4.0.2RC1
Hibernate deployment failed on JBossAS 4.0.2RC1 --- Key: JBAS-1624 URL: http://jira.jboss.com/jira/browse/JBAS-1624 Project: JBoss Application Server Type: Bug Components: Hibernate service Versions: JBossAS-4.0.2RC1 Environment: Linux FC2, jdk build 1.5.0_02-b09 Reporter: Joao Miranda Priority: Minor I have a .ear that contains a .har and works fine on 4.0.1 and 4.0.1sp1. The same .ear raises an exception during the deployment on a 4.0.2RC1. The workarond for this is to copy the commons-collections jar to the lib dir of the server. But I think that this jar can come with the JBoss distribution and don't need to copy it. 12:41:24,591 INFO [EARDeployer] Init J2EE application: file:/usr/local/jboss-4.0.2RC1/server/topticket/deploy/topticket.ear 12:41:26,960 INFO [Environment] Hibernate 2.1.6 12:41:26,969 INFO [Environment] hibernate.properties not found 12:41:26,977 INFO [Environment] using CGLIB reflection optimizer 12:41:27,014 INFO [Configuration] Searching for mapping documents in jar: topticket.har 12:41:27,352 INFO [Configuration] Found mapping documents in jar: pt/topsolutions/topticket/hibernate/AlType.hbm.xml 12:41:28,903 WARN [ServiceController] Problem starting service jboss.har:service=Hibernate java.lang.NoClassDefFoundError: org/apache/commons/collections/SequencedHashMap at net.sf.hibernate.mapping.PersistentClass.(PersistentClass.java:30) at net.sf.hibernate.mapping.RootClass.(RootClass.java:16) at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1255) at net.sf.hibernate.cfg.Configuration.add(Configuration.java:252) at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:288) at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:396) at org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:574) at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: non-java clients
Having mulled it over, my plan is to first implement a new IL based on the existing csil wireline protocol, in the original jbossmq. Thanks for the guidance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871768#3871768 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871768 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Opinion: TreeCache/CacheLoader isomorphism
I understand that the desire to form delegating cache networks has led to TreeCache and CacheLoader having the same interface, but IMHO that interface should be split into two so that the delegation/CacheLoader interface doesn't contain non-canonical methods such as get(Fqn, Object), get(String, Object), and get(String), where get(Fqn) will do. In any case, 2.1 only calls CacheLoader.get(Fqn) in response to TreeCache.get(Fqn, Object) so it's obviously canonicalizing to some extent, although it's not indicated anywhere which CacheLoader methods are 'required' i.e. form the canonical subset. Is there some additional reason for the interfaces to be the same that I'm not understanding? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871767#3871767 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871767 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - CacheLoader: exists() before get() inefficient - solution?
I have a CacheLoader that I am using to allow a TreeCache to act as the primary interface to a DAV/JDBC data model. Each access to the backend can be quite expensive. I note that a CacheLoader.get() is always preceeded by a CacheLoader.exists(), which seems redundant to me and has the unfortunate effect of doubling the backend load. Am I missing something here? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871766#3871766 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871766 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-166) exception during refactoring
[ http://jira.jboss.com/jira/browse/JBIDE-166?page=comments#action_12316441 ] mike andrews commented on JBIDE-166: i have jboss-ide 1.4.0 installed in eclipse 3.1M5a for windows XP (i.e., see http://cudlug.cudenver.edu/eclipse/eclipse/downloads/drops/S-3.1M5a-200502191500/ ) eclipse bug report contains stack trace, which i repeat here for completeness: java.lang.NullPointerException at org.jboss.ide.eclipse.jdt.j2ee.jsp.ui.decorators.JSPNatureDecorator.decorate(JSPNatureDecorator.java:69) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:220) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:65) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1015) at org.eclipse.core.runtime.Platform.run(Platform.java:757) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:287) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:273) at org.eclipse.ui.internal.decorators.DecorationScheduler$2.run(DecorationScheduler.java:299) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67) > exception during refactoring > > > Key: JBIDE-166 > URL: http://jira.jboss.com/jira/browse/JBIDE-166 > Project: JBoss IDE > Type: Bug > Environment: eclipse ide 3.1M5a > Reporter: mike andrews > Assignee: Marshall Culpepper > > > got a null pointer exception during refactoring. was not using any > functionality of jboss plugin. > see original eclipse bug report, which was redirected to jboss: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=89201 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-166) exception during refactoring
exception during refactoring Key: JBIDE-166 URL: http://jira.jboss.com/jira/browse/JBIDE-166 Project: JBoss IDE Type: Bug Environment: eclipse ide 3.1M5a Reporter: mike andrews Assigned to: Marshall Culpepper got a null pointer exception during refactoring. was not using any functionality of jboss plugin. see original eclipse bug report, which was redirected to jboss: https://bugs.eclipse.org/bugs/show_bug.cgi?id=89201 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Nukes with MS-SQL
Hello, i think you have to change "LENGTH" by "LEN" in ejb files. (\org\jboss\nukes\core\ejb). The EJBs create sql requests using the descriptions you can find in "comments". i know that there is a sql request using "LENGTH" in FileEJB.java file but i don't know if it is the only file that contain it. Regards, Emmanuel Lorge View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871758#3871758 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871758 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: fetchmail
Mike, the code first was that way, assuming that local aliases would direct the mail to the correct local or remote receipients. That was discussed in the "Injection is evil" thread. I could add yet another switch to get this behaviour. But then the user needs to set up more and at other places as well - a potential source of confusion. Heiko View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871745#3871745 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871745 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: CacheLoader.exists(Fqn) being repeatedly called with the
You are right: I'll fix this in CVS and it'll be ready in the next release (1.2.2). Thanks for this useful bug report ! Bela View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871743#3871743 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871743 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
