[JBoss-dev] feedback welcomed (Class Versioning and Loading)

[Andrew Oliver]

What do you guys think of this: 
http://linuxintegrators.com/acoliver/code/2006/05/02/x-242.html


-andy



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] the JBAS gui installer is messed up on FC5

[Andrew Oliver]

If you install Fedora Core 5 on your laptop and install JBAS404RC2 from 
the gui installer... things go off the screen and the screen isn't 
resizable.  I qualify this is bad.  There does not appear to be a 
forum for the installer (adrian) or if there is then it needs a better 
more CTRL-Fable name.  I'll log a bug for this too.


thanks,

-andy



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment/scanner ...

[Andrew Oliver]

*gives adrian a big hug and kiss*

:-*

Next thing you'll be wanting me to try compiling things first before I 
check them in...  sheesh.



Adrian Brock wrote:

Congratulations on:

1) Not discussing this change before implementing it.
2) Raising a JIRA task to document it.
3) Porting it to jboss-head so it doesn't get lost

On Sun, 2006-04-16 at 20:29 -0400, Andy Oliver wrote:

  User: acoliver
  Date: 06/04/16 20:29:00

  Modified:src/main/org/jboss/deployment/scanner   Tag: Branch_4_0
URLDeploymentScanner.java
URLDeploymentScannerMBean.java
  Log:
  Add abillity to ignore a file while it is being updated and then re-attend to it 
  once it is updated (assuming that some other service will attend to bringing the 
  runtime in sync without re-deployment)
  
  Revision  ChangesPath

  No   revision
  
  
  No   revision
  
  
  1.32.2.6  +81 -11jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: URLDeploymentScanner.java

  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java,v
  retrieving revision 1.32.2.5
  retrieving revision 1.32.2.6
  diff -u -b -r1.32.2.5 -r1.32.2.6
  --- URLDeploymentScanner.java 29 Oct 2005 05:06:09 -  1.32.2.5
  +++ URLDeploymentScanner.java 17 Apr 2006 00:29:00 -  1.32.2.6
  @@ -56,12 +56,14 @@
*
* @jmx:mbean extends=org.jboss.deployment.scanner.DeploymentScannerMBean
*
  - * @version tt$Revision: 1.32.2.5 $/tt
  + * @version tt$Revision: 1.32.2.6 $/tt
* @author  a href=mailto:[EMAIL PROTECTED]Jason Dillon/a
*/
   public class URLDeploymentScanner extends AbstractDeploymentScanner
  implements DeploymentScanner, URLDeploymentScannerMBean
   {
  +   /** The list of URLs to skip **/
  +   protected List skipList = Collections.synchronizedList(new ArrayList());
  /** The list of URLs to scan. */
  protected List urlList = Collections.synchronizedList(new ArrayList());
   
  @@ -251,6 +253,66 @@

 return urlList.contains(url);
  }
   
  +   /**
  +* You can ask the deployment scanner NOT to update a URL that you are 
  +* about to change.  This must be the same as the actual deployment URL and

  +* not the minor watchURL (deployment descriptor).  This operation ADDs a
  +* url to the list of not urls.  The actual time/datestamp of the 
deployed
  +* url will be modified to reflect the timestamp as if the url were 
actually
  +* deployed the first time scan is called either programmatically as an 
  +* mbean operation call or during normal temporal operations.  Note that this

  +* only affects UPDATES (redeploy) not undeploy or deploy(obviously).
  +*
  +* @jmx:managed-operation
  +*/
  +   public void addNotURL(final URL url) 
  +   {  //ACO wuz here

  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (!skipList.contains(url)) 
  +  {

  + skipList.add(url);
  +  } 
  +   }

  +
  +   /**
  +* removes a url from the list of urls NOT to update.  Make sure that you
  +* call scan before removing urls or if the scan window is wide enough the 
  +* timestamp may not get updated.  (the scan window IS wide enough by default)

  +*
  +* @jmx:managed-operation
  +*/
  +   public void removeNotURL(final URL url) 
  +   {  //ACO wuz here

  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (skipList.contains(url)) 
  +  {

  + skipList.remove(url);
  +  }
  +   }
  +
  +   /**
  +* list all deployed urls for this deployment scanner instance in a big comma 
  +* and carriage return seperated list

  +*
  +* @jmx:managed-operation
  +*/
  +   public String listDeployed() {
  +  String retval = ;
  +  Iterator i = deployedSet.iterator();
  +  while (i.hasNext()) {
  +  String url = i.next().toString();
  +  if (!retval.equals()) {
  +  retval += ,\n+url;
  +  } 
  +  else 
  +  {

  +  retval += url;
  +  }
  +  }
  +  return retval;
  +   }
   
  /

  //  Management/Configuration Helpers   //
  @@ -331,8 +393,15 @@
 }
 try
 {
  + if(!skipList.contains(du.url)) 
  + {

deployer.deploy(du.url);
 }
  + else 
  + {

  + du.deployed();
  + }
  +  }
 catch (IncompleteDeploymentException e)
 {
lastIncompleteDeploymentException = e;
  @@ -361,7 +430,10 @@
{
   log.trace(Undeploying: 

[JBoss-dev] Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment/scanner ...

[Andrew Oliver]

BTW Adrian,

parody
I did in fact discuss it and no one said much in reply.  Perhaps if 
you'd read the forum posts more closely, I would not have to repeat 
myself here.

/parody

So if it is needed for 5.0 I'll port it there.  I think it might be 
useful for that profile service thingy.  If not, then I won't.


peace,

Andy

Andrew Oliver wrote:

*gives adrian a big hug and kiss*

:-*

Next thing you'll be wanting me to try compiling things first before I 
check them in...  sheesh.



Adrian Brock wrote:

Congratulations on:

1) Not discussing this change before implementing it.
2) Raising a JIRA task to document it.
3) Porting it to jboss-head so it doesn't get lost

On Sun, 2006-04-16 at 20:29 -0400, Andy Oliver wrote:

  User: acoliver
  Date: 06/04/16 20:29:00

  Modified:src/main/org/jboss/deployment/scanner   Tag: Branch_4_0
URLDeploymentScanner.java
URLDeploymentScannerMBean.java
  Log:
  Add abillity to ignore a file while it is being updated and then 
re-attend to it   once it is updated (assuming that some other 
service will attend to bringing the   runtime in sync without 
re-deployment)

Revision  ChangesPath
  No   revision
  No   revision
  1.32.2.6  +81 -11
jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java 

(In the diff below, changes in quantity of whitespace are not 
shown.)

Index: URLDeploymentScanner.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java,v 


  retrieving revision 1.32.2.5
  retrieving revision 1.32.2.6
  diff -u -b -r1.32.2.5 -r1.32.2.6
  --- URLDeploymentScanner.java29 Oct 2005 05:06:09 -
1.32.2.5
  +++ URLDeploymentScanner.java17 Apr 2006 00:29:00 -
1.32.2.6

  @@ -56,12 +56,14 @@
*
* @jmx:mbean 
extends=org.jboss.deployment.scanner.DeploymentScannerMBean

*
  - * @version tt$Revision: 1.32.2.5 $/tt
  + * @version tt$Revision: 1.32.2.6 $/tt
* @author  a href=mailto:[EMAIL PROTECTED]Jason Dillon/a
*/
   public class URLDeploymentScanner extends AbstractDeploymentScanner
  implements DeploymentScanner, URLDeploymentScannerMBean
   {
  +   /** The list of URLs to skip **/
  +   protected List skipList = Collections.synchronizedList(new 
ArrayList());

  /** The list of URLs to scan. */
  protected List urlList = Collections.synchronizedList(new 
ArrayList());

 @@ -251,6 +253,66 @@
 return urlList.contains(url);
  }
 +   /**
  +* You can ask the deployment scanner NOT to update a URL that 
you are   +* about to change.  This must be the same as the 
actual deployment URL and
  +* not the minor watchURL (deployment descriptor).  This 
operation ADDs a
  +* url to the list of not urls.  The actual time/datestamp of 
the deployed
  +* url will be modified to reflect the timestamp as if the url 
were actually
  +* deployed the first time scan is called either 
programmatically as an   +* mbean operation call or during normal 
temporal operations.  Note that this
  +* only affects UPDATES (redeploy) not undeploy or 
deploy(obviously).

  +*
  +* @jmx:managed-operation
  +*/
  +   public void addNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (!skipList.contains(url))   +  {
  + skipList.add(url);
  +  }   +   }
  +
  +   /**
  +* removes a url from the list of urls NOT to update.  Make 
sure that you
  +* call scan before removing urls or if the scan window is wide 
enough the   +* timestamp may not get updated.  (the scan window 
IS wide enough by default)

  +*
  +* @jmx:managed-operation
  +*/
  +   public void removeNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (skipList.contains(url))   +  {
  + skipList.remove(url);
  +  }
  +   }
  +
  +   /**
  +* list all deployed urls for this deployment scanner instance 
in a big comma   +* and carriage return seperated list

  +*
  +* @jmx:managed-operation
  +*/
  +   public String listDeployed() {
  +  String retval = ;
  +  Iterator i = deployedSet.iterator();
  +  while (i.hasNext()) {
  +  String url = i.next().toString();
  +  if (!retval.equals()) {
  +  retval += ,\n+url;
  +  }   +  else   +  {
  +  retval += url;
  +  }
  +  }
  +  return retval;
  +   }
 
/ 

  //  Management/Configuration 
Helpers   //

  @@ -331,8 +393,15 @@
 }
 try

Re: [JBoss-dev] Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment/scanner ...

[Andrew Oliver]

Oh cool.  Can you repost those threads here?  I must have missed them.

Adrian Brock wrote:

And you were ignored because there must be at least 100
previous threads where it was already discussed.

Including me telling describing how to do it to somebody
who never contributed it back.

On Mon, 2006-04-17 at 10:44 -0400, Andrew Oliver wrote:

BTW Adrian,

parody
I did in fact discuss it and no one said much in reply.  Perhaps if 
you'd read the forum posts more closely, I would not have to repeat 
myself here.

/parody

So if it is needed for 5.0 I'll port it there.  I think it might be 
useful for that profile service thingy.  If not, then I won't.


peace,

Andy

Andrew Oliver wrote:

*gives adrian a big hug and kiss*

:-*

Next thing you'll be wanting me to try compiling things first before I 
check them in...  sheesh.



Adrian Brock wrote:

Congratulations on:

1) Not discussing this change before implementing it.
2) Raising a JIRA task to document it.
3) Porting it to jboss-head so it doesn't get lost

On Sun, 2006-04-16 at 20:29 -0400, Andy Oliver wrote:

  User: acoliver
  Date: 06/04/16 20:29:00

  Modified:src/main/org/jboss/deployment/scanner   Tag: Branch_4_0
URLDeploymentScanner.java
URLDeploymentScannerMBean.java
  Log:
  Add abillity to ignore a file while it is being updated and then 
re-attend to it   once it is updated (assuming that some other 
service will attend to bringing the   runtime in sync without 
re-deployment)

Revision  ChangesPath
  No   revision
  No   revision
  1.32.2.6  +81 -11
jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java 

(In the diff below, changes in quantity of whitespace are not 
shown.)

Index: URLDeploymentScanner.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java,v 


  retrieving revision 1.32.2.5
  retrieving revision 1.32.2.6
  diff -u -b -r1.32.2.5 -r1.32.2.6
  --- URLDeploymentScanner.java29 Oct 2005 05:06:09 -
1.32.2.5
  +++ URLDeploymentScanner.java17 Apr 2006 00:29:00 -
1.32.2.6

  @@ -56,12 +56,14 @@
*
* @jmx:mbean 
extends=org.jboss.deployment.scanner.DeploymentScannerMBean

*
  - * @version tt$Revision: 1.32.2.5 $/tt
  + * @version tt$Revision: 1.32.2.6 $/tt
* @author  a href=mailto:[EMAIL PROTECTED]Jason Dillon/a
*/
   public class URLDeploymentScanner extends AbstractDeploymentScanner
  implements DeploymentScanner, URLDeploymentScannerMBean
   {
  +   /** The list of URLs to skip **/
  +   protected List skipList = Collections.synchronizedList(new 
ArrayList());

  /** The list of URLs to scan. */
  protected List urlList = Collections.synchronizedList(new 
ArrayList());

 @@ -251,6 +253,66 @@
 return urlList.contains(url);
  }
 +   /**
  +* You can ask the deployment scanner NOT to update a URL that 
you are   +* about to change.  This must be the same as the 
actual deployment URL and
  +* not the minor watchURL (deployment descriptor).  This 
operation ADDs a
  +* url to the list of not urls.  The actual time/datestamp of 
the deployed
  +* url will be modified to reflect the timestamp as if the url 
were actually
  +* deployed the first time scan is called either 
programmatically as an   +* mbean operation call or during normal 
temporal operations.  Note that this
  +* only affects UPDATES (redeploy) not undeploy or 
deploy(obviously).

  +*
  +* @jmx:managed-operation
  +*/
  +   public void addNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (!skipList.contains(url))   +  {
  + skipList.add(url);
  +  }   +   }
  +
  +   /**
  +* removes a url from the list of urls NOT to update.  Make 
sure that you
  +* call scan before removing urls or if the scan window is wide 
enough the   +* timestamp may not get updated.  (the scan window 
IS wide enough by default)

  +*
  +* @jmx:managed-operation
  +*/
  +   public void removeNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (skipList.contains(url))   +  {
  + skipList.remove(url);
  +  }
  +   }
  +
  +   /**
  +* list all deployed urls for this deployment scanner instance 
in a big comma   +* and carriage return seperated list

  +*
  +* @jmx:managed-operation
  +*/
  +   public String listDeployed() {
  +  String retval = ;
  +  Iterator i = deployedSet.iterator();
  +  while (i.hasNext()) {
  +  String url = i.next().toString();
  +  if (!retval.equals()) {
  +  retval += ,\n+url;
  +  }   +  else

Re: [JBoss-dev] Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment/scanner ...

[Andrew Oliver]

yucky.

Adrian Brock wrote:

It is redundant.

You could always do this by naming your file
something the URLDeploymentScanner ignored then
renaming it.

Rename is an atomic operation on any filesystem.

On Mon, 2006-04-17 at 10:44 -0400, Andrew Oliver wrote:

BTW Adrian,

parody
I did in fact discuss it and no one said much in reply.  Perhaps if 
you'd read the forum posts more closely, I would not have to repeat 
myself here.

/parody

So if it is needed for 5.0 I'll port it there.  I think it might be 
useful for that profile service thingy.  If not, then I won't.


peace,

Andy

Andrew Oliver wrote:

*gives adrian a big hug and kiss*

:-*

Next thing you'll be wanting me to try compiling things first before I 
check them in...  sheesh.



Adrian Brock wrote:

Congratulations on:

1) Not discussing this change before implementing it.
2) Raising a JIRA task to document it.
3) Porting it to jboss-head so it doesn't get lost

On Sun, 2006-04-16 at 20:29 -0400, Andy Oliver wrote:

  User: acoliver
  Date: 06/04/16 20:29:00

  Modified:src/main/org/jboss/deployment/scanner   Tag: Branch_4_0
URLDeploymentScanner.java
URLDeploymentScannerMBean.java
  Log:
  Add abillity to ignore a file while it is being updated and then 
re-attend to it   once it is updated (assuming that some other 
service will attend to bringing the   runtime in sync without 
re-deployment)

Revision  ChangesPath
  No   revision
  No   revision
  1.32.2.6  +81 -11
jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java 

(In the diff below, changes in quantity of whitespace are not 
shown.)

Index: URLDeploymentScanner.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java,v 


  retrieving revision 1.32.2.5
  retrieving revision 1.32.2.6
  diff -u -b -r1.32.2.5 -r1.32.2.6
  --- URLDeploymentScanner.java29 Oct 2005 05:06:09 -
1.32.2.5
  +++ URLDeploymentScanner.java17 Apr 2006 00:29:00 -
1.32.2.6

  @@ -56,12 +56,14 @@
*
* @jmx:mbean 
extends=org.jboss.deployment.scanner.DeploymentScannerMBean

*
  - * @version tt$Revision: 1.32.2.5 $/tt
  + * @version tt$Revision: 1.32.2.6 $/tt
* @author  a href=mailto:[EMAIL PROTECTED]Jason Dillon/a
*/
   public class URLDeploymentScanner extends AbstractDeploymentScanner
  implements DeploymentScanner, URLDeploymentScannerMBean
   {
  +   /** The list of URLs to skip **/
  +   protected List skipList = Collections.synchronizedList(new 
ArrayList());

  /** The list of URLs to scan. */
  protected List urlList = Collections.synchronizedList(new 
ArrayList());

 @@ -251,6 +253,66 @@
 return urlList.contains(url);
  }
 +   /**
  +* You can ask the deployment scanner NOT to update a URL that 
you are   +* about to change.  This must be the same as the 
actual deployment URL and
  +* not the minor watchURL (deployment descriptor).  This 
operation ADDs a
  +* url to the list of not urls.  The actual time/datestamp of 
the deployed
  +* url will be modified to reflect the timestamp as if the url 
were actually
  +* deployed the first time scan is called either 
programmatically as an   +* mbean operation call or during normal 
temporal operations.  Note that this
  +* only affects UPDATES (redeploy) not undeploy or 
deploy(obviously).

  +*
  +* @jmx:managed-operation
  +*/
  +   public void addNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (!skipList.contains(url))   +  {
  + skipList.add(url);
  +  }   +   }
  +
  +   /**
  +* removes a url from the list of urls NOT to update.  Make 
sure that you
  +* call scan before removing urls or if the scan window is wide 
enough the   +* timestamp may not get updated.  (the scan window 
IS wide enough by default)

  +*
  +* @jmx:managed-operation
  +*/
  +   public void removeNotURL(final URL url)   +   {  //ACO wuz here
  +  if (url == null)
  + throw new NullArgumentException(url);
  +  if (skipList.contains(url))   +  {
  + skipList.remove(url);
  +  }
  +   }
  +
  +   /**
  +* list all deployed urls for this deployment scanner instance 
in a big comma   +* and carriage return seperated list

  +*
  +* @jmx:managed-operation
  +*/
  +   public String listDeployed() {
  +  String retval = ;
  +  Iterator i = deployedSet.iterator();
  +  while (i.hasNext()) {
  +  String url = i.next().toString();
  +  if (!retval.equals()) {
  +  retval += ,\n+url;
  +  }   +  else   +  {
  +  retval += url;
  +  }
  +  }
  +  return retval

Re: [JBoss-dev] Unassigned for 4.0.4

[Andrew Oliver]

Can I ask a dumb question:

Why?

-Andy

Max Rydahl Andersen wrote:


 Sounds good to me.  My next question is how do we tell Hibernate to 
use

 JBoss Cache as the first level cache?

*first* level cache ? Why would you ever want that ?

You mean second level cache, right ?
I mean first level cache, which by default is using ehcache-1.1.jar 
(jira JBAS-2868).  We don't include ehcache-1.1.jar with the 4.0.4 as


Again - Hibernate does not support pluggable first level cache; only the
second level cache is pluggable. and yes ehcache is the default *second* 
level

cache as currently that is the best available default singleprocess cache.

Mannik is the one who has the details about the current state of having
JBossCache work as an efficient single process cache with hibernate.


/max





---
This SF.Net email is sponsored by xPML, a groundbreaking scripting 
language
that extends applications into web and mobile media. Attend the live 
webcast
and join the prime developer group breaking into this new coding 
territory!

http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development





Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live 
webcast

and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development






---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Add dgc flags to defualt run.conf

[Andrew Oliver]

Does anyone mind if I add:

-Dsun.rmi.dgc.client.gcInterval=360
-Dsun.rmi.dgc.server.gcInterval=360

to the run.conf?

Problem:

By default, since JBoss links to RMI -- the RMI subsystem forces a full 
GC every 60 seconds.  This very negatively affecter performance.


Benefits:

* Will make JBoss perform better in customer benchmarks (instead of them 
having full GC every 60 seconds).
* Will NOT cause any VM specific problems (where -X:+DisableExplicitGC 
may). (they'll just ignore it)


Downside:

* anyone who wants the default DGC behavior will need to re-enable it

Mitigating:

* Anyone who wants the default DGC behvior probably knows they want it.
* I can put an echo at the top of each script if desirable

-Andy



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] About that rumor...

[Andrew Oliver]

That 'vi' kicks your puny yet bloated IDE's ass...this page has the 
testimony:


http://labs.jboss.com/portal/community/bestide?noproject=true

Do not argue it on here or the core, we need to capture the testimony 
with proper version tracking and tool integration and full featured HTML 
rather than wiki markup that doesn't have lots of pretty-foo.  There are 
instructions on how to modify the page on the page itself!


You can also send patches. (learn how 
http://labs.jboss.com/portal/index.html?ctrl:id=window.default.WikiPortletWindowctrl:type=actionpage=HowToContribute) 
and I will apply them.


At the moment there is a tie between Eclipse and vi but I'm sure its 
momentary.


-Andy



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] So does svn really work in the ides?

[Andrew Oliver]

The command line works okay (even on the mac after the 3 day 
installation procedure) except when it doesn't with weird opaque 
messages about locks that make even less sense than the CVS ones.  At 
least SVN is slower than CVS (or at least ours vs ours).  I was getting 
too unfrustrated when we moved off of sf and our checkouts started 
whizzing by the screen.  I think I even filed a jira bug at one point 
files scroll to fast for me to see what I'm checking out.


The good news is that with SVN and Maven2 we will be WAY cooler than we 
are now.  The bad news is that we must do things the Maven and SVN way 
and if we do not we will be badly punished.  However, pain is a 
necessary part of art and I applaud both these efforts for their 
necessity (as opposed to say making a kickass management console, the 
installer do more stuff) and focus as well as really helping move 
forward our pain^M^M^M^Mart.


-andy (who mostly uses command line cvs anyhow)

Scott M Stark wrote:

So I tried using this tomcat svn repo in both eclipse using the
http://subclipse.tigris.org/ plugin and in intellij 5.1.
 
http://svn.apache.org/repos/asf/tomcat/current/tc5.5.x
 
I found a line referring to the people wearing tin hats in one of the

tomcat files and wanted to see who the commedian was, but the annotate
command in intellij did nothing. The history view just showed a huge
list of number that could not be arranged into any type of structure and
I got tired of browsing through the comments to find the change.

Using eclipse I could not even checkout the tc5.5.x project using the
Import-Checkout from SVN command. When it got to the Select the folder
to be checked out from SVN dialog, it was just blank. So far I'm
underwhelmed with the svn tool support.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development






---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff

[Andrew Oliver]

gosh wouldn't it make more sense to do all of this for 5.0 where there 
is a free hand rather than 4.0?


Do we have feasibility targets (i.e. the build cannot suddenly take 5 
hours on a IA64 with 8 gb of ram) for this?


-andy (who finds maven and all things like it to be really frustrating)

Damon Sicore wrote:

Adding them now... ;-)

On Feb 11, 2006, at 2:38 PM, Scott M Stark wrote:


That would be a way to actually start with a 4.0 branch fork which  might
be more manageable due to fewer changes to merge between the cvs  and svn
repositories.

Can we get the jboss-4.0.x and jboss-head contents moved into svn  Damon?

-Original Message-
From: Adrian Brock
Sent: Saturday, February 11, 2006 3:48 AM
To: Scott M Stark
Cc: jboss-development@lists.sourceforge.net; QA
Subject: RE: Ongoing build changes: was RE: [JBoss-dev]
OntheedgeoftheMavencliff

On Sat, 2006-02-11 at 04:33, Adrian Brock wrote:


On Fri, 2006-02-10 at 13:28, Scott M Stark wrote:


Let's do that. Do you want to couple this to maven? It would help


Ruel I


suppose.



We may as well go Big Bang!. :-)



Speaking of Big Bang. It might be idea to convert to subversion at the
same time.
Given we want to refactor the project structures to native Maven
we could:

1) Import CVS into SVN
2) Use SVN rename to rework the project structure
3) Keep the history attached to those files!

http://weblogs.java.net/blog/joshy/archive/2005/03/ subversion_rena.html
--

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through  
log files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD  SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
files

for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development






---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] BasicThreadPool and Thread.stop()

[Andrew Oliver]

Its kind of sad there is no solution to this after all of this time. 
Gosh Java sucks... ;-)  I'm sure it all works perfectly in NuFuBarX 
lang...we must migrate JBoss immediately.


Adrian Brock wrote:

On Sat, 2006-02-04 at 17:44, Scott M Stark wrote:


It was the only way I found to implement a timeout behavior that had a
chance of working when there were uncooperative tasks. See the
org.jboss.test.util.test.
ThreadPoolTaskUnitTestCase.testCompleteTimeoutWithSpinLoop as an
example.



There is no real solution to that problem in java.
CPU loops don't respond to thread interrupts.

You can't even redefineClass() to add a 
Thread.interrupted()

check in the misbehaving method, because it won't take affect on that
invocation.

Stopping the thread will avoid the cpu utilization problem,
but your JVM is now in an unknown/unstable state.

Connection c = dataSource.getConnection();
try
{
   synchronized (lock)
   {
  spin(); // --- Stop
   }
}
finally
{
   c.close(); // Never done
}

The connection leaks, I don't know what happens to the lock?

A better solution would be to automatically trigger a reboot if you
detect a misbehaving thread.



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Saturday, February 04, 2006 2:33 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] BasicThreadPool and Thread.stop()

I don't think it is a good idea to invoke Thread.stop().
This has memory leak problems.

Why was this introduced? The pooled threads are already daemon threads
so they should not stop the system from exiting at shutdown.

If you are not shutting down the system, then any objects
on the stopped thread's stack are not garbage collected.





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] EJB RC5 PFD, HSQL and AUTO mode keys fail (ADRIAN DO NOT READ)

[Andrew Oliver]

This is JBAS 4.03SP1/last nights EJB3 and HSQL as distributed

If I do this:

@Id @GeneratedValue(strategy=GenerationType.SEQUENCE)
long id;

works with hypersonic

however

@Id @GeneratedValue(strategy=GenerationType.AUTO)
long id;

yields lovelies like this:

[org.hibernate.persister.entity.AbstractEntityPersister]  Identity 
insert: insert into Folder (name, parent_id, defaultInFolder_id, 
defaultOutFolder_id, TYPE, id) values (?, ?, ?, ?, 
'org.jboss.mail.mailbox.Mailbox', null)


And these of course fail with not null allowed (which is how the table 
was generated by hibernate) when they are executed


persistence.xml is:

persistence
  persistence-unit name=mail
  jta-data-sourcejava:/DefaultDS/jta-data-source
  properties
   property name=hibernate.dialect 
value=org.hibernate.dialect.HSQLDialect/

property name=hibernate.hbm2ddl.auto
  value=update/
property name=jboss.entity.manager.jndi.name
  value=java:/EntityManagers/mail/
property name=hibernate.show_sql
  value=true/
  /properties
  /persistence-unit
/persistence


So unless I goofed something up I don't think its the dialect.

Would post in the forum or log as bug but both appear to be inoperative 
at the moment.  Wanted someone to tell me why I'm wrong first.


-Andy



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-42) HTTP Protocol Proxy

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-42?page=comments#action_12316841 ]
 
Andrew Oliver commented on JBMAIL-42:
-

Thanks for that.  It looks very er...interesting.  While we'd still need a 
go-between to make the REST communicate to the rest of the world (oh bad bad 
pun), that looks like it not only solves the issue but goes one up on the 
issue.  

 HTTP Protocol Proxy
 ---

  Key: JBMAIL-42
  URL: http://jira.jboss.com/jira/browse/JBMAIL-42
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP, POP
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical


 Original Estimate: 2 days
 Remaining: 2 days

 Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.
 Example:
 C: GET /SMTP/Connect HTTP/1.1
 C:
 S: HTTP/1.1 200 OK
 S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1
 S:
 S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1) 
 ready March 17, 2005 10:00:36 AM EST
 Connection closed (not necessary for 1.1 but demonstrative)
 C: GET /SMTP/EHLO HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 VXNlcm5hbWU6
 C: GET /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 VXNlcm5hbWU6
 S:
 C: POST /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: {encoded user}
 S:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 UGFzc3dvcmQ6
 S:
 C: POST /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: {encoded pwd}
 S:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S: 
 S: 200 Authorized
 S:
 C: POST /SMTP/MAIL_FROM HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: [EMAIL PROTECTED]
 the intent is the proxy will be implemneted as a servlet and connect to 
 port 25 on the real mail server.  All submitted data can be based on HTTP 
 POSTS.  All requests should be valid HTTP.  (so urlencode and do 
 parm1=[EMAIL PROTECTED] if its not valid to pass just a key with no value)
 The Session ID is the key to the open connection from the proxy.  In the 
 event the connection from the proxy to real mail server closes then an 
 invalid session error should be returned to the client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-42) HTTP Protocol Proxy

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-42?page=comments#action_12316842 ]
 
Andrew Oliver commented on JBMAIL-42:
-

This rfc: http://www.faqs.org/rfcs/rfc2817.html

describes proxying via HTTP connect a bit better.  The simplicity of having a 
mail client just specify HTTP proxy and wrap all SMTP into that is 
appealing  


 HTTP Protocol Proxy
 ---

  Key: JBMAIL-42
  URL: http://jira.jboss.com/jira/browse/JBMAIL-42
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP, POP
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical


 Original Estimate: 2 days
 Remaining: 2 days

 Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.
 Example:
 C: GET /SMTP/Connect HTTP/1.1
 C:
 S: HTTP/1.1 200 OK
 S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1
 S:
 S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1) 
 ready March 17, 2005 10:00:36 AM EST
 Connection closed (not necessary for 1.1 but demonstrative)
 C: GET /SMTP/EHLO HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 VXNlcm5hbWU6
 C: GET /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 VXNlcm5hbWU6
 S:
 C: POST /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: {encoded user}
 S:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S:
 S: 334 UGFzc3dvcmQ6
 S:
 C: POST /SMTP/AUTH_LOGIN HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: {encoded pwd}
 S:
 S: HTTP/1.1 200 OK
 S: Content-Type: text/html;charset=UTF-8
 S: Content-Length: xxx
 S: Date: Thu, 17 Mar 2005 15:22:33 GMT
 S: Server: Apache-Coyote/1.1\
 S: 
 S: 200 Authorized
 S:
 C: POST /SMTP/MAIL_FROM HTTP/1.1
 C: Keep-Alive: 300^M
 C: Connection: keep-alive^M
 C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
 C: Content-Type: application/x-www-form-urlencoded
 C:
 C: [EMAIL PROTECTED]
 the intent is the proxy will be implemneted as a servlet and connect to 
 port 25 on the real mail server.  All submitted data can be based on HTTP 
 POSTS.  All requests should be valid HTTP.  (so urlencode and do 
 parm1=[EMAIL PROTECTED] if its not valid to pass just a key with no value)
 The Session ID is the key to the open connection from the proxy.  In the 
 event the connection from the proxy to real mail server closes then an 
 invalid session error should be returned to the client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-22) Implement Basic heap protection

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-22?page=history ]

Andrew Oliver updated JBMAIL-22:


Fix Version: 1.0-M4
 (was: 1.0-M3)

 Implement Basic heap protection
 ---

  Key: JBMAIL-22
  URL: http://jira.jboss.com/jira/browse/JBMAIL-22
  Project: JBoss Mail
 Type: Feature Request
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
  Fix For: 1.0-M4


 Original Estimate: 3 hours
 Remaining: 3 hours

 http://www.jboss.org/wiki/Wiki.jsp?page=MailServicesMilestone2HeapProtection

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-4) Add combo config finder to JBoss-Mail build

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-4?page=history ]

Andrew Oliver updated JBMAIL-4:
---

Fix Version: 1.0-M4
 (was: 1.0-M3)

 Add combo config finder to JBoss-Mail build
 ---

  Key: JBMAIL-4
  URL: http://jira.jboss.com/jira/browse/JBMAIL-4
  Project: JBoss Mail
 Type: Sub-task
   Components: build
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Minor
  Fix For: 1.0-M4


 Original Estimate: 1 hour
 Remaining: 1 hour

 After combo/list controls are added, add a combo to gui-install which 
 contains all the possible configs given a JBOSS_HOME.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-3) Add drop down list support to Cheese

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-3?page=history ]

Andrew Oliver updated JBMAIL-3:
---

Fix Version: 1.0-M4
 (was: 1.0-M3)

 Add drop down list support to Cheese
 

  Key: JBMAIL-3
  URL: http://jira.jboss.com/jira/browse/JBMAIL-3
  Project: JBoss Mail
 Type: Feature Request
   Components: build
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Minor
  Fix For: 1.0-M4


 Original Estimate: 1 day
 Remaining: 1 day

 Add Combo boxes, and list controls to Cheese. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-5) Implement new features for Cheese

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-5?page=history ]

Andrew Oliver updated JBMAIL-5:
---

Fix Version: 1.0-M4
 (was: 1.0-M3)

 Implement new features for Cheese
 -

  Key: JBMAIL-5
  URL: http://jira.jboss.com/jira/browse/JBMAIL-5
  Project: JBoss Mail
 Type: Feature Request
   Components: build
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Minor
  Fix For: 1.0-M4


 Original Estimate: 3 hours
 Remaining: 3 hours

 Add looping feature to cheese.  Implement Loop task in the same spirit as 
 When
 Cheese
  Loop iterations=5 propertyName=userNum
 antcall task=adduser/
  /Loop
 /Cheese
 Add buttonQuestion task to Cheese.
 Cheese
   buttonQuestion label=Add User task=addUserScreen/
 /Cheese
 Add increment task feature to cheese.
 Cheese
   increment propertyName=userNum/
 /Cheese
 That gives us what we need for a nicer adduser feature in jbmail build 
 install process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-54) Remove ALL hardcoded MBEAN NAMES!!!

[Andrew Oliver (JIRA)]

Remove ALL hardcoded MBEAN NAMES!!!
---

 Key: JBMAIL-54
 URL: http://jira.jboss.com/jira/browse/JBMAIL-54
 Project: JBoss Mail
Type: Task
  Components: Mail Server APIs, POP, Security, SMTP  
Versions: 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Michael Barker 
Priority: Critical
 Fix For: 1.0-M3


There are hardcoded MBean names...

...
public abstract class MailBody
{
...
   public final static String MAILBODY_MANAGER_NAME = 
jboss.mail:type=MailServices,name=MailBodyManager;


These should nver be in code but should always be externalized.  For one there 
might be multiple instances of JBMS hosted in the same appserver which would 
require different domains.  Moreover its just naughty :-)

I assigned this to Mike because I only see this in the store code so far.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-6) Develop Fetchmail MBean

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-6?page=comments#action_12316651 
]
 
Andrew Oliver commented on JBMAIL-6:


I remember that dots are escaped like so

.. == 1 dot

However they only have to be escaped IIRC if they are preceeded and anticeeded 
by a CR.

That being said headers are seperated from the body by a blank line (nothing 
more)

Hope that helps.

 Develop Fetchmail MBean
 ---

  Key: JBMAIL-6
  URL: http://jira.jboss.com/jira/browse/JBMAIL-6
  Project: JBoss Mail
 Type: Feature Request
   Components: POP
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Heiko W. Rupp
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 2 days
 Remaining: 2 days

 Develop an MBean which:
  
 1. retrieves messages from an external POP server and stores them in the 
 database.
 2. Writes a schedule to a database using Hibernate containing:
a. how often to check the external POP server (seconds, hours, days, day 
 of week, dates)
b. What user/password to use
 3. has checkAvailable operation which checks to see if there are mails 
 available for the user on the external server
 4. has retrieveMails operation which retrieves the mails and stores them in 
 the datbase.
 5. has addFetch(user, password, ScheduleSpecification spec) which adds a 
 fetch schedule to the database and creates a timer for runtime
 6. onStart sets up timers and polls the external POP servers as expected
 7. supports unencrypted POP, encrypted POP, TLS POP
 8. has provision for IMAP later
 (operation/attribute names are demonstrative only)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-52) Let (outgoing) mail be delivered through a smarthost

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-52?page=comments#action_12316659 ]
 
Andrew Oliver commented on JBMAIL-52:
-

We should target this for M4.  I think this should be part of the 
SMTPSenderMBean and the DNS stuff should be decoupled.  I think the DNS stuff 
should handle it however and you should be able to add MX records to it (for 
the purpose of relaying) including patterns.  Thus I could say relay.foo.com 
handles [EMAIL PROTECTED] and relaynet.foo.com handles [EMAIL PROTECTED]  

Eventually I actually want to add DNS as a protocol ;-) (Part of my world 
domination strategy)

 Let (outgoing) mail be delivered through a smarthost
 

  Key: JBMAIL-52
  URL: http://jira.jboss.com/jira/browse/JBMAIL-52
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Heiko W. Rupp
 Assignee: Andrew Oliver


 Original Estimate: 1 day
 Remaining: 1 day

 In some scenarios, mail should not be deliered directly to the MX, but only 
 be sent to a manually configured smarthost.
 This smarthost will then take care about mail delivery.
 This requirement is common in intranets, where branch offices don't deliver 
 (outgoing) mail on their own, but sent mail to the main office, that also 
 provdes content scanning etc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-53) Support SMTP after POP

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-53?page=comments#action_12316598 ]
 
Andrew Oliver commented on JBMAIL-53:
-

 you mean support it as a client from the fetchmail side not as a 
server to mail clients.  Okay now this makes more sense.  

 Support SMTP after POP
 --

  Key: JBMAIL-53
  URL: http://jira.jboss.com/jira/browse/JBMAIL-53
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Heiko W. Rupp
 Assignee: Andrew Oliver
 Priority: Minor


 Original Estimate: 1 day
 Remaining: 1 day

 Some smarthosts require a mail sender to first authenticate thenselves over 
 pop3 before allowing to send in mails via smtp.
 This requires a mail delivery queue for the smarthost, where the delivery can 
 be manually be triggered and where it otherwise just sits on the queuue.
 See JBMAIL-6 for fetchmail and the trgiggering scheduler and JBMAIL-52 for 
 the smarthost thingy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-53) Support SMTP after POP

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-53?page=comments#action_12316595 ]
 
Andrew Oliver commented on JBMAIL-53:
-

Yeah actually that should have said we support stronger SMTP authentication 
methods.  Can you detail out in this what this means (a P25 C:BLA S:BLA, P110 
C:BA S:BLA dialog description would be great)

 Support SMTP after POP
 --

  Key: JBMAIL-53
  URL: http://jira.jboss.com/jira/browse/JBMAIL-53
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Heiko W. Rupp
 Assignee: Andrew Oliver
 Priority: Minor


 Original Estimate: 1 day
 Remaining: 1 day

 Some smarthosts require a mail sender to first authenticate thenselves over 
 pop3 before allowing to send in mails via smtp.
 This requires a mail delivery queue for the smarthost, where the delivery can 
 be manually be triggered and where it otherwise just sits on the queuue.
 See JBMAIL-6 for fetchmail and the trgiggering scheduler and JBMAIL-52 for 
 the smarthost thingy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-53) Support SMTP after POP

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-53?page=comments#action_12316586 ]
 
Andrew Oliver commented on JBMAIL-53:
-

I'd not make this a top priority.  We support much stronger POP authentication 
methods which are supported by the major mail clients.  Probably should be done 
for functional completeness.

 Support SMTP after POP
 --

  Key: JBMAIL-53
  URL: http://jira.jboss.com/jira/browse/JBMAIL-53
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Heiko W. Rupp
 Assignee: Andrew Oliver


 Original Estimate: 1 day
 Remaining: 1 day

 Some smarthosts require a mail sender to first authenticate thenselves over 
 pop3 before allowing to send in mails via smtp.
 This requires a mail delivery queue for the smarthost, where the delivery can 
 be manually be triggered and where it otherwise just sits on the queuue.
 See JBMAIL-6 for fetchmail and the trgiggering scheduler and JBMAIL-52 for 
 the smarthost thingy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-6) Develop Fetchmail MBean

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-6?page=comments#action_12316217 
]
 
Andrew Oliver commented on JBMAIL-6:


Well its on the docket for M3 which I presently have the final targeted for mid 
april.  S if you commit it in at least compileable order then someone 
(probably me) will probably use where you left off.  If you DON'T then you may 
end up owning your own private half-implemented fetchmail :-P

 Develop Fetchmail MBean
 ---

  Key: JBMAIL-6
  URL: http://jira.jboss.com/jira/browse/JBMAIL-6
  Project: JBoss Mail
 Type: Feature Request
   Components: POP
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 2 days
 Remaining: 2 days

 Develop an MBean which:
  
 1. retrieves messages from an external POP server and stores them in the 
 database.
 2. Writes a schedule to a database using Hibernate containing:
a. how often to check the external POP server (seconds, hours, days, day 
 of week, dates)
b. What user/password to use
 3. has checkAvailable operation which checks to see if there are mails 
 available for the user on the external server
 4. has retrieveMails operation which retrieves the mails and stores them in 
 the datbase.
 5. has addFetch(user, password, ScheduleSpecification spec) which adds a 
 fetch schedule to the database and creates a timer for runtime
 6. onStart sets up timers and polls the external POP servers as expected
 7. supports unencrypted POP, encrypted POP, TLS POP
 8. has provision for IMAP later
 (operation/attribute names are demonstrative only)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-9) Amend build to (optionally) automatically create database tables using hbm2ddl

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-9?page=history ]

Andrew Oliver updated JBMAIL-9:
---

Fix Version: 1.0-M3

 Amend build to (optionally) automatically create database tables using hbm2ddl
 --

  Key: JBMAIL-9
  URL: http://jira.jboss.com/jira/browse/JBMAIL-9
  Project: JBoss Mail
 Type: Sub-task
   Components: build
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
  Fix For: 1.0-M3


 Original Estimate: 2 hours
 Remaining: 2 hours

 In order to properly do feature JBMAIL-8 we need the build process to 
 automatically should the user opt to do so.  This should be a check box or 
 boolean on the select your database secreen which should be yes by default.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-8) Hibernate Mailboxes

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-8?page=history ]

Andrew Oliver updated JBMAIL-8:
---

Fix Version: 1.0-M3

 Hibernate Mailboxes
 ---

  Key: JBMAIL-8
  URL: http://jira.jboss.com/jira/browse/JBMAIL-8
  Project: JBoss Mail
 Type: Feature Request
   Components: Mail Server APIs
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
  Fix For: 1.0-M3


 Original Estimate: 2 days
 Remaining: 2 days

 A new mail store implementation should be created which uses 
 Hibernate/JBossCache as the backend as opposed to entity beans.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-25) Modify StreamStore to be pluggable MessageStore

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-25?page=history ]

Andrew Oliver updated JBMAIL-25:


Version: 1.0-M3
Fix Version: 1.0-M3

 Modify StreamStore to be pluggable MessageStore
 ---

  Key: JBMAIL-25
  URL: http://jira.jboss.com/jira/browse/JBMAIL-25
  Project: JBoss Mail
 Type: Sub-task
 Versions: 1.0-M3
 Reporter: Dawie Malan
 Assignee: Michael Barker
  Fix For: 1.0-M3



 org.jboss.mail.store.* should be moved to org.jboss.mail.msgstore.stream.*, 
 and changed to implement the MessageStore interface.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-27) Create build flag to exclude test war

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-27?page=history ]

Andrew Oliver updated JBMAIL-27:


   Priority: Minor  (was: Major)
Version: 1.0-M3
Fix Version: 1.0-M3

 Create build flag to exclude test war
 -

  Key: JBMAIL-27
  URL: http://jira.jboss.com/jira/browse/JBMAIL-27
  Project: JBoss Mail
 Type: Sub-task
   Components: build
 Versions: 1.0-M3
 Reporter: Dawie Malan
 Priority: Minor
  Fix For: 1.0-M3



 The junitee-jbmail.war file should be included/excluded depending on a build 
 flag.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (JBMAIL-9) Amend build to (optionally) automatically create database tables using hbm2ddl

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-9?page=history ]
 
Andrew Oliver resolved JBMAIL-9:


Resolution: Rejected

not needed per comments

 Amend build to (optionally) automatically create database tables using hbm2ddl
 --

  Key: JBMAIL-9
  URL: http://jira.jboss.com/jira/browse/JBMAIL-9
  Project: JBoss Mail
 Type: Sub-task
   Components: build
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
  Fix For: 1.0-M3


 Original Estimate: 2 hours
 Remaining: 2 hours

 In order to properly do feature JBMAIL-8 we need the build process to 
 automatically should the user opt to do so.  This should be a check box or 
 boolean on the select your database secreen which should be yes by default.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-36) Support (optional) CRC or long hashkey generation for bodies

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-36?page=comments#action_12316219 ]
 
Andrew Oliver commented on JBMAIL-36:
-

Yeah.  

 Support (optional) CRC or long hashkey generation for bodies
 

  Key: JBMAIL-36
  URL: http://jira.jboss.com/jira/browse/JBMAIL-36
  Project: JBoss Mail
 Type: Sub-task
 Versions: 1.0-M4
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical
  Fix For: 1.0-M4


 Original Estimate: 1 week
 Remaining: 1 week

 The M3 Message Store prevents bodies from being stored multiple times and 
 allows messages to stream directly to the DB.  For large messages a line by 
 line hash should be calculable and if it matches an existing message (this 
 optimizes for disk size but costs performance) then the Mailbox entry is 
 reassigned to the existing mailstore and then the new body is deleted.
 Example.  
 1. Assume that the following is a 64mb stream that comes in (minus headers) 
 in duplicate for both mails (meaning we're sending the same file):
 body line  CRC/checksum/whatever
 X...XXX123456
 Y...YYY654321
 Z...ZZZ321654
 .....
 X...XXX123456
 Y...YYY654321
 Z...ZZZ321654
 cumulative checksum accurate to at least 1/5000
 12341235125132412512  
 if a select body_id from bodies where checksum='12341235125132412512' 
 returns more than 1 result then the new body is deleted and the mailbox is 
 assigned to the older of the two.
 So the idea above is important, algorythmic and method suggestions are not (I 
 don't know my posterior from my elbow when it comes to efficient binary 
 similarity detection -- I'm just pretty sure that's not to be done by direct 
 matching on content!).  
 It is important that minor revisions not cause collisions.  So the 1/5000 
 target for minimum collision should not be taken to mean if you send me a 
 doc, I edit it and send it back that it drops my edits and that's okay.  It 
 means that for this to be a viable algoyrthm if I upload the text of a speech 
 and you upload a completely different speech and somehow the checksum comes 
 out just rightwe could have that 1/50,000,000 chance of two very 
 different documents getting the same check, a minor revision to either should 
 fix it.
 It is also important that proper boundries be created (no chance that one 
 time we include fuzz surrounding the body and another time we don't).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-42) HTTP Protocol Proxy

[Andrew Oliver (JIRA)]

HTTP Protocol Proxy
---

 Key: JBMAIL-42
 URL: http://jira.jboss.com/jira/browse/JBMAIL-42
 Project: JBoss Mail
Type: Feature Request
  Components: POP, SMTP  
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical


Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.

Example:

C: GET /SMTP/Connect HTTP/1.1
C:
S: HTTP/1.1 200 OK
S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
S: Content-Type: text/html;charset=UTF-8
S: Content-Length: xxx
S: Date: Thu, 17 Mar 2005 15:22:33 GMT
S: Server: Apache-Coyote/1.1
S:
S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1) 
ready March 17, 2005 10:00:36 AM EST

Connection closed (not necessary for 1.1 but demonstrative)

C: GET /SMTP/EHLO HTTP/1.1
C: Keep-Alive: 300^M
C: Connection: keep-alive^M
C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
C:
S: HTTP/1.1 200 OK
S: Content-Type: text/html;charset=UTF-8
S: Content-Length: xxx
S: Date: Thu, 17 Mar 2005 15:22:33 GMT
S: Server: Apache-Coyote/1.1\
S:
S: 334 VXNlcm5hbWU6


C: GET /SMTP/AUTH_LOGIN HTTP/1.1
C: Keep-Alive: 300^M
C: Connection: keep-alive^M
C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
C:
S: HTTP/1.1 200 OK
S: Content-Type: text/html;charset=UTF-8
S: Content-Length: xxx
S: Date: Thu, 17 Mar 2005 15:22:33 GMT
S: Server: Apache-Coyote/1.1\
S:
S: 334 VXNlcm5hbWU6
S:
C: POST /SMTP/AUTH_LOGIN HTTP/1.1
C: Keep-Alive: 300^M
C: Connection: keep-alive^M
C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
C: Content-Type: application/x-www-form-urlencoded
C:
C: {encoded user}
S:
S: HTTP/1.1 200 OK
S: Content-Type: text/html;charset=UTF-8
S: Content-Length: xxx
S: Date: Thu, 17 Mar 2005 15:22:33 GMT
S: Server: Apache-Coyote/1.1\
S:
S: 334 UGFzc3dvcmQ6
S:
C: POST /SMTP/AUTH_LOGIN HTTP/1.1
C: Keep-Alive: 300^M
C: Connection: keep-alive^M
C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
C: Content-Type: application/x-www-form-urlencoded
C:
C: {encoded pwd}
S:
S: HTTP/1.1 200 OK
S: Content-Type: text/html;charset=UTF-8
S: Content-Length: xxx
S: Date: Thu, 17 Mar 2005 15:22:33 GMT
S: Server: Apache-Coyote/1.1\
S: 
S: 200 Authorized
S:
C: POST /SMTP/MAIL_FROM HTTP/1.1
C: Keep-Alive: 300^M
C: Connection: keep-alive^M
C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
C: Content-Type: application/x-www-form-urlencoded
C:
C: [EMAIL PROTECTED]

the intent is the proxy will be implemneted as a servlet and connect to port 
25 on the real mail server.  All submitted data can be based on HTTP POSTS.  
All requests should be valid HTTP.  (so urlencode and do parm1=[EMAIL 
PROTECTED] if its not valid to pass just a key with no value)

The Session ID is the key to the open connection from the proxy.  In the event 
the connection from the proxy to real mail server closes then an invalid 
session error should be returned to the client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-44) SMTP Proxy Servlet

[Andrew Oliver (JIRA)]

SMTP Proxy Servlet
--

 Key: JBMAIL-44
 URL: http://jira.jboss.com/jira/browse/JBMAIL-44
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


Issue to track the SMTP part http://jira.jboss.com/jira/browse/JBMAIL-42

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-48) Create support for Mozilla.org's Thunderbird to support SMTP over HTTP

[Andrew Oliver (JIRA)]

Create support for Mozilla.org's Thunderbird to support SMTP over HTTP
--

 Key: JBMAIL-48
 URL: http://jira.jboss.com/jira/browse/JBMAIL-48
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


Add support to Mozilla's Thunderbird to support SMTP over HTTP per 
http://jira.jboss.com/jira/browse/JBMAIL-42.  Thus users of thunderbird will 
only need the server to support the SMTP HTTP Proxy Servlet and will not 
require a client proxy.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-49) Add support to Mozilla's thunderbird for SMTP over HTTPS

[Andrew Oliver (JIRA)]

Add support to Mozilla's thunderbird for SMTP over HTTPS


 Key: JBMAIL-49
 URL: http://jira.jboss.com/jira/browse/JBMAIL-49
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


Add additional support for this http://jira.jboss.com/jira/browse/JBMAIL-48 
over HTTPS (just requires configuring the servlet over SSL on the server)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-50) Add support to Mozilla's thunderbird for POP over HTTP

[Andrew Oliver (JIRA)]

Add support to Mozilla's thunderbird for POP over HTTP
--

 Key: JBMAIL-50
 URL: http://jira.jboss.com/jira/browse/JBMAIL-50
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


 Add support to Mozilla's Thunderbird to support POP over HTTP per 
http://jira.jboss.com/jira/browse/JBMAIL-42. Thus users of thunderbird will 
only need the server to support the POP HTTP Proxy Servlet and will not require 
a client proxy. 

(estimate assumes same person who did the SMTP does the POP)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-43) check for existing RFCs

[Andrew Oliver (JIRA)]

check for existing RFCs
---

 Key: JBMAIL-43
 URL: http://jira.jboss.com/jira/browse/JBMAIL-43
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Minor


check for existing RFCs or implementations of 
http://jira.jboss.com/jira/browse/JBMAIL-42

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-45) POP subtask

[Andrew Oliver (JIRA)]

POP subtask
---

 Key: JBMAIL-45
 URL: http://jira.jboss.com/jira/browse/JBMAIL-45
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


Task to track the POP proxy for http://jira.jboss.com/jira/browse/JBMAIL-42

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-46) POP Client Proxy

[Andrew Oliver (JIRA)]

POP Client Proxy


 Key: JBMAIL-46
 URL: http://jira.jboss.com/jira/browse/JBMAIL-46
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


The POP client proxy mimic's a real POP Server however it translates the 
requests into the HTTP requests expected by:
http://jira.jboss.com/jira/browse/JBMAIL-42

Expectations:

1. It issues the http://servername/POP/CONNECT on initial connection from the 
client and returns the greeting from HTTP Pop proxy which in turn is just 
returning the real server's greeting.  From then on the jsessionid is 
associated with THIS connection to the client.
2. It hangs up on the client if it gets an invalid session from the server 
(avoid having to smartly implement the protocols to reconnect to a return to 
state and leave it up to the client to do that).
3. Server proxy is locked down to connect to only one host or set of hosts  
(so you can't use this to launch a distributed denial of service attack against 
a third party, sorry)

Possiblities:

1. Could be a protocol implementation for JBoss Mail's framework that simply 
uses something like Jakarta Commons HTTPClient to issue commands to the server 
proxy.  Thus you run parts of JBoss AS and JBMailServer on client and server.

2. This could be dumbly implemented to support ANY protocol if some 
standardization on the SERVER Proxy and Client Proxy can be thought of.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-47) SMTP Client Proxy

[Andrew Oliver (JIRA)]

SMTP Client Proxy
-

 Key: JBMAIL-47
 URL: http://jira.jboss.com/jira/browse/JBMAIL-47
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


The SMTP client proxy mimic's a real SMTP Server however it translates the 
requests into the HTTP requests expected by:
http://jira.jboss.com/jira/browse/JBMAIL-42

Expectations:

1. It issues the http://servername/SMTP/CONNECT on initial connection from the 
client and returns the greeting from HTTP SMTP proxy which in turn is just 
returning the real server's greeting.  From then on the jsessionid is 
associated with THIS connection to the client.
2. It hangs up on the client if it gets an invalid session from the server 
(avoid having to smartly implement the protocols to reconnect to a return to 
state and leave it up to the client to do that).
3. Server proxy is locked down to connect to only one host or set of hosts  
(so you can't use this to launch a distributed denial of service attack against 
a third party, sorry)

Possiblities:

1. Could be a protocol implementation for JBoss Mail's framework that simply 
uses something like Jakarta Commons HTTPClient to issue commands to the server 
proxy.  Thus you run parts of JBoss AS and JBMailServer on client and server.

2. This could be dumbly implemented to support ANY protocol if some 
standardization on the SERVER Proxy and Client Proxy can be thought of.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-51) Add support to Mozilla's thunderbird for POP over HTTPS

[Andrew Oliver (JIRA)]

Add support to Mozilla's thunderbird for POP over HTTPS
---

 Key: JBMAIL-51
 URL: http://jira.jboss.com/jira/browse/JBMAIL-51
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


 Add additional support for this http://jira.jboss.com/jira/browse/JBMAIL-50 
over HTTPS (just requires configuring the servlet over SSL on the server)

(estimate assumes that the developer of POP/SSL is the same as the SMTP/SSL who 
is the same as the POP and SMTP mozilla support)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-24) Mail that gets rejected with 5xx should be given back to user

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-24?page=history ]

Andrew Oliver updated JBMAIL-24:


Version: 1.0-M3

 Mail that gets rejected with 5xx should be given back to user
 -

  Key: JBMAIL-24
  URL: http://jira.jboss.com/jira/browse/JBMAIL-24
  Project: JBoss Mail
 Type: Bug
   Components: SMTP
 Versions: 1.0-M3
  Environment: jboss-mail, HEAD, jboss401
 Reporter: Heiko W. Rupp
 Assignee: Kabir Khan
  Fix For: 1.0-M3


 Original Estimate: 2 hours
 Remaining: 2 hours

 Mails that are refused by the remote with a 553 (any 5xx error) should not be 
 retired, but directly be given back into the mailbox of the submitting user.
 From RFC 2821:
 5yz   Permanent Negative Completion reply
   The command was not accepted and the requested action did not
   occur.  The SMTP client is discouraged from repeating the exact
   request (in the same sequence).  Even some permanent error
   conditions can be corrected, so the human user may want to direct
   the SMTP client to reinitiate the command sequence by direct
   action at some point in the future
 07:21:27,668 INFO  [STDOUT] MAIL FROM:[EMAIL PROTECTED]
 07:21:27,869 INFO  [STDOUT] 553 5.1.8 [EMAIL PROTECTED]... Domain of sender 
 address [EMAIL PROTECTED] does not exist
 07:21:27,869 ERROR [SMTPSender] Error sending mail
 javax.mail.MessagingException: 553 5.1.8 [EMAIL PROTECTED]... Domain of 
 sender address [EMAIL PROTECTED] does not exist
 [...]
 07:21:27,879 INFO  [STDOUT] QUIT
 07:21:27,879 INFO  [JMSMailListener] PUT MESSAGE ON QUEUE:[EMAIL PROTECTED]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-29) JBMail needs a mailq command

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-29?page=history ]

Andrew Oliver updated JBMAIL-29:


Priority: Minor  (was: Major)

target m4

 JBMail needs a mailq command
 --

  Key: JBMAIL-29
  URL: http://jira.jboss.com/jira/browse/JBMAIL-29
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Heiko W. Rupp
 Assignee: Andrew Oliver
 Priority: Minor



 There should be a command / operation for the admin to see all not-yet 
 delivered mail that are sitting for whatever reasons in the delivery queues.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-30) Merge the Nokia branch

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-30?page=history ]

Andrew Oliver updated JBMAIL-30:


 Assign To: Michael Barker  (was: Andrew Oliver)
 Original Estimate: 3600
Remaining Estimate: 3600
   Version: 1.0-M2
 Component: SMTP
   Fix Version: 1.0-M3
(was: 1.0-M2)

 Merge the Nokia branch
 --

  Key: JBMAIL-30
  URL: http://jira.jboss.com/jira/browse/JBMAIL-30
  Project: JBoss Mail
 Type: Task
   Components: SMTP
 Versions: 1.0-M2
 Reporter: Thomas Diesler
 Assignee: Michael Barker
  Fix For: 1.0-M3


 Original Estimate: 1 hour
 Remaining: 1 hour

 The nokia brach contains significant performance inprovements when 
 constructing the Mail object.
 Please ping me when the testsuite passes, so I can do the merge.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-24) Mail that gets rejected with 5xx should be given back to user

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-24?page=history ]

Andrew Oliver updated JBMAIL-24:


 Assign To: Kabir Khan  (was: Andrew Oliver)
 Original Estimate: 7200
Remaining Estimate: 7200
   Fix Version: 1.0-M3

 Mail that gets rejected with 5xx should be given back to user
 -

  Key: JBMAIL-24
  URL: http://jira.jboss.com/jira/browse/JBMAIL-24
  Project: JBoss Mail
 Type: Bug
   Components: SMTP
  Environment: jboss-mail, HEAD, jboss401
 Reporter: Heiko W. Rupp
 Assignee: Kabir Khan
  Fix For: 1.0-M3


 Original Estimate: 2 hours
 Remaining: 2 hours

 Mails that are refused by the remote with a 553 (any 5xx error) should not be 
 retired, but directly be given back into the mailbox of the submitting user.
 From RFC 2821:
 5yz   Permanent Negative Completion reply
   The command was not accepted and the requested action did not
   occur.  The SMTP client is discouraged from repeating the exact
   request (in the same sequence).  Even some permanent error
   conditions can be corrected, so the human user may want to direct
   the SMTP client to reinitiate the command sequence by direct
   action at some point in the future
 07:21:27,668 INFO  [STDOUT] MAIL FROM:[EMAIL PROTECTED]
 07:21:27,869 INFO  [STDOUT] 553 5.1.8 [EMAIL PROTECTED]... Domain of sender 
 address [EMAIL PROTECTED] does not exist
 07:21:27,869 ERROR [SMTPSender] Error sending mail
 javax.mail.MessagingException: 553 5.1.8 [EMAIL PROTECTED]... Domain of 
 sender address [EMAIL PROTECTED] does not exist
 [...]
 07:21:27,879 INFO  [STDOUT] QUIT
 07:21:27,879 INFO  [JMSMailListener] PUT MESSAGE ON QUEUE:[EMAIL PROTECTED]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-16) Add new RequireTLSForAuthenticated for SMTP

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-16?page=history ]

Andrew Oliver updated JBMAIL-16:


Priority: Critical  (was: Major)

 Add new RequireTLSForAuthenticated for SMTP
 ---

  Key: JBMAIL-16
  URL: http://jira.jboss.com/jira/browse/JBMAIL-16
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP, Security
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 2 hours
 Remaining: 2 hours

 Presently there is require TLS and not require TLS.  There ought to be 
 require TLS and require TLS for authenticated users.  Meaning if TLS is 
 not enabled when the user requests AUTH then an error occurs.  If this is a 
 relay request from another server, its acceptable without TLS.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-6) Develop Fetchmail MBean

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-6?page=history ]

Andrew Oliver updated JBMAIL-6:
---

   Priority: Critical  (was: Major)
Fix Version: 1.0-M3

 Develop Fetchmail MBean
 ---

  Key: JBMAIL-6
  URL: http://jira.jboss.com/jira/browse/JBMAIL-6
  Project: JBoss Mail
 Type: Feature Request
   Components: POP
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Andrew Oliver
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 2 days
 Remaining: 2 days

 Develop an MBean which:
  
 1. retrieves messages from an external POP server and stores them in the 
 database.
 2. Writes a schedule to a database using Hibernate containing:
a. how often to check the external POP server (seconds, hours, days, day 
 of week, dates)
b. What user/password to use
 3. has checkAvailable operation which checks to see if there are mails 
 available for the user on the external server
 4. has retrieveMails operation which retrieves the mails and stores them in 
 the datbase.
 5. has addFetch(user, password, ScheduleSpecification spec) which adds a 
 fetch schedule to the database and creates a timer for runtime
 6. onStart sets up timers and polls the external POP servers as expected
 7. supports unencrypted POP, encrypted POP, TLS POP
 8. has provision for IMAP later
 (operation/attribute names are demonstrative only)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-7) add a JAASUserRepository and support for JAAS-based security

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-7?page=history ]

Andrew Oliver updated JBMAIL-7:
---

Priority: Critical  (was: Major)

 add a JAASUserRepository and support for JAAS-based security
 

  Key: JBMAIL-7
  URL: http://jira.jboss.com/jira/browse/JBMAIL-7
  Project: JBoss Mail
 Type: Feature Request
   Components: Security
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 1 day
 Remaining: 1 day

 Mailboxes should be secured by roles and accounts should be checked by JAAS 
 authentication.  There should be a JAASUserRepository which merely checks 
 with JAAS in the test method and contains a jaas:/securityBlaBla
 Extend the present UserRepository interface for hasPermission(roleName, 
 user).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-33) Relaying

[Andrew Oliver (JIRA)]

Relaying


 Key: JBMAIL-33
 URL: http://jira.jboss.com/jira/browse/JBMAIL-33
 Project: JBoss Mail
Type: Feature Request
  Components: Security, SMTP  
Versions: 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical
 Fix For: 1.0-M3


Support acting as a middle-tier SMTP Relay.

MailClient---SMTPServerSMTPRelaySMTPServer(POP)---MailClient

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-34) Support Limiting Relay by domainlist

[Andrew Oliver (JIRA)]

Support Limiting Relay by domainlist


 Key: JBMAIL-34
 URL: http://jira.jboss.com/jira/browse/JBMAIL-34
 Project: JBoss Mail
Type: Sub-task
Versions: 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
 Fix For: 1.0-M3


For SMTP Relaying, support limiting relaying to/for a limited set of domains 
using the existing DomainList Mbean.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-35) Support Limiting Relay by source host IP address

[Andrew Oliver (JIRA)]

Support Limiting Relay by source host IP address


 Key: JBMAIL-35
 URL: http://jira.jboss.com/jira/browse/JBMAIL-35
 Project: JBoss Mail
Type: Sub-task
  Components: SMTP  
Versions: 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
 Fix For: 1.0-M3


Support limiting relaying by source host IP address.  Meaning limit relaying to 
only those connecting from an ip or range of ips.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBMAIL-23) Implement MailStore for bodies

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-23?page=history ]

Andrew Oliver updated JBMAIL-23:


Description: 
http://www.jboss.org/wiki/Wiki.jsp?page=MailStoreDesign

Mailstore allows you to prevent heap overflows by taking the inputstream and 
directly writing it to the database for the message body.  For M3 this will be 
optional behavior (use mailstore for bodies/don't use mailstore for bodies and 
suck it all into memory), but ultimately we plan to support size based 
limitations (only do this if the mail exceeds nKB) and possibly other 
perforamnce-based optimizations.

This will make JBoss Mail Server virtually unassailable by denial of service 
attacks provided you have a big disk.  This also ensures that only one copy of 
the body will be stored for all local message receipients.

  was:http://www.jboss.org/wiki/Wiki.jsp?page=MailStoreDesign

   Priority: Blocker  (was: Major)

 Implement MailStore for bodies
 --

  Key: JBMAIL-23
  URL: http://jira.jboss.com/jira/browse/JBMAIL-23
  Project: JBoss Mail
 Type: Feature Request
   Components: SMTP, POP, Mail Server APIs
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
 Priority: Blocker


 Original Estimate: 5 hours
 Remaining: 5 hours

 http://www.jboss.org/wiki/Wiki.jsp?page=MailStoreDesign
 Mailstore allows you to prevent heap overflows by taking the inputstream and 
 directly writing it to the database for the message body.  For M3 this will 
 be optional behavior (use mailstore for bodies/don't use mailstore for bodies 
 and suck it all into memory), but ultimately we plan to support size based 
 limitations (only do this if the mail exceeds nKB) and possibly other 
 perforamnce-based optimizations.
 This will make JBoss Mail Server virtually unassailable by denial of service 
 attacks provided you have a big disk.  This also ensures that only one copy 
 of the body will be stored for all local message receipients.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-36) Support (optional) CRC or long hashkey generation for bodies

[Andrew Oliver (JIRA)]

Support (optional) CRC or long hashkey generation for bodies 
-

 Key: JBMAIL-36
 URL: http://jira.jboss.com/jira/browse/JBMAIL-36
 Project: JBoss Mail
Type: Sub-task
Versions: 1.0-M4
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical
 Fix For: 1.0-M4


The M3 Message Store prevents bodies from being stored multiple times and 
allows messages to stream directly to the DB.  For large messages a line by 
line hash should be calculable and if it matches an existing message (this 
optimizes for disk size but costs performance) then the Mailbox entry is 
reassigned to the existing mailstore and then the new body is deleted.

Example.  

1. Assume that the following is a 64mb stream that comes in (minus headers) in 
duplicate for both mails (meaning we're sending the same file):

body line  CRC/checksum/whatever

X...XXX123456
Y...YYY654321
Z...ZZZ321654
.....
X...XXX123456
Y...YYY654321
Z...ZZZ321654

cumulative checksum accurate to at least 1/5000

12341235125132412512  

if a select body_id from bodies where checksum='12341235125132412512' returns 
more than 1 result then the new body is deleted and the mailbox is assigned to 
the older of the two.

So the idea above is important, algorythmic and method suggestions are not (I 
don't know my posterior from my elbow when it comes to efficient binary 
similarity detection -- I'm just pretty sure that's not to be done by direct 
matching on content!).  

It is important that minor revisions not cause collisions.  So the 1/5000 
target for minimum collision should not be taken to mean if you send me a doc, 
I edit it and send it back that it drops my edits and that's okay.  It means 
that for this to be a viable algoyrthm if I upload the text of a speech and you 
upload a completely different speech and somehow the checksum comes out just 
rightwe could have that 1/50,000,000 chance of two very different documents 
getting the same check, a minor revision to either should fix it.

It is also important that proper boundries be created (no chance that one time 
we include fuzz surrounding the body and another time we don't).


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-37) Support aggregate message store objects

[Andrew Oliver (JIRA)]

Support aggregate message store objects
---

 Key: JBMAIL-37
 URL: http://jira.jboss.com/jira/browse/JBMAIL-37
 Project: JBoss Mail
Type: Sub-task
  Components: SMTP, POP  
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical
 Fix For: 1.0-M4


Support the concept of storing different mime parts as seperate store objects 
and aggregate store objects that tie them together in a particular order.  
Meaning rather than storing the entire body of a message with seperate MIME 
parts, we can store each mime part seperately.


The mime aggregate should have a uniqueness checksum as well as each 
individual subpart.  Body replacement (deduplification) can happen either at 
the top level (the aggregate) or on an individual mime part.

In the case of a complete aggregate the checksum could probably be an aggregate 
flag and then what is essentially an array of the subpart store ids.

Again this should be toggleable off. It optimizes storage above performance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-38) JCA adaptor for incoming and outgoing mail using JBoss Mail Server

[Andrew Oliver (JIRA)]

JCA adaptor for incoming and outgoing mail using JBoss Mail Server
--

 Key: JBMAIL-38
 URL: http://jira.jboss.com/jira/browse/JBMAIL-38
 Project: JBoss Mail
Type: Feature Request
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical
 Fix For: 1.0-M4


A JCA adaptor for generic use of the mail server should be created for both 
sending and retrieving mails.

The following are conceptual interfaces.


Context ctx = new InitialContext();
MailServer svr = (MailServer)ctx.lookup(java://mail/Server);
if (svr.checkMail();) {  // current associated JAAS user is assumed
  int ids[] = svr.getMailIds();
  
  for (int k =0; k  ids.length; k++) {
 System.out.println(reading mail +ids[k]);
 Mail mail = srv.getMail(ids[k]);
 MailHeaders headers = mail.getHeaders();
 InputStream stream = mail.getBody();
 printHeaders(headers);
 printBody(stream);
  }
}

MailUserContext muc = new MailUserContext(user,password); 
svr.setUser(muc);
if (svr.checkMail(muc)) {
  int ids[] = svr.getMailIds(foldername);
  ...
}

Mail[] mail = svr.findMail(where SUBJECT like 'I like AOP' and FROM like 
'bburke');

For the first edition I do not want to support searching in bodies.

Mail mail = new Mail();
mail.setContentType(text/plain);
mail.setBody(I like cheese.);
mail.setTo([EMAIL PROTECTED]);
mail.setFrom([EMAIL PROTECTED]);  // should follow validate-identity rules 
(when enabled) for validating the JAAS user against the From.
svr.sendMail(mail);

svr.fetch(folder); // force a fetchmail to happen for the current 
authenticated user and block until it returns (if the user/folder aren't 
configured to fetchmail from external server then this should probably return 
without error)

svr.fetchAsynch(folder); //suggest that the server run a fetchmail and return

For a later revision I want an inbound/event driven version as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-39) Inbound event-driven JCA adaptor for receiving mails

[Andrew Oliver (JIRA)]

Inbound event-driven JCA adaptor for receiving mails


 Key: JBMAIL-39
 URL: http://jira.jboss.com/jira/browse/JBMAIL-39
 Project: JBoss Mail
Type: Sub-task
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


A user for a given folder will get mails which will trigger events which will 
notify registered listeners which will process the mail all through JCA.  
(which should probably just be a handle to a MailListener)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-40) Support Virtual Host/Domains

[Andrew Oliver (JIRA)]

Support Virtual Host/Domains


 Key: JBMAIL-40
 URL: http://jira.jboss.com/jira/browse/JBMAIL-40
 Project: JBoss Mail
Type: Feature Request
  Components: SMTP, POP, Security  
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
 Fix For: 1.0-M4


Large mail hosting systems may allow the same username on multiple hosts.  
Meaning if I connect to:

mail.nowhere.com with user andy and password foobar then that would be 
treated as a completely different account (POTENTIALLY) than if I connect to 
mail.somewhere.com with user andy and password barfoo (or this may be even 
the same password).

This should use the domain list mbeans and will require some changes in the 
user repository contracts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-41) Basic IMAP support

[Andrew Oliver (JIRA)]

Basic IMAP support
--

 Key: JBMAIL-41
 URL: http://jira.jboss.com/jira/browse/JBMAIL-41
 Project: JBoss Mail
Type: Feature Request
Versions: 1.0-M4
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Blocker
 Fix For: 1.0-M4


Basic IMAP protocol support. 

Create subtasks from here.  This will most likely cause substantial changes in 
security and mailboxes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-7) add a JAASUserRepository and support for JAAS-based security

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-7?page=comments#action_12316214 
]
 
Andrew Oliver commented on JBMAIL-7:


Sure.  I'll put a follow on for a later milestone.  JB's JACC implementation 
seems to be a bit of a moving target ATM.  Moreover, we'll want to support 
existing stuff more or less.

 add a JAASUserRepository and support for JAAS-based security
 

  Key: JBMAIL-7
  URL: http://jira.jboss.com/jira/browse/JBMAIL-7
  Project: JBoss Mail
 Type: Feature Request
   Components: Security
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan
 Priority: Critical
  Fix For: 1.0-M3


 Original Estimate: 1 day
 Remaining: 1 day

 Mailboxes should be secured by roles and accounts should be checked by JAAS 
 authentication.  There should be a JAASUserRepository which merely checks 
 with JAAS in the test method and contains a jaas:/securityBlaBla
 Extend the present UserRepository interface for hasPermission(roleName, 
 user).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1572) stop unzipping everything in the deploy on every startup

[Andrew Oliver (JIRA)]

stop unzipping everything in the deploy on every startup


 Key: JBAS-1572
 URL: http://jira.jboss.com/jira/browse/JBAS-1572
 Project: JBoss Application Server
Type: Feature Request
  Components: Deployment Service  
Versions:  JBossAS-4.0.1 SP1
Reporter: Andrew Oliver


Presently JBossAS unzips everything in the deploy directory into the tmp 
directory on every startup.  The desired behavior is to preserve the files in 
the tmp directory and only unzip if there is a newer associated file in the 
deploy directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-32) Bounced mails reuse mime type and produce invalid mails

[Andrew Oliver (JIRA)]

Bounced mails reuse mime type and produce invalid mails
---

 Key: JBMAIL-32
 URL: http://jira.jboss.com/jira/browse/JBMAIL-32
 Project: JBoss Mail
Type: Bug
  Components: SMTP  
Versions: 1.0-M2, 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
 Fix For: 1.0-M3


http://www.jboss.org/index.html?module=bbop=viewtopict=59373

if the bounced message was MIME, then the bounce message is MIME even though 
its text only.  It should always have a text content type because it will 
always be text.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (JBMAIL-32) Bounced mails reuse mime type and produce invalid mails

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-32?page=history ]

Andrew Oliver reassigned JBMAIL-32:
---

Assign To: Kabir Khan  (was: Andrew Oliver)

 Bounced mails reuse mime type and produce invalid mails
 ---

  Key: JBMAIL-32
  URL: http://jira.jboss.com/jira/browse/JBMAIL-32
  Project: JBoss Mail
 Type: Bug
   Components: SMTP
 Versions: 1.0-M2, 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Kabir Khan
  Fix For: 1.0-M3


 Original Estimate: 1 hour
 Remaining: 1 hour

 http://www.jboss.org/index.html?module=bbop=viewtopict=59373
 if the bounced message was MIME, then the bounce message is MIME even though 
 its text only.  It should always have a text content type because it will 
 always be text.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1538) commons-logging.jar should be in server/xxx/lib not server/xxx/deploy/jboss-tomcat.sar/

[Andrew Oliver (JIRA)]

commons-logging.jar should be in server/xxx/lib not 
server/xxx/deploy/jboss-tomcat.sar/
---

 Key: JBAS-1538
 URL: http://jira.jboss.com/jira/browse/JBAS-1538
 Project: JBoss Application Server
Type: Bug
  Components: Build System  
Versions: JBossAS-4.0.1 Final
Reporter: Andrew Oliver


the cluster stuff depends on apache's commons-logging nasty stuff as does 
tomcat.  Right now that means that as packaged cluster-service.xml depends on 
commons logging.  Bela should be smacked for adding this commons-logging 
monstrosity as a dependency.  Oh wait, he's here at JBossWorld.. . I'll smack 
him tomorrow!   I'd just fix it but sourceforge is not being cooperative 
tonight.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-31) S/Mime support

[Andrew Oliver (JIRA)]

S/Mime support
--

 Key: JBMAIL-31
 URL: http://jira.jboss.com/jira/browse/JBMAIL-31
 Project: JBoss Mail
Type: Feature Request
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 


Add S/MIME support. 
http://www.shoesobjects.com/blog/2005/02/26/1109434743279.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=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12315735 ]
 
Andrew Oliver commented on JBAS-1298:
-

The current behavior is noted as undesirable.  I want an MBean from which stats 
can be retrieved.

 HAR Deployer  JBCache config
 

  Key: JBAS-1298
  URL: http://jira.jboss.com/jira/browse/JBAS-1298
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 6 hours
 Remaining: 6 hours

 Presently HAR deployer picks up JBCache config from its classloader.  It does 
 not use an MBean.  It should use an MBean (and we should be able to get stats 
 from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12315747 ]
 
Andrew Oliver commented on JBAS-1319:
-

This is a known issue.  
http://www.jboss.org/wiki/Wiki.jsp?page=OutOfMemoryExceptionWhenRedeploying

Its an issue with the VM itself.  Use JRockit.


 redeploy causes OutOfMemoryError
 

  Key: JBAS-1319
  URL: http://jira.jboss.com/jira/browse/JBAS-1319
  Project: JBoss Application Server
 Type: Bug
   Components: JMX
 Versions: JBossAS-4.0.1 Final
  Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0
 Reporter: Matthew Todd
 Assignee: Clebert Suconic



 Constant redployment, even of a simple web application eventually causes an 
 OutOfMemoryError in JBoss. 
 To duplicate, keep on copying a .war package into a servers hot deploy 
 directory. Eventually an OutOfMemoryError occurs. 
 This is especially dangerous when running as a cluster, as when the node is 
 restarted, it is unable to join the cluster again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12315750 ]
 
Andrew Oliver commented on JBAS-1319:
-

I'd actually kinda like to close this and open a new feature request to use 
this: 
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/instrument/ClassDefinition.html
 in the deployer.

 redeploy causes OutOfMemoryError
 

  Key: JBAS-1319
  URL: http://jira.jboss.com/jira/browse/JBAS-1319
  Project: JBoss Application Server
 Type: Bug
   Components: JMX
 Versions: JBossAS-4.0.1 Final
  Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0
 Reporter: Matthew Todd
 Assignee: Clebert Suconic



 Constant redployment, even of a simple web application eventually causes an 
 OutOfMemoryError in JBoss. 
 To duplicate, keep on copying a .war package into a servers hot deploy 
 directory. Eventually an OutOfMemoryError occurs. 
 This is especially dangerous when running as a cluster, as when the node is 
 restarted, it is unable to join the cluster again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1458) EJB containers require JRMP invoker

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1458?page=comments#action_12315451 ]
 
Andrew Oliver commented on JBAS-1458:
-

Read the original bug for use case.  Overall just the ability to deploy 
EJBContainers with no remote invoker whatsoever is the idea.  Everything does 
local invocations (including for remote interfaces).  Nothing listening on any 
port for remote invocations, etc.  

 EJB containers require JRMP invoker
 ---

  Key: JBAS-1458
  URL: http://jira.jboss.com/jira/browse/JBAS-1458
  Project: JBoss Application Server
 Type: Feature Request
   Components: EJBs
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Priority: Minor



 EJBs require the JRMP invoker even if the container-configuration is not 
 bound to the JRMP invoker.  It should be possible to deploy EJBs that are not 
 remotely accessible (even if they have Remote interfaces) via any invoker 
 except for local.  Specifying the local invoker in the proxy binding doesn't 
 work either.  Consider standard WEB-EJB applications with no remote clients. 
  
 While you can just block the port, it would be nice not to have to expend 
 resources listening on a port that is blocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-73) Unpooled SLSB semantics

[Andrew Oliver (JIRA)]

Unpooled SLSB semantics
---

 Key: EJBTHREE-73
 URL: http://jira.jboss.com/jira/browse/EJBTHREE-73
 Project: EJB 3.0
Type: Feature Request
Versions: Preview 5, Preview 4
Reporter: Andrew Oliver
 Assigned to: Bill Burke 


EJB3 should allow optional servlet-style thread model semantics for stateless 
session beans.  Meaning, rarely is object pooling of SLSBs of any real 
advantage  aside from contraining resources which is usually better done in 
places like thread pools and isn't commonly made use of to constrain individual 
application components in practice.

basically a @TheadSafeSLSB or some like tag would mark that it was safe to 
send all threads to the a single instance of an SLSB.  You'd follow similar 
practices that you use for Servlets which you almost have to do anyhow for 
SLSBs.  You'd no longer be granted an object lock for the scope method 
invocation.

Possibly this should be the default behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1458) EJB containers require JRMP invoker

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1458?page=comments#action_12315383 ]
 
Andrew Oliver commented on JBAS-1458:
-

it is also not possible to not bind the jrmp invoker to any port.

 EJB containers require JRMP invoker
 ---

  Key: JBAS-1458
  URL: http://jira.jboss.com/jira/browse/JBAS-1458
  Project: JBoss Application Server
 Type: Bug
   Components: EJBs
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Priority: Minor



 EJBs require the JRMP invoker even if the container-configuration is not 
 bound to the JRMP invoker.  It should be possible to deploy EJBs that are not 
 remotely accessible (even if they have Remote interfaces) via any invoker 
 except for local.  Specifying the local invoker in the proxy binding doesn't 
 work either.  Consider standard WEB-EJB applications with no remote clients. 
  
 While you can just block the port, it would be nice not to have to expend 
 resources listening on a port that is blocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1465) Pooled Invoker should use common thread pool

[Andrew Oliver (JIRA)]

Pooled Invoker should use common thread pool


 Key: JBAS-1465
 URL: http://jira.jboss.com/jira/browse/JBAS-1465
 Project: JBoss Application Server
Type: Task
  Components: EJBs, JMX, Remoting  
Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
Priority: Minor


many clients prefer to have a fixed set of pooled threads.  The new 
BasicThreadPool service intends to provide this (and it ought be possible to 
have multiple instances for those who want seperate threads).  The 
PooledInvoker uses its own setup entirely.  It ought to be possible to get it 
to use a given instance of BasicThreadPool similar to how naming does.

mbean code=org.jboss.util.threadpool.BasicThreadPool
  name=jboss.system:service=ThreadPool
  attribute name=NameJBoss System Threads/attribute
  attribute name=ThreadGroupNameSystem Threads/attribute
  attribute name=KeepAliveTime6/attribute
  attribute name=MinimumPoolSize1/attribute
  attribute name=MaximumPoolSize10/attribute
  attribute name=MaximumQueueSize1000/attribute
  attribute name=BlockingModerun/attribute
   /mbean



   mbean code=org.jboss.invocation.pooled.server.PooledInvoker
  name=jboss:service=invoker,type=pooled
  attribute name=NumAcceptThreads1/attribute
  attribute name=MaxPoolSize300/attribute
  attribute name=ClientMaxPoolSize300/attribute
  attribute name=SocketTimeout6/attribute
  attribute name=ServerBindAddress${jboss.bind.address}/attribute
  attribute name=ServerBindPort4445/attribute
  attribute name=ClientConnectAddress${jboss.bind.address}/attribute
  attribute name=ClientConnectPort0/attribute
  attribute name=EnableTcpNoDelayfalse/attribute
  depends 
optional-attribute-name=TransactionManagerServicejboss:service=TransactionManager/depends
   /mbean


from naming service def:

  !-- The thread pool service used to control the bootstrap lookups --

  depends optional-attribute-name=LookupPool
 proxy-type=attributejboss.system:service=ThreadPool/depends


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1471) Implement HA Pooled Invoker

[Andrew Oliver (JIRA)]

Implement HA Pooled Invoker
---

 Key: JBAS-1471
 URL: http://jira.jboss.com/jira/browse/JBAS-1471
 Project: JBoss Application Server
Type: Task
  Components: Clustering, EJBs, Remoting  
Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver


Presently there is a pooled invoker and an HA jrmp invoker.  We should have a 
pooled JRMPHA invoker.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1457) Datasources require JAAS

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1457?page=comments#action_12315423 ]
 
Andrew Oliver commented on JBAS-1457:
-

confirmed.  Sorry about that.

 Datasources require JAAS
 

  Key: JBAS-1457
  URL: http://jira.jboss.com/jira/browse/JBAS-1457
  Project: JBoss Application Server
 Type: Bug
   Components: EJBs
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Priority: Minor



 do this:
 vi server/slim/jboss-service.xml
!--  
 --
!-- Security 
 --
!--  
 --
 !--
mbean code=org.jboss.security.plugins.SecurityConfig
   name=jboss.security:service=SecurityConfig
   attribute 
 name=LoginConfigjboss.security:service=XMLLoginConfig/attribute
/mbean
mbean code=org.jboss.security.auth.login.XMLLoginConfig
   name=jboss.security:service=XMLLoginConfig
   attribute name=ConfigResourcelogin-config.xml/attribute
/mbean
 --
!-- JAAS security manager and realm mapping --
 !--   mbean code=org.jboss.security.plugins.JaasSecurityManagerService
   name=jboss.security:service=JaasSecurityManager
   attribute name=SecurityManagerClassName
  org.jboss.security.plugins.JaasSecurityManager
   /attribute
   attribute name=DefaultCacheTimeout1800/attribute
   attribute name=DefaultCacheResolution60/attribute
/mbean
 --
 and this
  vi server/slim/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml
   !-- The JAAS security domain to use in the absense of an explicit
   security-domain specification in the war WEB-INF/jboss-web.xml
   --
 !--  attribute 
 name=DefaultSecurityDomainjava:/jaas/other/attribute--
 !--  depends optional-attribute-name=SecurityManagerService
  proxy-type=attributejboss.security:service=JaasSecurityManager
   /depends--
 you get this:
 17:51:23,961 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
 MBeans waiting for other MBeans:
 ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
  state: CONFIGURED
  I Depend On:  jboss.jca:service=ManagedConnectionPool,name=DefaultDS
  jboss.jca:service=CachedConnectionManager
  jboss.security:service=JaasSecurityManager
  jboss:service=TransactionManager
  Depends On Me: 
 MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
 ObjectName: jboss.security:service=JaasSecurityManager
  state: NOTYETINSTALLED
  I Depend On: 
  Depends On Me:  jboss.jca:service=LocalTxCM,name=DefaultDS
 even with the default hsql-db.xml.  However if you remove the (incorrect?) 
 dependence on the CachedConnectionManager from the jboss-jca.rar's stylesheet 
 it still depends on JAAS.  If you comment out the JAAS section (not sure why 
 the condition gets triggered anyhow since I have no domain specified) then 
 you get a NPE while it tried to look for JAAS.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1429) Reauthentication Support

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1429?page=comments#action_12315424 ]
 
Andrew Oliver commented on JBAS-1429:
-

also change the XSLT to recognize that when the change user support is in the 
-ds to not used the cached but to use the pooled.

 Reauthentication Support
 

  Key: JBAS-1429
  URL: http://jira.jboss.com/jira/browse/JBAS-1429
  Project: JBoss Application Server
 Type: Feature Request
   Components: JCA service
 Versions: JBossAS-4.0.1 Final
 Reporter: Andrew Oliver



 Add support for the reauthentication support (in particular MySQLChangeUser)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1458) EJB containers require JRMP invoker

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1458?page=comments#action_12315425 ]
 
Andrew Oliver commented on JBAS-1458:
-

I mean to tell it to bind to NO port and not allow any remote invocation 
requests to come in at all nor to attempt to reserve any port. 

 EJB containers require JRMP invoker
 ---

  Key: JBAS-1458
  URL: http://jira.jboss.com/jira/browse/JBAS-1458
  Project: JBoss Application Server
 Type: Bug
   Components: EJBs
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Priority: Minor



 EJBs require the JRMP invoker even if the container-configuration is not 
 bound to the JRMP invoker.  It should be possible to deploy EJBs that are not 
 remotely accessible (even if they have Remote interfaces) via any invoker 
 except for local.  Specifying the local invoker in the proxy binding doesn't 
 work either.  Consider standard WEB-EJB applications with no remote clients. 
  
 While you can just block the port, it would be nice not to have to expend 
 resources listening on a port that is blocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1457) Datasources require JAAS

[Andrew Oliver (JIRA)]

Datasources require JAAS


 Key: JBAS-1457
 URL: http://jira.jboss.com/jira/browse/JBAS-1457
 Project: JBoss Application Server
Type: Bug
  Components: EJBs  
Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
Priority: Minor


do this:

vi server/slim/jboss-service.xml

   !--  --
   !-- Security --
   !--  --
!--
   mbean code=org.jboss.security.plugins.SecurityConfig
  name=jboss.security:service=SecurityConfig
  attribute 
name=LoginConfigjboss.security:service=XMLLoginConfig/attribute
   /mbean
   mbean code=org.jboss.security.auth.login.XMLLoginConfig
  name=jboss.security:service=XMLLoginConfig
  attribute name=ConfigResourcelogin-config.xml/attribute
   /mbean
--

   !-- JAAS security manager and realm mapping --
!--   mbean code=org.jboss.security.plugins.JaasSecurityManagerService
  name=jboss.security:service=JaasSecurityManager
  attribute name=SecurityManagerClassName
 org.jboss.security.plugins.JaasSecurityManager
  /attribute
  attribute name=DefaultCacheTimeout1800/attribute
  attribute name=DefaultCacheResolution60/attribute
   /mbean
--

and this

 vi server/slim/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml

  !-- The JAAS security domain to use in the absense of an explicit
  security-domain specification in the war WEB-INF/jboss-web.xml
  --
!--  attribute 
name=DefaultSecurityDomainjava:/jaas/other/attribute--

!--  depends optional-attribute-name=SecurityManagerService
 proxy-type=attributejboss.security:service=JaasSecurityManager
  /depends--

you get this:

17:51:23,961 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
 state: CONFIGURED
 I Depend On:  jboss.jca:service=ManagedConnectionPool,name=DefaultDS
 jboss.jca:service=CachedConnectionManager
 jboss.security:service=JaasSecurityManager
 jboss:service=TransactionManager

 Depends On Me: 

MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.security:service=JaasSecurityManager
 state: NOTYETINSTALLED
 I Depend On: 
 Depends On Me:  jboss.jca:service=LocalTxCM,name=DefaultDS


even with the default hsql-db.xml.  However if you remove the (incorrect?) 
dependence on the CachedConnectionManager from the jboss-jca.rar's stylesheet 
it still depends on JAAS.  If you comment out the JAAS section (not sure why 
the condition gets triggered anyhow since I have no domain specified) then you 
get a NPE while it tried to look for JAAS.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1458) EJB containers require JRMP invoker

[Andrew Oliver (JIRA)]

EJB containers require JRMP invoker
---

 Key: JBAS-1458
 URL: http://jira.jboss.com/jira/browse/JBAS-1458
 Project: JBoss Application Server
Type: Bug
  Components: EJBs  
Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
Priority: Minor


EJBs require the JRMP invoker even if the container-configuration is not bound 
to the JRMP invoker.  It should be possible to deploy EJBs that are not 
remotely accessible (even if they have Remote interfaces) via any invoker 
except for local.  Specifying the local invoker in the proxy binding doesn't 
work either.  Consider standard WEB-EJB applications with no remote clients.  

While you can just block the port, it would be nice not to have to expend 
resources listening on a port that is blocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1326) LoaderRepositoryMbean does not display URLs properly

[Andrew Oliver (JIRA)]

LoaderRepositoryMbean does not display URLs properly


 Key: JBAS-1326
 URL: http://jira.jboss.com/jira/browse/JBAS-1326
 Project: JBoss Application Server
Type: Bug
  Components: JMX  
Versions: JBossAS-4.0.0 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


In JBoss 4.0 if you click on the default LoaderRepository (or any class loader 
repository) in the JMX console it improperly displays the URL[].toString() java 
reference literal rather than the list of URLs which are deployed as the return 
value of the attribute.  Past versions of JBoss used to display the full 
collection of  URLS in the CLR.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314869 ]
 
Andrew Oliver commented on JBAS-1301:
-

does this fix the issue in the case we had?  They had stuff in the server.xml 
for those vhs and the jboss-web pointed to it.

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final,  JBossAS-4.0.2RC1, JBossPOJOServer-1.0 
 Alpha
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1322) Farm service fails to deploy correctly on startup

[Andrew Oliver (JIRA)]

Farm service fails to deploy correctly on startup
-

 Key: JBAS-1322
 URL: http://jira.jboss.com/jira/browse/JBAS-1322
 Project: JBoss Application Server
Type: Bug
  Components: Clustering  
Versions: JBossAS-4.0.0 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


Assume we have two JBoss nodes in a cluster.  If we start node A and node B 
then deploy an ear file to farm it is propegated to both servers as expected.  
If we have the ear file in node A's farm but not node B's farm -- then start 
node B fully before starting node A -- Jboss fails to deploy the ear to node B.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-13) Make layouts and stuff work correctly in cheese

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBMAIL-13?page=comments#action_12314800 ]
 
Andrew Oliver commented on JBMAIL-13:
-

I use firefox as well.  JIRA kinda sucks but oh well.  looks like you succeeded 
despite JIRA in assigning it to yourself.

 Make layouts and stuff work correctly in cheese
 ---

  Key: JBMAIL-13
  URL: http://jira.jboss.com/jira/browse/JBMAIL-13
  Project: JBoss Mail
 Type: Bug
   Components: build
 Versions: 1.0-M2
 Reporter: Andrew Oliver
 Assignee: Kit McCormick
  Fix For: 1.0-M2


 Original Estimate: 2 hours
 Remaining: 2 hours

 make the layouts in cheese work properly.  Someone who sucks less at GUIs 
 should do 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



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314815 ]
 
Andrew Oliver commented on JBAS-1301:
-

I'm heading back out on the road tomorrow.  I have a running theory that goes 
like this:

what if an init on startup servlet threw an exception and swallowed it?  Then 
could the servlet container get created but tomcat not map it to virutal 
servers?  Could this be happening?

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314736 ]
 
Andrew Oliver commented on JBAS-1301:
-

I'll see if I can attach it tomorrow.  Its simple to reproduce though.  Create 
a server.xml with virtual hosts + aliases.  Make the virtual host not the 
actual host name of the server (not sure if that matters to reproduce it 
actually) and then point your EAR/WAR to root of one of the aliases.  Works 
(embedded in jboss-service.xml) in jb323.  IT doesn't work in 326 but in a 
bizzare random intermitent pattern (some do some don't and occassionally all 
do).

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
 Priority: Minor


 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1300) Non-Remote JMS HA

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1300?page=comments#action_12314739 ]
 
Andrew Oliver commented on JBAS-1300:
-

There is like next to no way I posted about this 3 times in the forums. :-P  Is 
the new messaging not called JBossMQ?  I'm only concerned about the ends not 
the means really.

 Non-Remote JMS HA
 -

  Key: JBAS-1300
  URL: http://jira.jboss.com/jira/browse/JBAS-1300
  Project: JBoss Application Server
 Type: Feature Request
   Components: JMS service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark


 Original Estimate: 1 week
 Remaining: 1 week

 It should be possible to use JMS on all servers in a cluster with HA enabled. 
  Meaning:
 1. Database as a store.  Everyone node uses shared DB.
 2. JMS_MESSAGES table includes node name
 3. In the event of group membership changes another node picks up the old 
 node's messages
 4. JMS Client proxy autofails to another node

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314745 ]
 
Andrew Oliver commented on JBAS-1301:
-

Is see this:

$ find ./tomcat -name *.java -exec grep -Hi virtual '{}' ';'
./tomcat/src/main/org/jboss/web/tomcat/security/JBossSecurityMgrRealm.java:
* trying to change the virtual host to which a Request should be
./tomcat/src/main/org/jboss/web/tomcat/tc4/authenticator/SingleSignOn.java: *   
  virtual host (typically an implementation of codeHost/code)./li
./tomcat/src/main/org/jboss/web/tomcat/tc4/ConfigHandler.java:  // Setup 
the mapping rules for Engine virtual hosts
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:/** A subclass 
of Embedded that accepts Services and locating virtual
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:* and 
directed to the specified context path on the virtual host
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:  Iterator 
hosts = metaData.getVirtualHosts();
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:  Host 
virtualHost = config.getCatalina().findHost(hostName);
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:   
new ClusterManager(virtualHost,
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:  
virtualHost.addChild(context);
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java: 
 virtualHost.getName(), config.getServiceName(), server);
./tomcat/src/main/org/jboss/web/tomcat/tc5/sso/ClusteredSingleSignOn.java: *
 virtual host (typically an implementation of codeHost/code)./li
./tomcat/src/main/org/jboss/web/tomcat/tc5/StatusServlet.java:// 
Display virtual machine statistics
./tomcat/src/main/org/jboss/web/tomcat/tc5/TomcatDeployer.java:  Iterator 
hostNames = metaData.getVirtualHosts();
./tomcat/src/main/org/jboss/web/tomcat/tc5/TomcatDeployer.java:  Iterator 
hostNames = metaData.getVirtualHosts();


However I also see this:

$ find ./tomcat -name *.java -exec grep -Hi alias '{}' ';'
./tomcat/src/main/org/jboss/web/tomcat/tc4/ConfigHandler.java:  
mapper.addCallMethod(Server/Service/Engine/Host/Alias, addAlias,0);
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:  // 
Search all Hosts for matching names and aliases
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:   
  // Check the aliases
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:   
  String[] aliases = tmpHost.findAliases();
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:   
  for(int a = 0; a  aliases.length; a ++)
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:   
 String alias = aliases[a];
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:   
 if( alias.equalsIgnoreCase(hostName) == true )

And then if you look at that you find this:

 // Check the aliases
 String[] aliases = tmpHost.findAliases();
 for(int a = 0; a  aliases.length; a ++)
 {
String alias = aliases[a];
if( alias.equalsIgnoreCase(hostName) == true )
{
   host = tmpHost;
   break;
}
 }

There is nothing similar in the TC5 jboss coupling code.  

A quick glance though the TC5 code shows things that MAY have taken its place 
but I'd have to run through it in a linear problem.

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final


 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
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

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314749 ]
 
Andrew Oliver commented on JBAS-1301:
-

gmailed to config to scott via gmail.

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final


 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314756 ]
 
Andrew Oliver commented on JBAS-1301:
-

Ran in the debugger.  at request time the VHost+Aliases are all there but the 
CONTEXT is not actually mapped to the VHost: 

Most interesting file: 
./jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper/Mapper.java

In fact only /jmx-console is mapped (kinda) which isn't actually mapped to an 
VHOST.

Still need to look through the deployment process.



 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314760 ]
 
Andrew Oliver commented on JBAS-1301:
-

it is mapped in the application.xml by war.  Do not ethat it doesn't happen 
most times we start up...

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314761 ]
 
Andrew Oliver commented on JBAS-1301:
-

Unfortunately I can't hit the jmx-console through the LB at the moment

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314762 ]
 
Andrew Oliver commented on JBAS-1301:
-

Oh but the alias and hosts did not appear in the mbean attributes of the errant 
containers when jboss-web vhost mapped to an alias.

 Tomcat backward compatbility loss VirtualHost-Alias mapping
 

  Key: JBAS-1301
  URL: http://jira.jboss.com/jira/browse/JBAS-1301
  Project: JBoss Application Server
 Type: Bug
   Components: Web (Tomcat) service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Scott M Stark
  Fix For:  JBossAS-3.2.7 Final
  Attachments: server.xml

 Original Estimate: 3 hours
 Remaining: 3 hours

 In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set 
 of Aliases in the jboss-service.xml and then map the webapps to the aliases 
 through the app deployment descriptors.  In tomcat 5 this works for *some* 
 apps that have been deployed.  The rest throw a 400 error saying no virtual 
 host has been configured.  The same apps mapped directly to the actual vhost 
 (not alias) do not throw this error.  The previous behavior can be useful for 
 builds which target multiple environments (stage/test/prod/etc).  Moreover it 
 should be preserverd for backward compatibility.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1300) Non-Remote JMS HA

[Andrew Oliver (JIRA)]

Non-Remote JMS HA
-

 Key: JBAS-1300
 URL: http://jira.jboss.com/jira/browse/JBAS-1300
 Project: JBoss Application Server
Type: Feature Request
  Components: JMS service  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


It should be possible to use JMS on all servers in a cluster with HA enabled.  
Meaning:

1. Database as a store.  Everyone node uses shared DB.
2. JMS_MESSAGES table includes node name
3. In the event of group membership changes another node picks up the old 
node's messages
4. JMS Client proxy autofails to another node


-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1301) Tomcat backward compatbility loss VirtualHost-Alias mapping

[Andrew Oliver (JIRA)]

Tomcat backward compatbility loss VirtualHost-Alias mapping


 Key: JBAS-1301
 URL: http://jira.jboss.com/jira/browse/JBAS-1301
 Project: JBoss Application Server
Type: Bug
  Components: Web (Tomcat) service  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 
Priority: Minor


In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set of 
Aliases in the jboss-service.xml and then map the webapps to the aliases 
through the app deployment descriptors.  In tomcat 5 this works for *some* apps 
that have been deployed.  The rest throw a 400 error saying no virtual host has 
been configured.  The same apps mapped directly to the actual vhost (not alias) 
do not throw this error.  The previous behavior can be useful for builds which 
target multiple environments (stage/test/prod/etc).  Moreover it should be 
preserverd for backward compatibility.

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1298) HAR Deployer JBCache config

[Andrew Oliver (JIRA)]

HAR Deployer  JBCache config


 Key: JBAS-1298
 URL: http://jira.jboss.com/jira/browse/JBAS-1298
 Project: JBoss Application Server
Type: Feature Request
  Components: Hibernate service  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


Presently HAR deployer picks up JBCache config from its classloader.  It does 
not use an MBean.  It should use an MBean (and we should be able to get stats 
from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1299) No production-quality Cache Invalidation framework for Hibernate 2nd level cache

[Andrew Oliver (JIRA)]

No production-quality Cache Invalidation framework for Hibernate 2nd level cache


 Key: JBAS-1299
 URL: http://jira.jboss.com/jira/browse/JBAS-1299
 Project: JBoss Application Server
Type: Feature Request
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


This is 50/50 Hibernate-JBC.  Presently Hiberante only supports one 
Cache-Invalidatable cache (Swarm) which isn't an ideal cache for running in 
JBossAS.  There are some data structures that lend themself for a 2 
configuration system.  Meaning I do read/write w/o 2nd level cache and reads 
from second level cache and send messages to evict members from second level 
cache (cluster-wide).  

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1302) Object Pooling considered harmful

[Andrew Oliver (JIRA)]

Object Pooling considered harmful
-

 Key: JBAS-1302
 URL: http://jira.jboss.com/jira/browse/JBAS-1302
 Project: JBoss Application Server
Type: Feature Request
  Components: EJBs  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


Object pooling is the enemy of highly concurrent garbage collection.  We should 
have a container for SLSB (and EJB3) that does not use object pooling but 
assumes a Servlet-like thread model.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1303) Field replication for session data

[Andrew Oliver (JIRA)]

Field replication for session data
--

 Key: JBAS-1303
 URL: http://jira.jboss.com/jira/browse/JBAS-1303
 Project: JBoss Application Server
Type: Feature Request
  Components: EJBs, JBoss Cache service, Web (Tomcat) service  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


We should have an AOP-ized fine grained session replication system.  Meaning if 
I stick a pojo into the session it should optionally break apart to its state 
and replicate accross the cluster through the deep object graph.  Same deal for 
SFSBs.

Thus

Customer cust = new Customer();
cust.setName(George W. Bush);
cust.setAddress(123 Don't call it Waco TX);
cust.setCity(Craford);
cust.setState(TX);

session.setAttribute(customer,cust);

cust.setAddress(1600 PA Ave);
cust.setCity(Washington);
cust.setState(DC);

should only replicate address/city/state and not serialize the whole object -- 
I should not have to call set Attribute().  Furthermore if Address had been a 
setter on customer and I only changed street then only street would replicate.

Lastly, it should be optional to transactionalize these for the scope of the 
replication (meaning I could say I really do want these transactional so that I 
send one message and not 3).

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBAS-1304) Abillity to add DB-specific hints into Hibernate

[Andrew Oliver (JIRA)]

Abillity to add DB-specific hints into Hibernate
--

 Key: JBAS-1304
 URL: http://jira.jboss.com/jira/browse/JBAS-1304
 Project: JBoss Application Server
Type: Feature Request
  Components: Hibernate service  
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
Reporter: Andrew Oliver
 Assigned to: Scott M Stark 


Customer has requested abillity to add hints to the underbelly of hibernate esp 
for use with MViews.

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-21) Mail Store tests should check to see if mysql driver is present

[Andrew Oliver (JIRA)]

Mail Store tests should check to see if mysql driver is present
---

 Key: JBMAIL-21
 URL: http://jira.jboss.com/jira/browse/JBMAIL-21
 Project: JBoss Mail
Type: Bug
Versions: 1.0-M3
Reporter: Andrew Oliver
 Assigned to: Andrew Oliver 
Priority: Critical
 Fix For: 1.0-M3


The MySQL driver is GPL and cannot be redistributed (without making JBMail also 
GPL) thus the unit tests should merely check to see if the driver is present, 
if it is not, they should WARN and continue without running the MYSQL dependent 
tests.

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-8) Hibernate Mailboxes

[Andrew Oliver (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBMAIL-8?page=comments#action_12314595 
]
 
Andrew Oliver commented on JBMAIL-8:


http://www.jboss.org/wiki/Wiki.jsp?page=MailServicesMilestone3HibernateMailboxImpelmentation

 Hibernate Mailboxes
 ---

  Key: JBMAIL-8
  URL: http://jira.jboss.com/jira/browse/JBMAIL-8
  Project: JBoss Mail
 Type: Feature Request
   Components: Mail Server APIs
 Versions: 1.0-M3
 Reporter: Andrew Oliver
 Assignee: Dawie Malan


 Original Estimate: 2 days
 Remaining: 2 days

 A new mail store implementation should be created which uses 
 Hibernate/JBossCache as the backend as opposed to entity beans.  

-- 
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



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development