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

[Jason Dillon]

I'm converting all of the assemblies tonight, should be done in  
another hour or so.


But, currently server/trunk is not building due to:


[INFO] Compiling 18 source files to /Users/jason/ws/geronimo/server/ 
modules/geronimo-openejb/target/classes
[INFO]  


[ERROR] BUILD FAILURE
[INFO]  


[INFO] Compilation failure

/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[131,30]  
cannot find symbol

symbol  : variable service
location: class  
org.apache.openejb.assembler.classic.TransactionServiceInfo


/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[139,27]  
cannot find symbol

symbol  : variable service
location: class org.apache.openejb.assembler.classic.SecurityServiceInfo

/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[145,24]  
cannot find symbol

symbol  : variable service
location: class org.apache.openejb.assembler.classic.ProxyFactoryInfo


So, I can't verify that everything is super happy...

--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
   geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/gshell

Where the bits in lib/* and lib/endorsed/* are the same as they  
were before.  The bits in lib/boot/* and lib/gshell/* are specific  
to gshell.  And normally a gshell installation would have  
everything I put into lib/gshell/* into lib/*, but I moved them to  
a sub dir for now... since the bin/*.jar's load jars from the ../ 
lib/* dirs.


The lib/boot/* stuff is the very minimal gshell bootstrap classes,  
which setup up the other happiness... and let you do things like:


   java -jar ./geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/ 
boot/gshell-bootstrap.jar


And that will give you a nice shell... or

   java -jar ./geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/ 
boot/gshell-bootstrap.jar start-server


That will launch the G server process using all of the right - 
Djava.ext.dirs and whatever properties that we currently have  
hacked into platform scripts.


Anyways, so the idea is to move all of the bits which are current  
in the lib/* into the repository, and then configure the gshell  
command impl to load put the correct dependency artifacts onto the  
classpath of the target jvm that is booted up.  This will augment  
the existing kernel bootstrap from repo stuff, putting evertying  
except what is needed from gshell into the repository...


And really, what I'd like to eventually get to is having the  
bootstrap from the repository... so that everything except for  
what is now it lib/boot/* and lib/endorsed/* can live in the  
repository like happy little communistic jars should be :-P


* * *

And then there are longer term things for GShell...

Remote administration (via, telnet, ssh, or custom ssl protocol...  
last is most likely to actually happen soonish)


Process management, which is great for clusters, or staging ->  
production management.  A full suite of command-line tools which  
can manage the configuration of a server... easily.  So, for  
example, lets say you've got a configuration that is working  
really well for you... but you want to play with something new...


So you might:

   ./bin/gsh backup-configuration before-mucking
   ./bin/gsh start-server

And then go and change a whole bunch of stuff...  and it doesn't  
work... yikes... so rollback...


   ./bin/gsh backup-configuration hosed-server
   ./bin/gsh restore-configuration before-mucking
   ./bin/gsh start-server

And then maybe you want to play with the "hosed-server"  
configuration again...


   ./bin/gsh start-server --configuration hosed-server

Of course, 

[BUILD] Trunk: Failed for Revision: 575212

[prasad]

OpenEJB trunk at 575210
Geronimo Revision: 575212 built with tests included
 
See the full build-0400.log file at 
http://people.apache.org/~prasad/binaries/trunk/20070913/build-0400.log
 
13K downloaded
Downloading: 
http://download.java.net/maven/1//com.sun.xml.bind/poms/jaxb-impl-2.0.5.pom
656b downloaded
Downloading: http://download.java.net/maven/1//ognl/poms/ognl-2.6.9.pom
[WARNING] Unable to get resource 'ognl:ognl:pom:2.6.9' from repository java.net 
(http://download.java.net/maven/1/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//ognl/ognl/2.6.9/ognl-2.6.9.pom
[WARNING] Unable to get resource 'ognl:ognl:pom:2.6.9' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repo1.maven.org/maven2/ognl/ognl/2.6.9/ognl-2.6.9.pom
792b downloaded
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
[WARNING] Unable to get resource 'woodstox:wstx-asl:pom:3.2.1' from repository 
java.net (http://download.java.net/maven/1/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[WARNING] Unable to get resource 'woodstox:wstx-asl:pom:3.2.1' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[WARNING] Unable to get resource 'woodstox:wstx-asl:pom:3.2.1' from repository 
central (http://repo1.maven.org/maven2)
Downloading: http://download.java.net/maven/1//woodstox/jars/wstx-asl-3.2.1.jar
[WARNING] Unable to get resource 'woodstox:wstx-asl:jar:3.2.1' from repository 
java.net (http://download.java.net/maven/1/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.jar
[WARNING] Unable to get resource 'woodstox:wstx-asl:jar:3.2.1' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.jar
493K downloaded
Downloading: http://download.java.net/maven/1//ognl/jars/ognl-2.6.9.jar
[WARNING] Unable to get resource 'ognl:ognl:jar:2.6.9' from repository java.net 
(http://download.java.net/maven/1/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//ognl/ognl/2.6.9/ognl-2.6.9.jar
[WARNING] Unable to get resource 'ognl:ognl:jar:2.6.9' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repo1.maven.org/maven2/ognl/ognl/2.6.9/ognl-2.6.9.jar
164K downloaded
Downloading: 
http://download.java.net/maven/1//com.sun.xml.bind/jars/jaxb-impl-2.0.5.jar
769K downloaded
[INFO] snapshot org.apache.geronimo.modules:geronimo-kernel:2.1-SNAPSHOT: 
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-kernel:2.1-SNAPSHOT: 
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-kernel:2.1-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
Downloading: 
http://repository.codehaus.org/com/sun/xml/bind/jaxb-xjc/2.0.3/jaxb-xjc-2.0.3.pom
[WARNING] Unable to get resource 'com.sun.xml.bind:jaxb-xjc:pom:2.0.3' from 
repository codehaus.org (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.0.3/jaxb-xjc-2.0.3.pom
165b downloaded
Downloading: 
http://repository.codehaus.org/com/sun/xml/bind/jaxb-xjc/2.0.3/jaxb-xjc-2.0.3.jar
[WARNING] Unable to get resource 'com.sun.xml.bind:jaxb-xjc:jar:2.0.3' from 
repository codehaus.org (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.0.3/jaxb-xjc-2.0.3.jar
2918K downloaded
[INFO] [jaxb2:xjc {execution: default}]
[INFO] Generating source...
[INFO] parsing a schema...
[INFO] compiling a schema...
[INFO] org/apache/geronimo/system/plugin/model/ArtifactType.java
[INFO] org/apache/geronimo/system/plugin/model/AttributeType.java
[INFO] org/apache/geronimo/system/plugin/model/AttributesType.java
[INFO] org/apache/geronimo/system/plugin/model/CopyFileType.java
[INFO] org/apache/geronimo/system/plugin/model/DependencyType.java
[INFO] org/apache/geronimo/system/plugin/model/GbeanType.java
[INFO] org/apache/geronimo/system/plugin/model/HashType.java
[INFO] org/apache/geronimo/system/plugin/model/LicenseType.java
[INFO] org/apache/geronimo/system/plugin/model/ModuleType.java
[INFO] org/apache/geronimo/system/plugin/model/ObjectFactory.java
[INFO] org/apache/geronimo/system/plugin/model/PluginArtifactType.java
[INFO] org/apache/geronimo/system/plugin/model/PluginListType.java
[INFO] org/apache/geronimo/system/plugin/model/PluginType.java
[INFO] org/apache/geronimo/system/plugin/model/PrerequisiteType.java
[INFO] org/apache/geronimo/syst

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

[Anita Kulshreshtha]

   I would like to see download links to the following items on the
project site at http://geronimo.apache.org/development-tools.html under
prerequisites section.

> 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> 2 -- Web Tools Platform (WTP) 2.0.1
> 3 -- Data Tools Platform (DTP) 1.5
> 4 -- Eclipse Modeling Framework (EMF) 2.3
> 5 -- Graphical Editing Framework (GEF) 3.3

   
Thanks
Anita

> On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > Start of discussion thread.
> > --
> > Thanks,
> > Tim McConnell
> >
> >

> ===  Step #1 -- Install prerequisites
>===
>

> The Geronimo Eclipse Plugin 2.0.0 has a number of prerequisites that
> must be 
> installed prior to the installation of the plugin itself. These are
> necessary 
> to establish the proper Eclipse installation. They are:
> 
> 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> 2 -- Web Tools Platform (WTP) 2.0.1
> 3 -- Data Tools Platform (DTP) 1.5
> 4 -- Eclipse Modeling Framework (EMF) 2.3
> 5 -- Graphical Editing Framework (GEF) 3.3
> 
> You can manually download the latest versions of these artifacts but
> it is 
> somewhat cumbersome. Instead I've created an ant script (that is
> based on 
> the one used to build the plugin) that you can use that will download
> and unzip 
> everything for you. You can get it from here:
> 
> http://people.apache.org/~mcconne/releases/RC2/build.xml
> 
> After you download it somewhere (preferably in a temp subdirectory)
> you can just 
> invoke it for your specific platform using one of these three
> commands:
> 
> > ant win32
> > ant linux
> > ant macos
> 
> It will create an /org/EUROPA/eclipse/3.3 subdirectory with all the 
> downloaded artifacts and an /EUROPA/eclipse subdirectory where
> everything has 
> been unzipped. This is now the Eclipse installation directly you
> should use to 
> test the Geronimo Eclipse 2.0.0 plugin. 
> 
> If you don't wish to use the ant script it's very important to ensure
> you have
> the latest versions of each -- otherwise the plugin will not function
> correctly. 
> For example, the WTP 2.0.0 release is fairly old and buggy, and our
> plugin will
> not function correctly. That is why this ant script downloads and
> installs the 
> WTP 2.0.1 RC1 artifacts. 
> 
> 
> Now that you have all the prerequisites you can do either of the two
> scenarios
> below since each must work and both should emulate how it will be
> installed and 
> used in the real world.  Scenarios #1 and #2 are mutually exclusive
> though -- 
> do one or the other but not both unless you first delete and recreate
> your
> Eclipse installation directory (preferably with the ant script
> above). 
> 
>

> ===  Scenario #1 -- Upzip everything 
>===
>

> You can just download the plugin itself and unzip it into the same
> directory
> where all the prereqs were installed (e.g., EUROPA/eclipse). If you
> choose 
> this option you must have an installed version of the Geronimo 2.0.1
> server 
> somewhere on your system so that you can define an Geronimo Server 
> configuration. If you've never done this before the steps are fairly 
> straightforward:
> 
> 1 -- Download the plugin and unzip into your EUROPA/eclipse
> directory.
>  You can download the plugin from here: 
> 
>
http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip
> 
> 2 -- Invoke the eclipse executable from your EUROPA/eclipse
> directory. Select or
>  accept the default workspace. 
> 
> 3 -- Open the Java EE perspective. From within Eclipse:
> 
>  a. Close the Welcome tab
> 
>  b. Select Window --> Open Perspective --> Other --> Java EE
> You should now be in the Java EE perspective. You can see the
> open 
> perspective tabs in the upper right-hand corner of your
> Eclipse  
> workspace.
> 
> 4 -- Define a new server. From Eclipse select:
> 
>  a. File --> New --> Other --> Server --> Server --> Next -->
> Apache. 
> At this point you must see the Apache Geronimo v2.0 Server
> selection
> or the plugin was not installed/unzipped correctly. 
> 
>  b. Select "Apache Geronimo v2.0 Server" --> Next --> then enter
> the root 
> directory of your Geronimo server installation --> Next -->
> Next --> 
> Next --> Finish
> 
>  c. Now in the Java EE perspective you should see the Apache
> Geronimo v2.0 
> server (bottom pane, middle tab usually) that you can now
> start in 
> Eclipse (either right-click on it and select start or select
> the little
> green and white arrow on t

[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application

[Vamsavardhana Reddy (JIRA)]

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

Vamsavardhana Reddy commented on GERONIMO-2964:
---

Have you tried changing/fixing the SUID for SerializedGBeanState?  ==>  How do 
I do that?

> Cannot specify the Tomcat work directory for a web application
> --
>
> Key: GERONIMO-2964
> URL: https://issues.apache.org/jira/browse/GERONIMO-2964
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 1.2, 2.0-M5
>Reporter: Aman Nanner
>Priority: Minor
> Fix For: 1.2, 2.1
>
> Attachments: g2964.war, GERONIMO-2964-combined-new.patch, 
> GERONIMO-2964-combined.patch, GERONIMO-2964.patch, 
> tomcat-config-workdir.patch, tomcat-workdir.patch
>
>
> In Tomcat, a work directory can be specified for a web application in a 
> WEB-INF/context.xml file.  The GeronimoStandardContext does not permit the 
> user to specify a work directory, and so the work directory defaults to 
> var/catalina/work/.
> I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to 
> permit the user to optionally specify a work directory.  This work directory 
> is then propagated into the TomcatContext.  I've tested this and it seems to 
> work well.

-- 
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 (RC2)

[Jacek Laskowski]

On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> Start of discussion thread.

Hi Tim,

I'm pretty sure I asked about it (or was about to have asked, but
failed), but why is the plugin called g-eclipse-plugin? Wouldn't it be
better off if it called geronimo-eclipse-plugin? It doesn't say much
when I have g-eclipse-plugin in my eclipse plugin repository and in
discussions people tend to use geronimo-eclipse-plugin even though it
may seem to be easier to say g-eclipse-plugin and following the
plugin's name. It can be confusing.

I think I should've noted it sooner and I do appologize to talk about
it now right before the plugin is to be released and am leaning
towards -1 because of the name (I don't want to be disruptive to the
process, so just a friendly reminder I should not do that do the trick
just fine ;-))

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

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

[Jason Dillon]

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
   geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/gshell

Where the bits in lib/* and lib/endorsed/* are the same as they  
were before.  The bits in lib/boot/* and lib/gshell/* are specific  
to gshell.  And normally a gshell installation would have  
everything I put into lib/gshell/* into lib/*, but I moved them to  
a sub dir for now... since the bin/*.jar's load jars from the ../ 
lib/* dirs.


The lib/boot/* stuff is the very minimal gshell bootstrap classes,  
which setup up the other happiness... and let you do things like:


   java -jar ./geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/ 
boot/gshell-bootstrap.jar


And that will give you a nice shell... or

   java -jar ./geronimo-jetty6-javaee5-gshell-2.1-SNAPSHOT/lib/ 
boot/gshell-bootstrap.jar start-server

[jira] Closed: (GERONIMO-3471) Enabling Web Server Manager statistics appears to have no effect in admin console

[Kevan Miller (JIRA)]

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

Kevan Miller closed GERONIMO-3471.
--

Resolution: Duplicate

Dup of GERONIMO-2775

> Enabling Web Server Manager statistics appears to have no effect in admin 
> console 
> --
>
> Key: GERONIMO-3471
> URL: https://issues.apache.org/jira/browse/GERONIMO-3471
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.0.1
>Reporter: Kevan Miller
>Priority: Minor
> Fix For: 2.0.x, 2.1
>
>
> Aleksandr reports that clicking "enable" statistics on the Web Server page of 
> the admin console has no effect. I tested on a Jetty server and it indeed 
> does not work (or has no visible impact). 

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

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

[Shiva Kumar H R (JIRA)]

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.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1


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.

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

[Shiva Kumar H R]

+1

Tested using
http://cwiki.apache.org/geronimo/java-ee-50-app-development-on-geronimo-simplified-using-eclipse.htmland
everything worked fine, except for a minor error as reported in
GERONIMODEVTOOLS-203, but that is a non-blocker.

- Shiva

On 9/13/07, Tim McConnell <[EMAIL PROTECTED]> 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
>

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

[Shiva Kumar H R]

Ted,
I see you have updated the version of Web Tools Platform (WTP) to 2.0.1 from
2.0. However on http://download.eclipse.org/webtools/downloads/ I see that
2.0.1 is not yet released (only RC1 is available). Was it a typo?

- Shiva

On 9/13/07, Ted Kirby <[EMAIL PROTECTED]> wrote:
>
> Looks good.  Thanks Tim.
> Attached are some minor updates/feedback on your instructions.
>
> On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > Start of discussion thread.
> > --
> > Thanks,
> > Tim McConnell
> >
>
>

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

[Shiva Kumar H R]

On 9/13/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
>
>I would like to see download links to the following items on the
> project site at http://geronimo.apache.org/development-tools.html under
> prerequisites section.


Thanks for capturing this Anita. Also
http://geronimo.apache.org/development-tools.htm currently mentions the
pre-requisite as "WebTools Platform Runtime 1.5.1 driver", version should be
updated to "2.0".

> 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> > 2 -- Web Tools Platform (WTP) 2.0.1


2.0.1 again! Am I missing something?? Shouldn't this be 2.0?

> 3 -- Data Tools Platform (DTP) 1.5
> > 4 -- Eclipse Modeling Framework (EMF) 2.3
> > 5 -- Graphical Editing Framework (GEF) 3.3
>
>
> Thanks
> Anita
>
> > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > > Start of discussion thread.
> > > --
> > > Thanks,
> > > Tim McConnell
> > >
> > >
>
> 
> > ===  Step #1 -- Install prerequisites
> >===
> >
>
> 
> > The Geronimo Eclipse Plugin 2.0.0 has a number of prerequisites that
> > must be
> > installed prior to the installation of the plugin itself. These are
> > necessary
> > to establish the proper Eclipse installation. They are:
> >
> > 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> > 2 -- Web Tools Platform (WTP) 2.0.1
> > 3 -- Data Tools Platform (DTP) 1.5
> > 4 -- Eclipse Modeling Framework (EMF) 2.3
> > 5 -- Graphical Editing Framework (GEF) 3.3
> >
> > You can manually download the latest versions of these artifacts but
> > it is
> > somewhat cumbersome. Instead I've created an ant script (that is
> > based on
> > the one used to build the plugin) that you can use that will download
> > and unzip
> > everything for you. You can get it from here:
> >
> > http://people.apache.org/~mcconne/releases/RC2/build.xml
> >
> > After you download it somewhere (preferably in a temp subdirectory)
> > you can just
> > invoke it for your specific platform using one of these three
> > commands:
> >
> > > ant win32
> > > ant linux
> > > ant macos
> >
> > It will create an /org/EUROPA/eclipse/3.3 subdirectory with all the
> > downloaded artifacts and an /EUROPA/eclipse subdirectory where
> > everything has
> > been unzipped. This is now the Eclipse installation directly you
> > should use to
> > test the Geronimo Eclipse 2.0.0 plugin.
> >
> > If you don't wish to use the ant script it's very important to ensure
> > you have
> > the latest versions of each -- otherwise the plugin will not function
> > correctly.
> > For example, the WTP 2.0.0 release is fairly old and buggy, and our
> > plugin will
> > not function correctly. That is why this ant script downloads and
> > installs the
> > WTP 2.0.1 RC1 artifacts.
> >
> >
> > Now that you have all the prerequisites you can do either of the two
> > scenarios
> > below since each must work and both should emulate how it will be
> > installed and
> > used in the real world.  Scenarios #1 and #2 are mutually exclusive
> > though --
> > do one or the other but not both unless you first delete and recreate
> > your
> > Eclipse installation directory (preferably with the ant script
> > above).
> >
> >
>
> 
> > ===  Scenario #1 -- Upzip everything
> >===
> >
>
> 
> > You can just download the plugin itself and unzip it into the same
> > directory
> > where all the prereqs were installed (e.g., EUROPA/eclipse). If you
> > choose
> > this option you must have an installed version of the Geronimo 2.0.1
> > server
> > somewhere on your system so that you can define an Geronimo Server
> > configuration. If you've never done this before the steps are fairly
> > straightforward:
> >
> > 1 -- Download the plugin and unzip into your EUROPA/eclipse
> > directory.
> >  You can download the plugin from here:
> >
> >
>
> http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zip
> >
> > 2 -- Invoke the eclipse executable from your EUROPA/eclipse
> > directory. Select or
> >  accept the default workspace.
> >
> > 3 -- Open the Java EE perspective. From within Eclipse:
> >
> >  a. Close the Welcome tab
> >
> >  b. Select Window --> Open Perspective --> Other --> Java EE
> > You should now be in the Java EE perspective. You can see the
> > open
> > perspective tabs in the upper right-hand corner of your
> > Eclipse
> > workspace.
> >
> > 4 -- Define a new server. From Eclipse select:
> >
> >  a. File --> New --> Other --> Server --> Server --> Next -->
> > Apache.
> > At this point you must see the Apache Geronimo v2.0 Server
> > selection
> > or the plugin was not installed/unzipped correctly.

[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application

[Anita Kulshreshtha (JIRA)]

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

Anita Kulshreshtha commented on GERONIMO-2964:
--

We need to find what exactly is being deserailized. Is this the full trace?  
There should be something like - 
Caused by: java.io.IOException: Unable to deserialize AbstractName for 
GBeanData of type org.apache.geronimo.jetty6.JettyFilterMapping 
or

Caused by: java.lang.ClassCastException: cannot assign instance of 
javax.management.ObjectName to field org.apache.geronimo.gbean.Ab
stractName.objectName of type javax.management.ObjectName in instance of 
org.apache.geronimo.gbean.AbstractName 

or

Caused by: java.io.InvalidClassException:
> org.apache.geronimo.gbean.GOperationInfo; local class incompatible:
> stream classdesc serialVersionUID = 5185515581104192976, local class
> serialVersionUID = -5593225815559931812
>at java.io.ObjectStreamClass.initNonProxy
> (ObjectStreamClass.java:519) 

In the past they have all lead to this error.

> Cannot specify the Tomcat work directory for a web application
> --
>
> Key: GERONIMO-2964
> URL: https://issues.apache.org/jira/browse/GERONIMO-2964
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 1.2, 2.0-M5
>Reporter: Aman Nanner
>Priority: Minor
> Fix For: 1.2, 2.1
>
> Attachments: g2964.war, GERONIMO-2964-combined-new.patch, 
> GERONIMO-2964-combined.patch, GERONIMO-2964.patch, 
> tomcat-config-workdir.patch, tomcat-workdir.patch
>
>
> In Tomcat, a work directory can be specified for a web application in a 
> WEB-INF/context.xml file.  The GeronimoStandardContext does not permit the 
> user to specify a work directory, and so the work directory defaults to 
> var/catalina/work/.
> I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to 
> permit the user to optionally specify a work directory.  This work directory 
> is then propagated into the TomcatContext.  I've tested this and it seems to 
> work well.

-- 
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 (RC2)

[Shiva Kumar H R]

On 9/13/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
>
> On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > Start of discussion thread.
>
> Hi Tim,
>
> I'm pretty sure I asked about it (or was about to have asked, but
> failed), but why is the plugin called g-eclipse-plugin? Wouldn't it be
> better off if it called geronimo-eclipse-plugin? It doesn't say much
> when I have g-eclipse-plugin in my eclipse plugin repository and in
> discussions people tend to use geronimo-eclipse-plugin even though it
> may seem to be easier to say g-eclipse-plugin and following the
> plugin's name. It can be confusing.
>
> I think I should've noted it sooner and I do appologize to talk about
> it now right before the plugin is to be released and am leaning
> towards -1 because of the name (I don't want to be disruptive to the
> process, so just a friendly reminder I should not do that do the trick
> just fine ;-))


Agree with Jacek about changing the name from "g-eclipse-plugin-*" to
"geronimo-eclipse-plugin-*". There will then be consistency in what we have
and what we speak.

Jacek,
Will it be fine if we do this in the next release 2.1? We probably can have
a JIRA opened for this so that we don't loose track of this. Getting 2.0 out
will allow us to focus back on trunk, in which we want to propose some major
changes to Geronimo deployment plan editors.

- Shiva

Jacek
>
> --
> Jacek Laskowski
> http://www.JacekLaskowski.pl
>

[jira] Commented: (GERONIMO-3466) car-maven-plugin can not generate server plugin which includes EJB

[YunFeng Ma (JIRA)]

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

YunFeng Ma commented on GERONIMO-3466:
--

Hi David,
This problem happened in car maven plugin v2.0.1, and I noticed there is big 
difference from the plugin in trunk. I'll try the plugin in trunk after trunk 
server build is successful.

> car-maven-plugin can not generate server plugin which includes EJB
> --
>
> Key: GERONIMO-3466
> URL: https://issues.apache.org/jira/browse/GERONIMO-3466
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: car-maven-plugin
>Affects Versions: 2.0.1
>Reporter: YunFeng Ma
> Fix For: 2.0.x
>
>
> openejb-deployer configuration depends on openejb configuration, and openejb 
> configuration depends on j2ee-server configuration. That means 
> car-maven-plugin has to start all the depended configurations, not only the 
> openejb-deployer configuration. This caused the following error.
> {code}
> [INFO] Scanning for projects...
> [INFO] 
> -
> ---
> [INFO] Building daytrader-derby-tomcat
> [INFO]task-segment: [install]
> [INFO] 
> -
> ---
> [INFO] [dependency:unpack {execution: unpack-distribution}]
> [INFO] Configured Artifact: 
> org.apache.geronimo.daytrader:daytrader-ear:2.0:ear
> [INFO] daytrader-ear-2.0.ear already unpacked.
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [car:prepare-plan]
> [INFO] Generated: 
> F:\WASCE\samples_v2\plugins\daytrader-derby-tomcat\target\plan
> \plan.xml
> log4j:WARN No appenders could be found for logger 
> (org.codehaus.mojo.pluginsuppo
> rt.logging.Logging).
> log4j:WARN Please initialize the log4j system properly.
> [INFO] [car:package]
> [INFO] Packaging module configuration: 
> F:\WASCE\samples_v2\plugins\daytrader-der
> by-tomcat\target\plan\plan.xml
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] start of org.apache.geronimo.configs/openejb-deployer/2.0.1/car failed
> Configuration org.apache.geronimo.configs/j2ee-system/2.0.1/car failed to 
> start
> due to the following reasons:
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=GBean,name=ServerInfo did not start because Could not determine 
> geronimo
> installation directory
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=Repository,name=Repository did not start because 
> org.apache.geronimo.conf
> igs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/
> 2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ConfigurationStore,name=Local did not start because 
> org.apache.geronimo.c
> onfigs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-syst
> em/2.0.1/car,j2eeType=Repository,name=Repository did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=AttributeStore,name=AttributeManager did not start because 
> org.apache.ger
> onimo.configs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2
> ee-system/2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ArtifactResolver,name=ArtifactResolver did not start because 
> org.apache.g
> eronimo.configs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/
> j2ee-system/2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ConfigurationManager,name=ConfigurationManager did not start because 
> the
> following dependent services did not start: 
> [org.apache.geronimo.configs/j2ee-sy
> stem/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j
> 2eeType=ArtifactResolver,name=ArtifactResolver, 
> org.apache.geronimo.configs/j2ee
> -system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/ca
> r,j2eeType=AttributeStore,name=AttributeManager]
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=SystemLog,name=Logger did not start because 
> org.apache.geronimo.configs/j
> 2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1
> /car,j2eeType=GBean,name=ServerInfo did not start.
> [INFO] 
> --

Re: [DISCUSS] Move J2G from sandbox to devtools

[Shiva Kumar H R]

Let's do both "move the current J2G files from sandbox/j2g to
devtools/trunk/j2g" and "update the Development Tools section of the
Geronimo site" at the earliest.

In http://www.mail-archive.com/[EMAIL PROTECTED]/msg07349.html a user
was still using some old wiki docs (
http://cwiki.apache.org/GMOxDOC10/jboss-to-geronimo-jca-migration.html) for
migrating from JBoss to Geronimo. I think it would be a good idea to update
all related wiki docs (like the one above) with a highlighted link at the
top pointing to the availability of J2G toolkit.

- Shiva

On 9/12/07, Erik B. Craig < [EMAIL PROTECTED]> wrote:
>
> Yes!
>
> I am all for this, especially so we can progress it onto the Development
> Tools section of the Geronimo site to make it more noticeable and easily
> accessible to people interested in migrating applications, as right now the
> only way to download it or even be aware of it is by digging through our
> wiki.
>
> On 9/12/07, Donald Woods < [EMAIL PROTECTED]> wrote:
> >
> > Given all of the work and interest in the J2G tool, I would like to move
> > the
> > current J2G files from sandbox/j2g to devtools/trunk/j2g, so we can
> > start
> > working towards an official release of the tool.
> >
> > Does this require a Vote first or does the CTR process apply here, as
> > the code
> > is already in our svn repo?
> >
> >
> > -Donald
> >
> >
>
>
> --
> Erik B. Craig

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

[Donald Woods]

You'd have to ask Sachin why he named the assemblies that way.


-Donald

Jacek Laskowski wrote:

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

Start of discussion thread.


Hi Tim,

I'm pretty sure I asked about it (or was about to have asked, but
failed), but why is the plugin called g-eclipse-plugin? Wouldn't it be
better off if it called geronimo-eclipse-plugin? It doesn't say much
when I have g-eclipse-plugin in my eclipse plugin repository and in
discussions people tend to use geronimo-eclipse-plugin even though it
may seem to be easier to say g-eclipse-plugin and following the
plugin's name. It can be confusing.

I think I should've noted it sooner and I do appologize to talk about
it now right before the plugin is to be released and am leaning
towards -1 because of the name (I don't want to be disruptive to the
process, so just a friendly reminder I should not do that do the trick
just fine ;-))

Jacek



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Donald Woods]

Need to be more specific on the Eclipse package that users need, now that 
there are 5 different distros -


> 1 -- Europa (also known as Eclipse 3.3), which is platform specific
1 -- Eclipse IDE for Java EE Developers (Europa v3.3 or later)

Also, by prereqing WTP 2.0.1, I think it requires newer levels of the all the 
packages, based on the current prereq levels listed for WTP 2.0.1 RC1 at the 
top of the following download page -


http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC1-20070907070540/

Which means its targeted to Eclipse 3.3.1 which is supposed to ship by end of 
Sept.



-Donald

Ted Kirby wrote:

Looks good.  Thanks Tim.
Attached are some minor updates/feedback on your instructions.

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

Start of discussion thread.
--
Thanks,
Tim McConnell



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Viet Hung Nguyen (JIRA)]

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

Viet Hung Nguyen updated GERONIMO-3413:
---

Attachment: geronimo-3413.patch

this patch fixes the Server Logs portlet. The "Web Access Log Viewer" does not 
do any querying because the parameters are not being passed correctly. 

additionally, the patch fixes the Shutdown portlet too. The shutdown option was 
not working properly before.

There are other known issues:
1. Apache HTTP --> step through the process --> attempt to step through it 
again (an error will occur)
2. Plugins --> Export Plugin --> I get one of two errors a) "Index=1, Size=0" 
or b) RequestURI=/console/car-export not found
3. When installing the plugin for the first time I get 2 different types of 
complaints a) no meta-data file found and b) unable to delete temporary 
directory
4. I have to log in through ://:/console. If i was 
previously on a page and stop/started the server and attempted to log in 
through the redirected log in page, I will get an error. In the previous 
console I had this ability.

This information is only valid for jetty. I have not yet tested them on tomcat.

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

Re: question about servicemix 3.1.2 release

[Guillaume Nodet]

ServiceMix 3.1.2 does not depend on camel afaik, only trunk does.And for the
branch, you should try using https instead of http
(could you fix the release instructions if they are misleading?)

On 9/13/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
>
> Hi Guillaume,
>
> The release guide say that there should be no snapshot dependency, but
> servicemix-camel depend on camel 1.1 snapshot, without this snapshot
> dependency, this service-engine can't get compiled.  How to handle this
> problem?
> And I failed to do
> svn mkdir
> http://svn.apache.org/repos/asf/incubator/servicemix/branches/servicemix-
> 3.1.2
> -m "ServiceMix 3.1.2 Release Branch"
> The error is
> svn: MKACTIVITY of
> '/repos/asf/!svn/act/334b9964-033a-0410-a474-8f0ea706a33b': 403
> Forbidden (http://svn.apache.org)
> Any Suggestion is appreciated.
> Thanks very much
>
>
> Freeman
>
> Guillaume Nodet wrote:
> > I have updated the releasing notes to something that I hope will work
> ;-)
> > See http://cwiki.apache.org/confluence/display/SM/Release+Guide
> > If you have any questions, just yell !
> >
> > On 9/12/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote:
> >
> >> On Sep 12, 2007, at 8:46 AM, Freeman Fang wrote:
> >>
> >> Hi all,
> >>
> >> When are we going to release servicemix 3.1.2? As a new commiter in
> >> servicemix team, I'd like to know how is the release process looks
> like.
> >> If possible, shall I be release manager of this time?  :-)
> >>
> >> Yeah of course you can :-)
> >> There are some instructions available at
> >> http://incubator.apache.org/servicemix/release-guide.html
> >> but these are a bit outdated, so we'll have to update those (and maven
> can
> >> not really be used for
> >> creating the release)...
> >> Let me have a breakfast and write something more accurate...
> >>
> >> Any suggestion is appreciated.
> >>
> >> Best Regards
> >>
> >>
> >> Freeman
> >>
> >>
> >> --
> >> Cheers,
> >> Guillaume Nodet
> >> 
> >> Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
>



-- 
Cheers,
Guillaume Nodet

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

unsubscribe

[Rogan, Henry]

Regards,
Henry   
Henry Rogan IT Architecture 972.516.5667
XO Communications Inc. 2700 Summit, Plano TX 75074  
 
 
 


-Original Message-
From: Guillaume Nodet [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 13, 2007 8:53 AM
To: [EMAIL PROTECTED]
Subject: Re: question about servicemix 3.1.2 release

ServiceMix 3.1.2 does not depend on camel afaik, only trunk does.And for
the
branch, you should try using https instead of http
(could you fix the release instructions if they are misleading?)

On 9/13/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
>
> Hi Guillaume,
>
> The release guide say that there should be no snapshot dependency, but
> servicemix-camel depend on camel 1.1 snapshot, without this snapshot
> dependency, this service-engine can't get compiled.  How to handle
this
> problem?
> And I failed to do
> svn mkdir
>
http://svn.apache.org/repos/asf/incubator/servicemix/branches/servicemix
-
> 3.1.2
> -m "ServiceMix 3.1.2 Release Branch"
> The error is
> svn: MKACTIVITY of
> '/repos/asf/!svn/act/334b9964-033a-0410-a474-8f0ea706a33b': 403
> Forbidden (http://svn.apache.org)
> Any Suggestion is appreciated.
> Thanks very much
>
>
> Freeman
>
> Guillaume Nodet wrote:
> > I have updated the releasing notes to something that I hope will
work
> ;-)
> > See http://cwiki.apache.org/confluence/display/SM/Release+Guide
> > If you have any questions, just yell !
> >
> > On 9/12/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote:
> >
> >> On Sep 12, 2007, at 8:46 AM, Freeman Fang wrote:
> >>
> >> Hi all,
> >>
> >> When are we going to release servicemix 3.1.2? As a new commiter in
> >> servicemix team, I'd like to know how is the release process looks
> like.
> >> If possible, shall I be release manager of this time?  :-)
> >>
> >> Yeah of course you can :-)
> >> There are some instructions available at
> >> http://incubator.apache.org/servicemix/release-guide.html
> >> but these are a bit outdated, so we'll have to update those (and
maven
> can
> >> not really be used for
> >> creating the release)...
> >> Let me have a breakfast and write something more accurate...
> >>
> >> Any suggestion is appreciated.
> >>
> >> Best Regards
> >>
> >>
> >> Freeman
> >>
> >>
> >> --
> >> 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)

[Ted Kirby]

Tim and I have been working hard on getting the "Download and Install"
function to work to download a server for the eclipse update site and
install it your machine.  The stablest level on which we have found
this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
lower WTP levels.  Running and debugging the plugin in eclipse has
been tedious and buggy.  I would vote -99 for releasing the plugin on
any level less than WTP2.0.1RC1.  I have been frustrated to not be
able to work on other things because of these issues.  You may well
judge that I am unduly focused on these issues.  I am glad that you
and others have success with the plugin and various enhancements.  I
am certainly disappointed in WTP2.0.x at this point.  What level of
WTP are you using?  The WTP 2.0.1 release schedule is here:
http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
when it comes out, I think we should upgrade our levels and Tim's
build.xml to move to that level.  It unfortunately seems prudent for
us to dig into the eclipse WTP community to make sure the parts we use
work.

Ted Kirby

On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
> Ted,
> I see you have updated the version of Web Tools Platform (WTP) to 2.0.1 from
> 2.0. However on
> http://download.eclipse.org/webtools/downloads/ I see that
> 2.0.1 is not yet released (only RC1 is available). Was it a typo?
>
> - Shiva
>
>
> On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:
> > Looks good.  Thanks Tim.
> > Attached are some minor updates/feedback on your instructions.
> >
> > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > > Start of discussion thread.
> > > --
> > > Thanks,
> > > Tim McConnell
> > >
> >
> >
>
>

[jira] Closed: (GERONIMO-3401) Stop of module from "System Modules" in console should warn user of destructive action

[Joe Bohn (JIRA)]

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

Joe Bohn closed GERONIMO-3401.
--


> Stop of module from "System Modules" in console should warn user of 
> destructive action
> --
>
> Key: GERONIMO-3401
> URL: https://issues.apache.org/jira/browse/GERONIMO-3401
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>Affects Versions: 2.0, 2.0.x
> Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly.  Most 
> likely affects others as well
>Reporter: Matt Hogstrom
>Assignee: Joe Bohn
> Fix For: 2.0.x, 2.1
>
>
> When using the Geronimo Console to stop of a module a 404 is received in the 
> console.  In this case an attempt to stop OpenEJB.  The console then becomes 
> unusable and also does not survive a restart.  It appears the console needs 
> to be re-installed.
> {panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc| 
> titleBGColor=#F7D6C1| bgColor=#CE} 
> HTTP Status 404 - 
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> type Status report
> message 
> /console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
> description The requested resource 
> (/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
>  is not available.
> {panel}
> {panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc| 
> titleBGColor=#F7D6C1| bgColor=#CE}
> [] received stop signal
> 00:59:03,833 ERROR [Servlet] Exception caught: 
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid 
> to gbean: 
> org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at 
> org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit()
> at 
> org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
> at 
> org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
> at 
> org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
> at 
> org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
> at 
> org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
> at 
> org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
> at 
> org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
> at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
> at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
> at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
> at 
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at 
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
> at 
> org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
> at 
> org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
> at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at 
> org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Auth

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

[Anita Kulshreshtha]

FWIW, I followed the "Use Staging Site" instructions and used update
manager's staging_site to download tomcat version on windows. The
server and the admin console started fine. I got download urls for
various parts from ant build file at
http://people.apache.org/~mcconne/releases/RC2/build.xml
   

Thanks
Anita
 
--- Ted Kirby <[EMAIL PROTECTED]> wrote:

> Tim and I have been working hard on getting the "Download and
> Install"
> function to work to download a server for the eclipse update site and
> install it your machine.  The stablest level on which we have found
> this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
> lower WTP levels.  Running and debugging the plugin in eclipse has
> been tedious and buggy.  I would vote -99 for releasing the plugin on
> any level less than WTP2.0.1RC1.  I have been frustrated to not be
> able to work on other things because of these issues.  You may well
> judge that I am unduly focused on these issues.  I am glad that you
> and others have success with the plugin and various enhancements.  I
> am certainly disappointed in WTP2.0.x at this point.  What level of
> WTP are you using?  The WTP 2.0.1 release schedule is here:
> http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
> 9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
> with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
> when it comes out, I think we should upgrade our levels and Tim's
> build.xml to move to that level.  It unfortunately seems prudent for
> us to dig into the eclipse WTP community to make sure the parts we
> use
> work.
> 
> Ted Kirby
> 
> On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
> > Ted,
> > I see you have updated the version of Web Tools Platform (WTP) to
> 2.0.1 from
> > 2.0. However on
> > http://download.eclipse.org/webtools/downloads/ I see that
> > 2.0.1 is not yet released (only RC1 is available). Was it a typo?
> >
> > - Shiva
> >
> >
> > On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:
> > > Looks good.  Thanks Tim.
> > > Attached are some minor updates/feedback on your instructions.
> > >
> > > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > > > Start of discussion thread.
> > > > --
> > > > Thanks,
> > > > Tim McConnell
> > > >
> > >
> > >
> >
> >
> 



  

Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, 
and more!
http://tv.yahoo.com/collections/3658 

Re: [DISCUSS] Move J2G from sandbox to devtools

[Hernan Cunico]

I think we could mention this tool and include some links to the main website 
on top level pages like *Migrating to Apache Geronimo*, here are some links

http://cwiki.apache.org/GMOxDOC10/migrating-to-apache-geronimo.html
http://cwiki.apache.org/GMOxDOC11/migrating-to-apache-geronimo.html
http://cwiki.apache.org/GMOxDOC20/migrating-to-apache-geronimo.html

Cheers!
Hernan

Shiva Kumar H R wrote:
Let's do both "move the current J2G files from sandbox/j2g to 
devtools/trunk/j2g" and "update the Development Tools section of the 
Geronimo site" at the earliest.


In http://www.mail-archive.com/[EMAIL PROTECTED]/msg07349.html a 
user was still using some old wiki docs 
(http://cwiki.apache.org/GMOxDOC10/jboss-to-geronimo-jca-migration.html 
) 
for migrating from JBoss to Geronimo. I think it would be a good idea to 
update all related wiki docs (like the one above) with a highlighted 
link at the top pointing to the availability of J2G toolkit.


- Shiva

On 9/12/07, *Erik B. Craig* < [EMAIL PROTECTED] 
> wrote:


Yes!

I am all for this, especially so we can progress it onto the
Development Tools section of the Geronimo site to make it more
noticeable and easily accessible to people interested in migrating
applications, as right now the only way to download it or even be
aware of it is by digging through our wiki.


On 9/12/07, *Donald Woods* < [EMAIL PROTECTED]
> wrote:

Given all of the work and interest in the J2G tool, I would like
to move the
current J2G files from sandbox/j2g to devtools/trunk/j2g, so we
can start
working towards an official release of the tool.

Does this require a Vote first or does the CTR process apply
here, as the code
is already in our svn repo?


-Donald




-- 
Erik B. Craig 

Re: unsubscribe

[Guillaume Nodet]

You need to send  mail to [EMAIL PROTECTED] instead...

On 9/13/07, Rogan, Henry <[EMAIL PROTECTED]> wrote:
>
>
>
> Regards,
> Henry
> Henry Rogan IT Architecture 972.516.5667
> XO Communications Inc. 2700 Summit, Plano TX 75074
>
>
>
>
>
> -Original Message-
> From: Guillaume Nodet [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 13, 2007 8:53 AM
> To: [EMAIL PROTECTED]
> Subject: Re: question about servicemix 3.1.2 release
>
> ServiceMix 3.1.2 does not depend on camel afaik, only trunk does.And for
> the
> branch, you should try using https instead of http
> (could you fix the release instructions if they are misleading?)
>
> On 9/13/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
> >
> > Hi Guillaume,
> >
> > The release guide say that there should be no snapshot dependency, but
> > servicemix-camel depend on camel 1.1 snapshot, without this snapshot
> > dependency, this service-engine can't get compiled.  How to handle
> this
> > problem?
> > And I failed to do
> > svn mkdir
> >
> http://svn.apache.org/repos/asf/incubator/servicemix/branches/servicemix
> -
> > 3.1.2
> > -m "ServiceMix 3.1.2 Release Branch"
> > The error is
> > svn: MKACTIVITY of
> > '/repos/asf/!svn/act/334b9964-033a-0410-a474-8f0ea706a33b': 403
> > Forbidden (http://svn.apache.org)
> > Any Suggestion is appreciated.
> > Thanks very much
> >
> >
> > Freeman
> >
> > Guillaume Nodet wrote:
> > > I have updated the releasing notes to something that I hope will
> work
> > ;-)
> > > See http://cwiki.apache.org/confluence/display/SM/Release+Guide
> > > If you have any questions, just yell !
> > >
> > > On 9/12/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote:
> > >
> > >> On Sep 12, 2007, at 8:46 AM, Freeman Fang wrote:
> > >>
> > >> Hi all,
> > >>
> > >> When are we going to release servicemix 3.1.2? As a new commiter in
> > >> servicemix team, I'd like to know how is the release process looks
> > like.
> > >> If possible, shall I be release manager of this time?  :-)
> > >>
> > >> Yeah of course you can :-)
> > >> There are some instructions available at
> > >> http://incubator.apache.org/servicemix/release-guide.html
> > >> but these are a bit outdated, so we'll have to update those (and
> maven
> > can
> > >> not really be used for
> > >> creating the release)...
> > >> Let me have a breakfast and write something more accurate...
> > >>
> > >> Any suggestion is appreciated.
> > >>
> > >> Best Regards
> > >>
> > >>
> > >> Freeman
> > >>
> > >>
> > >> --
> > >> Cheers,
> > >> Guillaume Nodet
> > >> 
> > >> Blog: http://gnodet.blogspot.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)

[Donald Woods]

Understand your frustrations, but the Eclipse levels in build.xml have nothing 
to do with the user runtime levels and don't need to be updated unless we want 
to use newer features/APIs in future Eclipse 3.3.x or WTP 2.0.x releases


I think we all have learned now not to depend on the major train releases of 
Eclipse, but to wait for the first maintenance release for any expected plugin 
releases


We also need to continue supporting the prior Eclipse level in future plugin 
updates, for any of our ISV and production users, who can't always upgrade to 
the latest Eclipse levels due to other project requirements or tool 
dependencies



-Donald

Ted Kirby wrote:

Tim and I have been working hard on getting the "Download and Install"
function to work to download a server for the eclipse update site and
install it your machine.  The stablest level on which we have found
this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
lower WTP levels.  Running and debugging the plugin in eclipse has
been tedious and buggy.  I would vote -99 for releasing the plugin on
any level less than WTP2.0.1RC1.  I have been frustrated to not be
able to work on other things because of these issues.  You may well
judge that I am unduly focused on these issues.  I am glad that you
and others have success with the plugin and various enhancements.  I
am certainly disappointed in WTP2.0.x at this point.  What level of
WTP are you using?  The WTP 2.0.1 release schedule is here:
http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
when it comes out, I think we should upgrade our levels and Tim's
build.xml to move to that level.  It unfortunately seems prudent for
us to dig into the eclipse WTP community to make sure the parts we use
work.

Ted Kirby

On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:

Ted,
I see you have updated the version of Web Tools Platform (WTP) to 2.0.1 from
2.0. However on
http://download.eclipse.org/webtools/downloads/ I see that
2.0.1 is not yet released (only RC1 is available). Was it a typo?

- Shiva


On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:

Looks good.  Thanks Tim.
Attached are some minor updates/feedback on your instructions.

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

Start of discussion thread.
--
Thanks,
Tim McConnell










smime.p7s
Description: S/MIME Cryptographic Signature

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

[Shiva Kumar H R]

On 9/13/07, Donald Woods <[EMAIL PROTECTED]> wrote:
>
> Need to be more specific on the Eclipse package that users need, now that
> there are 5 different distros -
>
> > 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> 1 -- Eclipse IDE for Java EE Developers (Europa v3.3 or later)


Oh! there seems to be a confusion here. Please see
http://www.eclipse.org/downloads/moreinfo/compare.php

1) So "Eclipse IDE for Java EE Developers" (125MB) is actually Eclipse
Platform + WTP & it's pre-reqs. Ideally this should have been 'the only'
pre-requisite for Geronimo Eclipse Plug-in (GEP). However we are currently
running into a problem using this (Geronimo v1.0 & v1.2 servers are not
appearing in the list of available servers). Hence we have deferred using
this until next GEP release i.e. 2.1. Please see GERONIMODEVTOOLS-180. I
guess not having another JIRA opened for this problem, is the source of
confusion. I will open a JIRA soon after this.

2) "Eclipse Classic" (140MB) is the one to be listed as the correct
pre-requisite here for GEP 2.0.

- Shiva

Also, by prereqing WTP 2.0.1, I think it requires newer levels of the all
> the
> packages, based on the current prereq levels listed for WTP 2.0.1 RC1 at
> the
> top of the following download page -
>
>
> http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC1-20070907070540/
>
> Which means its targeted to Eclipse 3.3.1 which is supposed to ship by end
> of
> Sept.
>
>
> -Donald
>
> Ted Kirby wrote:
> > Looks good.  Thanks Tim.
> > Attached are some minor updates/feedback on your instructions.
> >
> > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> >> Start of discussion thread.
> >> --
> >> Thanks,
> >> Tim McConnell
> >>
>
>

Re: [DISCUSS] Move J2G from sandbox to devtools

[Matt Hogstrom]

+1 to move it ... I agree with the other comments on lazy consensus.

On Sep 12, 2007, at 10:21 AM, Donald Woods wrote:

Given all of the work and interest in the J2G tool, I would like to  
move the current J2G files from sandbox/j2g to devtools/trunk/j2g,  
so we can start working towards an official release of the tool.


Does this require a Vote first or does the CTR process apply here,  
as the code is already in our svn repo?



-Donald

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

[Shiva Kumar H R (JIRA)]

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.1
Reporter: Shiva Kumar H R
 Fix For: 2.1


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] Commented: (GERONIMODEVTOOLS-204) Change pre-requisite from current "wtp-all-in-one-sdk-* (266MB)" to "Eclipse IDE for Java EE Developers (125MB)"

[Shiva Kumar H R (JIRA)]

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

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

An useful link -> http://www.eclipse.org/downloads/moreinfo/compare.php

> 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.1
>Reporter: Shiva Kumar H R
> Fix For: 2.1
>
>
> 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.

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

[Shiva Kumar H R]

On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
>
>
> On 9/13/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> >
> > Need to be more specific on the Eclipse package that users need, now
> > that
> > there are 5 different distros -
> >
> > > 1 -- Europa (also known as Eclipse 3.3), which is platform specific
> > 1 -- Eclipse IDE for Java EE Developers (Europa v3.3 or later)
>
>
> Oh! there seems to be a confusion here. Please see
> http://www.eclipse.org/downloads/moreinfo/compare.php
>
> 1) So "Eclipse IDE for Java EE Developers" (125MB) is actually Eclipse
> Platform + WTP & it's pre-reqs. Ideally this should have been 'the only'
> pre-requisite for Geronimo Eclipse Plug-in (GEP). However we are currently
> running into a problem using this (Geronimo v1.0 & v1.2 servers are not
> appearing in the list of available servers). Hence we have deferred using
> this until next GEP release i.e. 2.1. Please see GERONIMODEVTOOLS-180. I
> guess not having another JIRA opened for this problem, is the source of
> confusion. I will open a JIRA soon after this.
>

GERONIMODEVTOOLS-204 opened for this.

2) "Eclipse Classic" (140MB) is the one to be listed as the correct
> pre-requisite here for GEP 2.0.
>
> - Shiva
>
> Also, by prereqing WTP 2.0.1, I think it requires newer levels of the all
> > the
> > packages, based on the current prereq levels listed for WTP 2.0.1 RC1 at
> > the
> > top of the following download page -
> >
> >
> > http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC1-20070907070540/
> >
> > Which means its targeted to Eclipse 3.3.1 which is supposed to ship by
> > end of
> > Sept.
> >
> >
> > -Donald
> >
> > Ted Kirby wrote:
> > > Looks good.  Thanks Tim.
> > > Attached are some minor updates/feedback on your instructions.
> > >
> > > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > >> Start of discussion thread.
> > >> --
> > >> Thanks,
> > >> Tim McConnell
> > >>
> >
> >
>

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

[Donald Woods]

Thanks for the clarification.  Guess if users only wanted Geronimo 2.0 server 
support, then they could use the intended "for Java EE Developers" package, as 
that has been working for me, but I've only been testing against a 2.0.1 
server


-Donald

Shiva Kumar H R wrote:


On 9/13/07, *Donald Woods* <[EMAIL PROTECTED] 
> wrote:


Need to be more specific on the Eclipse package that users need, now
that
there are 5 different distros -

 > 1 -- Europa (also known as Eclipse 3.3), which is platform specific
1 -- Eclipse IDE for Java EE Developers (Europa v3.3 or later)


Oh! there seems to be a confusion here. Please see 
http://www.eclipse.org/downloads/moreinfo/compare.php


1) So "Eclipse IDE for Java EE Developers" (125MB) is actually Eclipse 
Platform + WTP & it's pre-reqs. Ideally this should have been 'the only' 
pre-requisite for Geronimo Eclipse Plug-in (GEP). However we are 
currently running into a problem using this (Geronimo v1.0 & v1.2 
servers are not appearing in the list of available servers). Hence we 
have deferred using this until next GEP release i.e. 2.1. Please see 
GERONIMODEVTOOLS-180. I guess not having another JIRA opened for this 
problem, is the source of confusion. I will open a JIRA soon after this.


2) "Eclipse Classic" (140MB) is the one to be listed as the correct 
pre-requisite here for GEP 2.0.


- Shiva

Also, by prereqing WTP 2.0.1, I think it requires newer levels of
the all the
packages, based on the current prereq levels listed for WTP 2.0.1
RC1 at the
top of the following download page -


http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC1-20070907070540/

Which means its targeted to Eclipse 3.3.1 which is supposed to ship
by end of
Sept.


-Donald

Ted Kirby wrote:
 > Looks good.  Thanks Tim.
 > Attached are some minor updates/feedback on your instructions.
 >
 > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]
> wrote:
 >> Start of discussion thread.
 >> --
 >> Thanks,
 >> Tim McConnell
 >>




smime.p7s
Description: S/MIME Cryptographic Signature

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

[Donald Woods]

Or use the WTP 2.0.1 All-in-one bundle when its released, as it should include 
the Eclipse SDK "Classic" bundle as the WTP 2.0 all-in-one bundle included.


-Donald

Donald Woods wrote:
Thanks for the clarification.  Guess if users only wanted Geronimo 2.0 
server support, then they could use the intended "for Java EE 
Developers" package, as that has been working for me, but I've only been 
testing against a 2.0.1 server


-Donald

Shiva Kumar H R wrote:


On 9/13/07, *Donald Woods* <[EMAIL PROTECTED] 
> wrote:


Need to be more specific on the Eclipse package that users need, now
that
there are 5 different distros -

 > 1 -- Europa (also known as Eclipse 3.3), which is platform 
specific

1 -- Eclipse IDE for Java EE Developers (Europa v3.3 or later)


Oh! there seems to be a confusion here. Please see 
http://www.eclipse.org/downloads/moreinfo/compare.php


1) So "Eclipse IDE for Java EE Developers" (125MB) is actually Eclipse 
Platform + WTP & it's pre-reqs. Ideally this should have been 'the 
only' pre-requisite for Geronimo Eclipse Plug-in (GEP). However we are 
currently running into a problem using this (Geronimo v1.0 & v1.2 
servers are not appearing in the list of available servers). Hence we 
have deferred using this until next GEP release i.e. 2.1. Please see 
GERONIMODEVTOOLS-180. I guess not having another JIRA opened for this 
problem, is the source of confusion. I will open a JIRA soon after this.


2) "Eclipse Classic" (140MB) is the one to be listed as the correct 
pre-requisite here for GEP 2.0.


- Shiva

Also, by prereqing WTP 2.0.1, I think it requires newer levels of
the all the
packages, based on the current prereq levels listed for WTP 2.0.1
RC1 at the
top of the following download page -


http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.1RC1-20070907070540/ 



Which means its targeted to Eclipse 3.3.1 which is supposed to ship
by end of
Sept.


-Donald

Ted Kirby wrote:
 > Looks good.  Thanks Tim.
 > Attached are some minor updates/feedback on your instructions.
 >
 > On 9/12/07, Tim McConnell <[EMAIL PROTECTED]
> wrote:
 >> Start of discussion thread.
 >> --
 >> Thanks,
 >> Tim McConnell
 >>




smime.p7s
Description: S/MIME Cryptographic Signature

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

[Tim McConnell]

Great, thanks Ted

Ted Kirby wrote:

Looks good.  Thanks Tim.
Attached are some minor updates/feedback on your instructions.

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

Start of discussion thread.
--
Thanks,
Tim McConnell



--
Thanks,
Tim McConnell

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

[Shiva Kumar H R]

Oh! wasn't aware of those problems. Hadn't tried "Download and Install",
rather was directly unzipping the *deployable.zip. And everything worked
fine even with WTP 2.0 (wtp-all-in-one-sdk-win32).

Good that we have discovered "Download and Install" doesn't work with WTP
2.0 and only works with WTP 2.0.1RC1.

Thanks Donald for hinting that we don't need to update build.xml and rebuild
GEP.

I will re-test
http://people.apache.org/~mcconne/releases/RC2/g-eclipse-plugin-2.0.0-deployable-RC2.zipusing
WTP
2.0.1RC1 and post my results.

- Shiva

On 9/13/07, Donald Woods <[EMAIL PROTECTED]> wrote:
>
> Understand your frustrations, but the Eclipse levels in build.xml have
> nothing
> to do with the user runtime levels and don't need to be updated unless we
> want
> to use newer features/APIs in future Eclipse 3.3.x or WTP 2.0.xreleases
>
> I think we all have learned now not to depend on the major train releases
> of
> Eclipse, but to wait for the first maintenance release for any expected
> plugin
> releases
>
> We also need to continue supporting the prior Eclipse level in future
> plugin
> updates, for any of our ISV and production users, who can't always upgrade
> to
> the latest Eclipse levels due to other project requirements or tool
> dependencies
>
>
> -Donald
>
> Ted Kirby wrote:
> > Tim and I have been working hard on getting the "Download and Install"
> > function to work to download a server for the eclipse update site and
> > install it your machine.  The stablest level on which we have found
> > this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
> > lower WTP levels.  Running and debugging the plugin in eclipse has
> > been tedious and buggy.  I would vote -99 for releasing the plugin on
> > any level less than WTP2.0.1RC1.  I have been frustrated to not be
> > able to work on other things because of these issues.  You may well
> > judge that I am unduly focused on these issues.  I am glad that you
> > and others have success with the plugin and various enhancements.  I
> > am certainly disappointed in WTP2.0.x at this point.  What level of
> > WTP are you using?  The WTP 2.0.1 release schedule is here:
> > http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
> > 9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
> > with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
> > when it comes out, I think we should upgrade our levels and Tim's
> > build.xml to move to that level.  It unfortunately seems prudent for
> > us to dig into the eclipse WTP community to make sure the parts we use
> > work.
> >
> > Ted Kirby
> >
> > On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
> >> Ted,
> >> I see you have updated the version of Web Tools Platform (WTP) to 2.0.1from
> >> 2.0. However on
> >> http://download.eclipse.org/webtools/downloads/ I see that
> >> 2.0.1 is not yet released (only RC1 is available). Was it a typo?
> >>
> >> - Shiva
> >>
> >>
> >> On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:
> >>> Looks good.  Thanks Tim.
> >>> Attached are some minor updates/feedback on your instructions.
> >>>
> >>> On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
>  Start of discussion thread.
>  --
>  Thanks,
>  Tim McConnell
> 
> >>>
> >>
> >
> >
>
>

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

[Tim McConnell]

Thanks for the reminder Anita, The project site and the accompanying release 
notes will be updated as soon as the release candidate is approved. I've also 
updated the Release Process steps (URL below) to include this step just so we 
don't forget. Thanks


http://cwiki.apache.org/GMOxPMGT/release-eclipse-plugin-process.html)


Anita Kulshreshtha wrote:

   I would like to see download links to the following items on the
project site at http://geronimo.apache.org/development-tools.html under
prerequisites section.


1 -- Europa (also known as Eclipse 3.3), which is platform specific
2 -- Web Tools Platform (WTP) 2.0.1
3 -- Data Tools Platform (DTP) 1.5
4 -- Eclipse Modeling Framework (EMF) 2.3
5 -- Graphical Editing Framework (GEF) 3.3


   
Thanks

Anita


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

Start of discussion thread.
--
Thanks,
Tim McConnell




===  Step #1 -- Install prerequisites
   ===





The Geronimo Eclipse Plugin 2.0.0 has a number of prerequisites that
must be 
installed prior to the installation of the plugin itself. These are
necessary 
to establish the proper Eclipse installation. They are:


1 -- Europa (also known as Eclipse 3.3), which is platform specific
2 -- Web Tools Platform (WTP) 2.0.1
3 -- Data Tools Platform (DTP) 1.5
4 -- Eclipse Modeling Framework (EMF) 2.3
5 -- Graphical Editing Framework (GEF) 3.3

You can manually download the latest versions of these artifacts but
it is 
somewhat cumbersome. Instead I've created an ant script (that is
based on 
the one used to build the plugin) that you can use that will download
and unzip 
everything for you. You can get it from here:


http://people.apache.org/~mcconne/releases/RC2/build.xml

After you download it somewhere (preferably in a temp subdirectory)
you can just 
invoke it for your specific platform using one of these three

commands:


ant win32
ant linux
ant macos
It will create an /org/EUROPA/eclipse/3.3 subdirectory with all the 
downloaded artifacts and an /EUROPA/eclipse subdirectory where
everything has 
been unzipped. This is now the Eclipse installation directly you
should use to 
test the Geronimo Eclipse 2.0.0 plugin. 


If you don't wish to use the ant script it's very important to ensure
you have
the latest versions of each -- otherwise the plugin will not function
correctly. 
For example, the WTP 2.0.0 release is fairly old and buggy, and our

plugin will
not function correctly. That is why this ant script downloads and
installs the 
WTP 2.0.1 RC1 artifacts. 



Now that you have all the prerequisites you can do either of the two
scenarios
below since each must work and both should emulate how it will be
installed and 
used in the real world.  Scenarios #1 and #2 are mutually exclusive
though -- 
do one or the other but not both unless you first delete and recreate

your
Eclipse installation directory (preferably with the ant script
above). 





===  Scenario #1 -- Upzip everything 
   ===





You can just download the plugin itself and unzip it into the same
directory
where all the prereqs were installed (e.g., EUROPA/eclipse). If you
choose 
this option you must have an installed version of the Geronimo 2.0.1
server 
somewhere on your system so that you can define an Geronimo Server 
configuration. If you've never done this before the steps are fairly 
straightforward:


1 -- Download the plugin and unzip into your EUROPA/eclipse
directory.
 You can download the plugin from here: 




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

2 -- Invoke the eclipse executable from your EUROPA/eclipse
directory. Select or
 accept the default workspace. 


3 -- Open the Java EE perspective. From within Eclipse:

 a. Close the Welcome tab

 b. Select Window --> Open Perspective --> Other --> Java EE
You should now be in the Java EE perspective. You can see the
open 
perspective tabs in the upper right-hand corner of your
Eclipse  
workspace.


4 -- Define a new server. From Eclipse select:

 a. File --> New --> Other --> Server --> Server --> Next -->
Apache. 
At this point you must see the Apache Geronimo v2.0 Server

selection
or the plugin was not installed/unzipped correctly. 


 b. Select "Apache Geronimo v2.0 Server" --> Next --> then enter
the root 
directory of your Geronimo server installation --> Next -->
Next --> 
Next --> Finish


 c. Now in the Java EE perspective you should see the Apache
Geronimo v2.0 
server (bottom pane, middle tab usually) that you can now
start in 
 

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

[Tim McConnell (JIRA)]

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.x
Reporter: Tim McConnell
 Fix For: 2.0.x


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.

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

[Tim McConnell]

Hi Jacek, yes that's a very good idea. To be honest, I'm not sure why Sachin 
called it "g-eclipse-plugin". But as Shiva has suggested I've opened a JIRA to 
include it in the next release


https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-205


Jacek Laskowski wrote:

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

Start of discussion thread.


Hi Tim,

I'm pretty sure I asked about it (or was about to have asked, but
failed), but why is the plugin called g-eclipse-plugin? Wouldn't it be
better off if it called geronimo-eclipse-plugin? It doesn't say much
when I have g-eclipse-plugin in my eclipse plugin repository and in
discussions people tend to use geronimo-eclipse-plugin even though it
may seem to be easier to say g-eclipse-plugin and following the
plugin's name. It can be confusing.

I think I should've noted it sooner and I do appologize to talk about
it now right before the plugin is to be released and am leaning
towards -1 because of the name (I don't want to be disruptive to the
process, so just a friendly reminder I should not do that do the trick
just fine ;-))

Jacek



--
Thanks,
Tim McConnell

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

[Tim McConnell (JIRA)]

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

Tim McConnell reassigned GERONIMODEVTOOLS-205:
--

Assignee: Tim McConnell

> 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.x
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.0.x
>
>
> 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.

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

[Tim McConnell]

Huge sigh of relief !! Thanks Anita

Anita Kulshreshtha wrote:

FWIW, I followed the "Use Staging Site" instructions and used update
manager's staging_site to download tomcat version on windows. The
server and the admin console started fine. I got download urls for
various parts from ant build file at
http://people.apache.org/~mcconne/releases/RC2/build.xml
   


Thanks
Anita
 
--- Ted Kirby <[EMAIL PROTECTED]> wrote:



Tim and I have been working hard on getting the "Download and
Install"
function to work to download a server for the eclipse update site and
install it your machine.  The stablest level on which we have found
this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
lower WTP levels.  Running and debugging the plugin in eclipse has
been tedious and buggy.  I would vote -99 for releasing the plugin on
any level less than WTP2.0.1RC1.  I have been frustrated to not be
able to work on other things because of these issues.  You may well
judge that I am unduly focused on these issues.  I am glad that you
and others have success with the plugin and various enhancements.  I
am certainly disappointed in WTP2.0.x at this point.  What level of
WTP are you using?  The WTP 2.0.1 release schedule is here:
http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
when it comes out, I think we should upgrade our levels and Tim's
build.xml to move to that level.  It unfortunately seems prudent for
us to dig into the eclipse WTP community to make sure the parts we
use
work.

Ted Kirby

On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:

Ted,
I see you have updated the version of Web Tools Platform (WTP) to

2.0.1 from

2.0. However on
http://download.eclipse.org/webtools/downloads/ I see that
2.0.1 is not yet released (only RC1 is available). Was it a typo?

- Shiva


On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:

Looks good.  Thanks Tim.
Attached are some minor updates/feedback on your instructions.

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

Start of discussion thread.
--
Thanks,
Tim McConnell









  

Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, 
and more!
http://tv.yahoo.com/collections/3658 



--
Thanks,
Tim McConnell

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

[Ted Kirby]

As to my frustrations, I was asked! :-)

Yes, that is a good point you raise about the distinction between
build level and user run level.  I view it, however, as a beneficial
short-term tactic, until WTP.2.0.1 GAs, but not a beneficial long term
strategy or approach.

I think Tim provided great service and innovation by giving us
build.xml to download all the required eclipse bits.  I think it makes
great sense to allow the user to use it to download eclipse at the
same level as the build, so users could easily get the supported
level.  This is also well documented in the instructions at
http://people.apache.org/~mcconne/releases/RC2/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC2.txt.

All things considered, I think it's a good thing to build and have
users run with the same level of eclipse.

Ted Kirby

On 9/13/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> Understand your frustrations, but the Eclipse levels in build.xml have nothing
> to do with the user runtime levels and don't need to be updated unless we want
> to use newer features/APIs in future Eclipse 3.3.x or WTP 2.0.x releases
>
> I think we all have learned now not to depend on the major train releases of
> Eclipse, but to wait for the first maintenance release for any expected plugin
> releases
>
> We also need to continue supporting the prior Eclipse level in future plugin
> updates, for any of our ISV and production users, who can't always upgrade to
> the latest Eclipse levels due to other project requirements or tool
> dependencies
>
>
> -Donald
>
> Ted Kirby wrote:
> > Tim and I have been working hard on getting the "Download and Install"
> > function to work to download a server for the eclipse update site and
> > install it your machine.  The stablest level on which we have found
> > this to work is WTP2.0.1RC1.  Other minor issues/problems occur at
> > lower WTP levels.  Running and debugging the plugin in eclipse has
> > been tedious and buggy.  I would vote -99 for releasing the plugin on
> > any level less than WTP2.0.1RC1.  I have been frustrated to not be
> > able to work on other things because of these issues.  You may well
> > judge that I am unduly focused on these issues.  I am glad that you
> > and others have success with the plugin and various enhancements.  I
> > am certainly disappointed in WTP2.0.x at this point.  What level of
> > WTP are you using?  The WTP 2.0.1 release schedule is here:
> > http://wiki.eclipse.org/WTP_Release_2.0.1_Schedule, and calls for a
> > 9/28 GA.  I am good with an Apache Geronimo Eclipse plugin GA running
> > with WTP2.0.1RC1.  Assuming WTP2.0.1 GA works as well as this one,
> > when it comes out, I think we should upgrade our levels and Tim's
> > build.xml to move to that level.  It unfortunately seems prudent for
> > us to dig into the eclipse WTP community to make sure the parts we use
> > work.
> >
> > Ted Kirby
> >
> > On 9/13/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
> >> Ted,
> >> I see you have updated the version of Web Tools Platform (WTP) to 2.0.1 
> >> from
> >> 2.0. However on
> >> http://download.eclipse.org/webtools/downloads/ I see that
> >> 2.0.1 is not yet released (only RC1 is available). Was it a typo?
> >>
> >> - Shiva
> >>
> >>
> >> On 9/13/07, Ted Kirby <[EMAIL PROTECTED] > wrote:
> >>> Looks good.  Thanks Tim.
> >>> Attached are some minor updates/feedback on your instructions.
> >>>
> >>> On 9/12/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
>  Start of discussion thread.
>  --
>  Thanks,
>  Tim McConnell
> 
> >>>
> >>
> >
> >
>
>

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

[Kevan Miller]

On Sep 13, 2007, at 3:17 AM, Jason Dillon wrote:

I'm converting all of the assemblies tonight, should be done in  
another hour or so.


But, currently server/trunk is not building due to:


[INFO] Compiling 18 source files to /Users/jason/ws/geronimo/server/ 
modules/geronimo-openejb/target/classes
[INFO]  
-- 
--

[ERROR] BUILD FAILURE
[INFO]  
-- 
--

[INFO] Compilation failure

/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[131,30]  
cannot find symbol

symbol  : variable service
location: class  
org.apache.openejb.assembler.classic.TransactionServiceInfo


/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[139,27]  
cannot find symbol

symbol  : variable service
location: class  
org.apache.openejb.assembler.classic.SecurityServiceInfo


/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[145,24]  
cannot find symbol

symbol  : variable service
location: class org.apache.openejb.assembler.classic.ProxyFactoryInfo


So, I can't verify that everything is super happy...


I've deployed a new version of OpenEJB 3.0 snapshots. So, verify  
away... :-)


You may need to delete old versions of OpenEJB snapshots from your  
maven repo (depending on when you built last...).


--kevan

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

[Viet Hung Nguyen (JIRA)]

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: console
Affects Versions: 2.0.1, 2.1, Verification Required
 Environment: windows xp
Reporter: Viet Hung Nguyen


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] Updated: (GERONIMO-3472) web server portlet does not save modifications to connectors correctly.

[Viet Hung Nguyen (JIRA)]

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

Viet Hung Nguyen updated GERONIMO-3472:
---

Attachment: geronimo-3472.patch

this fixes the HTTP connector fully. However, the SSL and AJP connectors (or 
maybe it's just the portlets) are having trouble saving/retrieving the 
"bufferSizeBytes" attribute. On any instance of a restart (connector or the 
server) the bufferSizeBytes gets reset. The config.xml shows the correct values 
though.

> 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: console
>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.

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

[Lin Sun]

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?


Lin


Tim McConnell wrote:

Start of discussion thread.

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

[Ted Kirby]

On 9/13/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?

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

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

[Jason Dillon]

Aighty, thanks Kevan, she builds for me now.  Going to run through  
some tests now to see if I've broken anything...


--jason


On Sep 13, 2007, at 10:27 AM, Kevan Miller wrote:



On Sep 13, 2007, at 3:17 AM, Jason Dillon wrote:

I'm converting all of the assemblies tonight, should be done in  
another hour or so.


But, currently server/trunk is not building due to:


[INFO] Compiling 18 source files to /Users/jason/ws/geronimo/ 
server/modules/geronimo-openejb/target/classes
[INFO]  
- 
---

[ERROR] BUILD FAILURE
[INFO]  
- 
---

[INFO] Compilation failure

/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[131,30]  
cannot find symbol

symbol  : variable service
location: class  
org.apache.openejb.assembler.classic.TransactionServiceInfo


/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[139,27]  
cannot find symbol

symbol  : variable service
location: class  
org.apache.openejb.assembler.classic.SecurityServiceInfo


/Users/jason/ws/geronimo/server/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[145,24]  
cannot find symbol

symbol  : variable service
location: class org.apache.openejb.assembler.classic.ProxyFactoryInfo


So, I can't verify that everything is super happy...


I've deployed a new version of OpenEJB 3.0 snapshots. So, verify  
away... :-)


You may need to delete old versions of OpenEJB snapshots from your  
maven repo (depending on when you built last...).


--kevan

Re: svn commit: r574770 - in /geronimo/devtools/eclipse-plugin/branches/2.0.0: ./ plugins/org.apache.geronimo.deployment.model.edit/ plugins/org.apache.geronimo.deployment.model/ plugins/org.apache.ge

[Kevan Miller]

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)

[Tim McConnell]

Hi Lin,

1) yes that is actually the last step in our "Release Eclipse Plugin Process" 
(i.e., to ensure that the server and/or plugin can be downloaded from Eclipse 
without having to add a new "Remote Site" from the Eclipse Help panels). 
Unfortunately, this is not a scenario that can be emulated with our "Staging 
site" so I didn't bother to list it.


2) I haven't noticed this but I don't know that I've actually deployed and run a 
"Hello World" project. I'll investigate though.


Thanks

Lin Sun 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?


Lin


Tim McConnell wrote:

Start of discussion thread.





--
Thanks,
Tim McConnell

[jira] Created: (GERONIMODEVTOOLS-206) Error while deploying EAR to running server Geronimo 2.0.1

[Tomasz Mazan (JIRA)]

Error while deploying EAR to running server Geronimo 2.0.1
--

 Key: GERONIMODEVTOOLS-206
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0
 Environment: Geronimo 2.0.1
WTP 2.0 + GEP 2.0
Reporter: Tomasz Mazan


Exception on deploy

Distribution of configuration failed.  See log for details.
  java.io.FileNotFoundException: 
C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip
 (File not found)
  org.apache.geronimo.common.DeploymentException: 
java.io.FileNotFoundException: 
C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip
 (File not found)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:121)
at 
org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865)
at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
at 
org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865)
at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at 
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
at 
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at 
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at 
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at 
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at java.security.AccessController.doPrivileged(Native Method)
at 
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at 
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source)
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)
  Caused by: java.io.FileNotFoundException: 
C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip
 (File not found)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at 
org.apache.geronimo.deployment.util.DeploymentUtil.copyFile(DeploymentUtil.java:92)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:118)
... 34 more


-- 
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: ./ plugins/org.apache.geronimo.deployment.model.edit/ plugins/org.apache.geronimo.deployment.model/ plugins/org.apache.ge

[Tim McConnell]

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

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

[Tim McConnell (JIRA)]

Update the license in the feature.properties file for each of the feature 
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] Updated: (GERONIMODEVTOOLS-207) Update the license in the feature.properties file for each of the features provided by the plugin

[Tim McConnell (JIRA)]

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

Tim McConnell updated GERONIMODEVTOOLS-207:
---

Summary: Update the license in the feature.properties file for each of the 
features provided by the plugin  (was: Update the license in the 
feature.properties file for each of the feature provided by the plugin)

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

Re: [Discuss] What next?

[Kevan Miller]

Apologies for such a late response. This thread came out while I was  
on vacation and got buried by a lot of other things...


This is a good list. Comments, below.

On Aug 30, 2007, at 8:12 PM, David Jencks wrote:

Getting 2.0.1 out the door was a great step and now might be a good  
time to start discussing where we want geronimo to head next.  Here  
are some ideas I've had or think are important.  If I were to try  
to write actual sentences about all of this I'd probably never send  
the email so this is way too fragmentary but maybe can spark more  
discussion.  I'm hoping everyone will chime in with their interests  
and viewpoints, this is just what I've been thinking about lately.


Modularity.

For a long time we've been on the brink of having an actually  
modular server, not just a conceptually modular server. As  
reflected in a lot of recent discussion on the dev list, I think we  
are so close we should really work hard to make this a pleasant  
reality.  Some of the steps I see:
- enhance the plugin framework so bits of more config files can be  
added, in particular artifact_aliases.properties and  
config_substitutions.properties.  IIUC Paul has some schema changes  
and xml handling rewrites in the wings as well
- finish up the pluggable admin console work and actually split the  
admin console into appropriate bits for the plugins

- rearrange the build so it is organized by plugin
- actually assemble the servers we ship using plugins, perhaps  
using gshell scripts
- have more server-building tools.  For instance, a "button" to  
push that spits out a server with just what is needed for a set of  
apps and nothing else.


I wouldn't go so far as saying G is a "conceptually modular server",  
but would agree that the modularity can be a lot more user-friendly.  
And would like to see us building our server assemblies from plugin  
parts. Sounds like you've been making some good progress on this path.


One caveat -- I would not want our Java EE servers (or other assembly  
flavors) to become harder to use. One concern I have is ending up  
with a bunch of differently versioned server plugins that we have a  
hard time managing... I'd really like us to keep a critical eye on  
ease-of-use...




Clustering

IIUC we have a lot of partial  clustering solutions.  For instance  
there's WADI, native tomcat clustering, a terracotta integration,  
and IIUC Jeff has been working on a clustering solution (my  
apologies if I left any out).  I'd like to know where these efforts  
are in terms of actual functionality and reliability and what they  
can be extended to do.  We also need some kind of cluster admin tools.


Security
jaspi
triplesec
administration
beyond javaee security for jetspeed and roller
There are some good things about javaee security such as the idea  
of using Permissions and evaluating them in a policy but there are  
also a lot of limitations and problems such as no support for  
restricting access to user generated content that didn't exist when  
the security was originally configured.  At least roller and  
jetspeed have run into this problem.  I think triplesec may provide  
a fairly generic solution and it might be interesting to see if  
other projects are interested in this.


Other apps
roller
jetspeed
proximity etc
It would be great to get "all popular apps" available as geronimo  
plugins.


Management and troubleshooting
ARM
"trace on error" facility.  Have a list of info that each component  
can add to as the request moves through the system.  If there's an  
error, we can show the entire path taken with all data.  Otherwise  
we discared it.

server farm management (gshell?)


As Jason D has mentioned (and I really, really agree with him), we  
need to address logging. We need to create a logging policy and need  
to start addressing this in a consistent and rigorous manner...




Transaction manager
implement a "do work in a new tx" interface, hook it up to  
openjpa.  IIUC IBM has proposed an interface that lets server  
pieces submit work to be done in a new transaction, thus  
eliminating the need to deal with suspend etc yourself.  There's  
been some discussion on the openjpa lists, and we should definitely  
do this.  There may be more commonj work to do also, but I've more  
or less lost track of that project.

make sure recovery actually works

Core
Better Spring application management


I think our basic issues have been resolved... But there are some  
follow on improvements that should be implemented   
for children, a separate Spring module, etc.


Investigate OSGI and figure out how it is different from what we  
are doing, what it can do better, and what is missing from it.   
Figure out an integration strategy whether it be "run OSGI as an  
application" or "replace the kernel with OSGI"  Don't break stuff  
if we start using OSGI more :-)


I have yet to see what I'd call a compelling argument for moving our  
kernel to an OSGI base. I can see

Re: Problem with referencing to beans from other ejb-jars

[Kevan Miller]

I thought I'd take the opportunity to send some love David B's way...  
I think it's great the way he's been addressing these user questions  
and documenting in the Wiki.


I hope we can get this stuff organized so that users can find this  
information in a reasonable manner...


--kevan

On Sep 13, 2007, at 3:54 PM, David Blevins wrote:


Hi Tomasz,

I created a doc for you that describes the missing parts.

  http://cwiki.apache.org/OPENEJB/ejb-refs.html

Keep what you have with the openejb-jar and add the parts described  
in this to your ejb-jar.xml.


Unfortunately, while looking into this I discovered that our code  
for overriding an @EJB annotation with an  in the xml is  
not implemented, thus if you have @EJB and the corresponding ref> as described in the first section of the document, you'll end  
up with two refs and not one as you should.


We'll get this fixed asap, but until then follow the technique  
described in the second part of the doc and in the next version of  
Geronimo you'll be able to delete some of that xml and readd the  
@EJB annotation.


-David



On Sep 13, 2007, at 6:58 AM, Tomasz Mazan wrote:



Hello

I got deployed module A (JAR) and application B (EAR).

A) Contains stateless bean

@Stateless(name = "JmsDispatcherGate")
public class JmsDispatcherGateImpl implements DispatcherGateLocal,
DispatcherGateRemote {

and - of course - necessary interfaces.

ejb-jar.xml does'nt contain interesting content,
openejb-jar.xml contains module description

  myejbmodule
  Dispatcher
  1.0
  jar


B) Application contains two ejb-jars with beans

geronimo-application.xml contains


myejbmodule
Dispatcher
1.0
jar



and one of B-module has openejb-jar.xml with similar dependencie's
definition.
Bean in B-module references to bean from A (EJB) using code below:

@EJB(name = "JmsDispatcherGate")
private DispatcherGateLocal dispatcherGate;

Problem occurs on deploying B-application (EAR) while A (EJB) is  
correctly
deployed and Geronimo Console JNDI Viewer show JmsDispatcherGate  
bean. I

tried to use Remote interface - with no special difference.

Exception stacktrace:
15:31:18,812 FATAL [startup] Cannot find bean "JmsDispatcherGate"  
referenced

by bean "CoreManagerLocal".
15:31:18,812 ERROR [Deployer] Deployment failed due to
org.apache.geronimo.common.DeploymentException:
org.apache.openejb.OpenEJBException: Cannot find bean  
"JmsDispatcherGate"

referenced by bean "CoreManagerLocal".
at
org.apache.geronimo.openejb.deployment.EjbModuleBuilder.getEjbJarInfo 
(EjbModuleBuilder.java:530)

at
org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext 
(EjbModuleBuilder.java:437)

at
org.apache.geronimo.openejb.deployment.EjbModuleBuilder$ 
$FastClassByCGLIB$$cd80af20.invoke()

at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke 
(FastMethodInvoker.java:38)

at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke 
(GBeanOperation.java:124)

at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke 
(GBeanInstance.java:830)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke 
(RawInvoker.java:57)

at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke 
(RawOperationInvoker.java:35)

at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept 
(ProxyMethodInterceptor.java:96)

at
org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$ 
$dc485bed.initContext()

at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfigurati 
on(EARConfigBuilder.java:576)

at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder$ 
$FastClassByCGLIB$$38e56ec6.invoke()

at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke 
(FastMethodInvoker.java:38)

at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke 
(GBeanOperation.java:124)

at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke 
(GBeanInstance.java:830)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke 
(RawInvoker.java:57)

at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke 
(RawOperationInvoker.java:35)

at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept 
(ProxyMethodInterceptor.java:96)

at
org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$ 
$EnhancerByCGLIB$$1375d602.buildConfiguration()

at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:304)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:126)
at
org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$ 
$734a235d.invoke()

at net.sf.cglib.reflect.FastMethod.inv

[jira] Updated: (GERONIMO-3466) car-maven-plugin can not generate server plugin which includes EJB

[YunFeng Ma (JIRA)]

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

YunFeng Ma updated GERONIMO-3466:
-

Attachment: calculator-stateless-ear.zip

I attached a sample which can show the same error in the car maven plugin trunk 
version.

1. Unzip calculator-stateless-ear.zip to %Geronimo_Source%\configs
2. cd %Geronimo_Source%\configs\calculator-stateless-ear
3. mvn install

Then car maven plugin will failed to start openejb configuration.


> car-maven-plugin can not generate server plugin which includes EJB
> --
>
> Key: GERONIMO-3466
> URL: https://issues.apache.org/jira/browse/GERONIMO-3466
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: car-maven-plugin
>Affects Versions: 2.0.1
>Reporter: YunFeng Ma
> Fix For: 2.0.x
>
> Attachments: calculator-stateless-ear.zip
>
>
> openejb-deployer configuration depends on openejb configuration, and openejb 
> configuration depends on j2ee-server configuration. That means 
> car-maven-plugin has to start all the depended configurations, not only the 
> openejb-deployer configuration. This caused the following error.
> {code}
> [INFO] Scanning for projects...
> [INFO] 
> -
> ---
> [INFO] Building daytrader-derby-tomcat
> [INFO]task-segment: [install]
> [INFO] 
> -
> ---
> [INFO] [dependency:unpack {execution: unpack-distribution}]
> [INFO] Configured Artifact: 
> org.apache.geronimo.daytrader:daytrader-ear:2.0:ear
> [INFO] daytrader-ear-2.0.ear already unpacked.
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [car:prepare-plan]
> [INFO] Generated: 
> F:\WASCE\samples_v2\plugins\daytrader-derby-tomcat\target\plan
> \plan.xml
> log4j:WARN No appenders could be found for logger 
> (org.codehaus.mojo.pluginsuppo
> rt.logging.Logging).
> log4j:WARN Please initialize the log4j system properly.
> [INFO] [car:package]
> [INFO] Packaging module configuration: 
> F:\WASCE\samples_v2\plugins\daytrader-der
> by-tomcat\target\plan\plan.xml
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] start of org.apache.geronimo.configs/openejb-deployer/2.0.1/car failed
> Configuration org.apache.geronimo.configs/j2ee-system/2.0.1/car failed to 
> start
> due to the following reasons:
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=GBean,name=ServerInfo did not start because Could not determine 
> geronimo
> installation directory
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=Repository,name=Repository did not start because 
> org.apache.geronimo.conf
> igs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/
> 2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ConfigurationStore,name=Local did not start because 
> org.apache.geronimo.c
> onfigs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-syst
> em/2.0.1/car,j2eeType=Repository,name=Repository did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=AttributeStore,name=AttributeManager did not start because 
> org.apache.ger
> onimo.configs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2
> ee-system/2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ArtifactResolver,name=ArtifactResolver did not start because 
> org.apache.g
> eronimo.configs/j2ee-system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/
> j2ee-system/2.0.1/car,j2eeType=GBean,name=ServerInfo did not start.
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=ConfigurationManager,name=ConfigurationManager did not start because 
> the
> following dependent services did not start: 
> [org.apache.geronimo.configs/j2ee-sy
> stem/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j
> 2eeType=ArtifactResolver,name=ArtifactResolver, 
> org.apache.geronimo.configs/j2ee
> -system/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/ca
> r,j2eeType=AttributeStore,name=AttributeManager]
>   The service 
> ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0.1/car,j2
> eeType=SystemLog,name=Logger did not start because 
> org.apache.geronimo

[jira] Updated: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown

[Freeman Fang (JIRA)]

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

Freeman Fang updated SM-998:


Affects Version/s: (was: 3.1.2)
   3.2
Fix Version/s: (was: 3.1.2)
   3.2

> In-Out Exchanges in a JMS queue cannot be successfully processed after a 
> crash/shutdown
> ---
>
> Key: SM-998
> URL: https://issues.apache.org/activemq/browse/SM-998
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jms
>Affects Versions: 3.2
> Environment: any
>Reporter: Sam Gerstein
> Fix For: 3.2
>
> Attachments: servicemix-jms_patch.txt
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Because a temporary queue is used for the reply-to destination and the 
> Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS 
> queue cannot be returned to their sender after a crash or shutdown of 
> ServiceMix.

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

[jira] Updated: (SM-984) Two exchanges with the same dynamic endpoint processed at the same lead to an exception

[Freeman Fang (JIRA)]

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

Freeman Fang updated SM-984:


Fix Version/s: (was: 3.1.2)

> Two exchanges with the same dynamic endpoint  processed at the same lead to 
> an exception
> 
>
> Key: SM-984
> URL: https://issues.apache.org/activemq/browse/SM-984
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-common
>Affects Versions: 3.1
>Reporter: Guillaume Nodet
> Fix For: 3.2
>
>
> The exception is thrown at:
> Thread [pool-flow.seda.ID:10.59.0.34-1136c103485-0:0-thread-3] (Suspended 
> (exception JBIException))   
>   EndpointRegistry.registerInternalEndpoint(ComponentContextImpl, QName, 
> String) line: 189
>   Registry.activateEndpoint(ComponentContextImpl, QName, String) line: 
> 192
>   ComponentContextImpl.activateEndpoint(QName, String) line: 126  
>   BeanEndpoint(ProviderEndpoint).start() line: 58 
>   BeanEndpoint.start() line: 94   
>   BeanEndpoint(SimpleEndpoint).activate() line: 55
>   BeanComponent.getResolvedEPR(ServiceEndpoint) line: 120 
>   BeanComponent(AsyncBaseLifeCycle).processExchange(MessageExchange) 
> line: 429
>   BeanComponent(BaseLifeCycle).onMessageExchange(MessageExchange) line: 
> 46
>   DeliveryChannelImpl.processInBound(MessageExchangeImpl) line: 595   
>   SedaFlow(AbstractFlow).doRouting(MessageExchangeImpl) line: 174 
>   SedaFlow.doRouting(MessageExchangeImpl) line: 176   
>   SedaQueue$1.run() line: 134 
>   ThreadPoolExecutor$Worker.runTask(Runnable) line: 665   
>   ThreadPoolExecutor$Worker.run() line: 690   
>   Thread.run() line: 595  

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

[jira] Updated: (SM-992) Fix XSD schema locations for use with plain spring

[Freeman Fang (JIRA)]

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

Freeman Fang updated SM-992:


Fix Version/s: (was: 3.1.2)

> Fix XSD schema locations for use with plain spring
> --
>
> Key: SM-992
> URL: https://issues.apache.org/activemq/browse/SM-992
> Project: ServiceMix
>  Issue Type: Task
>Reporter: Guillaume Nodet
> Fix For: 3.2
>
>
> The spring application loaders use validation and requires a schema location.
> We need to do the same as ActiveMQ did:
>   * 
> https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas
>   * http://activemq.apache.org/xml-reference.html
>   * http://activemq.apache.org/schemas/
> (12:10:25 PM) gnodet: jstrachan: what did you fix for the xbean / amq / 
> spring problem ?
> (12:10:43 PM) jstrachan: the spring 2 stuff on the AMQ lists?
> (12:11:03 PM) gnodet: the schemas locations iirc
> (12:11:26 PM) gnodet:  someone just reported the same problem on smx user list
> (12:11:32 PM) jstrachan: mostly it was to put the XSDs in a nice place and 
> use a nice URI to the location of the schemas
> (12:11:32 PM) jstrachan: http://activemq.apache.org/schema/
> (12:11:41 PM) jstrachan: so the namespaces URIS are like: 
> http://activemq.apache.org/schema/core/
> (12:11:47 PM) jstrachan: which points to all versions of the XSD
> (12:12:07 PM) jstrachan: then I've a cron script to copy 'em there from mvn 1 
> repo
> (12:12:15 PM) gnodet: and the spring.schemas metadata, right ?
> (12:12:20 PM) jstrachan: then the other one - and this was the biggie I guess 
> - was to create a spring.schemas
> (12:12:22 PM) jstrachan: yeah
> (12:12:32 PM) jstrachan: where it takes possible XSD locations (not namespace 
> URI)
> (12:12:55 PM) jstrachan: this also means you have to in spring 2 to put the 
> full XSD locations at the top of the XML file
> (12:13:11 PM) gnodet: yeah, because of strict validation
> (12:13:18 PM) jstrachan: http://activemq.apache.org/xml-reference.html
> (12:13:25 PM) jstrachan: yeah
> (12:13:32 PM) gnodet: ok, thx
> (12:13:43 PM) jstrachan: though there's no reason why an EntityResolver can't 
> resolve an XSD purely on the namespace URI
> (12:14:03 PM) jstrachan: seems a bit bizarre that spring only supports 
> namespace resolving on the XSD location (which is an optional thing)
> (12:14:26 PM) jstrachan: AFAIK an xml parser can still validate, so long as 
> an EntityResolver can find the XSD location
> (12:14:38 PM) jstrachan: (I might be wrong on that - but I thought that was 
> the case)
> (12:16:26 PM) jstrachan: here's the spring.schemas: 
> https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/resources/META-INF/spring.schemas
> (12:16:26 PM) jstrachan: notice how it points the XSD location to the local 
> embedded xsd
> (12:17:32 PM) gnodet: yeah
> (12:17:40 PM) jstrachan: I did 2 kinds, like spring do - one XSD with no 
> version number (which always resolves to the one on the classpath) and one 
> using the actual version - only the first 2 lines are useful
> (12:18:01 PM) jstrachan: (I experimented adding the namespace URI in there 
> but its never used)

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

[DISCUSS] G 2.0.2 Release plan

[Kevan Miller]

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