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: pvishnu <nu...@jb...> - 2005-07-12 09:10:51
|
Hi , I would like to contribute Jboss. Before that i have to run the testsuite and find out how the architecture is... I have downloaded testsuite from the jboss site, but am not sure how i can run the test suite ? Do i need to setup a JBoss Server for that ? If somebody could help that should be very much appreciated. Thanks & Regards, PV View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884485#3884485 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884485 |
From: <ovi...@jb...> - 2005-07-12 07:31:47
|
I fixed the problem that was causing TCK porting layer failures. See http://jira.jboss.org/jira/browse/JBAS-2012. To be able to deploy CTS tests again, do a full head check out, build it and repeat relevant installation steps (from 4.2 on) from http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCKInstallation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884472#3884472 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884472 |
From: vahcic <nu...@jb...> - 2005-07-12 06:34:05
|
Hi, When you are using postgresql, you can show characters? Do you use utf-8 jsp? HOw did you configure postgresql? Thanks, Anton View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884464#3884464 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884464 |
From: <sco...@jb...> - 2005-07-12 05:51:33
|
I guess the common module had not been made clean. After doing that the fFeatures access was ok, but the common module would not build due to a change in the org.apache.xerces.impl.xs.XMLSchemaValidator.fCurrentElemDecl now having private access. I have switched from the xni based to the sax based parser in the UnmarshallerImpl. The xni stuff should just be dropped as its api is too unstable. I'm still testing the jbxb parsing unit tests. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884459#3884459 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884459 |
From: rojaroja <nu...@jb...> - 2005-07-12 05:41:03
|
hi all, i want to find the jboss dependenies. can any one help me? and how to use the Maindeployer class to get the list of deployments View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884458#3884458 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884458 |
From: <sco...@jb...> - 2005-07-12 05:08:32
|
The 2.7.0 version requires a org.apache.xerces.dom.DOMXSImplementationSourceImpl to be installed as the DOMImplementationRegistry.PROPERTY: | import org.w3c.dom.DOMImplementationRegistry; | import org.apache.xerces.xs.XSImplementation; | import org.apache.xerces.xs.XSLoader; | | ... | | // Get DOM Implementation using DOM Registry | System.setProperty(DOMImplementationRegistry.PROPERTY, | "org.apache.xerces.dom.DOMXSImplementationSourceImpl"); | DOMImplementationRegistry registry = DOMImplementationRegistry.newInstance(); | | XSImplementation impl = | (XSImplementation) registry.getDOMImplementation("XS-Loader"); | | XSLoader schemaLoader = impl.createXSLoader(null); | | ... | I made that change, but there is another integration problem seen when the server starts up under jdk5: | 2005-07-11 21:27:36,294 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML | java.lang.NoSuchFieldError: fFeatures | at org.jboss.xb.binding.parser.xni.XniJBossXBParser$ParserConfiguration.configurePipeline(XniJBossXBParser.java:459) | at org.apache.xerces.parsers.DTDConfiguration.reset(Unknown Source) | at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) | at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.xni.XniJBossXBParser.parse(XniJBossXBParser.java:207) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:137) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:309) | As far as I can see the fFeatures field should be accessible based on the javap output of the lib/endoresed/xercesImpl.jar : | [starksm@banshee9100 bin]$ javap -s -classpath ../lib/endorsed/xercesImpl.jar o | rg.apache.xerces.util.ParserConfigurationSettings | public class org.apache.xerces.util.ParserConfigurationSettings extends java.lan | g.Object implements org.apache.xerces.xni.parser.XMLComponentManager{ | protected static final java.lang.String PARSER_SETTINGS; | Signature: Ljava/lang/String; | protected java.util.ArrayList fRecognizedProperties; | Signature: Ljava/util/ArrayList; | protected java.util.HashMap fProperties; | Signature: Ljava/util/HashMap; | protected java.util.ArrayList fRecognizedFeatures; | Signature: Ljava/util/ArrayList; | protected java.util.HashMap fFeatures; | Signature: Ljava/util/HashMap; | ... | This level of integration is certainly problematic. Is this still necessary with 2.7.0? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884457#3884457 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884457 |
From: <ad...@jb...> - 2005-07-12 03:46:32
|
http://jira.jboss.com/jira/browse/JBAS-1796 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884455#3884455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884455 |
From: <sco...@jb...> - 2005-07-12 03:36:42
|
So I'm trying to test the xerces 2.7.0 release and the compile fails because the org.apache.xerces.xs.XSImplementation has changed from org.apache.xerces.dom3.bootstrap.DOMImplementationRegistry to org.apache.xerces.impl.xs.XSImplementationImpl. When is jaxp going to have an xsd api? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884454#3884454 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884454 |
From: <ovi...@jb...> - 2005-07-12 02:18:42
|
Charles, Here are a few thoughts on possible management console features. Please feel free to add to the thread. 1. A desirable management capability would be to able to assign permissions on a per-destination basis. Currently JBossMQ reads security information from the destination's deployment descriptor. In principle, it needs to know what roles have permissions relative to a destination, and what those permissions are. This XML configuration snippet is self describing: | <attribute name="SecurityConf"> | <security> | <role name="guest" read="true" write="true"/> | <role name="publisher" read="true" write="true" create="false"/> | <role name="durpublisher" read="true" write="true" create="true"/> | </security> | </attribute> | However changing these the security attributes from the console raises the issue of being able to write them back to the deployment descriptor or as an XMBean state, so the next reboot won't loose the changes. 2. The authentication and user-to-role mapping is maintained by a JBoss SecurityManager. JBossMQ only maintains the association to a certain security manager, which is given by a the security manager's JNDI name. JBoss Messaging will use the same system: | <mbean code="org.jboss.mq.security.SecurityManager" name="jboss.mq:service=SecurityManager"> | <attribute name="DefaultSecurityConfig"> | <security> | <role name="guest" read="true" write="true" create="true"/> | </security> | </attribute> | <attribute name="SecurityDomain">java:/jaas/jbossmq</attribute> | </mbean> | 3. UIL2, HTTPIL and JVMIL sections are irrelevant. JBoss Messaging delegates to JBoss Remoting, which abstracts out the transport layer. The JBoss Messaging peer can be configured to used the same Remoting Connector the Unified invoker uses, or it can start its own. It would be nice to be able to configure the Connector from the GUI, but here we get into functionality that anyone using remoting needs. You should also speak with TomE about this. 4. Queue and Topic browsing would be an interesting feature to have. 5. JBoss Messaging will use a MemoryCache subsystem that is similar with what JBossMQ has now, but I am still working on details. In general, anything that is related to persistence is in a very fluid phase right now. It will solidify in a matter of weeks. 6. The distributed/replicated destinations rely on a JGroups channel (a JGroups channel per JBoss Messaging peer), so it would be nice to be able to configure this from console. Did you bump in JGroups configuration related issues yet? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884453#3884453 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884453 |
From: <ad...@jb...> - 2005-07-11 21:34:09
|
Yes please. We should remove libraries.xml and replace it uses with libraries.ent And do the same with modules.xml -> modules.ent if you have the time while you are there. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884440#3884440 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884440 |
From: <rl...@jb...> - 2005-07-11 21:25:36
|
The diff yielded excellent results. The structures are the same except for jar files which were constructed by the build, and these differ by only a few bytes (due to time stamps, or version numbers in the manifest files and such). I do have one task left which needs to be resolved. The testsuite build.xml file uses /tools/etc/libraries.xml for its properties definitions while the rest of the modules use libraries.ent. Upon examination the files look to be relatively the same (libraries.xml is slightly out of date). Could we modify the libraries.xml to include the libraries.ent rather than redefining it? This way we would only have to worry about the maintenance of one file. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884439#3884439 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884439 |
From: <aco...@jb...> - 2005-07-11 21:11:10
|
overall I think tis good but i think all exceptions should be runtime exceptions. If you choose to catch it locally, then fine. the state/conversational nature of the protocol doesn't always allow them to be caught at the entry point and I'm unsure that this will make the code cleaner. I think that we have 4 types: 1. Stream killers (so don't bother telling the user) 2. It didn't taste good/stream ok (so tell the user) 3. detached exceptions (couldn't deliever so maybe tell the user by sending him a "couldn't deliver" email preferrably with more detail than we have today!!!) 4. Panics (SQL Exception is a BAD BAD error, tell someone, bad stuff is happening, we've lost the DB, we have deadlocks, fix us!!!) -- we may want to do service unavailable rather than accept messages that won't be delivered. -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884437#3884437 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884437 |
From: <aco...@jb...> - 2005-07-11 20:54:50
|
I'm not yet satisfied with our testing effort or comprehensiveness. Its too painful ATM so something needs to change... So I see different types of testing and we need to fill out to handle them as automatically as possible: 1. Unit testing -- does a particular tiny component or class work. Should be as independent of the appserver/etc as possible. 2. Component testing -- does a service work -- that probably should run in the server. 3. protocol testing -- run in the server but pass in scripts. We have stuff for this but I don't know that we've really completed the toolkit. 4. performance testing/functional testing - actually sending emails and making sure they are properly routed and how many can be routed per second/minute/hour. This is the most difficult to automate. Do I want to start the appserver to test some minor class or feature? Probably not. I'm probably willing to start a subset (which is what the present stuff does) to satisfy dependencies. So do what you think is best but make sure I can just type "ant test" and that they don't take 5 years to run but I may need multiple targets depending on what i'm trying to accomplish. We probably need to change our dir structure a bit for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884435#3884435 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884435 |
From: mikezzz <nu...@jb...> - 2005-07-11 20:45:35
|
Hi, I think we need a consistant approach to exception handling. We have a mix of no exceptions (swallowing and returning false/null), checked and unchecked exceptions. I have been think about this for a while, but today an article cropped up on JavaWorld that sums up my preferred approach. http://www.javaworld.com/javaworld/jw-07-2005/jw-0711-exception.html I think the 3 guidelines specfied at the beginning of the article would work quite well. How should these be applied to JBoss-Mail? All module interfaces should be configured to only throw a MailException (or a sub-class). This would only apply to methods exposed to other modules. Internal to a module any type of exception may be declared. MailExceptions should be thrown in the case of an application error. E.g. User does not exist. A rule of thumb would be that you should throw a MailException in the case of an application check failing e.g. User user = Hibernate.getUser(); // Some system find method | if (user != null) { | return getFolderForUser(user); | } | else { | throw new UserNotFoundException("......"); // extends MailException | } Calling code may attempt handle the exception if appropriate. Folder f; | try { | f = getFolder(); | } | catch (UserNotFoundException e) { | f = createFolderForUser(); | } If the calling decides not to handle the exception it should be allowed to cascade up. try { | f = getFolder(); | } // no catch | finally { | // Do some clean up if necessary. | } There is a danger of this becoming programming by execption which is not good. However the cases where exception are simply allowed to cascade up the stack will outweigh the ones where it is caught and handled, i.e. the exceptional cases (pun intended). If an exception is thrown which can not be handled locally and it is not possible rethrow the same exception then a wrapped MailSystemException (sub-class of RuntimeException) should be thrown. try { | doStuff(); | } | catch (SQLException e) { | throw new MailSystemException("...", e); | } Exceptions should be handled at the entry point into the mail server. This includes the protocol implementations and delivery MDBs. Each entry point will contain a static table that maps internal mail exceptions to error responses appropriate to the particular entry (as defined by POP, IMAP etc.) try { | // do some stuff. | } | catch (MailException e) { | Response r = processException(e); | } | catch (RuntimeException e) { | Response r = processUnknownException(e); | } The motivation for this is there are a number of interfaces that don't throw exceptions on error, which causes problems when introducing AOP transactions that use exceptions to trigger a rollback when required. Also it would be cleaner to have a common approach to handling errors. I am interested in hearing peoples' thoughts on the subject. Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884433#3884433 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884433 |
From: oberon777 <nu...@jb...> - 2005-07-11 20:30:21
|
Is there a simple way to track all method calls on a particular object? For example, suppose I am interested what happens to objects that are returned as the result of Class.forName(..) and I want to record all method calls happening on them. I suppose tracking ALL calls is easy, but how do I make it so that the constraint that the object in question is the return result of Class.forName(..) is part of the pointcut expression. Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884430#3884430 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884430 |
From: oberon777 <nu...@jb...> - 2005-07-11 20:27:11
|
Hmm.. thanks for such a detailed reply. I'll experiment some more to see what was causing this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884429#3884429 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884429 |
From: <rya...@jb...> - 2005-07-11 17:29:44
|
We should run the testsuite, but the easiest way to verify that the distros are exactly the same is just to compare the output of one with the other: diff -br jboss-4.0/build/output/ jboss-4.0.x/build/output View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884412#3884412 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884412 |
From: <sco...@jb...> - 2005-07-11 16:40:59
|
I have created an initial jbxb_1_0.xsd schema under as server/src/resources/schema/jbxb_1_0.xsd and I see that we are out of synch with respect to jaxb. The top level jbxb:schema element mirrors the jaxb:schemaBindings element, and the only schema level binding is the jbxb:package which has the same behavior as the jaxb:package as far as I can see. If we have jaxb analogs, let's use the same names. I am going to change the current jbxb:schema to jbxb:schemaBindings to start with. In the future let's mirror the jaxb names and behavior where possible. Even if we end up extending a jaxb behavior, we should still use the jaxb element and attribute names where possible so that its easy to understand. I don't really want to actually import and extend the jaxb schema into the jbxb schema as I just find the resulting schema harder to read/understand given that I don't read/write schemas on a regular basis. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884402#3884402 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884402 |
From: <ju...@jb...> - 2005-07-10 23:33:56
|
I have refactored how the internal object model. It has not changed much, the big changes are : - a window is not really an entity by itself, it is a concept that symbolize a link from a page to a instance and hold data (the placement on the page) before it was an entity and it was raising an issue which is that when you refer to a window (by its id), you must resolve the page containing it. now when you refer to a window, you only have its ID which is valid in the scope of the page, so if you refer to a window globally, you must give the ID of the page it is + the id of the window in this page. - references between objects are not anymore java reference but strings that give the possiblity to locate the object (in the ContainerRegistry). with that lifecycles of objects are very independant, when you want to get all objects to invoke a portlet, you need to lookup all these objects and be prepared that some objects are not present : for instance you have a page that contains a window refering to an instance, the instance exists but refers to a component which is not deployed (yet), in that case we have to face that situation very properly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884317#3884317 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884317 |
From: <ju...@jb...> - 2005-07-09 22:35:43
|
in jira : http://jira.jboss.com/jira/browse/JBPORTAL View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884276#3884276 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884276 |
From: vahcic <nu...@jb...> - 2005-07-09 20:50:35
|
Btw how can i report problems and errors to jboss portal development team? Thanks, Anton View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884273#3884273 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884273 |
From: vahcic <nu...@jb...> - 2005-07-09 20:46:06
|
Hi, Can somebody tell me how i convince jsp page under jboss portal to correctly show the unicode characters? I have used pageEncoding="UTF-8" in jsp. It's like when going thru jboss portal engine - everything is converted to ascii?! Watching the source code in browser there is no sign of unicode. I am using mysql (default encoding is utf-8). Any idea - what should be done? Thanks. Anton View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884272#3884272 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884272 |
From: mikezzz <nu...@jb...> - 2005-07-09 19:36:01
|
Go for it! Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884271#3884271 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884271 |
From: jeff87 <nu...@jb...> - 2005-07-09 18:58:43
|
Great! Thanks Mike and Andy for all your help. What should I look at next? Perhaps the build file to see why I can't run with dev-deploy but yet I can with the deploy task? Thanks, Jeff View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884270#3884270 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884270 |
From: mikezzz <nu...@jb...> - 2005-07-09 16:14:57
|
Is committed. Thank you! Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884268#3884268 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884268 |