date:20080709


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

Tim McConnell commented on GERONIMODEVTOOLS-349:


Hi Ashish, do you know enough about the problem to provide a patch to fix it ??

> GEP synchronization with a server running outside of Eclipse no longer works
> 
>
> Key: GERONIMODEVTOOLS-349
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.0
>Reporter: Tim McConnell
>Assignee: Ashish Jain
> Fix For: 2.1.2
>
>
> The GEP should synchronize with a Geronimo server running either inside of 
> Eclipse or outside of Eclipse. It no longer works though when the server is 
> started outside of Eclipse

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

[jira] Created: (GERONIMODEVTOOLS-429) Testcase failures in org.apache.geronimo.st.core plugin

Testcase failures in org.apache.geronimo.st.core plugin
---

 Key: GERONIMODEVTOOLS-429
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-429
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.2
Reporter: Tim McConnell
Assignee: Tim McConnell
 Fix For: 2.1.2


---
Test set: org.apache.geronimo.st.core.internal.DependencyHelperTest
---
Tests run: 6, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 0.656 sec <<< 
FAILURE!
testMultipleParents(org.apache.geronimo.st.core.internal.DependencyHelperTest)  
Time elapsed: 0.078 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<[EMAIL PROTECTED]> but 
was:<[EMAIL PROTECTED]>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:71)
at 
org.apache.geronimo.st.core.internal.DependencyHelperTest.testMultipleParents(DependencyHelperTest.java:268)
at 
org.apache.geronimo.st.core.internal.DependencyHelperTest.testMultipleParents(DependencyHelperTest.java:268)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)

testMultipleChildrenAndParents1(org.apache.geronimo.st.core.internal.DependencyHelperTest)
  Time elapsed: 0.062 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<[EMAIL PROTECTED]> but 
was:<[EMAIL PROTECTED]>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:71)
at 
org.apache.geronimo.st.core.internal.DependencyHelperTest.testMultipleChildrenAndParents1(DependencyHelperTest.java:334)
at 
org.apache.geronimo.st.core.internal.DependencyHelperTest.testMultipleChildrenAndParents1(DependencyHelperTest.java:334)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)

[jira] Resolved: (GERONIMODEVTOOLS-356) geronimo-service.xml support in GEP is incomplete


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

Tim McConnell resolved GERONIMODEVTOOLS-356.


Resolution: Fixed

Hi BJ, thanks very much for your patch. I applied your patch with revision 
675428. I noticed another instance of jst.utility in the GeronimoUtils class 
and deleted that as well. Please verify that is correct -- the GEP seems to 
work as before. Thanks again.

> geronimo-service.xml support in GEP is incomplete
> -
>
> Key: GERONIMODEVTOOLS-356
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-356
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.1.2
>
> Attachments: GERONIMODEVTOOLS-356-remove.patch
>
>
> geronimo-service.xml support in GEP is incomplete. We need to analize and 
> determine whether to fully support or eliminate entirely

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

[jira] Created: (GERONIMODEVTOOLS-428) NullpointerException deploying warfile without Geronimo deployment descriptor

NullpointerException deploying warfile without Geronimo deployment descriptor
-

 Key: GERONIMODEVTOOLS-428
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-428
 Project: Geronimo-Devtools
  Issue Type: Bug
Reporter: Tim McConnell
Assignee: Tim McConnell




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

[jira] Updated: (GERONIMODEVTOOLS-428) NullpointerException deploying warfile without Geronimo deployment descriptor


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

Tim McConnell updated GERONIMODEVTOOLS-428:
---

  Component/s: eclipse-plugin
Affects Version/s: 2.1.2
Fix Version/s: 2.1.2

> NullpointerException deploying warfile without Geronimo deployment descriptor
> -
>
> Key: GERONIMODEVTOOLS-428
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-428
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.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-09 Thread Donald Woods


+1


-Donald


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



smime.p7s
Description: S/MIME Cryptographic Signature

[jira] Commented: (GERONIMODEVTOOLS-425) Query Dynamic Information from Server

2008-07-09 Thread Donald Woods (JIRA)


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

Donald Woods commented on GERONIMODEVTOOLS-425:
---

Shiva, how does this change handle -
1) older Geronimo servers, like 2.0.0.2, 2.1.0, 2.1.1 which do not have this 
new code?
2) the minimal server assemblies which do not have the console or Plan Creator 
installed
3) custom assemblies that do not have the console included?
Is there a way you can use JMX instead?


> Query Dynamic Information from Server
> -
>
> Key: GERONIMODEVTOOLS-425
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.x
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.1.x
>
>
> Plan Creator allows intuitive mapping of references declared in a Web 
> application to specific resources available in the server environment. On the 
> "References" page of Plan Creator, references declared in a web-app (like 
> EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection 
> Factory and JMS Destination references), and the resources available in the 
> server environment to which they can be linked are both shown, and users are 
> asked to just link them up.
> To enable this feature in GEP Deployment Plan Editor, GEP must be able to 
> query the server for deployed resources.

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

Re: version compatibility plugin?

2008-07-09 Thread David Jencks



On Jul 9, 2008, at 1:12 PM, Joe Bohn wrote:




Thanks for the post Lin.  I was going to start a new thread for this  
discussion.


I mentioned a third possibility in the Geronimo 2.1.2 plans  
thread ... that is adding the artifact alias entries for 2.1 & 2.1.1  
directly into the 2.1.2 server image as part of the release.


I guess each plugin can include aliases for previous versions of  
itself and the jars it depends on.  This might be better than the  
compatibility plugin but might also turn into a maintenance nightmare.



 I'm not exactly sure how I feel about this.  It would solve the  
problem and eliminate the need for a user to manually change the  
entries or install a compatibility plugin.  On the other hand it  
seems a bit heavy-handed and will expose the user a long list of  
alias entries if they need to manually change the file themselves.   
I also wonder if there are any performance implications as the list  
gets longer.


I'd say, no.  Currently it's a hashmap lookup and should not be  
noticeably affected by the size of the hashmap.



All in all, the alias approach will work in the short term but I  
think it's just a band-aid fix.  At some point it is going to cause  
grief when things are not really compatible but the aliases allow a  
user to install anyway.  At some point we're going to have to invest  
in a more complicated and complete plugin solution that address  
compatibility more completely.


Maybe.  Testing compatibility would be a nice thing to do but I have  
essentially no idea how.  Without testing I don't see the point in  
making things more complicated and with it I don't see a problem with  
the "lots of aliases" approach.  Representing the aliases in property  
files is not essential and if they start getting unwieldy we could  
look for an alternate notation.  On the other hand I don't expect  
users to be messing with the artifact alias files by hand anyway: i'd  
expect that normally they'd only be modified by installing more plugins.


thanks
david jencks





Joe

Lin Sun wrote:

Hi Joe/All,
Finally I was able to deploy the jaxws-calculator car file onto the
server, after adding a bunch of entries in the
artifact-aliases.properties file, which is essentially the same as
what your compatibility plugin does.
We'll have to quickly decide what to do with the compatability issue
otherwise none of our sample will be installable on 2.1.2 server.
One approach is to release the compatibility plugin you worked on.
Is this checked in?
Pros: we can have this quickly and get ready for the 2.1.2 release.
Cons: it is extra work for the user.
The other approach is to add the matching entries to the
artifact-aliases.properties and client_artifact-aliases.properties on
the fly.   We'll have to determine how to add them, what to add to
different assemblies (can different assemblies have same entries if
the extra entries don't hurt anything), etc.
Pros: no extra work for the user, assuming the server can add the
common matching entries to different assembly on the fly.
Cons: Could take longer and is this appropriate for 2.1.2 given we'll
release it very soon?






Thanks, Lin
On Tue, Jul 8, 2008 at 2:51 PM, Joe Bohn <[EMAIL PROTECTED]>  
wrote:

Lin Sun wrote:
Yes, I am able to move onto the next missing dependency module.
Thanks.


Is there a reason why we need both?  I thought we just need one and
version can be omitted on the left side per

http://cwiki.apache.org/GMOxDOC21/how-to-upgrade-jars-and-swap-modules.html
What you need depends on the way the dependency itself is  
specified.  If it
is specified with the version such as 2.1 then you need the /2.1/  
entry.
This is the case for the jsp sample.  If it is called out without  
a version
then you need the // entry.  The doc you referenced calls the  
former a

"fixed version".

IIRC the jsp sample had 2.1 in the jasper dependency ... but it  
also had a
dependency on the tomcat/jetty car.  The tomcat/jetty car has a  
dependency
on jasper without the version.  You might not need the // entry  
but in
general it is usually best to provide both the versioned and non- 
versioned

entries.

BTW, I was actually using a quick pass at a compatibility plugin I  
had
created for that included all of the cars for the tomcat server  
instance ...
so some other dependencies may have been resolved beyond jasper  
(such as the

tomcat dependency).

Joe


Lin

On Tue, Jul 8, 2008 at 2:06 PM, Joe Bohn <[EMAIL PROTECTED]>  
wrote:

Lin Sun wrote:

Hi Joe,

Is this scenario working for you after your fix?  I updated the
artifact-aliases.properties file in var/config manually when  
server is

shutdown -


org.apache.geronimo.configs/jasper// 
car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car

You need one more additional entry  ...

org.apache.geronimo.configs/jasper/2.1/ 
car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car


That worked for me.

Joe



However, I am still getting the "Missing dependency:
org.apa

Re: version compatibility plugin?

2008-07-09 Thread Lin Sun

I agree with you - I would be concerned about adding all the alias
entries for all the modules we have in the Geronimo.

Another approach is to release samples just for v2.1.2.   I kinda like
this so that we keep things simple.   Compatibility is nice but
unexpected behavior can cause users more trouble.

Lin



On Wed, Jul 9, 2008 at 4:28 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Joe Bohn wrote:
>>
>>
>> Thanks for the post Lin.  I was going to start a new thread for this
>> discussion.
>>
>> I mentioned a third possibility in the Geronimo 2.1.2 plans thread ...
>> that is adding the artifact alias entries for 2.1 & 2.1.1 directly into the
>> 2.1.2 server image as part of the release.  I'm not exactly sure how I feel
>> about this.  It would solve the problem and eliminate the need for a user to
>> manually change the entries or install a compatibility plugin.  On the other
>> hand it seems a bit heavy-handed and will expose the user a long list of
>> alias entries if they need to manually change the file themselves.  I also
>> wonder if there are any performance implications as the list gets longer.
>>
>> All in all, the alias approach will work in the short term but I think
>> it's just a band-aid fix.  At some point it is going to cause grief when
>> things are not really compatible but the aliases allow a user to install
>> anyway.  At some point we're going to have to invest in a more complicated
>> and complete plugin solution that address compatibility more completely.
>>
>> Joe
>>
>> Lin Sun wrote:
>>>
>>> Hi Joe/All,
>>>
>>> Finally I was able to deploy the jaxws-calculator car file onto the
>>> server, after adding a bunch of entries in the
>>> artifact-aliases.properties file, which is essentially the same as
>>> what your compatibility plugin does.
>>>
>>> We'll have to quickly decide what to do with the compatability issue
>>> otherwise none of our sample will be installable on 2.1.2 server.
>>>
>>> One approach is to release the compatibility plugin you worked on.
>>> Is this checked in?
>
> oops ... I had intended to answer this on the last response.  No, I did not
> check this in.  I just created a empty plugin containing all of the cars in
> a tomcat server instance mapped from 2.1 (or 2.1.1) to 2.1.2-SNAPSHOT.  If
> we want to pursue that we'll need to add the jetty specific cars (cxf too)
> and address the client_artifact_aliases as well.
>
>>> Pros: we can have this quickly and get ready for the 2.1.2 release.
>>> Cons: it is extra work for the user.
>>>
>>> The other approach is to add the matching entries to the
>>> artifact-aliases.properties and client_artifact-aliases.properties on
>>> the fly.   We'll have to determine how to add them, what to add to
>>> different assemblies (can different assemblies have same entries if
>>> the extra entries don't hurt anything), etc.
>>> Pros: no extra work for the user, assuming the server can add the
>>> common matching entries to different assembly on the fly.
>>> Cons: Could take longer and is this appropriate for 2.1.2 given we'll
>>> release it very soon?
>>
>>
>>
>>
>>>
>>> Thanks, Lin
>>>
>>> On Tue, Jul 8, 2008 at 2:51 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

 Lin Sun wrote:
>
> Yes, I am able to move onto the next missing dependency module.
> Thanks.
>
> Is there a reason why we need both?  I thought we just need one and
> version can be omitted on the left side per
>
>
> http://cwiki.apache.org/GMOxDOC21/how-to-upgrade-jars-and-swap-modules.html

 What you need depends on the way the dependency itself is specified.  If
 it
 is specified with the version such as 2.1 then you need the /2.1/ entry.
  This is the case for the jsp sample.  If it is called out without a
 version
 then you need the // entry.  The doc you referenced calls the former a
 "fixed version".

 IIRC the jsp sample had 2.1 in the jasper dependency ... but it also had
 a
 dependency on the tomcat/jetty car.  The tomcat/jetty car has a
 dependency
 on jasper without the version.  You might not need the // entry but in
 general it is usually best to provide both the versioned and
 non-versioned
 entries.

 BTW, I was actually using a quick pass at a compatibility plugin I had
 created for that included all of the cars for the tomcat server instance
 ...
 so some other dependencies may have been resolved beyond jasper (such as
 the
 tomcat dependency).

 Joe

> Lin
>
> On Tue, Jul 8, 2008 at 2:06 PM, Joe Bohn <[EMAIL PROTECTED]>
> wrote:
>>
>> Lin Sun wrote:
>>>
>>> Hi Joe,
>>>
>>> Is this scenario working for you after your fix?  I updated the
>>> artifact-aliases.properties file in var/config manually when server
>>> is
>>> shutdown -
>>>
>>>
>>>
>>> org.apache.geronimo.configs/jasper//car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car
>>
>>

[jira] Created: (GERONIMODEVTOOLS-427) Invalid text in generated geronimo-application-client.xml

Invalid text in generated geronimo-application-client.xml
-

 Key: GERONIMODEVTOOLS-427
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-427
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.1
Reporter: Tim McConnell
Assignee: Tim McConnell
 Fix For: 2.1.2


The following text is in the automatically generated 
geronimo-application-client.xml and must be manually deleted


 ServiceRefName



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

[jira] Updated: (GERONIMODEVTOOLS-356) geronimo-service.xml support in GEP is incomplete

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


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

B.J. Reed updated GERONIMODEVTOOLS-356:
---

Attachment: GERONIMODEVTOOLS-356-remove.patch

Patch to remove support of the geronimo-service.xml from the GEP.

> geronimo-service.xml support in GEP is incomplete
> -
>
> Key: GERONIMODEVTOOLS-356
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-356
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.1.2
>
> Attachments: GERONIMODEVTOOLS-356-remove.patch
>
>
> geronimo-service.xml support in GEP is incomplete. We need to analize and 
> determine whether to fully support or eliminate entirely

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

Re: version compatibility plugin?

Joe Bohn wrote:

Thanks for the post Lin. I was going to start a new thread for this
discussion.

I mentioned a third possibility in the Geronimo 2.1.2 plans thread ...
that is adding the artifact alias entries for 2.1 & 2.1.1 directly into
the 2.1.2 server image as part of the release. I'm not exactly sure how
I feel about this. It would solve the problem and eliminate the need
for a user to manually change the entries or install a compatibility
plugin. On the other hand it seems a bit heavy-handed and will expose
the user a long list of alias entries if they need to manually change
the file themselves. I also wonder if there are any performance
implications as the list gets longer.

All in all, the alias approach will work in the short term but I think
it's just a band-aid fix. At some point it is going to cause grief when
things are not really compatible but the aliases allow a user to install
anyway. At some point we're going to have to invest in a more
complicated and complete plugin solution that address compatibility more
completely.

Joe

Lin Sun wrote:

Hi Joe/All,

Finally I was able to deploy the jaxws-calculator car file onto the
server, after adding a bunch of entries in the
artifact-aliases.properties file, which is essentially the same as
what your compatibility plugin does.

We'll have to quickly decide what to do with the compatability issue
otherwise none of our sample will be installable on 2.1.2 server.

One approach is to release the compatibility plugin you worked on.
Is this checked in?

oops ... I had intended to answer this on the last response. No, I did
not check this in. I just created a empty plugin containing all of the
cars in a tomcat server instance mapped from 2.1 (or 2.1.1) to
2.1.2-SNAPSHOT. If we want to pursue that we'll need to add the jetty
specific cars (cxf too) and address the client_artifact_aliases as well.

Pros: we can have this quickly and get ready for the 2.1.2 release.
Cons: it is extra work for the user.

The other approach is to add the matching entries to the
artifact-aliases.properties and client_artifact-aliases.properties on
the fly. We'll have to determine how to add them, what to add to
different assemblies (can different assemblies have same entries if
the extra entries don't hurt anything), etc.
Pros: no extra work for the user, assuming the server can add the
common matching entries to different assembly on the fly.
Cons: Could take longer and is this appropriate for 2.1.2 given we'll
release it very soon?

Thanks, Lin

On Tue, Jul 8, 2008 at 2:51 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

Lin Sun wrote:
Yes, I am able to move onto the next missing dependency module.
Thanks.

Is there a reason why we need both? I thought we just need one and
version can be omitted on the left side per

http://cwiki.apache.org/GMOxDOC21/how-to-upgrade-jars-and-swap-modules.html

What you need depends on the way the dependency itself is specified.
If it

is specified with the version such as 2.1 then you need the /2.1/ entry.
This is the case for the jsp sample. If it is called out without a
version

then you need the // entry. The doc you referenced calls the former a
"fixed version".

IIRC the jsp sample had 2.1 in the jasper dependency ... but it also
had a
dependency on the tomcat/jetty car. The tomcat/jetty car has a
dependency

on jasper without the version. You might not need the // entry but in
general it is usually best to provide both the versioned and
non-versioned

entries.

BTW, I was actually using a quick pass at a compatibility plugin I had
created for that included all of the cars for the tomcat server
instance ...
so some other dependencies may have been resolved beyond jasper (such
as the

tomcat dependency).

Joe

Lin

On Tue, Jul 8, 2008 at 2:06 PM, Joe Bohn <[EMAIL PROTECTED]>
wrote:

Lin Sun wrote:

Hi Joe,

Is this scenario working for you after your fix? I updated the
artifact-aliases.properties file in var/config manually when
server is

shutdown -

org.apache.geronimo.configs/jasper//car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car

You need one more additional entry ...

org.apache.geronimo.configs/jasper/2.1/car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car

That worked for me.

Joe

However, I am still getting the "Missing dependency:
org.apache.geronimo.configs/jasper/2.1/car" error.

What am I missing? Thanks, Lin

On Thu, Jul 3, 2008 at 4:19 PM, Joe Bohn <[EMAIL PROTECTED]>
wrote:

Joe Bohn wrote:
Ok, I confirmed that DefaultArtifactResolver.queryArtifacts() was
not

including aliases for the query ... hence the problem. Thanks to a
good
pointer from David Jencks I was able to easily add this into the
query.

I
created GERONIMO-4182 for this problem and checked in a fix for
2.1.2-SNAPSHOT and 2.2-SNAPSHOT.

Unfortunately, that means that we won't be able to use a version
compatibility plugin for anything prior to 2.1.2/2.2 ... so we wil

Re: version compatibility plugin?

Thanks for the post Lin. I was going to start a new thread for this
discussion.

Joe

Lin Sun wrote:

Hi Joe/All,

We'll have to quickly decide what to do with the compatability issue
otherwise none of our sample will be installable on 2.1.2 server.

One approach is to release the compatibility plugin you worked on.
Is this checked in?
Pros: we can have this quickly and get ready for the 2.1.2 release.
Cons: it is extra work for the user.

Thanks, Lin

On Tue, Jul 8, 2008 at 2:51 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

Lin Sun wrote:

Yes, I am able to move onto the next missing dependency module. Thanks.

Is there a reason why we need both? I thought we just need one and
version can be omitted on the left side per

http://cwiki.apache.org/GMOxDOC21/how-to-upgrade-jars-and-swap-modules.html

What you need depends on the way the dependency itself is specified. If it
is specified with the version such as 2.1 then you need the /2.1/ entry.
This is the case for the jsp sample. If it is called out without a version
then you need the // entry. The doc you referenced calls the former a
"fixed version".

IIRC the jsp sample had 2.1 in the jasper dependency ... but it also had a
dependency on the tomcat/jetty car. The tomcat/jetty car has a dependency
on jasper without the version. You might not need the // entry but in
general it is usually best to provide both the versioned and non-versioned
entries.

BTW, I was actually using a quick pass at a compatibility plugin I had
created for that included all of the cars for the tomcat server instance ...
so some other dependencies may have been resolved beyond jasper (such as the
tomcat dependency).

Joe

Lin

On Tue, Jul 8, 2008 at 2:06 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

Lin Sun wrote:

Hi Joe,

Is this scenario working for you after your fix? I updated the
artifact-aliases.properties file in var/config manually when server is
shutdown -

org.apache.geronimo.configs/jasper//car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car

You need one more additional entry ...

org.apache.geronimo.configs/jasper/2.1/car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car

That worked for me.

Joe

However, I am still getting the "Missing dependency:
org.apache.geronimo.configs/jasper/2.1/car" error.

What am I missing? Thanks, Lin

On Thu, Jul 3, 2008 at 4:19 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

Joe Bohn wrote:
Ok, I confirmed that DefaultArtifactResolver.queryArtifacts() was not
including aliases for the query ... hence the problem. Thanks to a
good
pointer from David Jencks I was able to easily add this into the query.
I
created GERONIMO-4182 for this problem and checked in a fix for
2.1.2-SNAPSHOT and 2.2-SNAPSHOT.

Unfortunately, that means that we won't be able to use a version
compatibility plugin for anything prior to 2.1.2/2.2 ... so we will
need
to
come up with another solution for samples or other plugins created for
Geronimo 2.1 that we want to run on Geronimo 2.1.1.

Joe

thanks
david jencks

On Jul 2, 2008, at 8:46 AM, Joe Bohn wrote:

I attempted to create a version compatibility plugin such that
plugins
with dependencies on 2.1 artifacts could attempt to be installed in
a
2.2-SNAPSHOT server image (mapping 2.1 car arti

[jira] Updated: (GERONIMODEVTOOLS-350) Update "Source" view with unsaved changes in Deployment Plan Editor, or prompt user to save before switching to "Source" view

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


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

B.J. Reed updated GERONIMODEVTOOLS-350:
---

Attachment: GERONIMODEVTOOLS-350-optionb.patch

The optionb.patch is a quick fix prompting the user to save before switching 
pages.  This is not really the best solution, but may have to do for now.  To 
fix this the right way, we will need to have 2 versions of the deployment plan 
(saved and working copy) rather than just the one version we have now.  Will 
investigate further to determine how big of a change this will be.

> Update "Source" view with unsaved changes in Deployment Plan Editor, or 
> prompt user to save before switching to "Source" view
> -
>
> Key: GERONIMODEVTOOLS-350
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-350
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.0
> Environment: Eclipse Europa Winter, Geronimo 2.1.1, GEP 2.1.0
>Reporter: Cedric Hurst
>Assignee: Tim McConnell
> Fix For: 2.1.2
>
> Attachments: deploymentPlanUnsavedChanges.avi, 
> GERONIMODEVTOOLS-350-optionb.patch
>
>
> When editing metadata in one of the graphical views of the Deployment Plan 
> Editor (e.g. "General", "Security", "Deployment"), any unsaved changes are 
> not reflected after switching to the "Source" view.  This might be confusing 
> for the user, because the expectation is that they are editing a "working 
> copy" the values of the fields would be consistently reflected in the 
> "Source" view.   I am proposing two possible options (in order of preference):
> 1. Update the "Source" view to reflect unsaved changes
> 2. Prompt the user to save the Deployment Plan before switching from a 
> graphical view to the "Source" view
> I will attach a screencast to better demonstrate the issue.

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

Re: version compatibility plugin?

2008-07-09 Thread Lin Sun

Hi Joe/All,

Finally I was able to deploy the jaxws-calculator car file onto the
server, after adding a bunch of entries in the
artifact-aliases.properties file, which is essentially the same as
what your compatibility plugin does.

We'll have to quickly decide what to do with the compatability issue
otherwise none of our sample will be installable on 2.1.2 server.

One approach is to release the compatibility plugin you worked on.
Is this checked in?
Pros: we can have this quickly and get ready for the 2.1.2 release.
Cons: it is extra work for the user.

The other approach is to add the matching entries to the
artifact-aliases.properties and client_artifact-aliases.properties on
the fly.   We'll have to determine how to add them, what to add to
different assemblies (can different assemblies have same entries if
the extra entries don't hurt anything), etc.
Pros: no extra work for the user, assuming the server can add the
common matching entries to different assembly on the fly.
Cons: Could take longer and is this appropriate for 2.1.2 given we'll
release it very soon?

Thanks, Lin

On Tue, Jul 8, 2008 at 2:51 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Lin Sun wrote:
>>
>> Yes, I am able to move onto the next missing dependency module.   Thanks.
>>
>> Is there a reason why we need both?  I thought we just need one and
>> version can be omitted on the left side per
>>
>> http://cwiki.apache.org/GMOxDOC21/how-to-upgrade-jars-and-swap-modules.html
>
> What you need depends on the way the dependency itself is specified.  If it
> is specified with the version such as 2.1 then you need the /2.1/ entry.
>  This is the case for the jsp sample.  If it is called out without a version
> then you need the // entry.  The doc you referenced calls the former a
> "fixed version".
>
> IIRC the jsp sample had 2.1 in the jasper dependency ... but it also had a
> dependency on the tomcat/jetty car.  The tomcat/jetty car has a dependency
> on jasper without the version.  You might not need the // entry but in
> general it is usually best to provide both the versioned and non-versioned
> entries.
>
> BTW, I was actually using a quick pass at a compatibility plugin I had
> created for that included all of the cars for the tomcat server instance ...
> so some other dependencies may have been resolved beyond jasper (such as the
> tomcat dependency).
>
> Joe
>
>>
>> Lin
>>
>> On Tue, Jul 8, 2008 at 2:06 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>>>
>>> Lin Sun wrote:

 Hi Joe,

 Is this scenario working for you after your fix?  I updated the
 artifact-aliases.properties file in var/config manually when server is
 shutdown -


 org.apache.geronimo.configs/jasper//car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car
>>>
>>> You need one more additional entry  ...
>>>
>>> org.apache.geronimo.configs/jasper/2.1/car=org.apache.geronimo.configs/jasper/2.1.2-SNAPSHOT/car
>>>
>>> That worked for me.
>>>
>>> Joe
>>>
>>>
 However, I am still getting the "Missing dependency:
 org.apache.geronimo.configs/jasper/2.1/car" error.

 What am I missing?  Thanks, Lin

 On Thu, Jul 3, 2008 at 4:19 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>
> Joe Bohn wrote:
> Ok, I confirmed that DefaultArtifactResolver.queryArtifacts() was not
> including aliases for the query ... hence the problem.  Thanks to a
> good
> pointer from David Jencks I was able to easily add this into the query.
> I
> created GERONIMO-4182 for this problem and checked in a fix for
> 2.1.2-SNAPSHOT and 2.2-SNAPSHOT.
>
> Unfortunately, that means that we won't be able to use a version
> compatibility plugin for anything prior to 2.1.2/2.2 ... so we will
> need
> to
> come up with another solution for samples or other plugins created for
> Geronimo 2.1 that we want to run on Geronimo 2.1.1.
>
> Joe
>
>
>> Joe
>>
>>
>>
>>> thanks
>>> david jencks
>>>
>>> On Jul 2, 2008, at 8:46 AM, Joe Bohn wrote:
>>>
 I attempted to create a version compatibility plugin such that
 plugins
 with dependencies on 2.1 artifacts could attempt to be installed in
 a
 2.2-SNAPSHOT server image (mapping 2.1 car artifacts to 2.2-SNAPSHOT
 car
 artifacts).  However, thus far I'm not having any success.

 The plugin is fairly simple.  Just a bunch of entries for artifact
 aliases and no other content:

 
 ...
 >>>

 key="org.apache.geronimo.configs/jasper//car">org.apache.geronimo.configs/jasper/2.2-SNAPSHOT/car
 >>>

 key="org.apache.geronimo.configs/jasper/2.1/car">org.apache.geronimo.configs/jasper/2.2-SNAPSHOT/car
 ...

 I also verified that after installing the compatibility plugin that
 the
 entries are added to the artifact-aliases.properties

[jira] Closed: (GERONIMO-4191) give users a better message when context-root is not unique

2008-07-09 Thread Lin Sun (JIRA)


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

Lin Sun closed GERONIMO-4191.
-


> give users a better message when context-root is not unique
> ---
>
> Key: GERONIMO-4191
> URL: https://issues.apache.org/jira/browse/GERONIMO-4191
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.1.2, 2.1.x, 2.2
>Reporter: Lin Sun
>Assignee: Lin Sun
>Priority: Minor
> Fix For: 2.1.2
>
>
> A user raised this prob on user list -
> http://www.nabble.com/G2.1.2-SNAPSHOT%2C-java.lang.IllegalArgumentException%3A-addChild%3A--Child-name-%27-%27-is-not-unique-to18346411s134.html#a18346411
> I am able to recreate this by installing another welcome app (at context-root 
> "/") onto geronimo 2.1.2 snapshot.

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

[jira] Resolved: (GERONIMO-4191) give users a better message when context-root is not unique

2008-07-09 Thread Lin Sun (JIRA)


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

Lin Sun resolved GERONIMO-4191.
---

Resolution: Fixed

See subversion commit tab for revisions.  

> give users a better message when context-root is not unique
> ---
>
> Key: GERONIMO-4191
> URL: https://issues.apache.org/jira/browse/GERONIMO-4191
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.1.2, 2.1.x, 2.2
>Reporter: Lin Sun
>Assignee: Lin Sun
>Priority: Minor
> Fix For: 2.1.2
>
>
> A user raised this prob on user list -
> http://www.nabble.com/G2.1.2-SNAPSHOT%2C-java.lang.IllegalArgumentException%3A-addChild%3A--Child-name-%27-%27-is-not-unique-to18346411s134.html#a18346411
> I am able to recreate this by installing another welcome app (at context-root 
> "/") onto geronimo 2.1.2 snapshot.

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

[jira] Updated: (GERONIMO-3876) Allow configuring JMX over SSL

2008-07-09 Thread Jarek Gawor (JIRA)


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

Jarek Gawor updated GERONIMO-3876:
--

Attachment: GERONIMO-3876.21.patch

Here's a new patch (for branches/2.1) that adds a new JMXSecureConnector that 
extends the existing JMXConnector instead of modifying it. I think that's makes 
things a bit cleaner. The patch also introduces a new plugin (jmx-security) 
that starts the JMXSecureConnector (the plugin depends on the 
server-security-config/car and therefore the keystore information will always 
be available before this plugin starts - this solves the ordering issue). 

I don't see any backwards compatibility issues (for 2.1) with this solution or 
even the previous patch where the existing JMXConnector was modified to have 
the extra methods.



> Allow configuring JMX over SSL
> --
>
> Key: GERONIMO-3876
> URL: https://issues.apache.org/jira/browse/GERONIMO-3876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: management, security
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Vamsavardhana Reddy
>Assignee: Jarek Gawor
> Fix For: 2.2
>
> Attachments: GERONIMO-3876-B.patch, GERONIMO-3876.21.patch, 
> GERONIMO-3876.patch
>
>
> Currently JMX connections to Geronimo or non-SSL and Geronimo does not 
> provide configuring SSL for JMX connections.  It may be useful to provide 
> configuration for JMX connections over SSL.

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

Re: ASF Board Report - Initial Reminder for Jul 2008

2008-07-09 Thread Jason Dillon


Kay, updated a wee bit... :-)

--jason


On Jul 10, 2008, at 12:59 AM, Kevan Miller wrote:



On Jul 9, 2008, at 1:46 PM, Jason Dillon wrote:

Can I edit this a little, want to add some context to the gshell  
bits?


Go for it...

--kevan

[jira] Assigned: (GERONIMO-3876) Allow configuring JMX over SSL

2008-07-09 Thread Jarek Gawor (JIRA)


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

Jarek Gawor reassigned GERONIMO-3876:
-

Assignee: Jarek Gawor

> Allow configuring JMX over SSL
> --
>
> Key: GERONIMO-3876
> URL: https://issues.apache.org/jira/browse/GERONIMO-3876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: management, security
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Vamsavardhana Reddy
>Assignee: Jarek Gawor
> Fix For: 2.2
>
> Attachments: GERONIMO-3876-B.patch, GERONIMO-3876.patch
>
>
> Currently JMX connections to Geronimo or non-SSL and Geronimo does not 
> provide configuring SSL for JMX connections.  It may be useful to provide 
> configuration for JMX connections over SSL.

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

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

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

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.

Re: ASF Board Report - Initial Reminder for Jul 2008

2008-07-09 Thread Kevan Miller



On Jul 9, 2008, at 1:46 PM, Jason Dillon wrote:


Can I edit this a little, want to add some context to the gshell bits?


Go for it...

--kevan

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


+1

Looks good to me.

Thanks Rick.

Joe


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: ASF Board Report - Initial Reminder for Jul 2008

2008-07-09 Thread Jason Dillon


Can I edit this a little, want to add some context to the gshell bits?

--jason


On Jul 9, 2008, at 9:36 PM, Kevan Miller wrote:

I updated the new Board Report on the Wiki earlier in the week. Have  
a look at it please. I'll be submitting on Monday morning (will plan  
on removing empty sections before then).


--kevan
On Jul 3, 2008, at 10:47 AM, Kevan Miller wrote:


All,
We have a Geronimo Board report due by July 14th. I created a  
skeleton file at

http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2008-07+-+July

Will start filling it out over the weekend/early next week. Feel  
free to update with relevant information.


--kevan

Begin forwarded message:


From: ASF Board <[EMAIL PROTECTED]>
Date: June 30, 2008 8:50:04 PM EDT
To: Kevan Miller <[EMAIL PROTECTED]>
Subject: ASF Board Report - Initial Reminder for Jul 2008



This email was sent by an automated system on behalf of the ASF  
Board.
It is an initial reminder to give you plenty of time to prepare  
the report.


The meeting is scheduled for Wed, 16 July 2008, 10 am PST and the  
deadline for

submitting your report is two full days prior to that!

According to board records, you are listed as the chair of at  
least one

committee that is due to submit a report this month. [1] [2]

Details on which project reports are due and how to submit a report
are enclosed below.

Please submit your report with sufficient time to allow the board  
members
to review and digest. Again, the very latest you should submit  
your report

is two full days (48h) prior to the board meeting.

The exact date of the board meeting can be found in the  
calendar.txt file

in the board directory of the committers repository [2].

If you feel that an error has been made, please consult [1] and if  
there

is still an issue then contact the board directly.

Thanks,
The ASF Board

[1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt
[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt



Submitting your Report
--

Full details about the process and schedule are in [1].

Your report should be sent in plain-text format to [EMAIL PROTECTED]
with a Subject line that follows the below format:

   Subject: [REPORT] Project Name

Cutting and pasting directly from a Wiki is not acceptable due to  
formatting
issues. Line lengths should be limited to 77 characters. The  
content should
also be committed to the meeting agenda in the board directory in  
the

foundation repository.


ASF Board Reports
-

Reports are due from you for the following committees:

 - Geronimo

[jira] Created: (GERONIMO-4191) give users a better message when context-root is not unique

2008-07-09 Thread Lin Sun (JIRA)

give users a better message when context-root is not unique
---

 Key: GERONIMO-4191
 URL: https://issues.apache.org/jira/browse/GERONIMO-4191
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: Tomcat
Affects Versions: 2.1.2, 2.1.x, 2.2
Reporter: Lin Sun
Assignee: Lin Sun
Priority: Minor
 Fix For: 2.1.2


A user raised this prob on user list -

http://www.nabble.com/G2.1.2-SNAPSHOT%2C-java.lang.IllegalArgumentException%3A-addChild%3A--Child-name-%27-%27-is-not-unique-to18346411s134.html#a18346411

I am able to recreate this by installing another welcome app (at context-root 
"/") onto geronimo 2.1.2 snapshot.



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

[jira] Commented: (GERONIMO-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server


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

Shiva Kumar H R commented on GERONIMO-4189:
---

Oh! I will explore JMX too. Thanks Jarek for the hint.

Time being we need following dynamic info from the server:
1) Deployed EJBs, 
2) JDBC Connection Pools, 
3) JMS Connection Factories,
4) JMS Destinations, 
5) Java Mail Sessions, 
6) Credential Stores, 
7) Common Libs, and
8) Security Realms
Any hints if JMX provides all the above kind of information?

> Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server
> 
>
> Key: GERONIMO-4189
> URL: https://issues.apache.org/jira/browse/GERONIMO-4189
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: PlanCreator
>Affects Versions: 2.2
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.2
>
>
> For intuitive creation/editing of Geronimo Deployment Plans inside GEP 
> Deployment Plan Editors, GEP must be able to query the server for deployed 
> resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this 
> (thanks to Vamsi for the idea!) is as below:
> 1. Have a Servlet deployed & running on the server, that can issue GBean 
> queries to fetch the required dynamic info from the server (like deployed 
> EJBs, JDBC Connection Pools, JMS Connection Factories & Destinations, Java 
> Mail Sessions, Credential Stores, Common Libs & Security Realms) and pass 
> this info to the caller may be as a binary object.
> 2. Inside GEP, invoke the above Servlet with required arguments to get the 
> dynamic info.

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

[jira] Resolved: (GERONIMO-4147) EAR PlanCreator fix for Internet Explorer


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

Shiva Kumar H R resolved GERONIMO-4147.
---

Resolution: Fixed

Committed in trunk at revision: 675238. Thanks Shrey for the patch.

> EAR PlanCreator fix for Internet Explorer
> -
>
> Key: GERONIMO-4147
> URL: https://issues.apache.org/jira/browse/GERONIMO-4147
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: PlanCreator
>Affects Versions: 2.2
>Reporter: Shrey Banga
>Assignee: Shiva Kumar H R
> Fix For: 2.2
>
> Attachments: PlanCreator-EAR-Dep-IEFix.patch
>
>
> Patch available which fixes problems with display in IE:
> 1. A trailing comma broke the function that updates form fields to values 
> received from the server.
> 2. Since some versions of IE have issues with width="100%" the Dependencies 
> dialog looked different in FF and IE. Also, the Dependencies section did not 
> render correctly, causing the buttons to exceed the boundary.

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

[jira] Commented: (GERONIMODEVTOOLS-425) Query Dynamic Information from Server


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

Shiva Kumar H R commented on GERONIMODEVTOOLS-425:
--

svn commit in trunk at revision: 675230 adds an utility class 
/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/ServerInfo.java
 that provides dynamic info from the server.

For example, to get a list of JDBC connection pools deployed on the server, 
call 
ServerInfo.getInstance().getJDBCConnectionPools()

ServerInfo class invokes the ServerInfoServlet available on the server (please 
see GERONIMO-4189) with appropriate arguments and fetches required dynamic info.

> Query Dynamic Information from Server
> -
>
> Key: GERONIMODEVTOOLS-425
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.x
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.1.x
>
>
> Plan Creator allows intuitive mapping of references declared in a Web 
> application to specific resources available in the server environment. On the 
> "References" page of Plan Creator, references declared in a web-app (like 
> EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection 
> Factory and JMS Destination references), and the resources available in the 
> server environment to which they can be linked are both shown, and users are 
> asked to just link them up.
> To enable this feature in GEP Deployment Plan Editor, GEP must be able to 
> query the server for deployed resources.

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

Re: svn commit: r675220 - in /geronimo/server/trunk/plugins: console/console-core/src/main/java/org/apache/geronimo/console/util/ plancreator/plancreator-portlets/src/main/java/org/apache/geronimo/con

2008-07-09 Thread Jarek Gawor

Why can't GEP use JMX to get this information? Why expose this type of
information using a Servlet and return serialized data? I would be ok
with this if the servlet returned XML or JSON formatted data and work
in RESTful way or something (so that we could write a nice AJAX based
console) but otherwise I don't see a point to it (unless I missed
something).

Jarek

On Wed, Jul 9, 2008 at 11:03 AM,  <[EMAIL PROTECTED]> wrote:
> Author: shivahr
> Date: Wed Jul  9 08:03:08 2008
> New Revision: 675220
>
> URL: http://svn.apache.org/viewvc?rev=675220&view=rev
> Log:
> GERONIMO-4189 Enable Geronimo Eclipse Plug-in (GEP) to get dynamic 
> information from server
>
> Added:
>
> geronimo/server/trunk/plugins/plancreator/plancreator-portlets/src/main/java/org/apache/geronimo/console/configcreator/ServerInfoServlet.java
>(with props)
> Modified:
>
> geronimo/server/trunk/plugins/console/console-core/src/main/java/org/apache/geronimo/console/util/PortletManager.java
>
> geronimo/server/trunk/plugins/plancreator/plancreator-portlets/src/main/java/org/apache/geronimo/console/configcreator/JSR77_Util.java
>
> geronimo/server/trunk/plugins/plancreator/plancreator-portlets/src/main/webapp/WEB-INF/web.xml
>
> Modified: 
> geronimo/server/trunk/plugins/console/console-core/src/main/java/org/apache/geronimo/console/util/PortletManager.java
> URL: 
> http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/console/console-core/src/main/java/org/apache/geronimo/console/util/PortletManager.java?rev=675220&r1=675219&r2=675220&view=diff
> ==
> --- 
> geronimo/server/trunk/plugins/console/console-core/src/main/java/org/apache/geronimo/console/util/PortletManager.java
>  (original)
> +++ 
> geronimo/server/trunk/plugins/console/console-core/src/main/java/org/apache/geronimo/console/util/PortletManager.java
>  Wed Jul  9 08:03:08 2008
> @@ -40,7 +40,9 @@
>  import org.apache.geronimo.kernel.proxy.GeronimoManagedBean;
>  import org.apache.geronimo.kernel.repository.Artifact;
>  import org.apache.geronimo.kernel.repository.Repository;
> +import org.apache.geronimo.management.EJBModule;
>  import org.apache.geronimo.management.J2EEDeployedObject;
> +import org.apache.geronimo.management.J2EEResource;
>  import org.apache.geronimo.management.geronimo.J2EEDomain;
>  import org.apache.geronimo.management.geronimo.J2EEServer;
>  import org.apache.geronimo.management.geronimo.JCAAdminObject;
> @@ -121,7 +123,15 @@
> request.getPortletSession().setAttribute(DOMAIN_KEY, domain, 
> PortletSession.APPLICATION_SCOPE);
> }
> return domain;
> +}
>
> +public static J2EEDomain getCurrentDomain(HttpSession session) {
> +J2EEDomain domain = (J2EEDomain) session.getAttribute(DOMAIN_KEY);
> +if (domain == null) {
> +domain = getManagementHelper(session).getDomains()[0]; //todo: 
> some day, select a domain
> +session.setAttribute(DOMAIN_KEY, domain);
> +}
> +return domain;
> }
>
> public static J2EEServer getCurrentServer(PortletRequest request) {
> @@ -135,6 +145,17 @@
> return server;
> }
>
> +public static J2EEServer getCurrentServer(HttpSession session) {
> +J2EEServer server = (J2EEServer) session.getAttribute(SERVER_KEY);
> +if (server == null) {
> +server = getCurrentDomain(session).getServerInstances()[0]; 
> //todo: some day, select a server from the domain
> +session.setAttribute(SERVER_KEY, server);
> +} else {
> +// to do handle "should not occur" error   - message?
> +}
> +return server;
> +}
> +
> public static JVM getCurrentJVM(PortletRequest request) {
> JVM jvm = (JVM) request.getPortletSession(true).getAttribute(JVM_KEY, 
> PortletSession.APPLICATION_SCOPE);
> if (jvm == null) {
> @@ -155,15 +176,43 @@
> return helper.testLoginModule(getCurrentServer(request), module, 
> options, username, password);
> }
>
> +public static EJBModule[] getEJBModules(PortletRequest request) {
> +ManagementHelper helper = getManagementHelper(request);
> +return 
> helper.getEJBModules(PortletManager.getCurrentServer(request));
> +}
> +
> +public static EJBModule[] getEJBModules(HttpSession session) {
> +ManagementHelper helper = getManagementHelper(session);
> +return 
> helper.getEJBModules(PortletManager.getCurrentServer(session));
> +}
> +
> +public static J2EEResource[] getJ2EEResources(PortletRequest request) {
> +ManagementHelper helper = getManagementHelper(request);
> +return helper.getResources(PortletManager.getCurrentServer(request));
> +}
> +
> +public static J2EEResource[] getJ2EEResources(HttpSession session) {
> +ManagementHelper helper = getManagementHelper(session);
> +return helper.getResources(PortletManager.getCurrentServer

[jira] Commented: (GERONIMO-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server

2008-07-09 Thread Jarek Gawor (JIRA)


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

Jarek Gawor commented on GERONIMO-4189:
---

Wait, don't we have JMX for that?


> Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server
> 
>
> Key: GERONIMO-4189
> URL: https://issues.apache.org/jira/browse/GERONIMO-4189
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: PlanCreator
>Affects Versions: 2.2
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.2
>
>
> For intuitive creation/editing of Geronimo Deployment Plans inside GEP 
> Deployment Plan Editors, GEP must be able to query the server for deployed 
> resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this 
> (thanks to Vamsi for the idea!) is as below:
> 1. Have a Servlet deployed & running on the server, that can issue GBean 
> queries to fetch the required dynamic info from the server (like deployed 
> EJBs, JDBC Connection Pools, JMS Connection Factories & Destinations, Java 
> Mail Sessions, Credential Stores, Common Libs & Security Realms) and pass 
> this info to the caller may be as a binary object.
> 2. Inside GEP, invoke the above Servlet with required arguments to get the 
> dynamic info.

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

[jira] Commented: (GERONIMO-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server


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

Shiva Kumar H R commented on GERONIMO-4189:
---

svn commit at revision: 675220 adds required Servlet as mentioned above.

GEP (or other interested parties) after authenticating with server can invoke 
following Servlet and it would return a binary object with requested info.
http://:/plan-creator/ServerInfoServlet?requestedInfo=

For ex: 
http://localhost:8080/plan-creator/ServerInfoServlet?requestedInfo=jdbcConnectionPools
 
would return a list of connection pools deployed on the server.

For possible values of  and to understand/interpret the binary 
object output of above Servlet, please see 
https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/plancreator/plancreator-portlets/src/main/java/org/apache/geronimo/console/configcreator/ServerInfoServlet.java

> Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server
> 
>
> Key: GERONIMO-4189
> URL: https://issues.apache.org/jira/browse/GERONIMO-4189
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: PlanCreator
>Affects Versions: 2.2
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.2
>
>
> For intuitive creation/editing of Geronimo Deployment Plans inside GEP 
> Deployment Plan Editors, GEP must be able to query the server for deployed 
> resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this 
> (thanks to Vamsi for the idea!) is as below:
> 1. Have a Servlet deployed & running on the server, that can issue GBean 
> queries to fetch the required dynamic info from the server (like deployed 
> EJBs, JDBC Connection Pools, JMS Connection Factories & Destinations, Java 
> Mail Sessions, Credential Stores, Common Libs & Security Realms) and pass 
> this info to the caller may be as a binary object.
> 2. Inside GEP, invoke the above Servlet with required arguments to get the 
> dynamic info.

-- 
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-4049) Tutorials - SAAJ Web Services


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

sainath edited comment on GERONIMO-4049 at 7/9/08 8:04 AM:


The tutorial is up at the following link:
http://cwiki.apache.org/GMOxDOC21/saaj-messaging-web-services.html

Although this article creates a basic SAAJ client, the approach can be readily 
extended for creating and sending SAAJ messages without attachments for any 
JAX-WS web service.

Any Comments and Feedback are Welcome

  was (Author: sainath):
The tutorial is up at the following link:
http://cwiki.apache.org/GMOxDOC21/saaj-messaging-web-services.html

Although this article creates a basic SAAJ client, the approach can be readily 
extended for creating and sending SAAJ messages without attachments for any 
JAX-WS web service.
  
> Tutorials - SAAJ Web Services
> -
>
> Key: GERONIMO-4049
> URL: https://issues.apache.org/jira/browse/GERONIMO-4049
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.1, 2.1.1
>Reporter: Hernan Cunico
>Assignee: Sainath Chowdary
>
> Geronimo v2.1 documentation, Tutorials section.
> Develop a tutorial for "SAAJ Web Services" addressing the following common 
> topics (use this list as a guideline). This document should also match the 
> styling used in the existing tutorials.
> * Setting up Eclipse for Application development
> * Sample application overview 
> _identify the different components_
> * Prerequisites
> _external resources (i.e. databases, connection pools, JMS queues, etc)_
> * Sample app creation
> _breakdown into multiple bullets_
> * Deploy and Test the application
> See http://cwiki.apache.org/GMOxDOC21/tutorials.html

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

Re: ASF Board Report - Initial Reminder for Jul 2008

Kevan Miller wrote:
I updated the new Board Report on the Wiki earlier in the week. Have a
look at it please. I'll be submitting on Monday morning (will plan on
removing empty sections before then).

Looks good to me. I didn't notice anything missing.

Joe

--kevan
On Jul 3, 2008, at 10:47 AM, Kevan Miller wrote:

All,
We have a Geronimo Board report due by July 14th. I created a skeleton
file at
http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2008-07+-+July

Will start filling it out over the weekend/early next week. Feel free
to update with relevant information.

--kevan

Begin forwarded message:

*From: *ASF Board <[EMAIL PROTECTED] >
*Date: *June 30, 2008 8:50:04 PM EDT
*To: *Kevan Miller <[EMAIL PROTECTED] >
*Subject: **ASF Board Report - Initial Reminder for Jul 2008*

This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder to give you plenty of time to prepare the
report.

The meeting is scheduled for Wed, 16 July 2008, 10 am PST and the
deadline for

submitting your report is two full days prior to that!

According to board records, you are listed as the chair of at least one
committee that is due to submit a report this month. [1] [2]

Details on which project reports are due and how to submit a report
are enclosed below.

Please submit your report with sufficient time to allow the board members
to review and digest. Again, the very latest you should submit your
report

is two full days (48h) prior to the board meeting.

The exact date of the board meeting can be found in the calendar.txt file
in the board directory of the committers repository [2].

If you feel that an error has been made, please consult [1] and if there
is still an issue then contact the board directly.

Thanks,
The ASF Board

[1] -
https://svn.apache.org/repos/private/committers/board/committee-info.txt

[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt

Submitting your Report
--

Full details about the process and schedule are in [1].

Your report should be sent in plain-text format to [EMAIL PROTECTED]

with a Subject line that follows the below format:

Subject: [REPORT] Project Name

Cutting and pasting directly from a Wiki is not acceptable due to
formatting
issues. Line lengths should be limited to 77 characters. The content
should

also be committed to the meeting agenda in the board directory in the
foundation repository.

ASF Board Reports
-

Reports are due from you for the following committees:

- Geronimo

[jira] Commented: (GERONIMO-4190) Tutorials - Developing Clients for a deployed RESTful Web Service


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

Sainath Chowdary commented on GERONIMO-4190:


The tutorial is partially completed implementing only the GET method of 
accessing the deployed RESTful Web Service. It is up at the following link:

http://cwiki.apache.org/GMOxDOC21/developing-client-for-restful-web-service.html

Please provide feedback about the tutorial

> Tutorials - Developing Clients for a deployed RESTful Web Service
> -
>
> Key: GERONIMO-4190
> URL: https://issues.apache.org/jira/browse/GERONIMO-4190
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.1.1, 2.1.2
>Reporter: Sainath Chowdary
>
> Create a tutorial that discusses about the common issues involved in creating 
> client applications for RESTful Web Service such as bug in Axis2 1.3 jars of 
> Geronimo.
> If possible, the client application should also try to test the deployed 
> RESTful Web Service by both GET and POST methods.

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

[jira] Created: (GERONIMO-4190) Tutorials - Developing Clients for a deployed RESTful Web Service

Tutorials - Developing Clients for a deployed RESTful Web Service
-

 Key: GERONIMO-4190
 URL: https://issues.apache.org/jira/browse/GERONIMO-4190
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
  Components: documentation
Affects Versions: 2.1.1, 2.1.2
Reporter: Sainath Chowdary


Create a tutorial that discusses about the common issues involved in creating 
client applications for RESTful Web Service such as bug in Axis2 1.3 jars of 
Geronimo.

If possible, the client application should also try to test the deployed 
RESTful Web Service by both GET and POST methods.

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

[jira] Commented: (GERONIMO-4049) Tutorials - SAAJ Web Services


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

Sainath Chowdary commented on GERONIMO-4049:


The tutorial is up at the following link:
http://cwiki.apache.org/GMOxDOC21/saaj-messaging-web-services.html

Although this article creates a basic SAAJ client, the approach can be readily 
extended for creating and sending SAAJ messages without attachments for any 
JAX-WS web service.

> Tutorials - SAAJ Web Services
> -
>
> Key: GERONIMO-4049
> URL: https://issues.apache.org/jira/browse/GERONIMO-4049
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.1, 2.1.1
>Reporter: Hernan Cunico
>Assignee: Sainath Chowdary
>
> Geronimo v2.1 documentation, Tutorials section.
> Develop a tutorial for "SAAJ Web Services" addressing the following common 
> topics (use this list as a guideline). This document should also match the 
> styling used in the existing tutorials.
> * Setting up Eclipse for Application development
> * Sample application overview 
> _identify the different components_
> * Prerequisites
> _external resources (i.e. databases, connection pools, JMS queues, etc)_
> * Sample app creation
> _breakdown into multiple bullets_
> * Deploy and Test the application
> See http://cwiki.apache.org/GMOxDOC21/tutorials.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-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server

Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server


 Key: GERONIMO-4189
 URL: https://issues.apache.org/jira/browse/GERONIMO-4189
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: PlanCreator
Affects Versions: 2.2
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.2


For intuitive creation/editing of Geronimo Deployment Plans inside GEP 
Deployment Plan Editors, GEP must be able to query the server for deployed 
resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this (thanks 
to Vamsi for the idea!) is as below:

1. Have a Servlet deployed & running on the server, that can issue GBean 
queries to fetch the required dynamic info from the server (like deployed EJBs, 
JDBC Connection Pools, JMS Connection Factories & Destinations, Java Mail 
Sessions, Credential Stores, Common Libs & Security Realms) and pass this info 
to the caller may be as a binary object.

2. Inside GEP, invoke the above Servlet with required arguments to get the 
dynamic info.

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

[jira] Created: (GERONIMODEVTOOLS-425) Query Dynamic Information from Server

Query Dynamic Information from Server
-

 Key: GERONIMODEVTOOLS-425
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425
 Project: Geronimo-Devtools
  Issue Type: Sub-task
  Components: eclipse-plugin
Affects Versions: 2.1.x
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.x


Plan Creator allows intuitive mapping of references declared in a Web 
application to specific resources available in the server environment. On the 
"References" page of Plan Creator, references declared in a web-app (like EJB, 
EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection Factory and 
JMS Destination references), and the resources available in the server 
environment to which they can be linked are both shown, and users are asked to 
just link them up.

To enable this feature in GEP Deployment Plan Editor, GEP must be able to query 
the server for deployed resources.

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

Re: ASF Board Report - Initial Reminder for Jul 2008

2008-07-09 Thread Kevan Miller

I updated the new Board Report on the Wiki earlier in the week. Have a  
look at it please. I'll be submitting on Monday morning (will plan on  
removing empty sections before then).


--kevan
On Jul 3, 2008, at 10:47 AM, Kevan Miller wrote:


All,
We have a Geronimo Board report due by July 14th. I created a  
skeleton file at

http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2008-07+-+July

Will start filling it out over the weekend/early next week. Feel  
free to update with relevant information.


--kevan

Begin forwarded message:


From: ASF Board <[EMAIL PROTECTED]>
Date: June 30, 2008 8:50:04 PM EDT
To: Kevan Miller <[EMAIL PROTECTED]>
Subject: ASF Board Report - Initial Reminder for Jul 2008



This email was sent by an automated system on behalf of the ASF  
Board.
It is an initial reminder to give you plenty of time to prepare the  
report.


The meeting is scheduled for Wed, 16 July 2008, 10 am PST and the  
deadline for

submitting your report is two full days prior to that!

According to board records, you are listed as the chair of at least  
one

committee that is due to submit a report this month. [1] [2]

Details on which project reports are due and how to submit a report
are enclosed below.

Please submit your report with sufficient time to allow the board  
members
to review and digest. Again, the very latest you should submit your  
report

is two full days (48h) prior to the board meeting.

The exact date of the board meeting can be found in the  
calendar.txt file

in the board directory of the committers repository [2].

If you feel that an error has been made, please consult [1] and if  
there

is still an issue then contact the board directly.

Thanks,
The ASF Board

[1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt
[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt



Submitting your Report
--

Full details about the process and schedule are in [1].

Your report should be sent in plain-text format to [EMAIL PROTECTED]
with a Subject line that follows the below format:

   Subject: [REPORT] Project Name

Cutting and pasting directly from a Wiki is not acceptable due to  
formatting
issues. Line lengths should be limited to 77 characters. The  
content should

also be committed to the meeting agenda in the board directory in the
foundation repository.


ASF Board Reports
-

Reports are due from you for the following committees:

 - Geronimo

[jira] Created: (GERONIMODEVTOOLS-424) Port Plan Creator work into GEP Deployment Plan Editor

Port Plan Creator work into GEP Deployment Plan Editor
--

 Key: GERONIMODEVTOOLS-424
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-424
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 2.1.x
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.x


Port the features of Plan Creator into GEP Deployment Plan Editor, thereby 
enabling intuitive creation/editing of Geronimo Deployment Plans.

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

[BUILD] trunk: Failed for Revision: 675073

2008-07-09 Thread gawor

Geronimo Revision: 675073 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080708/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080708
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 18 seconds
[INFO] Finished at: Tue Jul 08 21:42:09 EDT 2008
[INFO] Final Memory: 373M/1014M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080708/logs-2100-tomcat/test.log
 
 
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.658
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 31 test build(s)
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:01:03.215) 
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:28.721) 
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:18.631) 
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:16.047) 
[INFO] console-testsuite/advanced   RUNNING
[INFO] console-testsuite/advanced   FAILURE (0:01:30.437) Java 
returned: 1
[INFO] console-testsuite/basic  RUNNING
[INFO] console-testsuite/basic  SUCCESS (0:01:40.833) 
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.409) 
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:01:03.578) 
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.026) 
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:29.952) 
[INFO] deployment-testsuite/jca-cms-tests   RUNNING
[INFO] deployment-testsuite/jca-cms-tests   SUCCESS (0:00:28.376) 
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.465) 
[INFO] enterprise-testsuite/ejb-tests   RUNNING
[INFO] enterprise-testsuite/ejb-tests   SUCCESS (0:00:39.943) 
[INFO] enterprise-testsuite/jms-tests   RUNNING
[INFO] enterprise-testsuite/jms-tests   SUCCESS (0:00:44.536) 
[INFO] ente

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

2008-07-09 Thread Dan Becker


Rick McGuire wrote:

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)


+1
--
Thanks, Dan Becker

[jira] Updated: (GERONIMO-4025) Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console

2008-07-09 Thread Rex Wang (JIRA)


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

Rex Wang updated GERONIMO-4025:
---

Attachment: GERONIMO-4025-DB-style.patch

Since I added the style "TableLine" in the css file, the 
"GERONIMO-4025-DB-style.patch" changed the redundant style code of the db 
portlets.

> Accessibility issues: No caption tag or summary property, no column and row 
> scope property for data tables in admin console
> ---
>
> Key: GERONIMO-4025
> URL: https://issues.apache.org/jira/browse/GERONIMO-4025
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.1, 2.1.2, 2.1.x, 2.2
> Environment: Windows XP SP2, IE 6.0
> JAWS 8.0
>Reporter: Xia Ming
> Fix For: 2.2
>
> Attachments: GERONIMO-4025-activemq-and-monitoring.patch, 
> GERONIMO-4025-configmanager-and-infomanager.patch, 
> GERONIMO-4025-DB-Properties_zh.patch, GERONIMO-4025-DB-style.patch, 
> GERONIMO-4025-DB.patch
>
>
> To enable accessibility feature for data tables in the admin console, these 
> techniques should be used:
> 1. Add caption tag or summary property to data table, for example
> 
> Server information
> OR
> 
> 2. Add scope property to column and row headers, for example
> 
> Property name
> Property value
> 
> 
> Geronimo Version
> 2.1.1
> 
> The data tables on these pages shall be improved:
> Server->Information
> Server->Java System Info
> server->Web Server
> Server->Thread Pools
> Server->JMS Server
> Server->Monitoring
> Services->Database Pools
> Services->JMS Resources
> Applications->Web App WARs
> Applications->System modules
> Applications->Application EARs
> Applications->EJB JARs
> Applications->J2EE Connectors
> Applications->App Clients
> Security->Users and Groups
> Security->Keystores
> Security->Security Realms
> Embedded DB->DB Info
> Embedded DB->DB Manager

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

[jira] Updated: (GERONIMO-4025) Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console

2008-07-09 Thread Rex Wang (JIRA)


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

Rex Wang updated GERONIMO-4025:
---

Attachment: GERONIMO-4025-configmanager-and-infomanager.patch

The "GERONIMO-4025-configmanager-and-infomanager.patch" modified the files in 
the 
"plugins\console\console-base-portlets\src\main\webapp\WEB-INF\view", and also 
added the related words in resource bundle.



> Accessibility issues: No caption tag or summary property, no column and row 
> scope property for data tables in admin console
> ---
>
> Key: GERONIMO-4025
> URL: https://issues.apache.org/jira/browse/GERONIMO-4025
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.1, 2.1.2, 2.1.x, 2.2
> Environment: Windows XP SP2, IE 6.0
> JAWS 8.0
>Reporter: Xia Ming
> Fix For: 2.2
>
> Attachments: GERONIMO-4025-activemq-and-monitoring.patch, 
> GERONIMO-4025-configmanager-and-infomanager.patch, 
> GERONIMO-4025-DB-Properties_zh.patch, GERONIMO-4025-DB.patch
>
>
> To enable accessibility feature for data tables in the admin console, these 
> techniques should be used:
> 1. Add caption tag or summary property to data table, for example
> 
> Server information
> OR
> 
> 2. Add scope property to column and row headers, for example
> 
> Property name
> Property value
> 
> 
> Geronimo Version
> 2.1.1
> 
> The data tables on these pages shall be improved:
> Server->Information
> Server->Java System Info
> server->Web Server
> Server->Thread Pools
> Server->JMS Server
> Server->Monitoring
> Services->Database Pools
> Services->JMS Resources
> Applications->Web App WARs
> Applications->System modules
> Applications->Application EARs
> Applications->EJB JARs
> Applications->J2EE Connectors
> Applications->App Clients
> Security->Users and Groups
> Security->Keystores
> Security->Security Realms
> Embedded DB->DB Info
> Embedded DB->DB Manager

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

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

2008-07-09 Thread Ashish Jain (JIRA)


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

Ashish Jain reassigned GERONIMODEVTOOLS-275:


Assignee: Ashish Jain  (was: Tim McConnell)

> 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: [VOTE] Release javamail spec 1.5 and javamail providers 1.5

2008-07-09 Thread Rick McGuire


My +1

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] Updated: (GERONIMODEVTOOLS-423) Add more options to the Security Section in Geronimo Deployment Plan Editor

2008-07-09 Thread Saurabh sharma (JIRA)


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

Saurabh sharma updated GERONIMODEVTOOLS-423:


Description: 
Current security section doesn't provide an intuitive way to add role mappings. 
Also the wizard doesn't ask for the complete information about role-mappings 
for the roles defined in web.xml.

Also the Table viewer isn't a very good option for displaying role mappings 
where a Tree viewer would fit well.
Summary: Add more options to the Security Section in Geronimo 
Deployment Plan Editor  (was: Add more options to the Security Section in )

> Add more options to the Security Section in Geronimo Deployment Plan Editor
> ---
>
> Key: GERONIMODEVTOOLS-423
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-423
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Saurabh sharma
>Assignee: Saurabh sharma
> Fix For: 2.1.2, 2.1.x
>
>
> Current security section doesn't provide an intuitive way to add role 
> mappings. Also the wizard doesn't ask for the complete information about 
> role-mappings for the roles defined in web.xml.
> Also the Table viewer isn't a very good option for displaying role mappings 
> where a Tree viewer would fit well.

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

[jira] Created: (GERONIMODEVTOOLS-423) Add more options to the Security Section in

2008-07-09 Thread Saurabh sharma (JIRA)

Add more options to the Security Section in 


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




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

[jira] Assigned: (GERONIMODEVTOOLS-422) Reduce the clutter of tables in Naming and Deployment page


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

Sainath Chowdary reassigned GERONIMODEVTOOLS-422:
-

Assignee: (was: Sainath Chowdary)

> Reduce the clutter of tables in Naming and Deployment page
> --
>
> Key: GERONIMODEVTOOLS-422
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-422
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Priority: Minor
> Fix For: 2.1.2, 2.1.x
>
> Attachments: clutter-reduce.patch, screenshot-1.jpg
>
>
> There are too many tables that clutter the Naming Form Page and Deployment 
> age in Geronimo Deployment Plan Editors. 
> GEP should try to show only the sections that are absolutely necessary and 
> rest of the sections can be shown in un-expanded state. If user wants to edit 
> the un-expanded sections, he can simply expand and edit those.

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

[jira] Updated: (GERONIMODEVTOOLS-422) Reduce the clutter of tables in Naming and Deployment page


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

Sainath Chowdary updated GERONIMODEVTOOLS-422:
--

Attachment: screenshot-1.jpg

screenshot-1 shows the new Naming Form Page with only two section starting in 
expanded state.

> Reduce the clutter of tables in Naming and Deployment page
> --
>
> Key: GERONIMODEVTOOLS-422
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-422
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Sainath Chowdary
>Priority: Minor
> Fix For: 2.1.2, 2.1.x
>
> Attachments: clutter-reduce.patch, screenshot-1.jpg
>
>
> There are too many tables that clutter the Naming Form Page and Deployment 
> age in Geronimo Deployment Plan Editors. 
> GEP should try to show only the sections that are absolutely necessary and 
> rest of the sections can be shown in un-expanded state. If user wants to edit 
> the un-expanded sections, he can simply expand and edit those.

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

[jira] Updated: (GERONIMODEVTOOLS-422) Reduce the clutter of tables in Naming and Deployment page


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

Sainath Chowdary updated GERONIMODEVTOOLS-422:
--

Attachment: clutter-reduce.patch

This patch makes some of the sections in Naming Form page and Deployment page 
start in unexpanded state which very much improves the look and feel of 
Deployment Editor.

Also contains some code regarding the look and feel of Web Container section in 
Web General Page.

> Reduce the clutter of tables in Naming and Deployment page
> --
>
> Key: GERONIMODEVTOOLS-422
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-422
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Sainath Chowdary
>Priority: Minor
> Fix For: 2.1.2, 2.1.x
>
> Attachments: clutter-reduce.patch
>
>
> There are too many tables that clutter the Naming Form Page and Deployment 
> age in Geronimo Deployment Plan Editors. 
> GEP should try to show only the sections that are absolutely necessary and 
> rest of the sections can be shown in un-expanded state. If user wants to edit 
> the un-expanded sections, he can simply expand and edit those.

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

[jira] Updated: (GERONIMODEVTOOLS-422) Reduce the clutter of tables in Naming and Deployment page


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

Sainath Chowdary updated GERONIMODEVTOOLS-422:
--

Description: 
There are too many tables that clutter the Naming Form Page and Deployment age 
in Geronimo Deployment Plan Editors. 

GEP should try to show only the sections that are absolutely necessary and rest 
of the sections can be shown in un-expanded state. If user wants to edit the 
un-expanded sections, he can simply expand and edit those.

  was:
There are too many tables that clutter the Naming Form Page and Deployment age 
in Geronimo Deployment Plan Editors. 

GEP should try to show only the sections that are absolutely necessary and rest 
of the sections can be shown in un-expanded state. If user wants to edit the 
un-expanded sections, he can simply expand and edit those.





 Patch Info: [Patch Available]

> Reduce the clutter of tables in Naming and Deployment page
> --
>
> Key: GERONIMODEVTOOLS-422
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-422
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.2, 2.1.x
>Reporter: Sainath Chowdary
>Assignee: Sainath Chowdary
>Priority: Minor
> Fix For: 2.1.2, 2.1.x
>
>
> There are too many tables that clutter the Naming Form Page and Deployment 
> age in Geronimo Deployment Plan Editors. 
> GEP should try to show only the sections that are absolutely necessary and 
> rest of the sections can be shown in un-expanded state. If user wants to edit 
> the un-expanded sections, he can simply expand and edit those.

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

[jira] Created: (GERONIMODEVTOOLS-422) Reduce the clutter of tables in Naming and Deployment page

Reduce the clutter of tables in Naming and Deployment page
--

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


There are too many tables that clutter the Naming Form Page and Deployment age 
in Geronimo Deployment Plan Editors. 

GEP should try to show only the sections that are absolutely necessary and rest 
of the sections can be shown in un-expanded state. If user wants to edit the 
un-expanded sections, he can simply expand and edit those.





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

[jira] Commented: (GERONIMO-3811) EjbServer portlet

2008-07-09 Thread Manu T George (JIRA)


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

Manu T George commented on GERONIMO-3811:
-

This uses dojo 0.4. Since 2.2 plans to ship only dojo 11 this needs to be 
ported to dojo 1.1. The patch also needs to be recreated as it no longer applies

> EjbServer portlet
> -
>
> Key: GERONIMO-3811
> URL: https://issues.apache.org/jira/browse/GERONIMO-3811
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
> Environment: All
>Reporter: Manu T George
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: g3811_r634213.patch, g3811_r639236.patch, 
> g3811_r640786.patch, screenshot-1.jpg, screenshot-2.jpg
>
>
> A portlet to show information about the OpenEJB container  integrated in 
> Geronimo. It should also allow configuration of some parameters like pool 
> size etc

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

[jira] Assigned: (GERONIMO-3811) EjbServer portlet

2008-07-09 Thread Manu T George (JIRA)


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

Manu T George reassigned GERONIMO-3811:
---

Assignee: Manu T George  (was: Donald Woods)

> EjbServer portlet
> -
>
> Key: GERONIMO-3811
> URL: https://issues.apache.org/jira/browse/GERONIMO-3811
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
> Environment: All
>Reporter: Manu T George
>Assignee: Manu T George
> Fix For: 2.2
>
> Attachments: g3811_r634213.patch, g3811_r639236.patch, 
> g3811_r640786.patch, screenshot-1.jpg, screenshot-2.jpg
>
>
> A portlet to show information about the OpenEJB container  integrated in 
> Geronimo. It should also allow configuration of some parameters like pool 
> size etc

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

[jira] Updated: (GERONIMO-4188) View Server portlet runs in unhandled exception if the statistics bean is not available

2008-07-09 Thread YunFeng Ma (JIRA)


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

YunFeng Ma updated GERONIMO-4188:
-

Attachment: GERONIMO-4188.patch

A patch for this. It will show "The statistics bean is not available now." if 
the statistics bean is not available.

> View Server portlet runs in unhandled exception if the statistics bean is not 
> available
> ---
>
> Key: GERONIMO-4188
> URL: https://issues.apache.org/jira/browse/GERONIMO-4188
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: YunFeng Ma
> Fix For: 2.2
>
> Attachments: GERONIMO-4188.patch
>
>
> The steps to recreate the error:
> 1. Deploy a web application, such as sample1
> 2. Monitor the web application in Admin Console
> 3. Stop the web application
> 4. Click "Monitoring" --> "localhost" , then get the following error:
> {noformat}
> javax.portlet.PortletException
>   at 
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
>   at 
> org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:337)
>   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
>   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
>   at 
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
>   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
>   at 
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
>   at 
> org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
>   at 
> org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
>   at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
>   at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:87)
>   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
>   at 
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
>   at 
> jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:219)
>   at 
> jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:105)
>   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
>   at 
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:151)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja

[jira] Created: (GERONIMO-4188) View Server portlet runs in unhandled exception if the statistics bean is not available

2008-07-09 Thread YunFeng Ma (JIRA)

View Server portlet runs in unhandled exception if the statistics bean is not 
available
---

 Key: GERONIMO-4188
 URL: https://issues.apache.org/jira/browse/GERONIMO-4188
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: monitoring
Reporter: YunFeng Ma
 Fix For: 2.2


The steps to recreate the error:
1. Deploy a web application, such as sample1
2. Monitor the web application in Admin Console
3. Stop the web application
4. Click "Monitoring" --> "localhost" , then get the following error:
{noformat}
javax.portlet.PortletException
at 
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
at 
org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:337)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at 
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
at 
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at 
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at 
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
at 
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at 
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:87)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:219)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:105)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at 
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:151)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at 
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBa

[jira] Updated: (GERONIMO-4081) Accessibility issue: Webking scan errors against "Check Web Accessibility(Section 508)" rules


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

xuhaihong updated GERONIMO-4081:


Attachment: GERONIMO-4081-plancreator.patch

Fix for accessibility issue .\plugins\plancreator

> Accessibility issue: Webking scan errors against "Check Web 
> Accessibility(Section 508)" rules
> -
>
> Key: GERONIMO-4081
> URL: https://issues.apache.org/jira/browse/GERONIMO-4081
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.1, 2.1.2, 2.2
> Environment: Windows XP SP2, IE 6.0
> Webking 5.5
>Reporter: Xia Ming
> Fix For: 2.2
>
> Attachments: GERONIMO-4081-activemq.patch, 
> GERONIMO-4081-ca-helper.patch, GERONIMO-4081-console.patch, 
> GERONIMO-4081-debugviews.patch, GERONIMO-4081-monitoring.patch, 
> GERONIMO-4081-plancreator.patch, GERONIMO-4081-system-database.patch, 
> GERONIMO-4081-welcome.patch, screenshot-1.jpg, webking_scan_results.csv, 
> webking_scan_results_src.csv
>
>
> Lots of instances are violated from the accessibility rules of section 508, 
> see the attachment for details. thanks!

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

[jira] Updated: (GERONIMO-4081) Accessibility issue: Webking scan errors against "Check Web Accessibility(Section 508)" rules


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

xuhaihong updated GERONIMO-4081:


Attachment: GERONIMO-4081-system-database.patch

Fix for accessibility issue .\plugins\system-database

> Accessibility issue: Webking scan errors against "Check Web 
> Accessibility(Section 508)" rules
> -
>
> Key: GERONIMO-4081
> URL: https://issues.apache.org/jira/browse/GERONIMO-4081
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.1, 2.1.2, 2.2
> Environment: Windows XP SP2, IE 6.0
> Webking 5.5
>Reporter: Xia Ming
> Fix For: 2.2
>
> Attachments: GERONIMO-4081-activemq.patch, 
> GERONIMO-4081-ca-helper.patch, GERONIMO-4081-console.patch, 
> GERONIMO-4081-debugviews.patch, GERONIMO-4081-monitoring.patch, 
> GERONIMO-4081-plancreator.patch, GERONIMO-4081-system-database.patch, 
> GERONIMO-4081-welcome.patch, screenshot-1.jpg, webking_scan_results.csv, 
> webking_scan_results_src.csv
>
>
> Lots of instances are violated from the accessibility rules of section 508, 
> see the attachment for details. thanks!

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

[jira] Updated: (GERONIMO-4081) Accessibility issue: Webking scan errors against "Check Web Accessibility(Section 508)" rules


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

xuhaihong updated GERONIMO-4081:


Attachment: GERONIMO-4081-monitoring.patch

Fix for accessibility issue .\plugins\monitoring

> Accessibility issue: Webking scan errors against "Check Web 
> Accessibility(Section 508)" rules
> -
>
> Key: GERONIMO-4081
> URL: https://issues.apache.org/jira/browse/GERONIMO-4081
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.1, 2.1.2, 2.2
> Environment: Windows XP SP2, IE 6.0
> Webking 5.5
>Reporter: Xia Ming
> Fix For: 2.2
>
> Attachments: GERONIMO-4081-activemq.patch, 
> GERONIMO-4081-ca-helper.patch, GERONIMO-4081-console.patch, 
> GERONIMO-4081-debugviews.patch, GERONIMO-4081-monitoring.patch, 
> GERONIMO-4081-plancreator.patch, GERONIMO-4081-system-database.patch, 
> GERONIMO-4081-welcome.patch, screenshot-1.jpg, webking_scan_results.csv, 
> webking_scan_results_src.csv
>
>
> Lots of instances are violated from the accessibility rules of section 508, 
> see the attachment for details. thanks!

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

[jira] Updated: (GERONIMO-4081) Accessibility issue: Webking scan errors against "Check Web Accessibility(Section 508)" rules