date:20080714



2.0.6 is fine ... I only noticed the problems with 2.0.7.  Something 
must have changed that requires comparable Geronimo changes.


Joe


Daniel Kulp wrote:


Was 2.0.6 OK or did it have the same TCK issues?

Dan


On Jul 14, 2008, at 4:21 PM, Joe Bohn wrote:

FWIW, I did a quick check with CXF 2.0.7 and hit some issues with the 
TCK tests under Geronimo.  There must be some Geronimo changes 
necessary for this upgrade.  We'll hold-off upgrading to 2.0.7 for 
2.1.2 unless someone has a chance to look into the tck issues before 
out branch.


Joe


Joe Bohn wrote:
Should we be considering CXF 2.0.7 for Geronimo 2.1.2? Does anybody 
know of specific reasons to move to 2.0.7 or hold at 2.0.6?

Joe
Reference this portion of post by Dan Kulp on the user list:
 Original Message 
Subject: Re: Re: Re: Using WS-Security with Geronimo 2.1.1
Date: Tue, 8 Jul 2008 11:10:07 -0700 (PDT)
From: Daniel Kulp <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]>
Geronimo pretty much includes just the parts of CXF that are needed 
to pass
the JAX-WS parts of the TCK.   It doesn't include the "extra" things 
like
ws-addressing, ws-security, ws-rm, aegis databinding, etc
Geronimo

didn't need them so they didn't pull them in.
When adding the jar like that, keep in mind that you may need other
dependencies like wss4j, xml-sec, etc.. that ws-security requires 
that might

not be shipped with Geronimo.
One thing to keep in mind is that the CXF ws-security implementation 
(and
the Axis2/Rampart implementation as well) is based on WSS4J which 
isn't up
to WS-Security 1.1 level yet.   Some of the profiles it supports are 
"close"
to 1.1 levels, but for the most part, it's 1.0.   A note to the wss4j 
dev

list ([EMAIL PROTECTED]) would probably a good start to figure out
what wss4j supports.
That said, it would be great if Geronimo could update to CXF 2.0.7
(non-incubator) for a 2.1.2 release.





---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog

Re: CXF 2.0.7 for G 2.1.2? - [Fwd: Re: Re: Re: Using WS-Security with Geronimo 2.1.1]

2008-07-14 Thread Daniel Kulp

Was 2.0.6 OK or did it have the same TCK issues?

Dan

On Jul 14, 2008, at 4:21 PM, Joe Bohn wrote:

FWIW, I did a quick check with CXF 2.0.7 and hit some issues with  
the TCK tests under Geronimo.  There must be some Geronimo changes  
necessary for this upgrade.  We'll hold-off upgrading to 2.0.7 for  
2.1.2 unless someone has a chance to look into the tck issues before  
out branch.

Joe

Joe Bohn wrote:
Should we be considering CXF 2.0.7 for Geronimo 2.1.2? Does anybody  
know of specific reasons to move to 2.0.7 or hold at 2.0.6?

Joe
Reference this portion of post by Dan Kulp on the user list:
 Original Message 
Subject: Re: Re: Re: Using WS-Security with Geronimo 2.1.1
Date: Tue, 8 Jul 2008 11:10:07 -0700 (PDT)
From: Daniel Kulp <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]> <[EMAIL PROTECTED] 
> [EMAIL PROTECTED]> <[EMAIL PROTECTED] 
> [EMAIL PROTECTED]> <[EMAIL PROTECTED] 
> <[EMAIL PROTECTED]> <[EMAIL PROTECTED] 
>
Geronimo pretty much includes just the parts of CXF that are needed  
to pass
the JAX-WS parts of the TCK.   It doesn't include the "extra"  
things like
ws-addressing, ws-security, ws-rm, aegis databinding, etc 
Geronimo

didn't need them so they didn't pull them in.
When adding the jar like that, keep in mind that you may need other
dependencies like wss4j, xml-sec, etc.. that ws-security requires  
that might

not be shipped with Geronimo.
One thing to keep in mind is that the CXF ws-security  
implementation (and
the Axis2/Rampart implementation as well) is based on WSS4J which  
isn't up
to WS-Security 1.1 level yet.   Some of the profiles it supports  
are "close"
to 1.1 levels, but for the most part, it's 1.0.   A note to the  
wss4j dev
list ([EMAIL PROTECTED]) would probably a good start to  
figure out

what wss4j supports.
That said, it would be great if Geronimo could update to CXF 2.0.7
(non-incubator) for a 2.1.2 release.

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog

[jira] Closed: (GERONIMO-4099) Calling isUserInRole wipes out run-as info

2008-07-14 Thread David Jencks (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks closed GERONIMO-4099.
--

Resolution: Fixed

apparently causes no tck problems.

> Calling isUserInRole wipes out run-as info
> --
>
> Key: GERONIMO-4099
> URL: https://issues.apache.org/jira/browse/GERONIMO-4099
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.0.x, 2.1.x, 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1.2, 2.2
>
>
> TomcatGeronimoRealm.hasRole sets callers which it has no business doing.  
> These were already set during authentication.  This wipes out the run-as info 
> which was set earlier.  Checking the principal is also unrelated to role 
> checks in geronimo and should be omitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4207) Provide a LoginModule which can be used to add user or group principals via configuration


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevan Miller reassigned GERONIMO-4207:
--

Assignee: Kevan Miller

> Provide a LoginModule which can be used to add user or group principals via 
> configuration
> -
>
> Key: GERONIMO-4207
> URL: https://issues.apache.org/jira/browse/GERONIMO-4207
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: security
>Affects Versions: 2.1.2, 2.2
>Reporter: Kevan Miller
>Assignee: Kevan Miller
> Fix For: 2.1.2, 2.2
>
>
> In some cases, it would be helpful if user or group principals could be added 
> to an authenticated Subject. For instance, you may want any authenticated 
> LDAP user to have the capability to perform some action. However, LDAP may 
> not have a group that can be used for this purpose. A configurable login 
> module could be used to automatically add a user/group principals to the 
> Subject.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (GERONIMO-4207) Provide a LoginModule which can be used to add user or group principals via configuration


[ 
https://issues.apache.org/jira/browse/GERONIMO-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613459#action_12613459
 ] 

kevan edited comment on GERONIMO-4207 at 7/14/08 2:34 PM:
-

Committed module. Should add some doc to the Wiki.

In the meantime, adding something like the following to an existing 
LoginModuleConfiguration is a usage example...

{code}
  
  Constant
  
org.apache.geronimo.security.realm.providers.ConstantLoginModule
  authenticated
  group1,group2
  
{code}


  was (Author: kevan):
Committed module. Should add some doc to the Wiki.

In the meantime, adding something like the following to an existing 
LoginModuleConfiguration is a usage example...

   
   Constant
   
org.apache.geronimo.security.realm.providers.ConstantLoginModule
   authenticated
   group1,group2
   


  
> Provide a LoginModule which can be used to add user or group principals via 
> configuration
> -
>
> Key: GERONIMO-4207
> URL: https://issues.apache.org/jira/browse/GERONIMO-4207
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: security
>Affects Versions: 2.1.2, 2.2
>Reporter: Kevan Miller
> Fix For: 2.1.2, 2.2
>
>
> In some cases, it would be helpful if user or group principals could be added 
> to an authenticated Subject. For instance, you may want any authenticated 
> LDAP user to have the capability to perform some action. However, LDAP may 
> not have a group that can be used for this purpose. A configurable login 
> module could be used to automatically add a user/group principals to the 
> Subject.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4207) Provide a LoginModule which can be used to add user or group principals via configuration


[ 
https://issues.apache.org/jira/browse/GERONIMO-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613459#action_12613459
 ] 

Kevan Miller commented on GERONIMO-4207:


Committed module. Should add some doc to the Wiki.

In the meantime, adding something like the following to an existing 
LoginModuleConfiguration is a usage example...

   
   Constant
   
org.apache.geronimo.security.realm.providers.ConstantLoginModule
   authenticated
   group1,group2
   



> Provide a LoginModule which can be used to add user or group principals via 
> configuration
> -
>
> Key: GERONIMO-4207
> URL: https://issues.apache.org/jira/browse/GERONIMO-4207
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: security
>Affects Versions: 2.1.2, 2.2
>Reporter: Kevan Miller
> Fix For: 2.1.2, 2.2
>
>
> In some cases, it would be helpful if user or group principals could be added 
> to an authenticated Subject. For instance, you may want any authenticated 
> LDAP user to have the capability to perform some action. However, LDAP may 
> not have a group that can be used for this purpose. A configurable login 
> module could be used to automatically add a user/group principals to the 
> Subject.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4205) unable to build samples on windows platoform due to Filename too long

2008-07-14 Thread Lin Sun (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-4205:
--

Attachment: G4205new.zip

Here's a proposed patch to workaround this issue.  Basically rename
customer-service to customer
calculator-stateless-pojo to calculator
jms-mdb-sample to jms-mdb

With the patch I am able to build fine at "c:\geronimosample" as the sample 2.1 
root dir.

Steps to apply -

1. unzip the zip file.
2. apply G4025.patch
3. copy samples\* to your 2.1 sample checkout dir\samples.




> unable to build samples on windows platoform due to Filename too long
> -
>
> Key: GERONIMO-4205
> URL: https://issues.apache.org/jira/browse/GERONIMO-4205
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 2.1, 2.1.2
> Environment: winxp
>Reporter: Lin Sun
>Assignee: Lin Sun
> Fix For: 2.1.2
>
> Attachments: G4205new.zip
>
>
> Steps-
> 1. check out branch 2.1 samples 
> https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/ to a very 
> short dir c:\21sam
> 2. install G2.1 private repo
> 3. use maven 2.0.7 to build samples at c:\21sam dir.
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Could not scan module for TLD files: 
> customer-service-war-2.1-SNAPSHOT.wa
> r Filename too long
> [INFO] 
> 
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Could not scan module 
> fo
> r TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:564)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:480)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:459)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not scan 
> module
>  for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
> at 
> org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:
> 137)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:443)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.geronimo.common.DeploymentException: Could not scan 
> module
>  for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
> at 
> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.scanM
> odule(JspModuleBuilderExtension.java:297)
> at 
> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getTl
> dFiles(JspModuleBuilderExtension.java:238)
> at 
> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.creat
> eJspClassFinder(JspModuleBuilderExtension.java:179)
> at 
> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGB
> eans(JspModuleBuilderExtension.java:149)
> at 
> org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(Je
> ttyModuleBuilder.java:518)
> at 
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(
> SwitchingMod

[jira] Commented: (GERONIMO-4099) Calling isUserInRole wipes out run-as info

2008-07-14 Thread Joe Bohn (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613453#action_12613453
 ] 

Joe Bohn commented on GERONIMO-4099:


I verified tck results with rev. 674565 and didn't notice any problems.  Can we 
close this issue?

> Calling isUserInRole wipes out run-as info
> --
>
> Key: GERONIMO-4099
> URL: https://issues.apache.org/jira/browse/GERONIMO-4099
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.0.x, 2.1.x, 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1.2, 2.2
>
>
> TomcatGeronimoRealm.hasRole sets callers which it has no business doing.  
> These were already set during authentication.  This wipes out the run-as info 
> which was set earlier.  Checking the principal is also unrelated to role 
> checks in geronimo and should be omitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Geronimo 2.1.2 branch reminder

Just a reminder that we're still planning to branch for a Geronimo 2.1.2 
release a week from today (7/21).  Please plan to have any fixes 
integrated by that time or notify the list if there is a concern with 
the branch date.


The only outstanding required item prior to the branch that I am aware 
of is integrating the newly released version of Javamail.  Anything else 
is a best attempt effort by next week.  Please reference the wiki and 
update as appropriate with status:

http://cwiki.apache.org/GMOxPMGT/geronimo-212-release-plan.html

BTW, I've recently verified legal files and did an interim check of tck 
with favorable results.


As we get closer to a release please be extra-careful integrating fixes 
and don't forget to mirror appropriate changes into trunk.


Thanks,
Joe

Re: CXF 2.0.7 for G 2.1.2? - [Fwd: Re: Re: Re: Using WS-Security with Geronimo 2.1.1]

FWIW, I did a quick check with CXF 2.0.7 and hit some issues with the 
TCK tests under Geronimo.  There must be some Geronimo changes necessary 
for this upgrade.  We'll hold-off upgrading to 2.0.7 for 2.1.2 unless 
someone has a chance to look into the tck issues before out branch.


Joe


Joe Bohn wrote:
Should we be considering CXF 2.0.7 for Geronimo 2.1.2? Does anybody know 
of specific reasons to move to 2.0.7 or hold at 2.0.6?


Joe

Reference this portion of post by Dan Kulp on the user list:

 Original Message 
Subject: Re: Re: Re: Using WS-Security with Geronimo 2.1.1
Date: Tue, 8 Jul 2008 11:10:07 -0700 (PDT)
From: Daniel Kulp <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]>



Geronimo pretty much includes just the parts of CXF that are needed to pass
the JAX-WS parts of the TCK.   It doesn't include the "extra" things like
ws-addressing, ws-security, ws-rm, aegis databinding, etcGeronimo
didn't need them so they didn't pull them in.

When adding the jar like that, keep in mind that you may need other
dependencies like wss4j, xml-sec, etc.. that ws-security requires that 
might

not be shipped with Geronimo.

One thing to keep in mind is that the CXF ws-security implementation (and
the Axis2/Rampart implementation as well) is based on WSS4J which isn't up
to WS-Security 1.1 level yet.   Some of the profiles it supports are 
"close"

to 1.1 levels, but for the most part, it's 1.0.   A note to the wss4j dev
list ([EMAIL PROTECTED]) would probably a good start to figure out
what wss4j supports.

That said, it would be great if Geronimo could update to CXF 2.0.7
(non-incubator) for a 2.1.2 release.

[RESULT][VOTE] Release javamail spec 1.5 and javamail providers 1.5


Heh. Done that before...

For the record, there were also +1 votes (possibly belated) in the  
vote thread from:


Jay McHugh
Jason Warner
Davanum Srinivas
Guillaume Nodet

--kevan
On Jul 14, 2008, at 3:10 PM, Rick McGuire wrote:

Hmmm, I did...but without noticing that when I selected my original  
email for a Reply, it only sent it to me!  Here's the one I thought  
I sent last Friday.


The vote for releasing the new javamail version has passed with 6 +1  
votes, and no 0 or -1 votes.  Voting in favor were


Dan Becker
Joe Bohn
Donald Woods
Jarek Gawor
Vamsavardhana Reddy
Rick McGuire

I will be uploading to the repository today, and will update the  
Geronimo code bases to point to the new version once it has  
propagated to central.

Rick



Kevan Miller wrote:

Rick,
Please send a [RESULT] note, if this vote has concluded.
On Jul 8, 2008, at 9:21 AM, Rick McGuire wrote:

This is a vote for a combined release of javamail spec and the  
javamail provider (+ the uber jar).  The provider changes have  
depedencies on the spec changes, so these need to be released at  
the same time.  Geronimo will need the updated uber jar for the  
2.1.2 release.


The components up for release are

geronimo-javamail_1.4_spec-1.4
geronimo-javamail_1.4-1.5
geronimo-javamail_1.4_provider-1.5
geronimo-javamail_1.4_mail-1.5(uber jar containing spec 
+providers)


This release contains a number of bug fixes uncovered by building/ 
running Apache James using the Geronimo javamail version.  With  
this release, James can be built and deployed using either the Sun  
version or the Geronimo version.


In addition to the James fixes, several enhancements have been  
added:


Sun javamail 1.4.1 compatibility:
Added support for mail..ssl.protocols and  
mail..ssl.ciphersuites properties.

MimeMessage.reply() now sets the In-Reply-To and References headers

Added SSL support to the NTTP Transport and Store.


Staging repo:
http://people.apache.org/~rickmcguire/staging-repo/ 


The svn locations are here:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.4
https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.5


The vote is open for 72 hours and will conclude on Thursday (7/10)  
at 10:00 AMET.


[ ] +1  Release the javamail spec and provider
[ ] +0  No opinion
[ ] -1  Don't release the javamail spec and provider


Rick

Re: Removing specific sample references on the Welcome Page?


Joe Bohn wrote:
The Geronimo welcome page (http://localhost:8080/) has long included 
links under a header of Geronimo Examples.


Under this header are the following 3 links:
- Servlet Examples
- JSP Examples
- LDAP Demo
- Additional Samples


I'd like to remove the first 3 links and rename the last link to simply 
"Samples" for trunk and branches/2.1 (prior to the 2.1.2 release).  The 
last link takes you to a page  on our wiki that lists doc links for the 
samples per release ... I think that is more appropriate.


The first 3 links present another html page from the local server that 
contains text similar to this:
This sample has not been installed yet. If this server can connect to 
the internet, click here to install and connect to the sample 
application. It will take a few minutes to download and install the 
sample and then load it.


Those 3 links present some problems (and currently don't work for 2.1 or 
2.1.1 that have already been released).
- Clicking the install link attempts to connect to a repository and 
initiate a install of the specified sample.
- The repository is not always as desired.  For me it defaults to my 
local maven2 repo.
- The current component IDs are incorrect.  That's easy enough to change 
but I suspect there would still be issues (see the next points).
- Even if it linked to the correct repo for the release, there would 
still be a period of time after a server release when the samples are 
not yet available in the repository.
- The LDAP demo requires some additional setup now because we no longer 
include Directory in the initial server image ... hence this gives a 
false impression that simply clicking on the link will make the example 
functional.


Given these problem and the fact that is has been broken for several 
releases. I'd like to remove the specific server example links from the 
welcome page before we ship 2.1.2.  Any objections?


Joe




It seems like the consensus is to remove the specific example links. 
I've created https://issues.apache.org/jira/browse/GERONIMO-4208 for 
this purpose.


Thanks,
Joe

[jira] Created: (GERONIMO-4208) Eliminate individual sample references from Geronimo Welcome Page

2008-07-14 Thread Joe Bohn (JIRA)

Eliminate individual sample references from Geronimo Welcome Page
-

Key: GERONIMO-4208
URL: https://issues.apache.org/jira/browse/GERONIMO-4208
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.1.2, 2.2
Reporter: Joe Bohn
Assignee: Joe Bohn
Fix For: 2.1.2, 2.2

Currently there is an issue with the specific samples listed in the Geronimo
Welcome Page. The 3 samples are the Servlet Examples, JSP Examples, and the
LDAP demo. In addition to this there is a link to the wiki pages describing
the complete set of samples. These samples present several problems and
therefore should be removed for the following reasons:
1) There is always a period of time when the links to install the samples will
not work because the samples themselves are not yet released. It is necessary
that the samples are released after the server release.
2) The LDAP demo requires a directory implementation either install in Geronimo
or external to Geronimo. In the past this was not an issue because directory
was embedded in the Geronimo server. However, that has since been removed and
is delivered as an independent plugin.
3) It is implied that the samples are readily available with the server image
by having them directly referenced on the welcome page. However, the samples
are not included in the server image. Therefore, even if the samples are
already published they still require network connectivity to download and
install.

Rather than include these specific samples with links we will instead just
include the link to the wiki pages with direction for installing and working
with the samples.

This was discussed on the Geronimo dev list:
http://www.nabble.com/Removing-specific-sample-references-on-the-Welcome-Page--td18386822s134.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-4207) Provide a LoginModule which can be used to add user or group principals via configuration

Provide a LoginModule which can be used to add user or group principals via 
configuration
-

 Key: GERONIMO-4207
 URL: https://issues.apache.org/jira/browse/GERONIMO-4207
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: security
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
 Fix For: 2.1.2, 2.2


In some cases, it would be helpful if user or group principals could be added 
to an authenticated Subject. For instance, you may want any authenticated LDAP 
user to have the capability to perform some action. However, LDAP may not have 
a group that can be used for this purpose. A configurable login module could be 
used to automatically add a user/group principals to the Subject.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Geronimo trunk build failure with fresh OpenEjb trunk build

2008-07-14 Thread Rick McGuire


David Blevins wrote:


On Jul 10, 2008, at 1:17 PM, Joe Bohn wrote:

If I build Geronimo trunk using the latest OpenEjb snapshots 
(published around 6/27-28) things build fine.  However, if I grab 
OpenEjb trunk and build it locally (to get the latest image) I get 
build failures (NoClassDefFoundError) in the Geronimo MEJB config.  I 
suspect we need to make some changes to accommodate the Singleton 
Session Beans implementation.  Is this complete yet and is anybody 
looking into the necessary Geronimo changes?


We'd need to get this dep in the right place if we wanted to keep 
using OpenEJB trunk:



  org.apache.openejb
  ejb31-api-experimental
  ${openejbVersion}


These two poms seem to be the only places where the ejb 3.0 spec jar 
is used:


 ./framework/configs/jee-specs/pom.xml
 ./framework/modules/geronimo-j2ee/pom.xml

I'm fine giving it a shot if no one objects to being dependent on a 
non-final spec jar.  We might try it out and see if the tck complains 
at least.
I needed to do this to get a clean build using the latest, and it's a 
lot more than just those two poms that needed updating.  I'm going to 
try doing some tck runs to see how things look.


Rick




-David


---
[INFO] Building Geronimo Plugins, MEJB :: Config
[INFO]task-segment: [install]
[INFO] 


[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: 
/home/jbohn/geronimo/plugins/mejb/mejb/target/resources/META-INF/plan.xml 


[INFO] [car:package]
[INFO] Packaging module configuration: 
/home/jbohn/geronimo/plugins/mejb/mejb/target/resources/META-INF/plan.xml 

[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[INFO] Started deployer: 
org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car
14:13:36,387 INFO  [config] Configuring Service(id=Default Stateless 
Container, type=Container, provider-id=Default Stateless Cont

ainer)
14:13:36,392 INFO  [config] Configuring Service(id=Default Stateful 
Container, type=Container, provider-id=Default Stateful Contai

ner)
14:13:36,393 INFO  [config] Configuring Service(id=Default BMP 
Container, type=Container, provider-id=Default BMP Container)
14:13:36,394 INFO  [config] Configuring Service(id=Default CMP 
Container, type=Container, provider-id=Default CMP Container)
14:13:36,402 INFO  [config] Configuring enterprise application: 
org.apache.geronimo.configs/mejb/2.2-SNAPSHOT/car

[ERROR] Deployment failed due to
java.lang.NoClassDefFoundError: javax/ejb/Singleton
org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:339) 

org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:230) 

org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:174) 

org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:228) 

org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:584) 

org.apache.geronimo.openejb.deployment.EjbModuleBuilder.configureApplication(EjbModuleBuilder.java:645)

Re: more exposure for LICENSE and NOTICE files?

2008-07-14 Thread Ted Kirby

On Mon, Jul 14, 2008 at 2:19 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Ted Kirby wrote:
>>>
>>> From our server release download pages, I see no reference to the
>>
>> license under which the server is released.  There is a link to
>> release notes, but it does not mention the information either.  The
>> legal information is collected in the LICENSE and NOTICE files.
>> Shouldn't we provide some link to it?  I would particularly like to
>> see these files in http://www.apache.org/dist/geronimo/2.1.1/.
>
> It wouldn't be difficult to add a copy of the LICENSE.txt and NOTICE.txt
> there. However, our official statement is what is included within each
> distribution item.  If we were to include something at the distribution
> level I suppose it would have match what we include in the server images
> (which I think is the most all-inclusive).  It might be a problem keeping
> these in sync.

Good point.  It does seem that a distribution should contain the
LICENSE and NOTICE  files of the components of which it is composed.
It would be nice if this were automated.  Is it?  For 2.1.1, it seems
these files match for the jetty and tomcat distributions, which is
surprising.  I don't think Jetty and CXF should be mentioned in the
tomcat distribution versions.  On the other hand, going with these
current versions as the most all-inclusive on the web site would
accomplish what I'm after.

>> I've been doing a lot of work lately on these files so they get
>> displayed properly in GEP.  Eclipse, particularly the Update Manager,
>> has many facilities for displaying this information.  If these files
>> were on the web site, it would make things easier in GEP, especially
>> for https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-416 Add
>> click-through license screen to Download and Install path.
>
> Could we pull the license info from the jar/zip itself?  That is really the
> requirement for our distribution and would eliminate any possibility of
> things getting out of sync.

I found a method to get this information from the feature, which is
good for the specific JIRA.  I'd like to have the files somewhere such
that a browser can view them.  I don't think this will work for the
files inside a jar/zip file.

Thanks.

>>
>> Ted Kirby
>>
>
>

Re: [VOTE] Release javamail spec 1.5 and javamail providers 1.5

2008-07-14 Thread Rick McGuire

Hmmm, I did...but without noticing that when I selected my original 
email for a Reply, it only sent it to me!  Here's the one I thought I 
sent last Friday.


The vote for releasing the new javamail version has passed with 6 +1 
votes, and no 0 or -1 votes.  Voting in favor were


Dan Becker
Joe Bohn
Donald Woods
Jarek Gawor
Vamsavardhana Reddy
Rick McGuire

I will be uploading to the repository today, and will update the 
Geronimo code bases to point to the new version once it has propagated 
to central.

Rick



Kevan Miller wrote:

Rick,
Please send a [RESULT] note, if this vote has concluded.
On Jul 8, 2008, at 9:21 AM, Rick McGuire wrote:

This is a vote for a combined release of javamail spec and the 
javamail provider (+ the uber jar).  The provider changes have 
depedencies on the spec changes, so these need to be released at the 
same time.  Geronimo will need the updated uber jar for the 2.1.2 
release.


The components up for release are

geronimo-javamail_1.4_spec-1.4
geronimo-javamail_1.4-1.5
geronimo-javamail_1.4_provider-1.5
geronimo-javamail_1.4_mail-1.5(uber jar containing spec+providers)

This release contains a number of bug fixes uncovered by 
building/running Apache James using the Geronimo javamail version. 
 With this release, James can be built and deployed using either the 
Sun version or the Geronimo version.


In addition to the James fixes, several enhancements have been added:

Sun javamail 1.4.1 compatibility:
 Added support for mail..ssl.protocols and 
mail..ssl.ciphersuites properties.

 MimeMessage.reply() now sets the In-Reply-To and References headers

Added SSL support to the NTTP Transport and Store.


Staging repo:
http://people.apache.org/~rickmcguire/staging-repo/ 



The svn locations are here:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.4
https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.5 




The vote is open for 72 hours and will conclude on Thursday (7/10) at 
10:00 AMET.


[ ] +1  Release the javamail spec and provider
[ ] +0  No opinion
[ ] -1  Don't release the javamail spec and provider


Rick

Re: more exposure for LICENSE and NOTICE files?


Ted Kirby wrote:

From our server release download pages, I see no reference to the

license under which the server is released.  There is a link to
release notes, but it does not mention the information either.  The
legal information is collected in the LICENSE and NOTICE files.
Shouldn't we provide some link to it?  I would particularly like to
see these files in http://www.apache.org/dist/geronimo/2.1.1/.


It wouldn't be difficult to add a copy of the LICENSE.txt and NOTICE.txt 
there. However, our official statement is what is included within each 
distribution item.  If we were to include something at the distribution 
level I suppose it would have match what we include in the server images 
(which I think is the most all-inclusive).  It might be a problem 
keeping these in sync.




I've been doing a lot of work lately on these files so they get
displayed properly in GEP.  Eclipse, particularly the Update Manager,
has many facilities for displaying this information.  If these files
were on the web site, it would make things easier in GEP, especially
for https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-416 Add
click-through license screen to Download and Install path.


Could we pull the license info from the jar/zip itself?  That is really 
the requirement for our distribution and would eliminate any possibility 
of things getting out of sync.




Ted Kirby

Re: [VOTE] Release javamail spec 1.5 and javamail providers 1.5


Rick,
Please send a [RESULT] note, if this vote has concluded.
On Jul 8, 2008, at 9:21 AM, Rick McGuire wrote:

This is a vote for a combined release of javamail spec and the  
javamail provider (+ the uber jar).  The provider changes have  
depedencies on the spec changes, so these need to be released at the  
same time.  Geronimo will need the updated uber jar for the 2.1.2  
release.


The components up for release are

geronimo-javamail_1.4_spec-1.4
geronimo-javamail_1.4-1.5
geronimo-javamail_1.4_provider-1.5
geronimo-javamail_1.4_mail-1.5(uber jar containing spec+providers)

This release contains a number of bug fixes uncovered by building/ 
running Apache James using the Geronimo javamail version.  With this  
release, James can be built and deployed using either the Sun  
version or the Geronimo version.


In addition to the James fixes, several enhancements have been added:

Sun javamail 1.4.1 compatibility:
 Added support for mail..ssl.protocols and  
mail..ssl.ciphersuites properties.

 MimeMessage.reply() now sets the In-Reply-To and References headers

Added SSL support to the NTTP Transport and Store.


Staging repo:
http://people.apache.org/~rickmcguire/staging-repo/

The svn locations are here:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.4
https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.5


The vote is open for 72 hours and will conclude on Thursday (7/10)  
at 10:00 AMET.


[ ] +1  Release the javamail spec and provider
[ ] +0  No opinion
[ ] -1  Don't release the javamail spec and provider


Rick

[jira] Resolved: (GERONIMO-3665) Create ghell commands for wsgen and wsimport tools

2008-07-14 Thread Jarek Gawor (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-3665.
---

Resolution: Fixed

Committed changes to trunk (revision 67) and branches/2.1 (revision 676667) 
that register the wsgen/wsimport commands with GShell. It's kind of a hacky 
solution but it works. 
Hopefully, in the future there will be an easier way to register new commands 
with the GShell runtime that will make this hack unnecessary.


> Create ghell commands for wsgen and wsimport tools
> --
>
> Key: GERONIMO-3665
> URL: https://issues.apache.org/jira/browse/GERONIMO-3665
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 2.1.2, 2.2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release javamail spec 1.5 and javamail providers 1.5

2008-07-14 Thread Jay D. McHugh


my late +1

Jay

Rick McGuire wrote:
This is a vote for a combined release of javamail spec and the javamail 
provider (+ the uber jar).  The provider changes have depedencies on the 
spec changes, so these need to be released at the same time.  Geronimo 
will need the updated uber jar for the 2.1.2 release.


The components up for release are

geronimo-javamail_1.4_spec-1.4
geronimo-javamail_1.4-1.5
geronimo-javamail_1.4_provider-1.5
geronimo-javamail_1.4_mail-1.5(uber jar containing spec+providers)

This release contains a number of bug fixes uncovered by 
building/running Apache James using the Geronimo javamail version.  With 
this release, James can be built and deployed using either the Sun 
version or the Geronimo version.


In addition to the James fixes, several enhancements have been added:

Sun javamail 1.4.1 compatibility:
  Added support for mail..ssl.protocols and 
mail..ssl.ciphersuites properties.

  MimeMessage.reply() now sets the In-Reply-To and References headers

Added SSL support to the NTTP Transport and Store.


Staging repo:
http://people.apache.org/~rickmcguire/staging-repo/

The svn locations are here:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.4 

https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.5 




The vote is open for 72 hours and will conclude on Thursday (7/10) at 
10:00 AMET.


[ ] +1  Release the javamail spec and provider
[ ] +0  No opinion
[ ] -1  Don't release the javamail spec and provider


Rick

[jira] Created: (GERONIMO-4206) Run geronimo embedded

2008-07-14 Thread David Jencks (JIRA)

Run geronimo embedded
-

 Key: GERONIMO-4206
 URL: https://issues.apache.org/jira/browse/GERONIMO-4206
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: kernel
Affects Versions: 2.2
Reporter: David Jencks


We should figure out how to run geronimo embedded and provide instructions in 
the docs.

I think what's needed is to either make the DaemonCLI constructor public or 
make a new class that doesn't call System.exit() when its done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-275) Eclipse does not allow to download Apache Geronimo

2008-07-14 Thread Ted Kirby (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613355#action_12613355
 ] 

Ted Kirby commented on GERONIMODEVTOOLS-275:


With Tim's help, I just updated 
http://www.apache.org/dist/geronimo/eclipse/updates/site.xml, which had bad 
entries for 2.1.1 tomcat and jetty servers.

> Eclipse does not allow to download  Apache Geronimo
> ---
>
> Key: GERONIMODEVTOOLS-275
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
> Environment: Windows XP, GEP 2.0, WTP 201 all in one
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> I have WTP 201 all in one with Eclipse plugin installed over it. While trying 
> to add a new server, Eclipse prompts to download and install the server. 
> While trying to do this I am not able to select DOWNLOAD and INSTALL Option. 
> It seems that eclipse has hanged but guess the check boxes and the Buttons 
> are not enabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sainath Chowdary updated GERONIMODEVTOOLS-434:
--

Attachment: jmxquery-sampleoutput.txt

"jmxquery-sampleoutput.txt" file shows the sample output retrieved from 
Geronimo v2.1 ruuning from eclipse workspace

> Query Dynamic Information from Server using JMX
> ---
>
> Key: GERONIMODEVTOOLS-434
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Shiva Kumar H R
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicquery-modified.patch, 
> jmx-dynamicserverinfo.patch, jmxquery-sampleoutput.txt
>
>
> Enabling GEP to query server for dynamic information on the lines of 
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on 
> server side that sends data to GEP. This has severe exceptions when a old 
> server is added or custom server assemblies are added to GEP which wont have 
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
> Destination references) from Server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sainath Chowdary updated GERONIMODEVTOOLS-434:
--

Attachment: jmx-dynamicquery-modified.patch

This patch corrects the part of listEJBModules() to get Deployed EJBS instead 
of getting deeployed EJB Modules

> Query Dynamic Information from Server using JMX
> ---
>
> Key: GERONIMODEVTOOLS-434
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Shiva Kumar H R
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicquery-modified.patch, 
> jmx-dynamicserverinfo.patch
>
>
> Enabling GEP to query server for dynamic information on the lines of 
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on 
> server side that sends data to GEP. This has severe exceptions when a old 
> server is added or custom server assemblies are added to GEP which wont have 
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
> Destination references) from Server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-275) Eclipse does not allow to download Apache Geronimo

2008-07-14 Thread Ted Kirby (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613345#action_12613345
 ] 

Ted Kirby commented on GERONIMODEVTOOLS-275:


http://www.apache.org/dist/geronimo/eclipse/updates/site.xml is bad, for 2.1 
servers.  I fixed this in site.xml with rev 675683, but it needs to be deployed 
to the production website.  Can you do this Tim?

> Eclipse does not allow to download  Apache Geronimo
> ---
>
> Key: GERONIMODEVTOOLS-275
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
> Environment: Windows XP, GEP 2.0, WTP 201 all in one
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> I have WTP 201 all in one with Eclipse plugin installed over it. While trying 
> to add a new server, Eclipse prompts to download and install the server. 
> While trying to do this I am not able to select DOWNLOAD and INSTALL Option. 
> It seems that eclipse has hanged but guess the check boxes and the Buttons 
> are not enabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: For which server version(s) should we release samples?



The consensus is that we should release samples for 2.1.2 and not for 
the prior releases.  Hence, the issue that was identified for a 2.1.2 
Server release regarding samples will be resolved by releasing the 
samples specifically for the 2.1.2 server (and therefore there are no 
compatibility issues attempting to run 2.1 or 2.1.1 samples on a 2.1.2 
server).  I have updated the our 2.1.2 plan in the wiki to indicate this 
item is resolved.


http://cwiki.apache.org/GMOxPMGT/geronimo-212-release-plan.html

Thanks,
Joe



Joe Bohn wrote:
We've been going back and forth on samples now for some time.  There are 
multiple reasons why the samples are not yet released -- but one of them 
has to do with compatibility for the 2.1.x releases.


Up until now I've been assuming that we would release samples for 2.1 
for the sake of completeness and ensure that we can get those same 
samples working on 2.1.1 and 2.1.2+.  If it wasn't possible to get the 
same samples working on higher releases then I figured we would release 
2.1.1 and 2.1.2+ versions of the samples.  Now, I'm starting to wonder 
if it is worth the effort to release samples for anything other than 2.1.2.


Here are the facts:
- We can add artifact-alias entries to get 2.1 samples working on a 
2.1.2 server or even a 2.2 server.
- A fix was required for the alias processing which was not included in 
2.1.1.  Therefore, if we release samples for 2.1 we will not be able to 
run them on 2.1.1 - but we could run them on 2.1.2 (when released). That 
seems like a strange scenario - 2.1 ok, 2.1.2 no, 2.1.2 ok.  If we 
release 2.1.1 samples in addition to 2.1 then which of those do we point 
users to leverage on 2.1.2?  IMO it would be clearer to say we support 
2.1.2+.
- Is there a strong need for samples on older releases or are they 
primarily of value on the latest release?  As Lin pointed out to me, 
users looking at samples will most likely be working with our latest 
release.  If we release samples for 2.1/2.1.1 will anybody actually use 
them (assuming we release 2.1.2 and follow that up quickly with the 
samples for 2.1.2)?


So these are the obvious choices:
1) Release samples for 2.1.  Release another version of samples for 
2.1.1.  Then either release samples for 2.1.2 or include alias entries 
in the 2.1.2 server so that the 2.1/2.1.1 samples will work on 2.1.2.

OR
2) Release samples for 2.1.  Skip 2.1.1.  Add artifact aliases to 
support the 2.1 samples on 2.1.2 and document that we don't support 
samples on 2.1.1.

OR
3) Release samples for 2.1.2 and then address any future 2.1.x releases 
with artifact aliases.  Point users that want to leverage samples to do 
so on 2.1.2+ and document that we don't support samples on 2.1 or 2.1.1.


There are a few potential issues with option #3:
- The ldap sample requires directory server to be installed on G or the 
use of an external LDAP server.  The recommended approach for the 
installed directory server is to install the Directory plugin.  However, 
this plugin is currently only released for a G 2.1 server.  We would 
need to either release a new version of the Directory plugin or do the 
compatibility trick with aliases again for 2.1.2.
- The 2.1 & 2.1.1 welcome page references to the jsp, servlet, and 
ldap-sample examples will never work.  Actually, they won't work even if 
we release 2.1 & 2.1.1 samples unless we want to change the 
groupid/module names of these samples back to the original names prior 
to a release of them (which I doubt we would want to do).


Any other issues, recommendations, or thoughts?

Joe

[jira] Commented: (GERONIMODEVTOOLS-275) Eclipse does not allow to download Apache Geronimo

2008-07-14 Thread Ted Kirby (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613339#action_12613339
 ] 

Ted Kirby commented on GERONIMODEVTOOLS-275:


I just noticed this old JIRA.  As far as I know, "Download and Install" works.  
Please identify outstanding issues/problems you are trying to fix.  
See   in 
plugins/oag.st.v2x.core/plugins.xml, in conjunction with site.xml for the 
location of the server.

> Eclipse does not allow to download  Apache Geronimo
> ---
>
> Key: GERONIMODEVTOOLS-275
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
> Environment: Windows XP, GEP 2.0, WTP 201 all in one
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> I have WTP 201 all in one with Eclipse plugin installed over it. While trying 
> to add a new server, Eclipse prompts to download and install the server. 
> While trying to do this I am not able to select DOWNLOAD and INSTALL Option. 
> It seems that eclipse has hanged but guess the check boxes and the Buttons 
> are not enabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-426) importing GEP feature plugins gives errors when building workspace

2008-07-14 Thread B.J. Reed (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1261#action_1261
 ] 

B.J. Reed commented on GERONIMODEVTOOLS-426:


Thanks Ted, I got a fresh everything this morning and no problems showed up.

> importing GEP feature plugins gives errors when building workspace
> --
>
> Key: GERONIMODEVTOOLS-426
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-426
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: Eclipse Ganymede
>Reporter: B.J. Reed
>Assignee: Ted Kirby
>Priority: Minor
> Fix For: 2.1.2
>
>
> I am trying to import the latest plugins and features into Eclipse.  When 
> importing the features, I get the following error messages when the workspace 
> builds:
> Errors during build.
>   Errors running builder 'Integrated External Tool Builder' on project 
> 'org.apache.geronimo.feature'.
>   The builder launch configuration could not be found.
>   Errors running builder 'Integrated External Tool Builder' on project 
> 'org.apache.geronimo.v20.feature'.
>   The builder launch configuration could not be found.
>   Errors running builder 'Integrated External Tool Builder' on project 
> 'org.apache.geronimo.v21.feature'.
>   The builder launch configuration could not be found.
> On the plus side, it appears that everything is working normally after I 
> close the Problem Window.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-275) Eclipse does not allow to download Apache Geronimo

2008-07-14 Thread Ashish Jain (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613331#action_12613331
 ] 

Ashish Jain commented on GERONIMODEVTOOLS-275:
--

Moving ahead with this issue. It seems there are two places where the code is 
broken.
1) Path problem
2) Download of geronimo

1 has been fixed and I donot see any error message regarding invalid path. 
However still to figure out how do we set the download link for geronimo. It 
seems features.xml 
in org.apache.geronimo.installableruntime.tomcat.feature is the one where we 
set fields for geronimo downloads. The content are as follows


   http://geronimo.apache.org/";>
%description
   

   http://www.apache.org/licenses/LICENSE-2.0.html";>
%copyright
   

   http://www.apache.org/licenses/LICENSE-2.0.html";>
%license
   
   
   
   
  
   

   



> Eclipse does not allow to download  Apache Geronimo
> ---
>
> Key: GERONIMODEVTOOLS-275
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-275
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
> Environment: Windows XP, GEP 2.0, WTP 201 all in one
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> I have WTP 201 all in one with Eclipse plugin installed over it. While trying 
> to add a new server, Eclipse prompts to download and install the server. 
> While trying to do this I am not able to select DOWNLOAD and INSTALL Option. 
> It seems that eclipse has hanged but guess the check boxes and the Buttons 
> are not enabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: jetty assembly deadlock (trunk only)



On Jul 10, 2008, at 10:48 AM, Jarek Gawor wrote:


It seems that once per day one of the automatic trunk builds deadlocks
in the following way (this only happens with the Jetty assembly):

Is anybody else seeing this too? We've had similar problems like  
this before...


I've not seen a deadlock like this, before. The previous ClassLoader  
deadlocks that I recall have involved TransformerCollections and the  
Finalizer thread (these should be fixed).


It looks like AspectJ is breaking the acyclic nature of our DAG  
ClassLoader structure -- causing monitors to be obtained out-of-order  
(making deadlocks a possibility). I haven't located the source for  
org.aspectj.weaver.loadtime.Aj.preProcess(Aj.java:73), which appears  
to be the source of the problem. So, don't yet fully understand the  
problem, or how to avoid...


--kevan




Found one Java-level deadlock:
=
"RMI TCP Connection(4)-9.42.75.229":
 waiting to lock monitor 0x0808c7fc (object 0xd1418d38, a
org.apache.geronimo.kernel.config.MultiParentClassLoader),
 which is held by "main"
"main":
 waiting to lock monitor 0x0808c83c (object 0xd16967d8, a
org.apache.geronimo.kernel.config.MultiParentClassLoader),
 which is held by "RMI TCP Connection(4)-9.42.75.229"

Java stack information for the threads listed above:
===
"RMI TCP Connection(4)-9.42.75.229":
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader 
.loadClassInternal(MultiParentClassLoader.java:449)

   - waiting to lock <0xd1418d38> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:501)

   - locked <0xd169c118> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader 
.loadClassInternal(MultiParentClassLoader.java:459)

   - locked <0xd169c118> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:501)

   - locked <0xd16967d8> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader 
.loadClassInternal(MultiParentClassLoader.java:459)

   - locked <0xd16967d8> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:501)

   - locked <0xd1530c78> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader 
.loadOptimizedClass(MultiParentClassLoader.java:410)

   - locked <0xd1530c78> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java: 
281)

   - locked <0xd1530c78> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java: 
319)

   - locked <0xd1530c78> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java: 
62)
   at  
javax 
.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java: 
214)
   at  
javax 
.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at  
sun 
.reflect 
.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at  
sun 
.reflect 
.DelegatingMethodAccessorImpl 
.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:585)
   at  
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)

   at sun.rmi.transport.Transport$1.run(Transport.java:153)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
   at  
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java: 
466)
   at sun.rmi.transport.tcp.TCPTransport 
$ConnectionHandler.run(TCPTransport.java:707)

   at java.lang.Thread.run(Thread.java:595)
"main":
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader 
.loadClassInternal(MultiParentClassLoader.java:449)

   - waiting to lock <0xd16967d8> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
org 
.apache 
.geronimo 
.kernel 
.config 
.MultiParentClassLoader.checkParents(MultiParentClassLoader.java:501)

   - locked <0xd16aaa28> (a
org.apache.geronimo.kernel.config.MultiParentClassLoader)
   at  
o

[jira] Created: (GERONIMO-4205) unable to build samples on windows platoform due to Filename too long

2008-07-14 Thread Lin Sun (JIRA)

unable to build samples on windows platoform due to Filename too long
-

 Key: GERONIMO-4205
 URL: https://issues.apache.org/jira/browse/GERONIMO-4205
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: sample apps
Affects Versions: 2.1, 2.1.2
 Environment: winxp
Reporter: Lin Sun
Assignee: Lin Sun
 Fix For: 2.1.2


Steps-


1. check out branch 2.1 samples 
https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/ to a very short 
dir c:\21sam
2. install G2.1 private repo
3. use maven 2.0.7 to build samples at c:\21sam dir.

[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.wa
r Filename too long

[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Could not scan module fo
r TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:564)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not scan module
 for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
at org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:
137)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.geronimo.common.DeploymentException: Could not scan module
 for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long
at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.scanM
odule(JspModuleBuilderExtension.java:297)
at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getTl
dFiles(JspModuleBuilderExtension.java:238)
at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.creat
eJspClassFinder(JspModuleBuilderExtension.java:179)
at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGB
eans(JspModuleBuilderExtension.java:149)
at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(Je
ttyModuleBuilder.java:518)
at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(
SwitchingModuleBuilder.java:165)
at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfigurati
on(EARConfigBuilder.java:647)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(Refl
ectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:867)
at org.apache.geronimo.kern

[BUILD] trunk: Failed for Revision: 676460

2008-07-14 Thread gawor

Geronimo Revision: 676460 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080714/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080714/unit-test-reports
 
[INFO] Building Geronimo Plugins, Concurrency Utilities :: Management API
[INFO]task-segment: [install]
[INFO] 
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 4 source files to 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/surefire-reports

---
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [jar:jar]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/geronimo-concurrent-management-2.2-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-concurrent-management/2.2-SNAPSHOT/geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO] 
[INFO] Building Geronimo Plugins, Concurrency Utilities :: Core
[INFO]task-segment: [install]
[INFO] 
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 31 source files to 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 17 source files to 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports

---
 T E S T S
---
Running 
org.apache.geronimo.concurrent.executor.ServerManagedScheduledExecutorServiceTest
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 96.219 sec
Running 
org.apache.geronimo.concurrent.executor.ComponentManagedExecutorServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.053 sec
Running org.apache.geronimo.concurrent.executor.ServerManagedExecutorServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.044 sec
Running org.apache.geronimo.concurrent.context.ContextServiceTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
Running org.apache.geronimo.concurrent.harmony.FutureTaskTest
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at

[jira] Assigned: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX

2008-07-14 Thread Shiva Kumar H R (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shiva Kumar H R reassigned GERONIMODEVTOOLS-434:


Assignee: Shiva Kumar H R  (was: Tim McConnell)

> Query Dynamic Information from Server using JMX
> ---
>
> Key: GERONIMODEVTOOLS-434
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Shiva Kumar H R
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicserverinfo.patch
>
>
> Enabling GEP to query server for dynamic information on the lines of 
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on 
> server side that sends data to GEP. This has severe exceptions when a old 
> server is added or custom server assemblies are added to GEP which wont have 
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
> Destination references) from Server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sainath Chowdary updated GERONIMODEVTOOLS-434:
--

   Assignee: Tim McConnell  (was: Sainath Chowdary)
Description: 
Enabling GEP to query server for dynamic information on the lines of 
Plancreator using a JMXConnectionFactory.

Querying dynamic information has already been done but having a Servlet on 
server side that sends data to GEP. This has severe exceptions when a old 
server is added or custom server assemblies are added to GEP which wont have 
the particular servlet added.

Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
Destination references) from Server.

  was:
Enabling GEP to query server for dynamic information on the lines of 
Plancreator using a JMXConnectionFactory.

Querying dynamic information has already been done but having a Servlet on 
server side that sends data to GEP. This has severe exceptions when a old 
server is added or custom server assemblies are added to GEP which wont have 
the particular servlet added.

Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
Destination references) from Server.




> Query Dynamic Information from Server using JMX
> ---
>
> Key: GERONIMODEVTOOLS-434
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Tim McConnell
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicserverinfo.patch
>
>
> Enabling GEP to query server for dynamic information on the lines of 
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on 
> server side that sends data to GEP. This has severe exceptions when a old 
> server is added or custom server assemblies are added to GEP which wont have 
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
> Destination references) from Server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sainath Chowdary updated GERONIMODEVTOOLS-434:
--

Attachment: jmx-dynamicserverinfo.patch

For example, to get a list of Credential Stores deployed on the server, call
GeronimoServerInfoUtil.getInstance().listCredentialStores()

This has a minor limitation as it queries all the servers that are running in 
workspace. Suppose 2 Geronimo servers are running, this queries from both of 
them which can potentially give raise to errors when dependencies from 2nd 
server are added but deployed onto first server.

> Query Dynamic Information from Server using JMX
> ---
>
> Key: GERONIMODEVTOOLS-434
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Sainath Chowdary
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicserverinfo.patch
>
>
> Enabling GEP to query server for dynamic information on the lines of 
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on 
> server side that sends data to GEP. This has severe exceptions when a old 
> server is added or custom server assemblies are added to GEP which wont have 
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
> Destination references) from Server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX

Query Dynamic Information from Server using JMX
---

 Key: GERONIMODEVTOOLS-434
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
 Project: Geronimo-Devtools
  Issue Type: Sub-task
  Components: eclipse-plugin
Affects Versions: 2.1.2, 2.1.x
Reporter: Sainath Chowdary
Assignee: Sainath Chowdary
 Fix For: 2.1.2, 2.1.x


Enabling GEP to query server for dynamic information on the lines of 
Plancreator using a JMXConnectionFactory.

Querying dynamic information has already been done but having a Servlet on 
server side that sends data to GEP. This has severe exceptions when a old 
server is added or custom server assemblies are added to GEP which wont have 
the particular servlet added.

Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, 
JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS 
Destination references) from Server.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Restarting console-base from command line

2008-07-14 Thread Shrey Banga

Thanks Manu, it worked like a charm and it saves a lot of hassle.

On Mon, Jul 14, 2008 at 2:59 AM, Manu George <[EMAIL PROTECTED]>
wrote:

> Hi Shrey,
> I also faced this issue recently. My understanding is
> that all the DWR calls go through the
> org.apache.geronimo.console.servlet.ContextForwardServlet servlet
> currently. In that servlet we have a reference to the web app context
> of say plan creator or any other console plugin. Since plan creator is
> stopped that context object that we refer to becomes stale. So we need
> to refresh that context reference in the ContextForwardServlet. I have
> opened a JIRA and attached a patch. The link to the jira is
> https://issues.apache.org/jira/browse/GERONIMO-4201
>
> Regards
> Manu
>
> On Fri, Jul 11, 2008 at 11:01 AM, Shrey Banga <[EMAIL PROTECTED]>
> wrote:
> > I was trying to write a bat file for automating the process of building
> > plancreator, stopping the plancreator module on the server, replacing it
> > with the new build and restarting plancreator. Once this process is done,
> > the DWR stops working, which is probably because requests to DWR go
> through
> > /console webapp context. So I manually restart the console-base from the
> > admin console which does the trick. Now for the purpose of the bat file,
> I
> > need to use the deploy tool to restart only the console-base but it in
> > list-modules it is shown as:
> >>
> >>  + org.apache.geronimo.plugins/console-tomcat/2.2-SNAPSHOT/car
> >>  `-> portal-driver.war
> >>  `-> base-portlets.war
> >
> >
> > If I do a deploy restart
> > org.apache.geronimo.plugins/console-tomcat/2.2-SNAPSHOT/car many of the
> > other deployed webapps get stopped. How do I restart only console-base ?
> Or
> > is there a simpler workaround for the dwr problem ?
> > --
> > Shrey Banga
> > Bachelor of Technology, III year
> > Department of Electrical Engineering
> > Indian Institute of Technology Roorkee
>



-- 
Shrey Banga
Bachelor of Technology, III year
Department of Electrical Engineering
Indian Institute of Technology Roorkee

Re: An unexpected error has been detected by HotSpot Virtual Machine: