date:20070914


Thanks Tim and Kevan!

Lin

Tim McConnell wrote:

Hi Kevan, yes I shall handle via:

http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-207

Kevan Miller wrote:


On Sep 13, 2007, at 5:39 PM, Kevan Miller wrote:


On Sep 13, 2007, at 4:44 PM, Lin Sun wrote:


I think we also need to update the license in the feature.properties 
file for each of the feature we provide.   Right now, I only saw ASL 
2.0 there.   The license in the feature.properties file is presented 
to a user when they install the Geronimo Eclipse plugin or server 
runtime using the Eclipse update manager, before he/she clicks on 
accept the license to install our Geronimo eclipse plugin or server 
runtime.



It may make sense to put the contents of both the license and notice 
file there.




Ah, ok. That makes sense. I didn't know what the feature.properties 
files were used for (just saw that they didn't have any non 
ASL/Geronimo artifacts). Thanks for reviewing!




Lin or Tim,
Is that something that one of you can take care of?

--kevan

Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Guillaume Nodet

If this is the case, the consumer endpoint can be accessed on the message
exchange.  IIRC there is also a property that has a unique ID for this
endpoint.
The URI should also be available as a property.

On 9/14/07, Gert Vanthienen [EMAIL PROTECTED] wrote:

 Guillaume,

 I think this this user has several http consumer endpoints, configured
 at different URIs (e.g. http://0.0.0.0/service1,
 http://0.0.0.0/service2, http://0.0.0.0/service3).  On all of these
 endpoints, the same targetService is configured (ex:Service) and it is
 in this targetService that he would like to distinguish between the
 originating consumer endpoints.

 Gert

 Guillaume Nodet wrote:
  Maybe you could rewrite your question ?
  I don't really understand what you want to do.
  The URI of the http endoint is usually configured using
  the httpLocation attribute of the endpoint...
 
  On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:
 
  No help for me ?
  --
  View this message in context:
 
 http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
  Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
 
 
 
 
 
 




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Re: Getting started: Using the Maven tooling

2007-09-14 Thread Gert Vanthienen


L.S.,

Done!  Wouldn't it be a good idea to add the distinction between 
beginner - intermediate - advanced to this page 
(http://incubator.apache.org/servicemix/tutorials.html) as well, just to 
'discourage' beginner users to start writing SE/BC on day 1?


Secondly, how about adding a links to these tutorials in the sites 
navigation (e.g. between user's guide and documentation)?


Gert

Guillaume Nodet wrote:

What about moving these tutorials out of the sandbox ...

On 8/9/07, Gert Vanthienen [EMAIL PROTECTED] wrote:
  

L.S.,

I added a second tutorial to the wiki Sandbox
(http://cwiki.apache.org/confluence/x/Q94), explaining to a newbie user
how to leverage the Maven archetypes and tooling for building their own
service assemblies.  Any comments, corrections, feedback, ... are welcome.


Gert

Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Guillaume Nodet

The consumer *component* can be retrieved using:

((MessageExchangeImpl) exchange).getSourceContext().getComponent()

ServiceMix components also set the following property:

exchange.getProperty(JbiConstants.SENDER_ENDPOINT)

which returns a string uniquely identifying the endpoint.

I don't really recall where/if the uri is stored...

On 9/14/07, Guillaume Nodet [EMAIL PROTECTED] wrote:

If this is the case, the consumer endpoint can be accessed on the message
exchange. IIRC there is also a property that has a unique ID for this
endpoint.
The URI should also be available as a property.

On 9/14/07, Gert Vanthienen [EMAIL PROTECTED] wrote:

Guillaume,

I think this this user has several http consumer endpoints, configured
at different URIs (e.g. http://0.0.0.0/service1,
http://0.0.0.0/service2 , http://0.0.0.0/service3). On all of these
endpoints, the same targetService is configured (ex:Service) and it is
in this targetService that he would like to distinguish between the
originating consumer endpoints.

Gert

Guillaume Nodet wrote:
Maybe you could rewrite your question ?
I don't really understand what you want to do.
The URI of the http endoint is usually configured using
the httpLocation attribute of the endpoint...

On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:

No help for me ?
--
View this message in context:
http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738

Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

Things don't automatically happen in WTP 1.5.1.   We had to register our 
features with WTP to get it shown up on the list.  I hope they are doing 
this automatically for 2.0.1 RC too, but if not, we probably should 
raise a WTP bugzilla as soon as possible to get it into 2.0.1.


Lin

Ted Kirby wrote:


Cool!  I just tried this.  It looks like it interrogates known sites
for supported servers.  It appears that once we add our plugins/server
adapters to our production site, they will be picked up.
Interestingly, when clicking this button, I was offered one Apache
Geronimo server: 1.2.0!  (from
http://www.apache.org/dist/geronimo/eclipse/updates/.)  So yeah, I
think we need to fix this.

Ted Kirby


2) I tried to deploy a hello war project and able to deploy fine.   But
right click the project and do a run as, run on server doesn't bring up
the eclipse internal web browser automatically.   I wonder if someone
else has noticed this?

Lin


Tim McConnell wrote:

Start of discussion thread.

[jira] Created: (SM-1056) Add NamespaceContextImpl to servicemix-core

2007-09-14 Thread Gert Vanthienen (JIRA)

Add NamespaceContextImpl to servicemix-core
---

 Key: SM-1056
 URL: https://issues.apache.org/activemq/browse/SM-1056
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-core, servicemix-drools, servicemix-eip
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen


Currently, servicemix-eip and servicemix-drools each ship with an almost 
identical copy of NamespaceContextImpl.  It would be better to move this to 
servicemix-core (where the XPathExpression classes are -- which might also 
require a NamespaceContextImpl).  

In order not to break any existing xbean.xml files, we should keep the current 
classes in servicemix-eip and servicemix-drools (can become empty, simply 
inherit from the core one) to make sure that eip:namespace-context and 
drools:namespace-context still exist.

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

Re: [DISCUSS] G 2.0.2 Release plan

2007-09-14 Thread Jarek Gawor

Kevan,

I have one remaining task to do for 2.0.2. I would like to update the
version of CXF to 2.0.1 (or 2.0.2 if it is released really soon). Just
need to verify first if it is all good from TCK standpoint.

Jarek

On 9/14/07, Kevan Miller [EMAIL PROTECTED] wrote:
 All,
 I think it's time to start rolling out a 2.0.2 release. There have
 been a number of fixes in response to user issues, since 2.0.1. Time,
 I think, to make these available in a release. We'd also be able to
 make use of released versions of OpenJPA, Axis2, and hopefully
 OpenEjb, whittling away at our local builds...

 I think we have one must-fix problem that is outstanding -- the MEJB
 security issue. Assuming we resolve this problem, are there any other
 issues which must be resolved prior to a 2.0.2 release?

 Assuming we're in general agreement, I'd set a goal of creating a
 release candidate by next Friday (Sept 21). I'm volunteering to be
 the release manager.

 Thoughts?

 --kevan

[jira] Assigned: (GERONIMO-2925) Key used for encryption same for all server instances

2007-09-14 Thread David Jencks (JIRA)


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

David Jencks reassigned GERONIMO-2925:
--

Assignee: David Jencks

 Key used for encryption same for all server instances
 -

 Key: GERONIMO-2925
 URL: https://issues.apache.org/jira/browse/GERONIMO-2925
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: security
Affects Versions: 1.1.1, 1.1.2, 1.1.x, 1.2, 2.0-M5
Reporter: Michael Malgeri
Assignee: David Jencks
Priority: Critical

 We understand that WASCE use AES to encrypt the password.  You do 
 javax.crypto.Cipher.getInstance(AES) and init() with a hard-coded key.
 This key is same for all the WASCE server instances.  Anyone getting access 
 to a downloaded version of the software can have the algorithm and decrypt 
 the password.  So we need your urgent help on the following:
 1. provide a solution with key management that we can control
 2. provide a pluggable encryption solution so that we can use our internal 
 algorithms and key management
 At least,
 3. the key should be dynamically generated in each of the installations that 
 would reduce the ability to decrypt to someone who has access to the server.

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

Re: [DISCUSS] G 2.0.2 Release plan

2007-09-14 Thread Hernan Cunico


Kevan Miller wrote:

All,
I think it's time to start rolling out a 2.0.2 release. There have been 
a number of fixes in response to user issues, since 2.0.1. Time, I 
think, to make these available in a release. We'd also be able to make 
use of released versions of OpenJPA, Axis2, and hopefully OpenEjb, 
whittling away at our local builds...


I think we have one must-fix problem that is outstanding -- the MEJB 
security issue. 


Yup, need this one fixed before releasing 2.0.2

Assuming we resolve this problem, are there any other 

issues which must be resolved prior to a 2.0.2 release?

Assuming we're in general agreement, I'd set a goal of creating a 
release candidate by next Friday (Sept 21). I'm volunteering to be the 
release manager.


Thoughts?

--kevan



Cheers!
Hernan

[jira] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database

2007-09-14 Thread David Jencks (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527520
 ] 

David Jencks commented on GERONIMO-2188:


I'm mystified as to what you want me to do.  AFAICT the entire patch 
G2188-latest.patch was applied many months ago to trunk.  Could you please 
provide a patch against current trunk?  If you have all of tranql checked out 
the best would be to make the patch from the file system location corresponding 
to https://svn.codehaus.org/tranql  (the root of the tranql checkout) so it's 
really clear where the changes go.

 When oracle wrapper is used, commits are not immediately committed to oracle 
 database
 -

 Key: GERONIMO-2188
 URL: https://issues.apache.org/jira/browse/GERONIMO-2188
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: connector
Affects Versions: 1.1.1
Reporter: Krishnakumar B
Assignee: David Jencks
 Attachments: G2188-2.patch, G2188-latest.patch, G2188.patch


 We have to configure CommitBeforeAutCommit=true property exclusively in the 
 database connection pool plan, to have the ejb -based transactions 
 immediately committed for oracle database. Otherwise it only commits 
 transaction when  the server  shuts-down. This problem is not faces with 
 Derby database.

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

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:


Hi Lin/Kevan, do you all feel this change is a show-stopped for RC2 ?? If so,
I'll cancel the vote and start another one for RC3. Please advise. Thanks.

Lin Sun wrote:

Thanks Tim and Kevan!

Lin

Tim McConnell wrote:

Hi Kevan, yes I shall handle via:

http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-207

Kevan Miller wrote:


On Sep 13, 2007, at 5:39 PM, Kevan Miller wrote:


On Sep 13, 2007, at 4:44 PM, Lin Sun wrote:


I think we also need to update the license in the 
feature.properties file for each of the feature we provide.   Right 
now, I only saw ASL 2.0 there.   The license in the 
feature.properties file is presented to a user when they install 
the Geronimo Eclipse plugin or server runtime using the Eclipse 
update manager, before he/she clicks on accept the license to 
install our Geronimo eclipse plugin or server runtime.



It may make sense to put the contents of both the license and 
notice file there.




Ah, ok. That makes sense. I didn't know what the feature.properties 
files were used for (just saw that they didn't have any non 
ASL/Geronimo artifacts). Thanks for reviewing!




Lin or Tim,
Is that something that one of you can take care of?

--kevan







--
Thanks,
Tim McConnell

Re: New GShell-based Geronimo Server launcher now in server/trunk

2007-09-14 Thread David Jencks

BTW we should be careful of preserving the work Gianny did a while  
back to reduce the number of jars that need to be in lib by providing  
a bootstrap repository.  (I don't understand exactly what he did,  
this might not be exactly right).  I was hoping we could take the  
stax/jaxb jars back out of lib and thought I had an example of this  
working.


thanks
david jencks

On Sep 14, 2007, at 10:46 AM, Paul McMahan wrote:

Looking good.   I ran into a couple of CNFE's while trying to  
install plugins using bin/deploy.sh.   It was looking for the stax  
and jaxb classes.   I hacked around that by manually adding the  
stax and jaxb jars from geronimo/lib to my classpath.


Best wishes,
Paul


On Sep 13, 2007, at 6:11 AM, Jason Dillon wrote:

Aighty, I've converted *all* of the assemblies to include the new  
GShell-based server launcher goodness.


I'm still working on cleaning things up and adding more features  
to the core GShell bits.  And some things I'm going to change in  
direct response to how we end up integrating it into Geronimo.


I've already hooked up a custom GShell branding instance which  
helps change the default welcome text/help text/version muck to be  
Geronimo specific (and not GShell specific).  This is the first  
real usage of GShell being used to support another application  
(um, the server) so I imagine that I'll (we'll) learn a little bit  
about that and refactor the branding bits as we go along.


 * * *

I did a few things... first, I've changed the boilerplate modules  
to use the assembly module for most of the heavy lifting.


And then I've put in the same structure that was in my POC  
assembly into everything.


So that means that everything now has these additional goodies:

*Scripts

bin/gsh
bin/gsh.bat
bin/start-server
bin/start-server.bat

* Boot Jars

lib/boot/gshell-bootstrap.jar
lib/boot/plexus-classworlds-1.2-alpha-10.jar

* Runtime Jars

lib/gshell/ant-1.7.0.jar
lib/gshell/ant-launcher-1.7.0.jar
lib/gshell/geronimo-commands-2.1-SNAPSHOT.jar
lib/gshell/groovy-all-1.1-beta-2.jar
lib/gshell/gshell-cli-1.0-alpha-1-SNAPSHOT.jar
lib/gshell/gshell-embeddable-1.0-alpha-1-SNAPSHOT.jar
lib/gshell/jcl104-over-slf4j-1.4.3.jar
lib/gshell/slf4j-log4j12-1.4.3.jar

* Configuration

etc/gsh-classworlds.conf
etc/gsh-log4j.properties
etc/layout.xml
etc/META-INF/plexus
etc/META-INF/plexus/plexus.xml

* Example RC bits

etc/rc.d/start-server,default.groovy

And if you run the shell once, then you'll also find this:

var/log/gshell.log

I've left all of the other goodies there for now too, so for  
example these both should do very similar things:


bin/start-server
bin/geronimo run
bin/gsh -q start-server

 * * *

I'm not sure if I broke anything in the process, so I'd really  
appreciate it others could look this stuff over and provide some  
feedback.  I probably did break something... (sorry)... but I  
can't tell at the moment due to the tree not being buildable.


Remember I'm still whacking bits out... but if you think of  
something you want/need that is related, please send mail (to the  
list should do as long as the subject looks gshell-ish).


My goal is to get *all* of the command-line bits for the server to  
run through GShell, and use that experience to tighten up the  
framework and hopefully provide some simple documentation to allow  
other projects to easily consume the GShell for their application  
needs.  And in the process of doing all that I'm going to get that  
'remote-shell' command stuff working at least as a minimal  
prototype.  Might need to ping the network gurus for help after  
the proto is working to finish up the design and make it truly  
kick ass :-)


Anyways... email for any reason.  Aighty?

Cheers,

--jason


On Sep 8, 2007, at 12:52 PM, Jeff Genender wrote:


Is this working for the Tomcat assembly?  If not...can it soon?

Thanks,

Jeff
Sent from my iPhone

On Sep 8, 2007, at 1:40 PM, Jason Dillon [EMAIL PROTECTED] wrote:

A little bit more insight into what I'm thinking of doing...  
since some of you can't read minds to well :-P


I'd like to convert all of the assemblies to basically look like  
what the assemblies/geronimo-jetty6-javaee5-gshell produces.


And then I'd like to start converting the other cli bits to  
gshell command impls, like: deployer, client and shutdown.


And then (maybe around the same time or before the above), I'd  
like to adapt the gshell of target jvm bits to load jars from  
the repository, instead of using the lib/* bits.


A little background for those who haven't looked at assemblies/ 
geronimo-jetty6-javaee5-gshell and what it produces from a lib/*  
perspective.  Right now I've set up the assembly to produce:


   geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib
   geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/boot
   geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/endorsed

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:


Hi Tim,

I think it would be nice to get this addressed, as this is the GUI that 
users will see before they click on the accept radio button to accept 
the license.   But I can be convinced the other way too.


Do you need to spin another build because of this site below is still 
pointing at your staging site?  This is a snippet from the plugin.xml 
from org.apache.geronimo.st.v20.core_2.0.0.jar I installed:


installableRuntime id=org.apache.geronimo.runtime.tomcat.20
featureVersion=2.0.1

featureId=org.apache.geronimo.installableruntime.tomcat.feature

featureSite=http://people.apache.org/~mcconne/releases/RC2/staging_site/;
path=geronimo-tomcat6-jee5-2.0.1.zip
/installableRuntime

Lin

Tim McConnell wrote:
Hi Lin/Kevan, do you all feel this change is a show-stopped for RC2 ?? 
If so,

I'll cancel the vote and start another one for RC3. Please advise. Thanks.

Lin Sun wrote:

Thanks Tim and Kevan!

Lin

Tim McConnell wrote:

Hi Kevan, yes I shall handle via:

http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-207

Kevan Miller wrote:


On Sep 13, 2007, at 5:39 PM, Kevan Miller wrote:


On Sep 13, 2007, at 4:44 PM, Lin Sun wrote:


I think we also need to update the license in the 
feature.properties file for each of the feature we provide.   
Right now, I only saw ASL 2.0 there.   The license in the 
feature.properties file is presented to a user when they install 
the Geronimo Eclipse plugin or server runtime using the Eclipse 
update manager, before he/she clicks on accept the license to 
install our Geronimo eclipse plugin or server runtime.



It may make sense to put the contents of both the license and 
notice file there.




Ah, ok. That makes sense. I didn't know what the feature.properties 
files were used for (just saw that they didn't have any non 
ASL/Geronimo artifacts). Thanks for reviewing!




Lin or Tim,
Is that something that one of you can take care of?

--kevan

[jira] Created: (GERONIMODEVTOOLS-208) Always appends default value into Server VM Arguments field after modifying this field.

2007-09-14 Thread Kan Ogawa (JIRA)

Always appends default value into Server VM Arguments field after modifying 
this field.
---

 Key: GERONIMODEVTOOLS-208
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-208
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Kan Ogawa


Assumes that the following value is set in Server VM Arguments field now:
 - start -
 -javaagent:C:/Apache/Geronimo/2.0.1/bin/jpa.jar
 -Djava.ext.dirs=C:/Apache/Geronimo/2.0.1/lib/ext;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\ext
 -Djava.endorsed.dirs=C:/Apache/Geronimo/2.0.1/lib/endorsed;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\endorsed
 - end -
 ( NOTE: C:\Program Files\Java\jdk1.5.0_11 is JAVA_HOME. And 
C:/Apache/Geronimo/2.0.1 is GERONIMO_HOME. )

Issue scenario:
1. Opens Geronimo 2.0 Server in Servers view.
2. Inputs the following value to head of Server VM Arguments field.
   -server 
3. Saves and closes Geronimo 2.0 Server overview page.
4. Reopens Geronimo 2.0 Server in Servers view.
5. Displays the following value in Server VM Arguments field.
 - start -
 -javaagent:C:/Apache/Geronimo/2.0.1/bin/jpa.jar
 -Djava.ext.dirs=C:/Apache/Geronimo/2.0.1/lib/ext;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\ext
 -Djava.endorsed.dirs=C:/Apache/Geronimo/2.0.1/lib/endorsed;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\endorsed
 -server -javaagent:C:/Apache/Geronimo/2.0.1/bin/jpa.jar
 -Djava.ext.dirs=C:/Apache/Geronimo/2.0.1/lib/ext;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\ext
 -Djava.endorsed.dirs=C:/Apache/Geronimo/2.0.1/lib/endorsed;C:\Program 
Files\Java\jdk1.5.0_11\jre\lib\endorsed
 - end -


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

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:

2007-09-14 Thread Kevan Miller



On Sep 14, 2007, at 10:48 AM, Tim McConnell wrote:

Hi Lin/Kevan, do you all feel this change is a show-stopped for  
RC2 ?? If so,
I'll cancel the vote and start another one for RC3. Please advise.  
Thanks.


Hey Tim,
From a binary perspective, things are fine. However, if the  
installation of the plugin is presenting LICENSE information that we  
purport to represent the license information for the plugin, and that  
information is incorrect. Then, yes, I think it needs to be fixed.


--kevan

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:

Hi again Lin, I'll create an RC3 to fix the licensing problems. But the 
plugin.xml for geronimo.st.v20.core_2.0.0.jar is correct if you look at it from 
the actual deployable zip that is being (and will be) voted on, or even in svn. 
It actually points to a real eclipse update site (e.g., 
http://www.apache.org/dist/geronimo/eclipse/updates). I change it on the staging 
site only so that when Scenario #2 is executed, and that  particular plugin gets 
installed from the staging site, it will subsequently search on the staging site 
when downloading server runtimes. Otherwise, the download and install button 
of the Eclipse plugin could not be tested during the review period. That's also 
one of the reason that Scenario #1 and Scenario #2 are mutually exclusive. If 
you do Scenario #1, which is just an unzip of the deployable zip file, you 
cannot use the staging site to download and install the server runtimes. Thanks



Lin Sun wrote:

Hi Tim,

I think it would be nice to get this addressed, as this is the GUI that 
users will see before they click on the accept radio button to accept 
the license.   But I can be convinced the other way too.


Do you need to spin another build because of this site below is still 
pointing at your staging site?  This is a snippet from the plugin.xml 
from org.apache.geronimo.st.v20.core_2.0.0.jar I installed:


installableRuntime id=org.apache.geronimo.runtime.tomcat.20
featureVersion=2.0.1

featureId=org.apache.geronimo.installableruntime.tomcat.feature

featureSite=http://people.apache.org/~mcconne/releases/RC2/staging_site/;
path=geronimo-tomcat6-jee5-2.0.1.zip
/installableRuntime

Lin

Tim McConnell wrote:
Hi Lin/Kevan, do you all feel this change is a show-stopped for RC2 ?? 
If so,
I'll cancel the vote and start another one for RC3. Please advise. 
Thanks.


Lin Sun wrote:

Thanks Tim and Kevan!

Lin

Tim McConnell wrote:

Hi Kevan, yes I shall handle via:

http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-207

Kevan Miller wrote:


On Sep 13, 2007, at 5:39 PM, Kevan Miller wrote:


On Sep 13, 2007, at 4:44 PM, Lin Sun wrote:


I think we also need to update the license in the 
feature.properties file for each of the feature we provide.   
Right now, I only saw ASL 2.0 there.   The license in the 
feature.properties file is presented to a user when they install 
the Geronimo Eclipse plugin or server runtime using the Eclipse 
update manager, before he/she clicks on accept the license to 
install our Geronimo eclipse plugin or server runtime.



It may make sense to put the contents of both the license and 
notice file there.




Ah, ok. That makes sense. I didn't know what the 
feature.properties files were used for (just saw that they didn't 
have any non ASL/Geronimo artifacts). Thanks for reviewing!




Lin or Tim,
Is that something that one of you can take care of?

--kevan












--
Thanks,
Tim McConnell

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:


Okay, thanks for the information

Kevan Miller wrote:


On Sep 14, 2007, at 10:48 AM, Tim McConnell wrote:

Hi Lin/Kevan, do you all feel this change is a show-stopped for RC2 ?? 
If so,
I'll cancel the vote and start another one for RC3. Please advise. 
Thanks.


Hey Tim,
 From a binary perspective, things are fine. However, if the 
installation of the plugin is presenting LICENSE information that we 
purport to represent the license information for the plugin, and that 
information is incorrect. Then, yes, I think it needs to be fixed.


--kevan



--
Thanks,
Tim McConnell

Re: svn commit: r574694 - in /geronimo/server/trunk: configs/jetty6-deployer/src/main/plan/ configs/jetty6-deployer/src/plan/ configs/tomcat6-deployer/src/main/plan/ configs/tomcat6-deployer/src/plan/

2007-09-14 Thread Paul McMahan

Jarek,  This commit is causing some problems for the new admin  
console plugin because it needs to inherit the spring classes from  
its parent component (pluto-support).   This situation is the inverse  
of the original problem we were hoping to solve where a web-app does  
*not* want to inherit the spring classes :-)


Could we move the springframework hidden-classes filter from the  
tomcat and jetty deployers to the cxf-deployer?   Doing that  
alleviated the problem for me since the console webapp doesn't  
contain any web services, and therefore won't inherit these  
filters.   To me it seems more correct to apply the filters via cxf- 
deployer since cxf's dependency on spring was really the issue.  Here  
is a patch showing what I changed.   If it works OK for you then  
please go ahead and commit or let me know and I will do it.


Index: configs/tomcat6-deployer/src/main/plan/plan.xml
===
--- configs/tomcat6-deployer/src/main/plan/plan.xml (revision  
575651)

+++ configs/tomcat6-deployer/src/main/plan/plan.xml (working copy)
@@ -70,10 +70,7 @@
 typecar/type
 /dependency
 /dependencies
-hidden-classes
-filterorg.springframework./filter
-filterMETA-INF/spring/filter
-/hidden-classes
+hidden-classes/
 non-overridable-classes
 filterjava./filter
 filterjavax./filter
Index: configs/tomcat6-deployer/src/plan/plan.xml
===
--- configs/tomcat6-deployer/src/plan/plan.xml  (revision 575651)
+++ configs/tomcat6-deployer/src/plan/plan.xml  (working copy)
@@ -70,10 +70,7 @@
 typecar/type
 /dependency
 /dependencies
-hidden-classes
-filterorg.springframework./filter
-filterMETA-INF/spring/filter
-/hidden-classes
+hidden-classes/
 non-overridable-classes
 filterjava./filter
 filterjavax./filter
Index: configs/jetty6-deployer/src/main/plan/plan.xml
===
--- configs/jetty6-deployer/src/main/plan/plan.xml  (revision  
575651)

+++ configs/jetty6-deployer/src/main/plan/plan.xml  (working copy)
@@ -170,10 +170,7 @@
 typecar/type
   /dependency
 /dependencies
-hidden-classes
-  filterorg.springframework./filter
-  filterMETA-INF/spring/filter
-/hidden-classes
+hidden-classes/
 non-overridable-classes
   filterjava./filter
   filterjavax./filter
@@ -213,4 +210,4 @@
   gbean name=POJOTemplate  
class=org.apache.geronimo.jetty6.JettyPOJOWebServiceHolder

 attribute name=servletNamedummy/attribute
   /gbean
-/module
\ No newline at end of file
+/module
Index: configs/jetty6-deployer/src/plan/plan.xml
===
--- configs/jetty6-deployer/src/plan/plan.xml   (revision 575651)
+++ configs/jetty6-deployer/src/plan/plan.xml   (working copy)
@@ -130,10 +130,7 @@
 typecar/type
 /dependency
 /dependencies
-hidden-classes
-filterorg.springframework./filter
-filterMETA-INF/spring/filter
-/hidden-classes
+hidden-classes/
 non-overridable-classes
 filterjava./filter
 filterjavax./filter
Index: configs/cxf-deployer/src/main/plan/plan.xml
===
--- configs/cxf-deployer/src/main/plan/plan.xml (revision 575651)
+++ configs/cxf-deployer/src/main/plan/plan.xml (working copy)
@@ -30,6 +30,10 @@
 typecar/type
 /dependency
 /dependencies
+hidden-classes
+filterorg.springframework./filter
+filterMETA-INF/spring/filter
+/hidden-classes
 /environment
 /xml-attribute
 /gbean







On Sep 11, 2007, at 5:21 PM, [EMAIL PROTECTED] wrote:


Author: gawor
Date: Tue Sep 11 14:21:15 2007
New Revision: 574694

URL: http://svn.apache.org/viewvc?rev=574694view=rev
Log:
fix the cxf/spring issues by hiding the spring classes and  
resources from the application classloader and by making cxf to use  
cxf/car module classloader to load spring resources instead of the  
application classloader


Modified:
geronimo/server/trunk/configs/jetty6-deployer/src/main/plan/ 
plan.xml

geronimo/server/trunk/configs/jetty6-deployer/src/plan/plan.xml

Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Micky Santomax


Yes this was my case :

  I think this this user has several http consumer endpoints, configured
  at different URIs (e.g. http://0.0.0.0/service1,
  http://0.0.0.0/service2 , http://0.0.0.0/service3).  On all of these
  endpoints, the same targetService is configured (ex:Service) and it is
  in this targetService that he would like to distinguish between the
  originating consumer endpoints.

Thanks to Guillaume for reply which give me the solution
:-)


gnodet wrote:
 
 The consumer *component* can be retrieved using:
 
   ((MessageExchangeImpl) exchange).getSourceContext().getComponent()
 
 ServiceMix components also set the following property:
 
exchange.getProperty(JbiConstants.SENDER_ENDPOINT)
 
 which returns a string uniquely identifying the endpoint.
 
 I don't really recall where/if the uri is stored...
 

-- 
View this message in context: 
http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12679719
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

2007-09-14 Thread Shiva Kumar H R

On 9/14/07, Lin Sun [EMAIL PROTECTED] wrote:

 Tim, thanks for your nice instruction.  I am able to do scenario 2 fine
 without any prob!

 I have noticed 2 things:

 1) one other recommended scenario (may be the most recommended scenario)
 used to be not download anything, but start at define a server then
 choose the link called download additional server adapters when a user
 doesn't see the adapter he wants there.   From the resulting page, he
 can just download the geronimo eclipse plugin.   I don't know if you or
 anyone has worked with WTP team to get our geronimo server to be on the
 list?

 2) I tried to deploy a hello war project and able to deploy fine.   But
 right click the project and do a run as, run on server doesn't bring up
 the eclipse internal web browser automatically.   I wonder if someone
 else has noticed this?


Yes! there seems to be a problem. I tried these:
a) Created a dynamic web project and then added an index.jsp. Right click on
the index.jsp file and select Run As - Run on Server. Everything worked
fine including the internal web browser getting opened with the URL of
index.jsp!

An important thing to note here is that the geronimo-web.xml that got
created was using 1.1 version of Geronimo schemas as shown below:
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; xmlns:nam=
http://geronimo.apache.org/xml/ns/naming-1.1; xmlns:sec=
http://geronimo.apache.org/xml/ns/security-1.1; xmlns:sys=
http://geronimo.apache.org/xml/ns/deployment-1.1;

b) I now changed the schema versions in geronimo-web.xml as below:
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; xmlns:nam=
http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:sec=
http://geronimo.apache.org/xml/ns/security-2.0; xmlns:sys=
http://geronimo.apache.org/xml/ns/deployment-1.2;

When I now right click on the same index.jsp and select Run As - Run on
Server I see that the internal web browser is *not* getting opened.

I see the same behaviour (as described in a)  b) above) with both WTP 2.0 
WTP 2.0.1RC1.

- Shiva

Lin


 Tim McConnell wrote:
  Start of discussion thread.

Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

2007-09-14 Thread Shiva Kumar H R

Thanks for catching this Kan Ogawa. I will re-open GERONIMODEVTOOLS-107.

- Shiva

On 9/14/07, Kan Ogawa [EMAIL PROTECTED] wrote:

 Tim,

 Tim McConnell wrote:
  Start of discussion thread.
 
 The GERONIMODEVTOOLS-107 issue that was already closed is not
 fully fixed yet in 2.0.0 RC2.
 ( Now, I don't reopen this issue yet. )

 I forward here my reply to question that Ted Kirby posted from
 WAS-CE forum. For more detail, please see it.

 http://www.ibm.com/developerworks/forums/dw_thread.jsp?message=13991399cat=51thread=171097treeDisplayType=threadmode1forum=541#13991399

 Can you fix it immediately?

 --
 Kan Ogawa
 [EMAIL PROTECTED]

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0:

Hi Tim, cool.  as long as you got it covered that is great.  I was only 
looking at what I downloaded (didn't check the svn.).


Lin

Tim McConnell wrote:
Hi again Lin, I'll create an RC3 to fix the licensing problems. But the 
plugin.xml for geronimo.st.v20.core_2.0.0.jar is correct if you look at 
it from the actual deployable zip that is being (and will be) voted on, 
or even in svn. It actually points to a real eclipse update site (e.g., 
http://www.apache.org/dist/geronimo/eclipse/updates). I change it on the 
staging site only so that when Scenario #2 is executed, and that  
particular plugin gets installed from the staging site, it will 
subsequently search on the staging site when downloading server 
runtimes. Otherwise, the download and install button of the Eclipse 
plugin could not be tested during the review period. That's also one of 
the reason that Scenario #1 and Scenario #2 are mutually exclusive. If 
you do Scenario #1, which is just an unzip of the deployable zip file, 
you cannot use the staging site to download and install the server 
runtimes. Thanks



Lin Sun wrote:

Hi Tim,

I think it would be nice to get this addressed, as this is the GUI 
that users will see before they click on the accept radio button to 
accept the license.   But I can be convinced the other way too.


Do you need to spin another build because of this site below is still 
pointing at your staging site?  This is a snippet from the plugin.xml 
from org.apache.geronimo.st.v20.core_2.0.0.jar I installed:


installableRuntime id=org.apache.geronimo.runtime.tomcat.20
featureVersion=2.0.1

featureId=org.apache.geronimo.installableruntime.tomcat.feature

featureSite=http://people.apache.org/~mcconne/releases/RC2/staging_site/; 


path=geronimo-tomcat6-jee5-2.0.1.zip
/installableRuntime

Lin

Tim McConnell wrote:
Hi Lin/Kevan, do you all feel this change is a show-stopped for RC2 
?? If so,
I'll cancel the vote and start another one for RC3. Please advise. 
Thanks.


Lin Sun wrote:

Thanks Tim and Kevan!

Lin

Tim McConnell wrote:

Hi Kevan, yes I shall handle via:

http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-207

Kevan Miller wrote:


On Sep 13, 2007, at 5:39 PM, Kevan Miller wrote:


On Sep 13, 2007, at 4:44 PM, Lin Sun wrote:


I think we also need to update the license in the 
feature.properties file for each of the feature we provide.   
Right now, I only saw ASL 2.0 there.   The license in the 
feature.properties file is presented to a user when they install 
the Geronimo Eclipse plugin or server runtime using the Eclipse 
update manager, before he/she clicks on accept the license to 
install our Geronimo eclipse plugin or server runtime.



It may make sense to put the contents of both the license and 
notice file there.




Ah, ok. That makes sense. I didn't know what the 
feature.properties files were used for (just saw that they didn't 
have any non ASL/Geronimo artifacts). Thanks for reviewing!




Lin or Tim,
Is that something that one of you can take care of?

--kevan

Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.0.0 (RC2)


Hi Kan, we shall try !!

Kan Ogawa wrote:

Tim,

Tim McConnell wrote:

Start of discussion thread.

 
The GERONIMODEVTOOLS-107 issue that was already closed is not fully 
fixed yet in 2.0.0 RC2.

( Now, I don't reopen this issue yet. )

I forward here my reply to question that Ted Kirby posted from WAS-CE 
forum. For more detail, please see it.
http://www.ibm.com/developerworks/forums/dw_thread.jsp?message=13991399cat=51thread=171097treeDisplayType=threadmode1forum=541#13991399 



Can you fix it immediately?



--
Thanks,
Tim McConnell

Re: [VOTE] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

Vote is canceled. An RC3 will be forthcoming very shortly.

Tim McConnell wrote:
Hi, Please review and vote on the release of the Geronimo Eclipse Plugin
2.0.0 RC2 (to correspond with the Geronimo 2.0.1 Server release).
Changes from RC1 include:

1. Updates to License/Notice files
2. Numerous JIRA fixes

The deployable zip file is here:

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip

The update site zip file is here:

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-updatesite-RC2.zip

The current svn location is here (revision number 575055):

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0.0

The future svn location will be here:

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0

There is a rudimentary set of install instructions available at the URL
below that will hopefully describe the necessary prereqs and steps
required to install and run the plugin. I'm in the process of creating
Wiki pages for the Plugin Release Process and General Information about
the plugin, and would like to use this document as a base for the
General Information page. So, I would be very interested in getting
feedback on these instructions:

http://people.apache.org/~mcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt

Additionally, there is an ant build.xml file that can be used to
download all the prereqs for the plugin. It is documented in the
instructions.
Finally, I've created a Staging Site that used to test the update
manager functions of Eclipse for downloading both the plugin itself and
the Geronimo Server. This is also documented in the instructions.

The vote will conclude at 11:00 PM EST on Saturday, September 15th.

--
Thanks,
Tim McConnell

[jira] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database

2007-09-14 Thread Lin Sun (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527583
]

Lin Sun commented on GERONIMO-2188:
---

David,

I think I know where the confusion is now. Geronimo 2.0 or 2.0.1 uses tranql
connector 1.3, which is where I started to look at the prob as that is the code
base I use to recreate it. So the patch I submitted is created against the
tagged version of connector 1.3, which surprisingly was created sometime last
year (I assumed it was fairly recently but I am wrong.) I just went to tranql
connector trunk, which did have all the changes there.

I think to resolve this, we just need to get a newer version of tranql out.

Lin

When oracle wrapper is used, commits are not immediately committed to oracle
database
-

Key: GERONIMO-2188
URL: https://issues.apache.org/jira/browse/GERONIMO-2188
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: connector
Affects Versions: 1.1.1
Reporter: Krishnakumar B
Assignee: Lin Sun
Attachments: G2188-2.patch, G2188-latest.patch, G2188.patch

We have to configure CommitBeforeAutCommit=true property exclusively in the
database connection pool plan, to have the ejb -based transactions
immediately committed for oracle database. Otherwise it only commits
transaction when the server shuts-down. This problem is not faces with
Derby database.

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

[jira] Commented: (GERONIMODEVTOOLS-107) Invalid file name of the deployment plan for a Connector


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527593
 ] 

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

This is fixed in
1) \branches\2.0.0 at revision 575767, and 
2) \trunk at revision 575769.

Thanks Kan Ogawa for re-capturing this.

 Invalid file name of the deployment plan for a Connector
 

 Key: GERONIMODEVTOOLS-107
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 1.1.0
 Environment: Windows XP SP2, Sun J2RE SE 1.5.0._08, Eclipse SDK 
 3.2.0, Geronimo Eeclipse Plugin 1.1.x (11-Aug-2006)
Reporter: Ilya Kanonirov
 Fix For: 1.2.1


 After creating a new connector using the Connector Project wizard, the name 
 of module's deployment plan is geronimo-connector.xml instead of expected 
 geronimo-ra.xml.

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

[jira] Commented: (SM-952) ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml

2007-09-14 Thread Srivatsan Sridharan (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40135
 ] 

Srivatsan Sridharan commented on SM-952:


Adding comment here as it is a related issue:

When the library element provided under classpath has a value, the 
following code snippet to get the SharedLibrary sl returns null if the shared 
library is not installed and throws NPE when sl.getClassLoader() is called. A 
typical scenario when this could occur is when running maven junit test cases 
for a su that references a shared-library in the xbean.xml/servicemix.xml. 
 
   // create the classloader
ListClassLoader parents = new ArrayListClassLoader();
parents.add(getParentClassLoader(applicationContext));
for (String library : sls) {
SharedLibrary sl = 
container.getRegistry().getSharedLibrary(library);
// Check for null to prevent the NPE
if ((sl != null)  (sl.getClassLoader() != null)) {
parents.add(sl.getClassLoader());
}
}
A check for null (as shown in the code) prevents the NPE that is thrown.

 ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml
 ---

 Key: SM-952
 URL: https://issues.apache.org/activemq/browse/SM-952
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-common
Affects Versions: 3.2
Reporter: Honi Jain
Priority: Critical
 Fix For: 3.2

 Attachments: ClassLoaderXmlPreprocessor.java, 
 ClassLoaderXmlPreprocessor.java.patch


 If we dont specify location child node but specify library child node of 
 parent node classpath in xbean.xml we are getting Null Pointer Exception when 
 we deploy our service assembly in servicemix.
 getClassLoader method of ClassLoaderXmlPreprocessor  parses the xbean.xml for 
 the tag 'classpath'. For loading shared-libraries it searches for the child 
 nodes with tag name 'library'.  After it found all the child library nodes it 
 adds to the arraylist for the shared library using the child node list of 
 'location'. This will give null pointer exception if no location node is 
 there. Even if location node is present when the code will try to look for 
 shared library it will give an error.
 I am attaching the patch file ClassLoaderXmlPreprocessor  .java

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

[jira] Commented: (GERONIMO-3413) factor the console portlets into separate plugins

2007-09-14 Thread Paul McMahan (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527602
]

Paul McMahan commented on GERONIMO-3413:

thanks for Viet for the patch! committed in rev 575775.

factor the console portlets into separate plugins
-

Key: GERONIMO-3413
URL: https://issues.apache.org/jira/browse/GERONIMO-3413
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1
Reporter: Paul McMahan
Assignee: Paul McMahan
Fix For: 2.1

Attachments: geronimo-3413.patch

The administration console contains portlets for configuring the components
in a JEE5 server, and a few more things like debugging, creating deployment
plans, etc. Right now the collection of portlets is hard coded in the
console's pluto configuration. This makes it difficult for users to choose
which portlets they want in their console. For example some users may not
want the various classloader/dependency/JMX/LDAP/etc viewers because they
require the dojo library, which adds a non-trivial server footprint. But
more importantly this makes it difficult to deploy the administration console
into a customized geronimo assembly (like the minimal ones) because those
assemblies typically don't have all the JEE5 components installed that would
be necessary to satisfy the console's dependencies.
There is some work going on to make the console customizable using pluto
1.2's portal driver framework. The portal driver allows the console to
dynamically add/remove portlets. Using this new capability from pluto
provides the capability to create an administration console for the minimal
assembly that contains only the base portlets, such as those necessary for
deployment and web server configuration. The other portlets need to be
factored out of the admin console as separately deployable WAR files and
provided as plugins. This allows the user to selectively install portlets
from the plugin catalog. And when the user deploys a component into the
minimal assembly such as ActiveMQ they should be able to install the JMS
administration portlet at that point in time, if desired.

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

[jira] Closed: (GERONIMODEVTOOLS-195) problems with defining new server: can't download and install, can't choose jetty


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

Tim McConnell closed GERONIMODEVTOOLS-195.
--

Resolution: Fixed

This was fixed sometime ago--should be closed

 problems with defining new server: can't download and install, can't choose 
 jetty
 -

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


 Download and Install button will not install the Server correctly, No 
 matter what directory is indicated,
 Clicking the button will always prompt an error The specified directory does 
 not exist, Then Both
 Next and Finish button also become gray and cannot be clicked.
 there are radio buttons for tomcat and jetty, but the jetty button does not 
 work.  The tomcat just stays selected.

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

[jira] Updated: (GERONIMODEVTOOLS-197) Mechanism required to LICENSE/NOTICE files management


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

Tim McConnell updated GERONIMODEVTOOLS-197:
---

Affects Version/s: (was: 2.0)
   2.1
Fix Version/s: (was: 2.0)
   2.1

 Mechanism required to LICENSE/NOTICE files management
 -

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


 Per suggestions from David Jencks there seems to be a couple alternatives to 
 consider (maven-rat-plugin or the maven-remote-resources-plugin)

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

Re: svn commit: r574694 - in /geronimo/server/trunk: configs/jetty6-deployer/src/main/plan/ configs/jetty6-deployer/src/plan/ configs/tomcat6-deployer/src/main/plan/ configs/tomcat6-deployer/src/plan/

2007-09-14 Thread Jarek Gawor

Ugh... I had a feeling that this filtering will cause problems for
someone. Anyway, in general I think moving the hidden-classes filter
to the CXF deployer is a better solution (to keep it all together and
assuming it has the same effect as when specified in the web container
deployer). But, in this case I don't think this will work right still.
First, in CXF there are two key deployers. One that handles deployment
of web services and another one that handles service references (it's
a naming builder). Both will need the hidden-classes filter (the patch
only updates the web service deployer). However, because the way
currently the naming builders work in Geronimo, the environment of
naming builders is always merged no matter if the application has a
service reference or not (or whatever the naming builder is looking
for). So at the end, even if we moved the hidden-classes filter to the
CXF deployers, the filter will still be injected. So we might need to
fix how the naming builders work or find a better way to deal with
Spring filtering. I'm not sure what's the right solution here.

Jarek

On 9/14/07, Paul McMahan [EMAIL PROTECTED] wrote:
 Jarek,  This commit is causing some problems for the new admin
 console plugin because it needs to inherit the spring classes from
 its parent component (pluto-support).   This situation is the inverse
 of the original problem we were hoping to solve where a web-app does
 *not* want to inherit the spring classes :-)

 Could we move the springframework hidden-classes filter from the
 tomcat and jetty deployers to the cxf-deployer?   Doing that
 alleviated the problem for me since the console webapp doesn't
 contain any web services, and therefore won't inherit these
 filters.   To me it seems more correct to apply the filters via cxf-
 deployer since cxf's dependency on spring was really the issue.  Here
 is a patch showing what I changed.   If it works OK for you then
 please go ahead and commit or let me know and I will do it.

 Index: configs/tomcat6-deployer/src/main/plan/plan.xml
 ===
 --- configs/tomcat6-deployer/src/main/plan/plan.xml (revision
 575651)
 +++ configs/tomcat6-deployer/src/main/plan/plan.xml (working copy)
 @@ -70,10 +70,7 @@
   typecar/type
   /dependency
   /dependencies
 -hidden-classes
 -filterorg.springframework./filter
 -filterMETA-INF/spring/filter
 -/hidden-classes
 +hidden-classes/
   non-overridable-classes
   filterjava./filter
   filterjavax./filter
 Index: configs/tomcat6-deployer/src/plan/plan.xml
 ===
 --- configs/tomcat6-deployer/src/plan/plan.xml  (revision 575651)
 +++ configs/tomcat6-deployer/src/plan/plan.xml  (working copy)
 @@ -70,10 +70,7 @@
   typecar/type
   /dependency
   /dependencies
 -hidden-classes
 -filterorg.springframework./filter
 -filterMETA-INF/spring/filter
 -/hidden-classes
 +hidden-classes/
   non-overridable-classes
   filterjava./filter
   filterjavax./filter
 Index: configs/jetty6-deployer/src/main/plan/plan.xml
 ===
 --- configs/jetty6-deployer/src/main/plan/plan.xml  (revision
 575651)
 +++ configs/jetty6-deployer/src/main/plan/plan.xml  (working copy)
 @@ -170,10 +170,7 @@
   typecar/type
 /dependency
   /dependencies
 -hidden-classes
 -  filterorg.springframework./filter
 -  filterMETA-INF/spring/filter
 -/hidden-classes
 +hidden-classes/
   non-overridable-classes
 filterjava./filter
 filterjavax./filter
 @@ -213,4 +210,4 @@
 gbean name=POJOTemplate
 class=org.apache.geronimo.jetty6.JettyPOJOWebServiceHolder
   attribute name=servletNamedummy/attribute
 /gbean
 -/module
 \ No newline at end of file
 +/module
 Index: configs/jetty6-deployer/src/plan/plan.xml
 ===
 --- configs/jetty6-deployer/src/plan/plan.xml   (revision 575651)
 +++ configs/jetty6-deployer/src/plan/plan.xml   (working copy)
 @@ -130,10 +130,7 @@
   typecar/type
   /dependency
   /dependencies
 -hidden-classes
 -filterorg.springframework./filter
 -filterMETA-INF/spring/filter
 -/hidden-classes
 +hidden-classes/
   non-overridable-classes
   filterjava./filter

[jira] Updated: (GERONIMODEVTOOLS-197) Mechanism required to LICENSE/NOTICE files management


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

Tim McConnell updated GERONIMODEVTOOLS-197:
---

Affects Version/s: (was: 2.1)
   2.0

 Mechanism required to LICENSE/NOTICE files management
 -

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


 Per suggestions from David Jencks there seems to be a couple alternatives to 
 consider (maven-rat-plugin or the maven-remote-resources-plugin)

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

[jira] Updated: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse


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

Tim McConnell updated GERONIMODEVTOOLS-198:
---

Fix Version/s: (was: 2.0)
   2.1

 Daytrader deployment exception in Eclipse
 -

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


 There is a deployment exception occurring in Eclipse when deploying 
 Daytrader, although it seems to be fairly benign since Daytrader ultimately 
 does deploy and seems to function correctly. 
 Booting Geronimo Kernel (in Java 1.5.0_12)...
 Module  1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car  
started in  1.453s
 Module  2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car 
started in   .359s
 Module  3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car 
started in   .875s
 Module  4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car   
started in   .000s
 Module  5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car 
   INFO - Configuring Service(id=Default MDB Container, type=Container, 
 provider-id=Default MDB Container)
 INFO - Configuring Service(id=Default Stateless Container, type=Container, 
 provider-id=Default Stateless Container)
 INFO - Configuring app: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Loaded Module: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Assembling app: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome)
 INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, 
 container=Default Stateless Container)
 INFO - Configuring Service(id=Default Stateful Container, type=Container, 
 provider-id=Default Stateful Container)
 INFO - Configuring Service(id=Default BMP Container, type=Container, 
 provider-id=Default BMP Container)
 INFO - Configuring Service(id=Default CMP Container, type=Container, 
 provider-id=Default CMP Container)
  started in 11.328s
 Module  6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car 
started in  1.782s
 Module  7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car 
started in   .000s
 Module  8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car 
started in   .000s
 Module  9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car 
started in   .000s
 Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car  
started in   .000s
 Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car 
started in   .016s
 Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car 
   ERROR - Restricted listeners property file not found
  started in  3.172s
 Module 13/31 
 org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car
 started in   .844s
 Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car   
started in   .516s
 Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car  
started in   .234s
 Module 16/31 
 org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car 
 started in   .172s
 Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car
started in   .219s
 Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car 
started in   .250s
 Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car  
started in   .312s
 Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car   
started in  1.672s
 Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car
started in   .125s
 Module 22/31 org.apache.geronimo.configs/sharedlib/2.1-SNAPSHOT/car   
started in   .015s
 Module 23/31 org.apache.geronimo.configs/tomcat6-deployer/2.1-SNAPSHOT/car
started in   .187s
 Module 24/31 org.apache.geronimo.configs/jasper-deployer/2.1-SNAPSHOT/car 
started in   .063s
 Module 25/31 org.apache.geronimo.configs/myfaces-deployer/2.1-SNAPSHOT/car

Re: [VOTE] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

2007-09-14 Thread Shiva Kumar H R

Summarizing list of things to be completed before we re-spin RC3:
1) Fix problem reported by Lin (a JIRA for this will be opened)
2) Open a JIRA to make sure we don't loose track of updating build.xml to
use WTP 2.0.1 once they are GAed. This probably will happen after GEP
2.0gets released.
3) Fix license files as reported in GERONIMODEVTOOLS-207
4) Fix GERONIMODEVTOOLS-205 [Jacek happy? ;) ]

Please feel free to add if we have missed something very important.

Thanks,
Shiva

On 9/14/07, Tim McConnell [EMAIL PROTECTED] wrote:

Vote is canceled. An RC3 will be forthcoming very shortly.

Tim McConnell wrote:
Hi, Please review and vote on the release of the Geronimo Eclipse Plugin
2.0.0 RC2 (to correspond with the Geronimo 2.0.1 Server release).
Changes from RC1 include:

1. Updates to License/Notice files
2. Numerous JIRA fixes

The deployable zip file is here:

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.ziphttp://people.apache.org/%7Emcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip

The update site zip file is here:

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-updatesite-RC2.zip

http://people.apache.org/%7Emcconne/releases/RC2/g-eclipse-plugin-2.0.0-updatesite-RC2.zip

The current svn location is here (revision number 575055):

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0.0

The future svn location will be here:

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0

http://people.apache.org/~mcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt

http://people.apache.org/%7Emcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt

The vote will conclude at 11:00 PM EST on Saturday, September 15th.

--
Thanks,
Tim McConnell

bodyAttributes NonePositionLeft: 0pxTop: 0pxWidth: 581pxHeight: 280pxOther Font
Family:arial,sans-serifFont Size:13.2667pxAncestors

html
Children

span

div

div #webdeveloper-element-information

[jira] Created: (GERONIMODEVTOOLS-209) Hello World JSP does not open in Eclipse browser when invoked with run as, run on server from within Eclipse

Hello World JSP does not open in Eclipse browser when invoked with run as, run 
on server from within Eclipse
--

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




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

[jira] Created: (GERONIMODEVTOOLS-210) Upgrade build process to download the WTP 2.0.1 artifacts when it GA'es at the end of September

Upgrade build process to download the WTP 2.0.1 artifacts when it GA'es at the 
end of September
---

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




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

[jira] Updated: (GERONIMO-3472) web server portlet does not save modifications to connectors correctly.

2007-09-14 Thread Paul McMahan (JIRA)


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

Paul McMahan updated GERONIMO-3472:
---

Component/s: (was: console)
 Jetty

from the patch this looks like a problem with the GBeanInfo's for Jetty

 web server portlet does not save modifications to connectors correctly.
 ---

 Key: GERONIMO-3472
 URL: https://issues.apache.org/jira/browse/GERONIMO-3472
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Jetty
Affects Versions: 2.0.1, 2.1, Verification Required
 Environment: windows xp
Reporter: Viet Hung Nguyen
 Attachments: geronimo-3472.patch


 When the admin tries to edit a connector, any modifications to 
 bufferSizeBytes, acceptQueueSize, and lingerMillis are not saved once the 
 server is restarted.

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

[jira] Assigned: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development


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

Shiva Kumar H R reassigned GERONIMODEVTOOLS-211:


Assignee: Shiva Kumar H R

 Eliminate compile time errors (related to XmlBeans schemas) reported by 
 Eclipse during plug-in development
 --

 Key: GERONIMODEVTOOLS-211
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.0


 After checking-out source code and doing an mvn build, import the source 
 plug-ins into Eclipse for development, as illustrated in 
 http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html
 After import and a build within Eclipse, some 25 errors similar to the one 
 below get reported:
 Package 
 'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868'
  does not exist in this plug-in.
 Eliminate these compile time errors.

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

[jira] Created: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development

Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse 
during plug-in development
--

 Key: GERONIMODEVTOOLS-211
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Shiva Kumar H R
 Fix For: 2.0


After checking-out source code and doing an mvn build, import the source 
plug-ins into Eclipse for development, as illustrated in 
http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html

After import and a build within Eclipse, some 25 errors similar to the one 
below get reported:
Package 
'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868'
 does not exist in this plug-in.

Eliminate these compile time errors.

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

[jira] Closed: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development


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

Shiva Kumar H R closed GERONIMODEVTOOLS-211.


Resolution: Fixed

Fixed in branches\2.0.0 at revision 575782.

 Eliminate compile time errors (related to XmlBeans schemas) reported by 
 Eclipse during plug-in development
 --

 Key: GERONIMODEVTOOLS-211
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.0


 After checking-out source code and doing an mvn build, import the source 
 plug-ins into Eclipse for development, as illustrated in 
 http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html
 After import and a build within Eclipse, some 25 errors similar to the one 
 below get reported:
 Package 
 'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868'
  does not exist in this plug-in.
 Eliminate these compile time errors.

-- 
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 Eclipse Plugin 2.0.0 (RC2)

2007-09-14 Thread Donald Woods

Lets try and stick to the release often goal of open source and not try to 
fix everything before we release the 2.0.0 plugin.  There will always be bugs 
that need to be fixed (just look at all of the open JIRAs for the Server) and 
we should try to maintain the past goals of always shipping a plugin within 30 
days of the server being released


Any new bugs found after the initial 72 hour voting window that are not 
security related or block major portions of existing features in the plugin, 
should be moved out to a 2.0.1 plugin release target.



-Donald

Shiva Kumar H R wrote:

Summarizing list of things to be completed before we re-spin RC3:
1) Fix problem reported by Lin (a JIRA for this will be opened)
2) Open a JIRA to make sure we don't loose track of updating build.xml 
 to use WTP 2.0.1 once they are GAed. This probably will happen after 
GEP 2.0 gets released.

3) Fix license files as reported in GERONIMODEVTOOLS-207
4) Fix GERONIMODEVTOOLS-205 [Jacek happy? ;) ]

Please feel free to add if we have missed something very important.

Thanks,
Shiva

On 9/14/07, * Tim McConnell* [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


Vote is canceled. An RC3 will be forthcoming very shortly.

Tim McConnell wrote:
  Hi, Please review and vote on the release of the Geronimo Eclipse
Plugin
  2.0.0 RC2 (to correspond with the Geronimo 2.0.1 Server release).
  Changes from RC1 include:
 
  1.  Updates to License/Notice files
  2.  Numerous JIRA fixes
 
 
  The deployable zip file is here:
 
  
 

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip

http://people.apache.org/%7Emcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip
 
 
  The update site zip file is here:
 
  
 

http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-updatesite-RC2.zip

http://people.apache.org/%7Emcconne/releases/RC2/g-eclipse-plugin-2.0.0-updatesite-RC2.zip
 
 
  The current svn location is here (revision number 575055):
 
  
 

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0.0

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0.0
 
 
  The future svn location will be here:
 
  
 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0
 
 
 
  There is a rudimentary set of install instructions available at
the URL
  below that will hopefully describe the necessary prereqs and steps
  required to install and run the plugin. I'm in the process of
creating
  Wiki pages for the Plugin Release Process and General Information
about
  the plugin, and would like to use this document as a base for the
  General Information page. So, I would be very interested in getting
  feedback on these instructions:
 
  
 

http://people.apache.org/~mcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt

http://people.apache.org/%7Emcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt
 
 
  Additionally, there is an ant build.xml file that can be used to
  download all the prereqs for the plugin. It is documented in the
  instructions.
  Finally, I've created a Staging Site that used to test the update
  manager functions of Eclipse for downloading both the plugin
itself and
  the Geronimo Server. This is also documented in the instructions.
 
  The vote will conclude at 11:00 PM EST on Saturday, September 15th.
 
  --
  Thanks,
  Tim McConnell
 

--
Thanks,
Tim McConnell


body

Attributes
None

Position
Left: 0px   Top: 0px
Width: 581pxHeight: 280px

Other
Font Family:arial,sans-serif
Font Size:  13.2667px

Ancestors

html

Children

br

span

span

br

br

br

div

br

div #webdeveloper-element-information



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release Geronimo Eclipse Plugin 2.0.0 (RC2)

2007-09-14 Thread Ted Kirby

WTP2.0.1RC2 is now available.

See
http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC2-20070913200918/

Ted Kirby

[jira] Updated: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse


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

Donald Woods updated GERONIMODEVTOOLS-198:
--

Fix Version/s: (was: 2.1)
   2.0.x

 Daytrader deployment exception in Eclipse
 -

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


 There is a deployment exception occurring in Eclipse when deploying 
 Daytrader, although it seems to be fairly benign since Daytrader ultimately 
 does deploy and seems to function correctly. 
 Booting Geronimo Kernel (in Java 1.5.0_12)...
 Module  1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car  
started in  1.453s
 Module  2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car 
started in   .359s
 Module  3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car 
started in   .875s
 Module  4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car   
started in   .000s
 Module  5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car 
   INFO - Configuring Service(id=Default MDB Container, type=Container, 
 provider-id=Default MDB Container)
 INFO - Configuring Service(id=Default Stateless Container, type=Container, 
 provider-id=Default Stateless Container)
 INFO - Configuring app: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Loaded Module: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Assembling app: 
 jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
 INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome)
 INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, 
 container=Default Stateless Container)
 INFO - Configuring Service(id=Default Stateful Container, type=Container, 
 provider-id=Default Stateful Container)
 INFO - Configuring Service(id=Default BMP Container, type=Container, 
 provider-id=Default BMP Container)
 INFO - Configuring Service(id=Default CMP Container, type=Container, 
 provider-id=Default CMP Container)
  started in 11.328s
 Module  6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car 
started in  1.782s
 Module  7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car 
started in   .000s
 Module  8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car 
started in   .000s
 Module  9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car 
started in   .000s
 Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car  
started in   .000s
 Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car 
started in   .016s
 Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car 
   ERROR - Restricted listeners property file not found
  started in  3.172s
 Module 13/31 
 org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car
 started in   .844s
 Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car   
started in   .516s
 Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car  
started in   .234s
 Module 16/31 
 org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car 
 started in   .172s
 Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car
started in   .219s
 Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car 
started in   .250s
 Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car  
started in   .312s
 Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car   
started in  1.672s
 Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car
started in   .125s
 Module 22/31 org.apache.geronimo.configs/sharedlib/2.1-SNAPSHOT/car   
started in   .015s
 Module 23/31 org.apache.geronimo.configs/tomcat6-deployer/2.1-SNAPSHOT/car
started in   .187s
 Module 24/31 org.apache.geronimo.configs/jasper-deployer/2.1-SNAPSHOT/car 
started in   .063s
 Module 25/31 org.apache.geronimo.configs/myfaces-deployer/2.1-SNAPSHOT/car

[jira] Updated: (GERONIMODEVTOOLS-204) Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse IDE for Java EE Developers (125MB)


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

Donald Woods updated GERONIMODEVTOOLS-204:
--

Fix Version/s: (was: 2.1)
Affects Version/s: (was: 2.1)
   2.0

 Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse 
 IDE for Java EE Developers (125MB)
 

 Key: GERONIMODEVTOOLS-204
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-204
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Shiva Kumar H R

 Geronimo Eclipse Plug-in (GEP) v2.0 currently has following pre-requisites:
 1 -- Eclipse Classic 3.3
 2 -- Web Tools Platform (WTP) 2.0
 3 -- Data Tools Platform (DTP) 1.5
 4 -- Eclipse Modeling Framework (EMF) 2.3
 5 -- Graphical Editing Framework (GEF) 3.3
 A wtp-all-in-one-sdk-* bundle that includes all the above 5 pre-requisites 
 can be downloaded from
 http://download.eclipse.org/webtools/downloads/drops/R2.0/R-2.0-200706260303/
 and it has a size of around 260MB.
 eclipse.org starting with Europa release (http://www.eclipse.org/europa/) 
 have a new package by name Eclipse IDE for Java EE Developers with a size 
 of just 125MB (no source bundles included) and has all the pre-requistes 
 for GEP.
 GEP should be updated to utilize this new package of smaller download size.
 (This was attempted in GERONIMODEVTOOLS-180 and due to some problems faced, 
 this has been deferred to GEP 2.1).

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

[jira] Updated: (GERONIMODEVTOOLS-197) Mechanism required to LICENSE/NOTICE files management


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

Donald Woods updated GERONIMODEVTOOLS-197:
--

Fix Version/s: (was: 2.1)

 Mechanism required to LICENSE/NOTICE files management
 -

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

 Per suggestions from David Jencks there seems to be a couple alternatives to 
 consider (maven-rat-plugin or the maven-remote-resources-plugin)

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

Re: automatic builds with tests

2007-09-14 Thread David Jencks


+1000

david jencks

On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote:


I know that at least the 5am build runs with tests on. I would like to
change that so that each build always runs with all tests enabled.
Some of the tests in testsuite/ directory actaully start the server so
if they are successful we should at least know that the server starts
up ok and applications can be deployed to it. That should enable us to
quickly catch and address problems as people commit their changes.

If people agree on this change, I'm willing to spend whatever time is
necessary to make this happen.

Jarek

automatic builds with tests

2007-09-14 Thread Jarek Gawor

I know that at least the 5am build runs with tests on. I would like to
change that so that each build always runs with all tests enabled.
Some of the tests in testsuite/ directory actaully start the server so
if they are successful we should at least know that the server starts
up ok and applications can be deployed to it. That should enable us to
quickly catch and address problems as people commit their changes.

If people agree on this change, I'm willing to spend whatever time is
necessary to make this happen.

Jarek

[jira] Updated: (GERONIMODEVTOOLS-203) No-harm error dialog while switching from Run-to-Debug or Debug-to-Run


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

Donald Woods updated GERONIMODEVTOOLS-203:
--

Affects Version/s: (was: 2.1)
   2.0
Fix Version/s: (was: 2.1)
   2.0.x

 No-harm error dialog while switching from Run-to-Debug or Debug-to-Run
 --

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


 Start server as usual. Once server has started, right click on the server and 
 select Debug. Server will now be stopped and restarted in Debug mode. 
 Although this succeeds, sometimes during the process it throws a confusing 
 error dialog saying Problem Occurred ... Server Apache Geronimo v2.0 Server 
 at localhost failed to start.
 Similarly scenario while switching back from Debug to Run modes.

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

[jira] Updated: (GERONIMODEVTOOLS-193) Runs ping and throws java.lang.SecurityException during Geronimo server startup.


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

Donald Woods updated GERONIMODEVTOOLS-193:
--

Affects Version/s: (was: 2.1)
   2.0
Fix Version/s: (was: 2.1)
   2.0.x

 Runs ping and throws java.lang.SecurityException during Geronimo server 
 startup.
 

 Key: GERONIMODEVTOOLS-193
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
 Environment: Windows XP, Eclipse 3.3, WTP 2.0, Geronimo server 2.0.1, 
 Sun JDK 1.5.0_11
Reporter: Kan Ogawa
Assignee: Shiva Kumar H R
 Fix For: 2.0.x


 Hi,
 While launching Geronimo server on Eclipse, a ping runs in async and the 
 server startup sometimes fails.
 This server hostname is localhost.
 Eclipse error log:
 java.lang.SecurityException: Invalid login
 at 
 org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73)
 at 
 javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:214)
 at 
 javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
 at sun.rmi.transport.Transport$1.run(Transport.java:153)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
 at 
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
 at 
 sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
 at java.lang.Thread.run(Thread.java:595)
 at 
 sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
 at 
 sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
 at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown 
 Source)
 at 
 javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
 at 
 javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
 at 
 javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
 at 
 org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getServerConnection(GeronimoServerBehaviourDelegate.java:689)
 at 
 org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.getKernel(GeronimoServerBehaviour.java:73)
 at 
 org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isKernelAlive(GeronimoServerBehaviour.java:93)
 at 
 org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isFullyStarted(GeronimoServerBehaviour.java:113)
 at org.apache.geronimo.st.core.PingThread.run(PingThread.java:75)

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

Re: automatic builds with tests

2007-09-14 Thread Erik B. Craig

Yes! This would definitely take care of at least some of MY headaches.
+1

On 9/14/07, David Jencks [EMAIL PROTECTED] wrote:

 +1000

 david jencks

 On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote:

  I know that at least the 5am build runs with tests on. I would like to
  change that so that each build always runs with all tests enabled.
  Some of the tests in testsuite/ directory actaully start the server so
  if they are successful we should at least know that the server starts
  up ok and applications can be deployed to it. That should enable us to
  quickly catch and address problems as people commit their changes.
 
  If people agree on this change, I'm willing to spend whatever time is
  necessary to make this happen.
 
  Jarek




-- 
Erik B. Craig

[jira] Updated: (GERONIMODEVTOOLS-210) Upgrade build process to download the WTP 2.0.1 artifacts when it GA'es at the end of September


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

Donald Woods updated GERONIMODEVTOOLS-210:
--

Fix Version/s: (was: 2.1)
   2.0.x
Affects Version/s: (was: 2.1)
   2.0

 Upgrade build process to download the WTP 2.0.1 artifacts when it GA'es at 
 the end of September
 ---

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




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

Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.0.0

2007-09-14 Thread Vamsavardhana Reddy

Why is the discussion on the eclipse plugin release happening in the [VOTE]
thread?

Vamsi

On 9/12/07, Tim McConnell [EMAIL PROTECTED] wrote:

 Hi Donalds, Yes now that all the License files have been fixed (thanks to
 Kevan)
 I plan on another vote later today. Thanks

 Donald Woods wrote:
  Tim, how is the 2.0.0 plugin updates coming?
 
  Do you have an outlook for when we'll be ready for another RC vote?
 
  -Donald
 
 
  Kevan Miller wrote:
  Hey Tim,
  Apologies for my slow review of the Eclipse plugin. Reviewing the
  binary distribution, it looks like we are missing license and notice
  information for xpp3. There may be a few more notices missing, also.
  With your permission, I'll make updates to the license and notice
  files in branches/2.0.0...
 
  --kevan
 
 
 
 
 

 --
 Thanks,
 Tim McConnell

[jira] Commented: (GERONIMO-1053) Session Bean, Finder, Method Permissions

2007-09-14 Thread Vamsavardhana Reddy (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527639
 ] 

Vamsavardhana Reddy commented on GERONIMO-1053:
---

Can someone verify if this is still a problem?  Posting a testcase would be 
helpful if this is still a problem.

 Session Bean, Finder,  Method Permissions
 --

 Key: GERONIMO-1053
 URL: https://issues.apache.org/jira/browse/GERONIMO-1053
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: OpenEJB, security
Affects Versions: 1.0-M5
Reporter: Aaron Mulder
Priority: Blocker

 I have an EAR with a Web App, Session Bean, and CMP Entity Bean, using the M5 
 release.
 The user brings up a secure page on the web app and logs in.
 The web code invoked after the login calls the session bean.
 The session bean calls a finder on the entity bean, and gets this (in the 
 session bean method code, where it calls the finder):
 {noformat}
 Caused by: javax.ejb.TransactionRolledbackLocalException
 at 
 org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:123)
 at 
 org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
 at 
 org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82)
 at 
 org.openejb.GenericEJBContainer$DefaultSubjectInterceptor.invoke(GenericEJBContainer.java:545)
 at 
 org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238)
 at 
 org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129)
 at 
 org.openejb.proxy.EntityEJBLocalHome$$EnhancerByCGLIB$$afb1a239.findAll(generated)
 at 
 org.loadmagus.ejb.TestManagerBean.getAllApplications(TestManagerBean.java:70)
 ... 48 more
 Caused by: javax.ejb.AccessLocalException: access denied 
 (javax.security.jacc.EJBMethodPermission EntityBean findAll,LocalHome,)
 at 
 org.openejb.security.EJBSecurityInterceptor.invoke(EJBSecurityInterceptor.java:107)
 at 
 org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56)
 at 
 org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81)
 at 
 org.openejb.entity.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:136)
 at 
 org.openejb.entity.cmp.InTxCacheInterceptor.invoke(InTxCacheInterceptor.java:84)
 at 
 org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:119)
 ... 55 more
 {noformat}
 The ejb-jar.xml for the EJBs in question has:
 {noformat}
 security-role
 role-nameDeveloper/role-name
 /security-role
 method-permission
 role-nameDeveloper/role-name
 method
 ejb-nameSessionBean/ejb-name
 method-name*/method-name
 /method
 /method-permission
 method-permission
 role-nameDeveloper/role-name
 method
 ejb-nameEntityBean/ejb-name
 method-name*/method-name
 /method
 /method-permission
 {noformat}
 So it's a little odd that the session bean sees a transaction rolled back 
 exception rather than the real security exception, but whatever.
 The real problem is that both the session bean and the entity bean are 
 covered by identical all-inclusive method permission blocks, so if the user 
 got into the session bean, there should be no reason they can't get into the 
 entity bean.  The syntax above is specifically supported in the 
 ejb-jar-2_1.xsd Schema (#1; This style is used to refer to all the methods 
 of the specified enterprise bean's home, component, and/or web service 
 endpoint interfaces.)

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

[jira] Updated: (GERONIMODEVTOOLS-179) XDoclet 1.2 Support


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

Donald Woods updated GERONIMODEVTOOLS-179:
--

Component/s: xdoclet

 XDoclet 1.2 Support
 ---

 Key: GERONIMODEVTOOLS-179
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-179
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: xdoclet
Affects Versions: 2.1.x
Reporter: Jonathan Gallimore
Assignee: Tim McConnell
 Fix For: 2.1.x


 Currently, there is no XDoclet support available to generate openejb-jar.xml 
 deployment descriptors from annotations on EJB classes. XDoclet already has 
 plugins to generate ejb-jar.xml, and descriptors for other EJB containers 
 such as JBoss, and it would be nice to have this available to Geronimo 
 developers as well.
 I have made a start on an XDoclet plugin that generates a basic 
 openejb-jar.xml, the code for which I have made available in my subversion 
 repository here: https://jrg.me.uk/XDoclet-Geronimo/Geronimo-Plugin/trunk
 Currently this is doing the bear minimum to assist with the project I'm 
 currently working on, I feel that this could be extended and made more robost 
 - the following issues need to be addressed before this is really usable:
 * Provide a test suite to verify the descriptors generated by the plugin 
 (currently I'm eyeballing them using the sample Bank Geronimo project)
 * Thoroughly go through the schemas for openejb-jar.xml and geronimo-web.xml 
 and remove stuff that is currently hardcoded in my templates, and add any 
 tags necessary to build more complete descriptors.

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

[jira] Created: (GERONIMODEVTOOLS-212) Move J2G from Sandbox to Devtools

Move J2G from Sandbox to Devtools
-

 Key: GERONIMODEVTOOLS-212
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-212
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: J2G
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor


Move J2G from Sandbox to Devtools

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

Re: svn commit: r574694 - in /geronimo/server/trunk: configs/jetty6-deployer/src/main/plan/ configs/jetty6-deployer/src/plan/ configs/tomcat6-deployer/src/main/plan/ configs/tomcat6-deployer/src/plan/

2007-09-14 Thread Kevan Miller



On Sep 14, 2007, at 2:56 PM, Jarek Gawor wrote:


Ugh... I had a feeling that this filtering will cause problems for
someone. Anyway, in general I think moving the hidden-classes filter
to the CXF deployer is a better solution (to keep it all together and
assuming it has the same effect as when specified in the web container
deployer). But, in this case I don't think this will work right still.
First, in CXF there are two key deployers. One that handles deployment
of web services and another one that handles service references (it's
a naming builder). Both will need the hidden-classes filter (the patch
only updates the web service deployer). However, because the way
currently the naming builders work in Geronimo, the environment of
naming builders is always merged no matter if the application has a
service reference or not (or whatever the naming builder is looking
for). So at the end, even if we moved the hidden-classes filter to the
CXF deployers, the filter will still be injected. So we might need to
fix how the naming builders work or find a better way to deal with
Spring filtering. I'm not sure what's the right solution here.


Heh. Well, I had hopes for Paul's proposal... Sounds like it's still  
better than where we are now...


I think the right way to address the problem is at the CXF module,  
itself (which we've talked about on other threads). Basic idea is  
that the CXF module would declare the classes that it will hide from  
classloader children.


You'd specify something like:

child-hidden-classes
filterorg.springframework./filter
filterMETA-INF/spring/filter
/child-hidden-classes

The CXF module classloader would hide these classes/resources from  
child classloaders. We could also consider separating hidden- 
classes and hidden-resources...


Other final (?) thing to consider is creating a Spring module. Both  
cxf and pluto-support could depend on this new module...


--kevan

[jira] Updated: (GERONIMODEVTOOLS-205) Name change from Geronimo Eclipse Plugin


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

Tim McConnell updated GERONIMODEVTOOLS-205:
---

Fix Version/s: (was: 2.0.x)
   2.0
Affects Version/s: (was: 2.0.x)
   2.0

 Name change from Geronimo Eclipse Plugin
 

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


 To something like geronimo-eclipse-plugin instead of g-eclipse-plugin

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

[jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not open in Eclipse browser when invoked with run as, run on server from within Eclipse


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

Tim McConnell updated GERONIMODEVTOOLS-209:
---

  Description: 
This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The 
Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, 
to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when 
it is ultimately ready to be launched that launchable object is null causing a 
NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla 
report against WTP 2.0.x.

java.lang.NullPointerException
at 
org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
at 
org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at 
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at 
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at 
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at 
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at 
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)

 
Affects Version/s: (was: 2.0)
   2.1
Fix Version/s: (was: 2.0)
   2.1

 Hello World JSP does not open in Eclipse browser when invoked with run as, 
 run on server from within Eclipse
 --

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


 This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. 
 The Eclipse plugin is passing a valid HttpLaunchable object, with the correct 
 url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). 
 But when it is ultimately ready to be launched that launchable object is null 
 causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a 
 bugzilla report against WTP 2.0.x.
 java.lang.NullPointerException
   at 
 org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
   at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
   at 
 org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
   at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
   at 
 org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
   at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
   at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
   at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
   at

[jira] Closed: (GERONIMODEVTOOLS-207) Update the license in the feature.properties file for each of the features provided by the plugin


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

Tim McConnell closed GERONIMODEVTOOLS-207.
--

Resolution: Fixed

Fixed in revision 575868

 Update the license in the feature.properties file for each of the features 
 provided by the plugin
 -

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




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

[jira] Closed: (GERONIMODEVTOOLS-205) Name change from Geronimo Eclipse Plugin