You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: timfox <nu...@jb...> - 2005-05-25 14:33:18
|
Currently, when a JMS Transacted session is committed, any messages sent in the tx are sent to the client's server peer where the handle() method is called on the Destination (Queue or Topic) to which the message was intended. Handle() is called once for each message in the tx that needs to be sent. If failure of the server peer occurs before all the messages are handled() and positively acknowledged then it may be the case that only some of the messages in the tx end up being sent. It seems to me that this breaks the atomicity of the transaction. One solution for this would be to make sure that all the messages for the tx are persisted in a reliable store *before* delivery is attempted for any of them. Currently, synchronous delivery is attempted before persisting the messages. We could introduce a new method boolean handle(Routable[] routables) which makes sure that *all* or *none* of the messages are persisted (and thus positively acknowledged). I'm not sure whether this should go on Receiver, or Channel (??) Under the bonnet (hood) this could be implemented by making message store and acknowledgement store transactional, which is required anyway IMHO for the analogous problem of transactional acknowledgements. -Tim View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879040#3879040 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879040 |
From: <ad...@jb...> - 2005-05-25 13:32:23
|
So the next step would be to have a SchemaBindingResolver that looks at a JBossXB annotation inside the schema for a SchemaBindingFactory and then uses that SchemaBinding to create the object. The schema being loaded through an entity resolver. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879034#3879034 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879034 |
From: <sco...@jb...> - 2005-05-25 10:46:01
|
It does not exist in cvs yet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879021#3879021 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879021 |
From: <sco...@jb...> - 2005-05-25 10:44:59
|
To date the release process has been a simple copying of the ill defined module aspects into the release distribution structure. In working on an installer that allows for selection of specific services + customization of said services. The current build artifacts have several problems for this type of install: 1. The current jars and descriptors are too monolithic. For the jars this means uneccessary size and dependencies. For the descriptors this means service configurations are combined that disallow finer grained installations. 2. The conf/jboss-service.xml has a number of services that significantly increase the minimal footprint. Either this needs to be stripped down to a minimal view (just the hot deployment service), or services that are candidates for static configuration would need a mbean descriptor artifact fragment to allow for inclusion into the conf/jboss-service.xml as part of the install. 3. Some optional services need to be registered before others. The binding service and jsr77 service both operation as listeners of mbean registration events and need to be registered before any services that they should intercept. This is not a functional dependency that can be addressed with a depends tag. These services should really be custom interceptors on the SARDeployer. 4. Customization of the selected services is not a notion that exists in the current release build process. Post installation steps like configuring scoped classloading, call by value invocations, security, a custom datasource, enabling SSL, etc. are all configuration steps that would require the component artifacts to identify the configuration elements that should be transformed along with the variables availble. Something like velocity templatized descriptors along with supported varaibles would need to be declared. None of this is specific to a gui based installer. The existing testsuite makes use of custom installs of the server based on hard-coded transformations of an existing configuration with overrides of selected service descriptors/config files based on the testsuite/src/resources/test-configs contents. This should be viewed as an installation of selected components with customization of the components. The issue for the new build is how to support fine grained installation and configuration of a selection of components from both ant driven and gui based installers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879020#3879020 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879020 |
From: <ale...@jb...> - 2005-05-25 10:34:46
|
Have a look at org.jboss.test.xml.AnyUnitTestCase.java. This is the first approach to anyType. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879019#3879019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879019 |
From: prasadgudipati <nu...@jb...> - 2005-05-25 04:02:32
|
Guys, Can the latest jobss be integrated with latest tomcat? i.e jboss 4.0.2 with tomcat 5.5.9? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878998#3878998 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878998 |
From: prasadgudipati <nu...@jb...> - 2005-05-25 03:59:44
|
Hi guys, What is the jboss and tomcat combination available in the market now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878997#3878997 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878997 |
From: aows <nu...@jb...> - 2005-05-25 02:52:06
|
where could i find the source for your installer module? (not the izpack sources, but the xml and scripts you used to create it and that perform any installation actions)... Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878993#3878993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878993 |
From: <sco...@jb...> - 2005-05-25 01:22:31
|
I'm not sure the release process can be defined in much detail as there are issues to look into regarding how the installer fits into this. I'll create a seperate thread on issues with creating a 4.0.x installer. The long term release features should not be holding up getting the new build working so that projects can get migrated over to it. The plan seems fine, but I want to see it validated with a minimal prototype build as we have to get the features validated as soon as possible. The approach of migrating a large existing project like jboss-head for each feature change will simply take too long. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878983#3878983 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878983 |
From: <ad...@jb...> - 2005-05-24 23:30:13
|
My preferred solution is to try to define upfront what we want it do (I'm not sure what this is anymore ;-) I think Scott wants to prototype so he is confident it is correctly managing thirdparty/versioning. But I'm in favour of anything that speeds up the ditching of buildmagic and enables us to get useful information out of the build so we can more easily manage the process! We don't have any information at the moment other than reading the build scripts or refering to the manually maintained xml files in thirdparty. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878981#3878981 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878981 |
From: chlabreu <nu...@jb...> - 2005-05-24 23:04:58
|
O don=C2=B4t know why, but it happens to me when I name a field begining wi= th "_" character in the interceptor class to prevent recursive behaviour (= interceptor trying to intercept its own fields)=20 -- minduim View the original post : http://www.jboss.org/index.html?module=3Dbb&op=3Dv= iewtopic&p=3D3878979#3878979 Reply to the post : http://www.jboss.org/index.html?module=3Dbb&op=3Dpostin= g&mode=3Dreply&p=3D3878979 |
From: <rya...@jb...> - 2005-05-24 22:42:26
|
Ok, I would like to propose the following plan: 1. Get agreement on the following use cases (by mid next week): - versioning/materialize - top-level build structure - release process/markup 2. Create a partial build of jbossas which implements the above use cases - in jbossas/jbossbuild.xml on HEAD. - have a task breakdown/roadmap complete by end of next week - each task tied to an approved use case Objections/approval/acquiescence? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878976#3878976 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878976 |
From: <ad...@jb...> - 2005-05-24 22:21:22
|
I'd only anticapted supporting lifecycle methods with no arguments. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878971#3878971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878971 |
From: <ad...@jb...> - 2005-05-24 22:17:39
|
Ok, so you just want to inject a bean's property rather than the bean value. The only way this could be done with the current metadata model would be to put a dummy factory inbetween that did the getting. But this seems such a trivial usecase that I don't see why it could not be supported directly. In MC XML (note the property attribute is what we are talking about and is not currently supported) | <property name="roles"> | <inject bean="PropertiesSource" property="roles" /> | </property> | Whether we want to go further into xml scripting is another issue, e.g. | <inject bean="PropertiesSource" script="getRoles().toString()" /> | <inject bean="PropertiesSource" script="getRoles().get("Value1"))" /> | // transient property PropertiesSource.getRoles().getSize() | <inject bean="PropertiesSource" property="roles.size" /> | etc. | Including "abitrary" initialize methods could also be supported with something like | <depends> | <create method="initialize"> | <parameter><inject bean="PropertiesSource" property="roles"/></parameter> | </create> | One problem with the latter (besides it fails the 95%/5% use case rule) is that the annotation version requires parameter annotations (although it isn't something you want to do in this case :-) | @CreateLifecycle | public void initialize( | @Inject(bean="PropertiesSource", property="users") | Map users, | @Inject(bean="PropertiesSource", property="roles") | Map roles | ) | { | // Do it | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878970#3878970 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878970 |
From: <ani...@jb...> - 2005-05-24 22:04:42
|
http://jira.jboss.com/jira/browse/JBWS-228 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878969#3878969 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878969 |
From: <ani...@jb...> - 2005-05-24 22:01:12
|
This is a placeholder for discussion on document/literal style web services support in JBossWS Tools. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878968#3878968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878968 |
From: <sco...@jb...> - 2005-05-24 21:51:19
|
By wiring I did not mean that it had to be strictly via configuration level constructs between the two pojos. There actually is a natural point for joining these before having to deal with the initialize() method. The usecase here is a login configuration with a login module that may take its options from a static configuration, or injection of another object's attributes. static: | <application-policy name="testXMLLoginModule"> | <authentication> | <login-module code="SomeLoginModule" flag="required"> | <module-option name="users"> | <lm:users xmlns:lm="urn:jboss:jaas"> | <lm:user name="user1" password="pass1" /> | <lm:user name="user2" password="pass2" /> | </lm:users> | </module-option> | <module-option name="roles"> | <lm:roles xmlns:lm="urn:jboss:jaas"> | <lm:user name="user1"> | <lm:role name="Role1"/> | <lm:role name="Role2"/> | <lm:role name="callerJduke" group="CallerPrincipal" /> | </lm:user> | </lm:users> | </module-option> | ... | injection: | <application-policy name="testXMLLoginModule2"> | <authentication> | <login-module code="SomeLoginModule" flag="required"> | <module-option name="users"> | <depends name="PropertiesSource" property="Users" /> | </module-option> | <module-option name="roles"> | <depends name="PropertiesSource" property="Roles" /> | </module-option> | ... | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878967#3878967 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878967 |
From: <rya...@jb...> - 2005-05-24 21:42:23
|
"ad...@jb..." wrote : The main issue as to whether this applies to the build is whether such a notion can be understood at the ant/repository level. | Perhaps extension points could use the same repository structure as components, but have a different descriptor: /jms/1.1/extension-info.xml: <project> | <extension-point name="jms" version="1.1"> | <implementation default="true" name="jbossmq" version="4.0.2"/> | <implementation name="jbossmq" version="4.0.1"/> | <implementation name="jbossmessaging" version="4.0.2"/> | </extension-point> | </project> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878966#3878966 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878966 |
From: <ad...@jb...> - 2005-05-24 21:20:29
|
"sco...@jb..." wrote : Do we have all the pieces in place for this scenario: | | - A named pojo instance (in its most strict form this could be a singleton) that has two Properties maps attributes | + The pojo has methods to manipulating the Properties contents | + The pojo has these methods exposed via JMX | Yes anonymous wrote : | - Another pojo needs the named pojo instance Properties maps injected to function correctly. This pojo only has a default ctor, and the only point for injecting the Properties maps is this initialize method: | | | | public void initialize(Subject subject, CallbackHandler callbackHandler, | | Map sharedState, Map options) | | | | The Properties should be found in the options argument under the keys "users" and "roles". However, by the time the initialize method is called, the options Map is a read-only object. | | Do we have a framework that can acomplish this wiring yet? | No. Do we really want to support an xml scripting language in the configuration? Complicated/Programmatic config like this can be handled by "lifecycle advices". I'd guess in this case it would be "create"? But it could also be construction or any other joinpoint. i.e. advice depends upon properties (or named pojo) "another" depends upon advice View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878965#3878965 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878965 |
From: nmuralid <nu...@jb...> - 2005-05-24 21:16:47
|
I'm refering to 8.4.5 of "JBoss 4 ApplicationServer guide". This states that the "LoginConfig" of the SecurityConfig MBean is used for default JAAS login configuration. I'd like to substitute this default configuration - should I necessarily write an MBean? I'm not able to get it to default to Sun's JAAS provider though the documentation mentions that it does. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878963#3878963 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878963 |
From: <roy...@jb...> - 2005-05-24 21:06:04
|
I will have to check... We do support multiple instances of the same portlet on one page. However, I'm not sure if this applies to JSF. I have enountered problems trying to get the MyFaces sample portlet to work with JBossAS4.0.2, but Stan will be looking in to it. I will have more answers when my time frees up after tomorrow's webinar. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878961#3878961 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878961 |
From: <sco...@jb...> - 2005-05-24 21:04:10
|
Do we have all the pieces in place for this scenario: - A named pojo instance (in its most strict form this could be a singleton) that has two Properties maps attributes + The pojo has methods to manipulating the Properties contents + The pojo has these methods exposed via JMX - Another pojo needs the named pojo instance Properties maps injected to function correctly. This pojo only has a default ctor, and the only point for injecting the Properties maps is this initialize method: | public void initialize(Subject subject, CallbackHandler callbackHandler, | Map sharedState, Map options) | The Properties should be found in the options argument under the keys "users" and "roles". However, by the time the initialize method is called, the options Map is a read-only object. Do we have a framework that can acomplish this wiring yet? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878960#3878960 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878960 |
From: pomatto <nu...@jb...> - 2005-05-24 20:29:17
|
I'm developing a web app with JSF. I have some javascript files that I would like to have access control on. I have inserted the following code into the web.xml file: <security-constraint> <display-name>Restrict access to js pages</display-name> <web-resource-collection> <web-resource-name> Restrict access to js pages </web-resource-name> <url-pattern>*.js</url-pattern> </web-resource-collection> <auth-constraint> role names <role-name>xyzUser</role-name> </auth-constraint> </security-constraint> I'm using JBuilder2005 as an IDE and when I go to deploy to JBoss app server I get the following error: "kb": Restrict access to js pages - Authorization Constraint: There is no security role with the name "xyzUser". kb being my war file. Where is it checking for the role name? I have used role names in my database under my roles table, I get the same error. Any input would be appreciated. P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878957#3878957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878957 |
From: echoi1975 <nu...@jb...> - 2005-05-24 20:29:02
|
Hi, I'm having non-reactive behavior to my action and actionListeners on my jsf portlet when I add another jsf portlet to the page? is jboss portal setup to handle multiple jsfs on one portal? only workaround i can come up w/ to address this is to have only one jsf and to have additonal portlets written in servlets/jsps... thx in advance.. ec. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878956#3878956 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878956 |
From: <ad...@jb...> - 2005-05-24 16:56:08
|
There is a new module in jboss-head called "dependency" it relates to this work: http://jira.jboss.com/jira/browse/JBMICROCONT-37 Nothing uses it at the moment, but soon both the microcontainer and system will. So this shouldn't cause you problems immediately. To retrieve the new module without doing a full checkout cd jboss-head cvs co -d dependency jboss-dependency View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878939#3878939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878939 |