[jira] Created: (GERONIMO-4605) Text based apache license at the bottom of every console pages

2009-03-30 Thread Shawn Jiang (JIRA)
Text based apache license at the bottom of every console pages
--

 Key: GERONIMO-4605
 URL: https://issues.apache.org/jira/browse/GERONIMO-4605
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.1.4, 2.1.5
 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP
Reporter: Shawn Jiang
Priority: Minor


There are text based apache licenses at the bottom of every console pages like 
this:

---
* * Licensed to the Apache Software Foundation (ASF) under one or more * 
contributor license agreements. See the NOTICE file distributed with * this 
work for additional information regarding copyright ownership. * The ASF 
licenses this file to You under the Apache License, Version 2.0 * (the 
License); you may not use this file except in compliance with * the License. 
You may obtain a copy of the License at * * 
http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable 
law or agreed to in writing, software * distributed under the License is 
distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY 
KIND, either express or implied. * See the License for the specific language 
governing permissions and * limitations under the License. */ 
---

It's not a big but an annoying problem from user's perspective. 

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



[jira] Updated: (GERONIMO-4605) Text based apache license at the bottom of every console pages

2009-03-30 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4605:
--

Attachment: G4605.patch

The patch to change the comments format in js file to fix this problem.

 Text based apache license at the bottom of every console pages
 --

 Key: GERONIMO-4605
 URL: https://issues.apache.org/jira/browse/GERONIMO-4605
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.4, 2.1.5
 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP
Reporter: Shawn Jiang
Priority: Minor
 Attachments: G4605.patch


 There are text based apache licenses at the bottom of every console pages 
 like this:
 ---
 * * Licensed to the Apache Software Foundation (ASF) under one or more * 
 contributor license agreements. See the NOTICE file distributed with * this 
 work for additional information regarding copyright ownership. * The ASF 
 licenses this file to You under the Apache License, Version 2.0 * (the 
 License); you may not use this file except in compliance with * the 
 License. You may obtain a copy of the License at * * 
 http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable 
 law or agreed to in writing, software * distributed under the License is 
 distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY 
 KIND, either express or implied. * See the License for the specific language 
 governing permissions and * limitations under the License. */ 
 ---
 It's not a big but an annoying problem from user's perspective. 

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



Re: [VOTE] Release Geronimo Server 2.1.4 RC2

2009-03-30 Thread Shawn Jiang
There are text based apache licenses at the bottom of every console pages
like this:
---
* * Licensed to the Apache Software Foundation (ASF) under one or more *
contributor license agreements. See the NOTICE file distributed with * this
work for additional information regarding copyright ownership. * The ASF
licenses this file to You under the Apache License, Version 2.0 * (the
License); you may not use this file except in compliance with * the
License. You may obtain a copy of the License at * *
http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable
law or agreed to in writing, software * distributed under the License is
distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. * See the License for the specific language
governing permissions and * limitations under the License. */
---

It's not a big  problem.  I opened a JIRA here with a patch:
https://issues.apache.org/jira/browse/GERONIMO-4605.https://issues.apache.org/jira/browse/GERONIMO-4605


On Fri, Mar 27, 2009 at 6:20 AM, Joe Bohn joe.b...@earthlink.net wrote:

 All,

 I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for
 your review and vote.

 The only differences from rc1 are:
 - addition of a missing license header in
 plugins/console/console-filter/src/main/resources/XSRF.js
 - removal of an extraneous (TBD) in README.txt


 The source for rc2 is Rev758842 from the following svn branch:
  https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/

 When the release vote is approved, I will svn mv the code to:
  https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

 An archive of this source code can be found here:

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz
 OR

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10
 server binary distributions to be released (framework, tomcat/jetty, Java
 EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE,
 DISCLAIMER, and source code archives for the release.  These extra txt files
 were included so that they could be leveraged by GEP if necessary (they are
 also included in the assembly images).

 For your convenience, here are pointers to the urls for the
 distributions in zip format:

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip

 http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip


 The maven artifacts for the release can be found here:
  http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/

 When the release vote is approved, these maven artifacts will be moved
 to the m2-ibiblio-rsync-repository at Apache.


 [ ] +1 Release Geronimo Server 2.1.4
 [ ] 0 No opinion
 [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale)


 The voting will be open for 72 hours or until sufficient input has been
 received and the tck results have been verified.

 Thanks,
 Joe




-- 
Shawn


[jira] Created: (GERONIMO-4606) a error when creating a JMS destination for a JMS resouse group.

2009-03-30 Thread Shawn Jiang (JIRA)
a error when creating a JMS destination for a JMS resouse group.


 Key: GERONIMO-4606
 URL: https://issues.apache.org/jira/browse/GERONIMO-4606
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: geronimo tomcat 2.1.4 snapshot.  + IBM JDK 1.5 + windows 
XP.
Reporter: Shawn Jiang


Steps to reproduce:

1, Use IE7 to connect the started geronimo-tomcat 2.1.4 RC2.

2, Go to CONSOLE  -- JMS Resources  -- create a JMS Resource Group  -- 
create a connect factory --- create a destination -- input two name for the 
destination -- click next to create the destination.


Expected result:  the destination is created and return to JMS Resource Group 
list view.

Actual result:  an error page displayed with something like IE can't display 
the requested page



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



Re: [VOTE] Release Geronimo Server 2.1.4 RC2

2009-03-30 Thread Joe Bohn
Doh! ... I can't believe that we all missed that.  But as you said, it 
doesn't seem to be a big deal from a user perspective so I think it can 
wait until the next release.  Thanks for reporting the issue!


Joe


Shawn Jiang wrote:
There are text based apache licenses at the bottom of every console 
pages like this:

---
* * Licensed to the Apache Software Foundation (ASF) under one or more * 
contributor license agreements. See the NOTICE file distributed with * 
this work for additional information regarding copyright ownership. * 
The ASF licenses this file to You under the Apache License, Version 2.0 
* (the License); you may not use this file except in compliance with * 
the License. You may obtain a copy of the License at * * 
http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by 
applicable law or agreed to in writing, software * distributed under the 
License is distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR 
CONDITIONS OF ANY KIND, either express or implied. * See the License for 
the specific language governing permissions and * limitations under the 
License. */ 
---


It's not a big  problem.  I opened a JIRA here with a patch:
https://issues.apache.org/jira/browse/GERONIMO-4605. 
https://issues.apache.org/jira/browse/GERONIMO-4605



On Fri, Mar 27, 2009 at 6:20 AM, Joe Bohn joe.b...@earthlink.net 
mailto:joe.b...@earthlink.net wrote:


All,

I've prepared a second release candidate (RC2) of Geronimo Server
2.1.4 for your review and vote.

The only differences from rc1 are:
- addition of a missing license header in
plugins/console/console-filter/src/main/resources/XSRF.js
- removal of an extraneous (TBD) in README.txt


The source for rc2 is Rev758842 from the following svn branch:
 https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/

When the release vote is approved, I will svn mv the code to:
 https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

An archive of this source code can be found here:

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz
OR

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains
the 10 server binary distributions to be released (framework,
tomcat/jetty, Java EE/Minimal, tar/zip) as well as the
RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code
archives for the release.  These extra txt files were included so
that they could be leveraged by GEP if necessary (they are also
included in the assembly images).

For your convenience, here are pointers to the urls for the
distributions in zip format:

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip

http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip


The maven artifacts for the release can be found here:
 http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/

When the release vote is approved, these maven artifacts will be moved
to the m2-ibiblio-rsync-repository at Apache.


[ ] +1 Release Geronimo Server 2.1.4
[ ] 0 No opinion
[ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale)


The voting will be open for 72 hours or until sufficient input has
been received and the tck results have been verified.

Thanks,
Joe




--
Shawn




[jira] Updated: (GERONIMO-4605) Text based apache license at the bottom of every console pages

2009-03-30 Thread Joe Bohn (JIRA)

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

Joe Bohn updated GERONIMO-4605:
---

Affects Version/s: 2.2

 Text based apache license at the bottom of every console pages
 --

 Key: GERONIMO-4605
 URL: https://issues.apache.org/jira/browse/GERONIMO-4605
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
 Attachments: G4605.patch


 There are text based apache licenses at the bottom of every console pages 
 like this:
 ---
 * * Licensed to the Apache Software Foundation (ASF) under one or more * 
 contributor license agreements. See the NOTICE file distributed with * this 
 work for additional information regarding copyright ownership. * The ASF 
 licenses this file to You under the Apache License, Version 2.0 * (the 
 License); you may not use this file except in compliance with * the 
 License. You may obtain a copy of the License at * * 
 http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable 
 law or agreed to in writing, software * distributed under the License is 
 distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY 
 KIND, either express or implied. * See the License for the specific language 
 governing permissions and * limitations under the License. */ 
 ---
 It's not a big but an annoying problem from user's perspective. 

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



[jira] Resolved: (GERONIMO-4605) Text based apache license at the bottom of every console pages

2009-03-30 Thread Joe Bohn (JIRA)

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

Joe Bohn resolved GERONIMO-4605.


   Resolution: Fixed
Fix Version/s: 2.2
   2.1.5

fixed integrated in branches/2.1 with rev. 759950 and trunk with rev. 759952

 Text based apache license at the bottom of every console pages
 --

 Key: GERONIMO-4605
 URL: https://issues.apache.org/jira/browse/GERONIMO-4605
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: G4605.patch


 There are text based apache licenses at the bottom of every console pages 
 like this:
 ---
 * * Licensed to the Apache Software Foundation (ASF) under one or more * 
 contributor license agreements. See the NOTICE file distributed with * this 
 work for additional information regarding copyright ownership. * The ASF 
 licenses this file to You under the Apache License, Version 2.0 * (the 
 License); you may not use this file except in compliance with * the 
 License. You may obtain a copy of the License at * * 
 http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable 
 law or agreed to in writing, software * distributed under the License is 
 distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY 
 KIND, either express or implied. * See the License for the specific language 
 governing permissions and * limitations under the License. */ 
 ---
 It's not a big but an annoying problem from user's perspective. 

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



Re: [DISCUSSION] to create a set of maven archetypes for applications running on geronimo ?

2009-03-30 Thread David Jencks
I had a lot more thoughts on this subject while working up my  
apachecon eu talk on geronimo server assemblies.


Right now we have a _lot_ of deployer code that carefully examines  
exactly what your app needs and depending on what it finds adds  
dependencies to the classloader.  For instance if it figures out you  
have a web app and it's the jetty deployer it adds the jetty car as a  
parent.  (Some of the smaller deployer bits I think currently always  
add their dependencies since there was a problem with changing the  
classpath but I hope this can be fixed with the recent configuration/ 
classloader work).


I think the plugin archetype should do this too.  You tell it what app  
you are trying to deploy and some kind of profile like jetty/tomcat  
and cxf/axis2 and it (should) use the same logic as the deployer to  
figure out what is needed.  For the archetype, it should be adding the  
dependencies and deployer dependencies to the pom and listing the  
deployer dependencies the car-maven-plugin needs to start.


re stringtemplate vs. velocity I don't know enough about how the  
archetype framework to judge whether anything except velocity is  
plausible.


Are you actively working on this project?  If not I might see if  
there's some fairly easy way to access the decision making the current  
deployers use.


thanks!
david jencks

On Mar 17, 2009, at 1:26 AM, Shawn Jiang wrote:

It looks to me as if there are no plans in the javaee apps parts of  
the samples apps, so the plans are all in the plugin modules.  I  
really don't think we want to duplicate the functionality of the  
existing archetypes that do a fine job of creating projects for java  
ee apps.  If you really do want to help people make projects like  
the sample apps, the way to do that is to improve the plugin  
archetype.


Thanks for your comments.  actually, what I said was to make the  
pom.xml and plan.xml template but not the JEE app itself.  For  
example:


servlet-examples/
pom.xml
servlet-examples-jetty/
pom.xml
src/
main/
plan/
plan.xml
servlet-examples-tomcat/
servlet-examples-war/

 From this pespective, what I was talking about is to create plugins  
archetype instead of JEE app archetype.



 I like your ideas about what can be generated in the geronimo  
plan.  I think we can also generate a lot more of the pom than we do  
now.


I agree.

I would be very tempted to try stringtemplate instead of velocity.   
I think its clear MVC separation and roots in code generation  
technology (it's the output stage for antlr)  may prove useful for  
the manipulation we need to do.


But how could we reuse the existing powerful maven archetype if  
using stringtemplate ?  I feel that StringTemplate is more useful in  
a MVC framework but not in a project generating  tool.  Do you agree ?


While enabling people to reproduce our sample apps is probably  
better than what we do now, I'd prefer to help them with apps that  
actually do a realistic amount of work.  I think improving the  
plugin archetype would be a really big help.


I suggest to start with the current sample plugins.   The final goal  
is to reduce most of the effort to release all samples for each  
geronimo version by providing stable archetype.


thanks
david jencks





On Tue, Mar 17, 2009 at 3:35 PM, David Jencks  
david_jen...@yahoo.com wrote:


On Mar 16, 2009, at 11:50 PM, Shawn Jiang wrote:

From my point of view, every current geronimo sample could be  
converted to a archetype. So that the user just needs install maven  
and he could just type a command like this:


mvn archetype:generate 
-DarcheTypeCatalog=http://geronimo.apache.org/archetypes/samples

he will get a sample menu like this:

Choose archetype:
1: internal - hello (geronimo sample web application project)
2: internal - calculator-stateless-pojo (geronimo sample ejb  
project)

3: internal - mdb (geronimo Message-Driven Bean sample project)
4: internal - GBean(simple geronimo GBean project)
5: internal - 
6: internal - 
7: internal - 

Choose a number:  (1/2/3/4/5/6/7) 1: : 1

select 1 to create a hello sample project will bring him to a  
wizard like this:



Define value for geronimo_version: : 2.1.4
Define value for context_root: : hellocontext
Define value for groupId: : my.first.geronimo.web
Define value for artifactId: : helloApp
Define value for version:  1.0-SNAPSHOT: :
Define value for package:  my.first.geronimo.web: :
Confirm properties configuration:
geronimo_version: 2.1.4
context_root: hellocontext
groupId: my.first.geronimo.web
artifactId: helloApp
version: 1.0-SNAPSHOT
package: my.first.geronimo.web
 Y: : Y

notice the user could define which geronimo version he is using and  
defind the context root 

[BUILD] trunk: Failed for Revision: 760269

2009-03-30 Thread gawor
Geronimo Revision: 760269 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090330/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090330
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 12 seconds
[INFO] Finished at: Mon Mar 30 21:40:47 EDT 2009
[INFO] Final Memory: 678M/978M
[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/20090330/logs-2100-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-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:41.607
[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 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:00:59.577) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:28.267) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:33.165) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.931) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:24.349) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:28.502) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:53.557) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:47.840) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:49.414) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:42.960) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:29.744) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.294) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:32.894) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.517) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.539) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.861) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:28.128) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:49.167) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:37.087) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:31.930) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5

Initial Draft for gsoc [WS-Security support for JAX-WS Web Services] project

2009-03-30 Thread rahul.soa
Hello Devs,

I have written a very initial draft for gsoc WS-Security support for
JAX-WS Web Services project [1]. Please suggest any modifications.
Thanks to Jarek for his thoughts and immediate help.

// Quote

Title: WS-Security support for JAX-WS Web Services

Abstract:

To integrate and enable the WS-Security features of Apache Axis2 and
Apache CXF in Apache Geronimo on web services.

Description:

Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both
of these libraries have some WS-Security features. But these features
are not integrated/enabled in Geronimo. So the goal is to enable these
features from within Geronimo. That involves basically two things:

1) that the modules (i.e. WSS4J) that provide the WS-Security features
for Axis2 and CXF are installed with Geronimo, and

2) that the WS-Security features such as [XML Security ('XML
Signature' - allows one to send along with the message a digital
signature of it, which assures that no one modified the message
content between the sender and receiver, 'XML Encryption' -allows one
to encrypt the message body or only its part using the given
cryptography algorithm) and Tokens ('Username Tokens' - WS-Security
scenario adds username and password values to the message header,
'Timestamps' - Timestamps specify how long the security data remains
valid, 'SAML Tokens')] can be enabled and configured on web services
via Geronimo deployment descriptors and/or annotations. For example,
given some web service that is annotated with @WebService; so to
ensure that the service only accepts WS-Security -secured messages, it
should be something like “to add @WS-Security annotation”.

Further in detail, we can consider WS-Security policies which can be
applied to the SOAP messages that pass between web services and web
service controls. A WS-Security is controlled in WS-Security policy
files. The WS-Security policy file (WSSE file) defines the security
policy applied to the SOAP messages that pass between web services and
their clients.[1]

So we can use something like following annotation
@WS-Security file=MyWebServicePolicy.wsse
Example:
@WebService
@WS-Security file=MyWebServicePolicy.wsse
public class xyz

The @WS-Security annotation determines the WS-Security policy file
(WSSE) to be applied to (1) incoming SOAP invocations of the web
service's methods and (2) the outgoing SOAP messages containing the
value returned by the web service's methods.[1]. The attribute file in
the above mentioned annotation specifies the path to the WS-Security
policy file (WSSE file - MyWebServicePolicy.wsse) used by the web
service.

In addition, I think we can also define some security feature
something like SecurityFeature similar to other WebService Feature(s)
such as AddressingFeature, MTOMFeature
 and RespectBindingFeature
. This new feature can also have the “enabled property” like other
features that is used to store whether a particular feature should be
enabled or disabled. This type should provide either a constructor
argument
 and/or a method that will allow the web service developer to set the
enabled property. The meaning of enabled or disabled is determined by
each individual WebServiceFeature. It is important that web services
developers be able to enable/disable specific features when writing
their web applications. [2]

[1] http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html

[2] http://jcp.org/aboutJava/communityprocess/mrel/jsr224/index2.html


//Unquote

Any suggestion will be appreciable.

* Please put my email id in cc if you reply to mailing list only as I
am not on the mailing list at this time. I have sent requests many
times but could not get the confirmation reply for joining the mailing
list so far.

Many Thanks.

Best Regards,
Rahul

[1] http://wiki.apache.org/general/SummerOfCode2009#cxf-project


Re: Develop a Geronimo Quartz Plugin

2009-03-30 Thread Ivan
Hi, Martin Benkov:
 Very appreciated with your interest in the idea. Since you have 3 years
experience with java, I think you should be OK.
 If you have used Geronimo in the past, that would be better
 Quartz plugin is introduced in Geronimo 1.*, while in the Geronimo 2.*,
it is not updated. So we wish to update the Quartz plugin to the 2.*.
 Before you begin the work, I suggest that
 1. Subscribe the geronimo dev maillist, so that the discussion could be
seen by all the members, and someone may give some good suggestions.
 2. Read some articles in the Geronimo wiki (
http://geronimo.apache.org/documentation.html), following the instructions,
you could know how to build the developement envorionment, how the plugin
works 
 3. Check out the source codes from geroniom trunk (
https://svn.apache.org/repos/asf/geronimo/server/trunk), I wish to create
the plugin based on the trunk
 4. You could also check out the old quartz plugin codes from
https://svn.apache.org/repos/asf/geronimo/sandbox/quartz-plugin
 But it could not work in the new Geronimo 2.*, only can refer to
how it works in the past.
 5. If you finally decided to be involved in it, maybe you need to
register in the google's website.
 Thanks!
  Ivan



2009/3/31 Мартин Бенков martinben...@gmail.com

 Hello,

 I'm willing to attend SoC this year. I have 3 years experience with java
 and year and a half with J2EE(I've worked at SAP Labs Bulgaria in the team
 responsible for the JMS specification)

 My main concern is am I appropriate for this task. If yes where can I find
 more information about this Quartz plugin.

 I'm looking forward to hearing from you.

 Regards,
 Martin Benkov




-- 
Ivan


[jira] Reopened: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter

2009-03-30 Thread Forrest Xia (JIRA)

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

Forrest Xia reopened GERONIMO-4549:
---


 JMS resource jndi entries are not removed after uninstalling the JMS connect 
 adapter
 

 Key: GERONIMO-4549
 URL: https://issues.apache.org/jira/browse/GERONIMO-4549
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
Reporter: Forrest Xia
Assignee: Jack Cai
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: Geronimo-4549_0307.patch


 Steps to reproduce this problem:
 1. login admin console
 2. Create a ActiveMQ resource connector with the wizard
 3. Deploy it and check it is in running state
 4. Click J2EE connector to uninstall it
 5. Check JNDI viewer, you will see the JNDI entry still there, even you've 
 uninstalled it.

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