[jira] Closed: (GERONIMO-3898) Provide handy way to configure log4j for a particular app

2008-03-13 Thread David Jencks (JIRA)

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

David Jencks closed GERONIMO-3898.
--

Resolution: Fixed

branches 2.1 rev 636646, trunk rev 636647 make the gbean actually work.

plugins/directory/branches/1.0 converted to g 2.1.1-SNAPSHOT and use of this 
gbean to segregate apacheds logging rev 636649

> Provide handy way to configure log4j for a particular app
> -
>
> Key: GERONIMO-3898
> URL: https://issues.apache.org/jira/browse/GERONIMO-3898
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Logging
>Affects Versions: 2.1.1, 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1.1, 2.2
>
>
> It may or may not be obvious to people how to configure log4j for their app 
> without breaking geronimo's log setup.  We can easily provide a gbean that 
> reads a property file, removes stuff that applies to global logging, and 
> feeds the rest to log4j.  Then people can supply a properties file for their 
> apps log4j configuration, either in the classpath or var/.

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



[jira] Commented: (GERONIMO-3898) Provide handy way to configure log4j for a particular app

2008-03-13 Thread syvalta (JIRA)

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

syvalta commented on GERONIMO-3898:
---

I would prefer having geronimo-internal classes (I consider log4j as such) not 
visible to applications (at least by default). Currently there's a possibility 
for version mismatches and classloader issues, if the application includes 
different version of a library than geronimo has. Is there any plans to 
implement that (couldn't find anything in Jira)?. I know that it is possible to 
hide classes by configuration, but to be able to deploy an app without any 
extra configuration would be nice.

> Provide handy way to configure log4j for a particular app
> -
>
> Key: GERONIMO-3898
> URL: https://issues.apache.org/jira/browse/GERONIMO-3898
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Logging
>Affects Versions: 2.1.1, 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1.1, 2.2
>
>
> It may or may not be obvious to people how to configure log4j for their app 
> without breaking geronimo's log setup.  We can easily provide a gbean that 
> reads a property file, removes stuff that applies to global logging, and 
> feeds the rest to log4j.  Then people can supply a properties file for their 
> apps log4j configuration, either in the classpath or var/.

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



[jira] Created: (GERONIMODEVTOOLS-296) Set svn properties on newly added files

2008-03-13 Thread Shiva Kumar H R (JIRA)
Set svn properties on newly added files
---

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


See the guidelines:
http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html

Some of the newly added files under directories listed below don't have the 
required svn properties set. Set them manually to adhere to guidelines:

\plugins\org.apache.geronimo.deployment.v11.jaxbmodel
\plugins\org.apache.geronimo.deployment.v21.jaxbmodel
\plugins\org.apache.geronimo.st.core\src\org\apache\geronimo\st\core\jaxb
\plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\providers
\plugins\org.apache.geronimo.st.v21.core\src\org\apache\geronimo\st\v21\core\jaxb
\plugins\org.apache.geronimo.st.v20.core\src\org\apache\geronimo\st\v20\core\jaxb

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



Re: link to eclipse settings on coding standards page?

2008-03-13 Thread Shiva Kumar H R
Thanks Jarek. I had totally missed out setting this configuration!! and all
new files I have added in GEP don't have the required svn properties set. I
have created GERONIMODEVTOOLS-296 for this and will fix it up. In fact it's
only now I am realizing that, in the files I have committed "" never got expanded!

-- 
Thanks,
Shiva

On Wed, Mar 12, 2008 at 9:55 PM, Jarek Gawor <[EMAIL PROTECTED]> wrote:

> Can we also add the following link to the coding-standards page:
>
> http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html
>
> Jarek
>
> On Thu, Mar 6, 2008 at 4:57 PM, Ted Kirby <[EMAIL PROTECTED]> wrote:
> > From http://geronimo.apache.org/coding-standards.html, can you add
> >  some text and a link to
> >  http://cwiki.apache.org/GMOxDEV/developing-geronimo-in-eclipse.html,
> >  which is available from devtools page, developing geronimo in eclipse?
> >   I took a shot at it, but did not appear to have permission to do so.
> >  It's nice to describe the coding standards, but even better, I think,
> >  to tell how to configure them IDEs that support it.
> >
> >  Thanks,
> >  Ted Kirby
> >
>


Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Vamsavardhana Reddy
+1

to anything that makes life easier :)

++Vamsi

On Thu, Mar 13, 2008 at 5:04 AM, David Jencks <[EMAIL PROTECTED]>
wrote:

> IIUC we have a coding standard of a 4 space indent for all files
> (documented at http://cwiki.apache.org/GMOxDEV/coding-
> standards.html).  This can make working with maven difficult because
> its files and xml output generatiion use 2 space indent for xml
> and .vm files.
>
> I think we could make life a lot easier when using maven tooling to
> use a 2 space indent for xml and .vm and possibly other files.  At
> least with IDEA its easy to have different indents for java and xml
> files.
>
> Comments?
>
> thanks
> david jencks
>
>


[BUILD] trunk: Failed for Revision: 636647

2008-03-13 Thread gawor
Geronimo Revision: 636647 built with tests included
 
See the full build-0300.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/build-0300.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 30 minutes 45 seconds
[INFO] Finished at: Thu Mar 13 03:38:48 EDT 2008
[INFO] Final Memory: 310M/701M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/logs-0300-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/logs-0300-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 74.35 
sec <<< FAILURE!
 
Samples: trunk
=
Log: 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/samples-0300.log
 
Build status: OK
 


[jira] Commented: (GERONIMO-3907) Persistence Exception is not visible/lost for client.

2008-03-13 Thread Ralf Baumhof (JIRA)

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

Ralf Baumhof commented on GERONIMO-3907:


I have just upgraded my geronimo 2.1 with a new openjpa (1.0.2) version. The 
error is the same. The situation always occurs if you have only one insert on 
the database. So, the physical insert on database is performed AFTER the 
stateless session bean is executed (by ejb container on performing the commit 
with the jta datasource). If i throw an exception by myself it is recognized. 
Did you try this situation in your environment?  The situation does not occur 
if i have several inserts on dependant objects. In this case OpenJPA writes to 
database earlier and the exception is thrown during one of the persist calls. 
The database is a postgresql 8.2 database. Is there a possibility to force 
OpenJPA always write through to the database on each persist call?? Much thanks 
in advance!!

> Persistence Exception is not visible/lost for client. 
> --
>
> Key: GERONIMO-3907
> URL: https://issues.apache.org/jira/browse/GERONIMO-3907
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 2.0.2, 2.1
> Environment: Linux, Windows
>Reporter: Ralf Baumhof
>Priority: Blocker
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> I am trying an insert on a table. The Entity class is wrong annotated, one 
> column was renamed in the table. Then the following situation occurs.  
> The call to persist(entity) is successfully, no exception is thrown. On 
> leaving the ejb container and returning to tomact a commit is performed (it's 
> a managed datasource, so container performs commit). This leads to the insert 
> on database. This insert fails, a rollback is performed. On return to the JSF 
> bean no exception can be seen by the bean. In the same class i have got a 
> query method. If i replace the call to persist with the call to the query 
> method everything works ok. The exception is thrown and is visible at the 
> client site. 
> This is the geronimo console output. The last line comes from the JSB bean 
> which reports a successful insert.
> 11:58:04,390 WARN  [Transaction] Unexpected exception from beforeCompletion; 
> transaction will roll back
>  
> org.apache.openjpa.persistence.PersistenceException: The transaction has been 
> rolled back.  See the nested exceptions for details on the errors that 
> occurred.
> at 
> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107)
> at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954)
> at 
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852)
> at 
> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257)
> at 
> org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245)
> at 
> org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141)
> at 
> org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75)
> at 
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233)
> at 
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188)
> at 
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165)
> at 
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
> at 
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
> at 
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321)
> at 
> org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
> at $Proxy75.anlegenBenutzer(Unknown Source)
> at 
> de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.

[jira] Closed: (GERONIMODEVTOOLS-296) Set svn properties on newly added files

2008-03-13 Thread Shiva Kumar H R (JIRA)

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

Shiva Kumar H R closed GERONIMODEVTOOLS-296.


Resolution: Fixed

Completed: At revision: 636723  

> Set svn properties on newly added files
> ---
>
> Key: GERONIMODEVTOOLS-296
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.0
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.1.0
>
>
> See the guidelines:
> http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html
> Some of the newly added files under directories listed below don't have the 
> required svn properties set. Set them manually to adhere to guidelines:
> \plugins\org.apache.geronimo.deployment.v11.jaxbmodel
> \plugins\org.apache.geronimo.deployment.v21.jaxbmodel
> \plugins\org.apache.geronimo.st.core\src\org\apache\geronimo\st\core\jaxb
> \plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\providers
> \plugins\org.apache.geronimo.st.v21.core\src\org\apache\geronimo\st\v21\core\jaxb
> \plugins\org.apache.geronimo.st.v20.core\src\org\apache\geronimo\st\v20\core\jaxb

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



[jira] Created: (GERONIMO-3913) NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect JAVA_HOME or JRE_HOME

2008-03-13 Thread Kevan Miller (JIRA)
NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect 
JAVA_HOME or JRE_HOME
--

 Key: GERONIMO-3913
 URL: https://issues.apache.org/jira/browse/GERONIMO-3913
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.1, 2.0.2, 2.0.1
Reporter: Kevan Miller
 Fix For: 2.1, 2.0.2


An incorrect setting of JRE_HOME or JAVA_HOME can cause the following error. We 
should indicate to users the potential cause of the problem. Known to be a 
problem with 2.0.x, depending on the method used to start geronimo, may be a 
problem with 2.1


ERROR [org.apache.geronimo.gbean.runtime.GBeanInstanceState] [main] Error
while starting; GBean is now in the FAILED state:
abstractName="org.apache.geronimo.configs/webconsole-jetty6/2.0.1/car?J2EEApplication=org.apache.geronimo.configs/webconsole-jetty6/2.0.1/car,j2eeType=JACCManager,name=JACCManager"
java.lang.ExceptionInInitializerError
   at
org.apache.geronimo.security.jacc.ApplicationPolicyConfigurationManager.(ApplicationPolicyConfigurationManager.java:109)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
   at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
   at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:946)
   at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
   at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
   at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539)
   at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
   at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
   at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
   at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
   at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
   at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
   at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
   at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
   at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
   at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
   at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
   at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
   at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
   at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
   at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.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.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$e380e87b.startConfiguration()
   at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:156)
   at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
   at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
   at
org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
   at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
Caused by: java.lang.NullPointerException
   at
org.apache.geronimo.security.SubjectId.hashCode(SubjectId.java:79)
   at java.util.HashMap.put(HashM

Re: [DISCUSS] Geronimo 2.1.1 release

2008-03-13 Thread Kevan Miller


On Mar 11, 2008, at 11:53 AM, Joe Bohn wrote:

I think it's about time we got a 2.1.1 release out.  The main  
motivation is to deliver a fix for the PortletSecurityException when  
using https on the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855 
). but there are a lot of other fixes that have been integrated as  
well.


The TCK looked good with a recent run ... so I think that should not  
be an issue.


As far as snapshots go, it looks like we're now pulling in a  
snapshot for javamail that we would need to resolve (geronimo- 
javamail_1.4_mail-1.4-SNAPSHOT.jar).  I think that's the only one.


Are there any other changes/fixes that we should be looking to  
include prior to a release?


I am willing to get my feet wet as the release manager unless  
somebody else wants to pick it up.


That'd be great, Joe.

I definitely think it's time to get rolling on 2.1.1.

I see David B has started a release vote for OpenEJB 3.0. I'd like to  
pull that in, if possible (we'll want to get a TCK run using this  
version, regardless).


--kevan

Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Donald Woods

+1


-Donald

David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files 
(documented at http://cwiki.apache.org/GMOxDEV/coding-standards.html).  
This can make working with maven difficult because its files and xml 
output generatiion use 2 space indent for xml and .vm files.


I think we could make life a lot easier when using maven tooling to use 
a 2 space indent for xml and .vm and possibly other files.  At least 
with IDEA its easy to have different indents for java and xml files.


Comments?

thanks
david jencks




smime.p7s
Description: S/MIME Cryptographic Signature


Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Kevan Miller


On Mar 12, 2008, at 7:34 PM, David Jencks wrote:

IIUC we have a coding standard of a 4 space indent for all files  
(documented at http://cwiki.apache.org/GMOxDEV/coding- 
standards.html).  This can make working with maven difficult because  
its files and xml output generatiion use 2 space indent for xml  
and .vm files.


I think we could make life a lot easier when using maven tooling to  
use a 2 space indent for xml and .vm and possibly other files.  At  
least with IDEA its easy to have different indents for java and xml  
files.


Comments?


K. So, you're proposing that either 2 or 4 space indent is acceptable  
for xml and .vm files? Or are you proposing that we'll update the  
indent in all existing files to be 2 space?


Is this what you're proposing?

"Either 2 or 4 space indent may be used for .xml and .vm files. 2- 
space indenting is preferred because that is the style generated by  
maven. When editing an existing file, either follow the convention  
already used in that file or convert it to use 2-space indent"


--kevan

Re: [VOTE] release specs-parent 1.5 and geronimo-servlet_2.5_spec-1.2

2008-03-13 Thread Donald Woods

+1  Thanks for pulling in the GERONIMO-3896 patch.


-Donald

David Jencks wrote:

Hi,

(dependent on genesis 1.4 take 5 release vote passing).


A user recently reported a bug in the servlet spec jar, 
see https://issues.apache.org/jira/browse/GERONIMO-3896



Tomcat has accepted the proposed fix in their trunk.


While working to upgrade to genesis-1.4 and thus release a new specs 
"parent" I realized the current layout was confusing during release.



The changes in this release:


update to use genesis-1.4 (thus this vote is dependent on the current 
genesis 1.4 vote passing)


GERONIMO-3908 reorganize the specs layout so the "parent" pom is in a 
different directory, specs-parent, so tagging does not copy the entire 
set of specs that happen to be in trunk at that moment.


GERONIMO-3896 make HEAD forward/include requests work.


Also I am moving the spec release numbering back to what I consider more 
sensible, namely x.y rather than x.y.z where the need for z or not is 
entirely up to the releaser.



specs-parent:
Staging repo:
http://people.apache.org/~djencks/staging-repo/specs/

Staging site:
http://people.apache.org/~djencks/staging-site/specs/1.5/


geronimo-servlet_2.5_spec-1.2:
Staging repo:
http://people.apache.org/~djencks/staging-repo/specs/servlet-2.5/

Staging site:
http://people.apache.org/~djencks/staging-site/specs/servlet-2.5/1.2/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

thanks
david jencks



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Donald Woods

+1 to only changing the .xml and .vm indents to 2 spaces.

-Donald

Donald Woods wrote:

+1


-Donald

David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files 
(documented at 
http://cwiki.apache.org/GMOxDEV/coding-standards.html).  This can make 
working with maven difficult because its files and xml output 
generatiion use 2 space indent for xml and .vm files.


I think we could make life a lot easier when using maven tooling to 
use a 2 space indent for xml and .vm and possibly other files.  At 
least with IDEA its easy to have different indents for java and xml 
files.


Comments?

thanks
david jencks




smime.p7s
Description: S/MIME Cryptographic Signature


Re: svn commit: r636529 [1/15] - in /geronimo/samples/branches/1.0: ./ migration-ejb-bmp/ migration-ejb-bmp/dd/ migration-ejb-bmp/dd/META-INF/ migration-ejb-bmp/jndi/ migration-ejb-bmp/src/ migration-

2008-03-13 Thread Joe Bohn


Hi Eric,

I'm confused about this new samples branch.

Is it your intention to release these migration samples independently of 
the other samples (this seems to contradict your earlier affirmation on 
the discussion thread that we should release them concurrently and 
mirror the Geronimo version).   When you mentioned you were thinking of 
putting the migration samples under 
samples/branches/#/migration- I assumed the # was 2.1 (and 
echoed in trunk).


Is this because you are trying to figure out how to include them given 
that they are not built with maven?


Joe



[EMAIL PROTECTED] wrote:

Author: ecraig
Date: Wed Mar 12 14:54:41 2008
New Revision: 636529

URL: http://svn.apache.org/viewvc?rev=636529&view=rev
Log:
Initial check in of 1.0 migration demo apps from wiki
License headers, LICENSE.txt, NOTICE.txt have been added to all packages/files.







[jira] Created: (GERONIMO-3914) Use of hidden classes

2008-03-13 Thread Jean-Jacques Parent (JIRA)
Use of hidden classes
-

 Key: GERONIMO-3914
 URL: https://issues.apache.org/jira/browse/GERONIMO-3914
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
  Components: core
Affects Versions: 2.0.1
Reporter: Jean-Jacques Parent


First of all, thank you for your quick reply.
We have applied your solution and it works now. We encoutered some similar 
problems, which were also due to jar conflicts. So we had to add another hidden 
class as follow : 

org.jaxen
org.apache.axis2


If I understand well, by default the jar are always loaded from the parent 
classloader and not from the WEB-INF/lib directory of our web application (such 
as weblogic does for example). I find this quite dangerous because when I will 
migrate to Geronimo 2.0.2 which may contains new versions of jar, I will have 
to check that my application still work with those versions.
The solution will be to hide (as above) all the jar of our web application and 
which are shipped with Geronimo. This may be quite forcing to do.
Another solution may be to use the inverseClassloading flag of the 'Resource 
Adapter Geronimo Deployment Plan' if this is its purpose.
What is the best practise?


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



Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Joe Bohn

+1 assuming we are not forcing everything to a 2 space indent.

Joe


David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files 
(documented at http://cwiki.apache.org/GMOxDEV/coding-standards.html).  
This can make working with maven difficult because its files and xml 
output generatiion use 2 space indent for xml and .vm files.


I think we could make life a lot easier when using maven tooling to use 
a 2 space indent for xml and .vm and possibly other files.  At least 
with IDEA its easy to have different indents for java and xml files.


Comments?

thanks
david jencks






Re: link to eclipse settings on coding standards page?

2008-03-13 Thread Hernan Cunico

Done!

Cheers!
Hernan

Jarek Gawor wrote:

Can we also add the following link to the coding-standards page:

http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html

Jarek

On Thu, Mar 6, 2008 at 4:57 PM, Ted Kirby <[EMAIL PROTECTED]> wrote:

From http://geronimo.apache.org/coding-standards.html, can you add
 some text and a link to
 http://cwiki.apache.org/GMOxDEV/developing-geronimo-in-eclipse.html,
 which is available from devtools page, developing geronimo in eclipse?
  I took a shot at it, but did not appear to have permission to do so.
 It's nice to describe the coding standards, but even better, I think,
 to tell how to configure them IDEs that support it.

 Thanks,
 Ted Kirby





Re: Gshell fails to launch on trunk

2008-03-13 Thread Jason Dillon
Ooops, I think I forgot to update that when I upgraded :-(  Hopefully  
this type of problem will go away soon when I finish the dependency  
muck for gshell plugins... which will be soon.


--jason


On Mar 13, 2008, at 12:31 AM, Jason Warner wrote:


Donald,

It looks good to me.  Thanks!

On Wed, Mar 12, 2008 at 12:42 PM, Donald Woods <[EMAIL PROTECTED]>  
wrote:

This should be fixed now.  I updated -

assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/gsh- 
classworlds.conf
to use the same mina 1.1.5 version as the server in branches/2.1 and  
trunk.



-Donald


Jason Warner wrote:
> I checked out the latest trunk and tried to launch gshell, but found
> that it failed due to an error in plexus.  The problem seems to be
> caused by the recent update to using mina 1.1.5.  The 1.0-alpha-1
> version of gshell that is being used is telling plexus to look for
> version 1.1.2 of mina-core.  When it doesn't find it, it blows up  
and
> the console isn't launched.  This can be fixed by changing the  
version
> of mina that it is searching for in the gsh-classworlds.conf file  
in the
> etc directory.  What would be the proper fix for this?  1.0- 
alpha-1 is

> the latest tag.  It looks like trunk was recently updated to use
> mina-1.1.6.  I imagine we'd have the same problem using a snapshot  
build
> of trunk given that there's a version difference.  Is there  
another way
> to fix this problem or do we need to move gshell trunk over to  
1.1.5 and

> then include the snapshot build in geronimo trunk?
>
> Thanks,
>
>
> --
> ~Jason Warner



--
~Jason Warner




Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Jason Dillon
-1.  I don't think there is any value in making the indent for xml or  
any other files different than the normal indent for all other files.


--jason


On Mar 13, 2008, at 6:34 AM, David Jencks wrote:

IIUC we have a coding standard of a 4 space indent for all files  
(documented at http://cwiki.apache.org/GMOxDEV/coding- 
standards.html).  This can make working with maven difficult because  
its files and xml output generatiion use 2 space indent for xml  
and .vm files.


I think we could make life a lot easier when using maven tooling to  
use a 2 space indent for xml and .vm and possibly other files.  At  
least with IDEA its easy to have different indents for java and xml  
files.


Comments?

thanks
david jencks





Re: [VOTE] release specs-parent 1.5 and geronimo-servlet_2.5_spec-1.2

2008-03-13 Thread Jarek Gawor
+1

Jarek

On Wed, Mar 12, 2008 at 7:03 PM, David Jencks <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> (dependent on genesis 1.4 take 5 release vote passing).
>
>
>
>
> A user recently reported a bug in the servlet spec jar, see
> https://issues.apache.org/jira/browse/GERONIMO-3896
>
>
>
>
> Tomcat has accepted the proposed fix in their trunk.
>
>
>
>
> While working to upgrade to genesis-1.4 and thus release a new specs
> "parent" I realized the current layout was confusing during release.
>
>
>
>
> The changes in this release:
>
>
>
>
> update to use genesis-1.4 (thus this vote is dependent on the current
> genesis 1.4 vote passing)
>
> GERONIMO-3908 reorganize the specs layout so the "parent" pom is in a
> different directory, specs-parent, so tagging does not copy the entire set
> of specs that happen to be in trunk at that moment.
>
> GERONIMO-3896 make HEAD forward/include requests work.
>
>
>
>
> Also I am moving the spec release numbering back to what I consider more
> sensible, namely x.y rather than x.y.z where the need for z or not is
> entirely up to the releaser.
>
> specs-parent:
> Staging repo:
> http://people.apache.org/~djencks/staging-repo/specs/
>
> Staging site:
> http://people.apache.org/~djencks/staging-site/specs/1.5/
>
>
> geronimo-servlet_2.5_spec-1.2:
> Staging repo:
> http://people.apache.org/~djencks/staging-repo/specs/servlet-2.5/
>
> Staging site:
> http://people.apache.org/~djencks/staging-site/specs/servlet-2.5/1.2/
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> thanks
> david jencks
>
>


Re: svn commit: r636529 [1/15] - in /geronimo/samples/branches/1.0: ./ migration-ejb-bmp/ migration-ejb-bmp/dd/ migration-ejb-bmp/dd/META-INF/ migration-ejb-bmp/jndi/ migration-ejb-bmp/src/ migration-

2008-03-13 Thread Erik B. Craig
Joe,

I am trying to back-port the migration samples relevant for the older
branches of the server into the svn repository.
I started by cleaning up the ones intended for the 1.0 version of the server
yesterday, and am working my way up from there, as all of them have not yet
been verified or modified to work on later versions of the server, while
some of them have and are attached to the wiki articles for those versions (
1.1, 2.0, 2.1)

On Thu, Mar 13, 2008 at 8:22 AM, Joe Bohn <[EMAIL PROTECTED]> wrote:

>
> Hi Eric,
>
> I'm confused about this new samples branch.
>
> Is it your intention to release these migration samples independently of
> the other samples (this seems to contradict your earlier affirmation on
> the discussion thread that we should release them concurrently and
> mirror the Geronimo version).   When you mentioned you were thinking of
> putting the migration samples under
> samples/branches/#/migration- I assumed the # was 2.1 (and
> echoed in trunk).
>
> Is this because you are trying to figure out how to include them given
> that they are not built with maven?
>
> Joe
>
>
>
> [EMAIL PROTECTED] wrote:
> > Author: ecraig
> > Date: Wed Mar 12 14:54:41 2008
> > New Revision: 636529
> >
> > URL: http://svn.apache.org/viewvc?rev=636529&view=rev
> > Log:
> > Initial check in of 1.0 migration demo apps from wiki
> > License headers, LICENSE.txt, NOTICE.txt have been added to all
> packages/files.
> >
> >
>
> 
>



-- 
Erik B. Craig


Re: [VOTE] release specs-parent 1.5 and geronimo-servlet_2.5_spec-1.2

2008-03-13 Thread Jay D. McHugh

+1

Jay

David Jencks wrote:

Hi,

(dependent on genesis 1.4 take 5 release vote passing).

A user recently reported a bug in the servlet spec jar, see 
https://issues.apache.org/jira/browse/GERONIMO-3896


Tomcat has accepted the proposed fix in their trunk.

While working to upgrade to genesis-1.4 and thus release a new specs 
"parent" I realized the current layout was confusing during release.


The changes in this release:

update to use genesis-1.4 (thus this vote is dependent on the current 
genesis 1.4 vote passing)
GERONIMO-3908 reorganize the specs layout so the "parent" pom is in a 
different directory, specs-parent, so tagging does not copy the entire 
set of specs that happen to be in trunk at that moment.

GERONIMO-3896 make HEAD forward/include requests work.

Also I am moving the spec release numbering back to what I consider more 
sensible, namely x.y rather than x.y.z where the need for z or not is 
entirely up to the releaser.


specs-parent:
Staging repo:
http://people.apache.org/~djencks/staging-repo/specs/

Staging site:
http://people.apache.org/~djencks/staging-site/specs/1.5/


geronimo-servlet_2.5_spec-1.2:
Staging repo:
http://people.apache.org/~djencks/staging-repo/specs/servlet-2.5/

Staging site:
http://people.apache.org/~djencks/staging-site/specs/servlet-2.5/1.2/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

thanks
david jencks




Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread David Jencks


On Mar 13, 2008, at 7:21 AM, Jason Dillon wrote:

-1.  I don't think there is any value in making the indent for xml  
or any other files different than the normal indent for all other  
files.


Let me give a couple of examples where the 4-space indent causes a  
lot of pain and will continue to:


- in genesis geronimo-skin we have a site.vm file that is a slightly  
modified copy of the default .vm file from doxia-sitetools.  Trying  
to update it or compare it with different indents is quite an  
experience.
- maven archetypes pop out xml with 2 space indenting, and maven xml  
has 2 space indenting.  Re-indenting our stuff any time you run an  
archetype or borrow some configuration from maven is a nuisance that  
frequently is ignored and again the spacing difference makes  
comparison quite difficult.


Do you have an editor that can't deal with different indents for  
different file types?


thanks
david jencks



--jason


On Mar 13, 2008, at 6:34 AM, David Jencks wrote:

IIUC we have a coding standard of a 4 space indent for all files  
(documented at http://cwiki.apache.org/GMOxDEV/coding- 
standards.html).  This can make working with maven difficult  
because its files and xml output generatiion use 2 space indent  
for xml and .vm files.


I think we could make life a lot easier when using maven tooling  
to use a 2 space indent for xml and .vm and possibly other files.   
At least with IDEA its easy to have different indents for java and  
xml files.


Comments?

thanks
david jencks







[jira] Commented: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code

2008-03-13 Thread Jarek Gawor (JIRA)

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

Jarek Gawor commented on GERONIMO-3833:
---

Viet,

Wouldn't it be better to let the server do the actual query instead of shipping 
all the gbean names to the client and doing the query yourself? E.g. do 
something like that:

Set objectNameSet =
mbServerConn.queryNames(new 
ObjectName("*:name=MasterRemoteControlJMX,j2eeType=GBean,*), null);






> Hard-coded gbean names and versions in monitoring code
> --
>
> Key: GERONIMO-3833
> URL: https://issues.apache.org/jira/browse/GERONIMO-3833
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Jarek Gawor
>Assignee: Viet Hung Nguyen
> Fix For: 2.1.1, 2.2
>
>
> The monitoring code has hard-coded values in Java code and sql file:
> 1)
> The 
> ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java
>  contains the following constant:
> private static final String PATH = 
> "geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo,
> name=MasterRemoteControlJMX,j2eeType=GBean";
> 2)
> The  
> ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql 
> contains a bunch of the following values:
> 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector'
> I'm not sure how these are used but in general these type of hardcoded values 
> should be avoided. It's really hard to maintain and keep track of.

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



[jira] Commented: (GERONIMO-3907) Persistence Exception is not visible/lost for client.

2008-03-13 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-3907:


Have you tried entityManager.flush()?

> Persistence Exception is not visible/lost for client. 
> --
>
> Key: GERONIMO-3907
> URL: https://issues.apache.org/jira/browse/GERONIMO-3907
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 2.0.2, 2.1
> Environment: Linux, Windows
>Reporter: Ralf Baumhof
>Priority: Blocker
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> I am trying an insert on a table. The Entity class is wrong annotated, one 
> column was renamed in the table. Then the following situation occurs.  
> The call to persist(entity) is successfully, no exception is thrown. On 
> leaving the ejb container and returning to tomact a commit is performed (it's 
> a managed datasource, so container performs commit). This leads to the insert 
> on database. This insert fails, a rollback is performed. On return to the JSF 
> bean no exception can be seen by the bean. In the same class i have got a 
> query method. If i replace the call to persist with the call to the query 
> method everything works ok. The exception is thrown and is visible at the 
> client site. 
> This is the geronimo console output. The last line comes from the JSB bean 
> which reports a successful insert.
> 11:58:04,390 WARN  [Transaction] Unexpected exception from beforeCompletion; 
> transaction will roll back
>  
> org.apache.openjpa.persistence.PersistenceException: The transaction has been 
> rolled back.  See the nested exceptions for details on the errors that 
> occurred.
> at 
> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107)
> at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954)
> at 
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852)
> at 
> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257)
> at 
> org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245)
> at 
> org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141)
> at 
> org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75)
> at 
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233)
> at 
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188)
> at 
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165)
> at 
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
> at 
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
> at 
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321)
> at 
> org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
> at $Proxy75.anlegenBenutzer(Unknown Source)
> at 
> de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
> at 
> org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
> at 
> org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68)
> at 
> javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75)
> at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:54)
> at javax.faces.component.UICommand.broadcast(UICommand.java:121)
> at 
> javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:292)
>

[jira] Created: (GERONIMO-3915) Upgrade Monitoring and Debugview plugins to use Dojo instead of Dojolegacy

2008-03-13 Thread Donald Woods (JIRA)
Upgrade Monitoring and Debugview plugins to use Dojo instead of Dojolegacy
--

 Key: GERONIMO-3915
 URL: https://issues.apache.org/jira/browse/GERONIMO-3915
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Donald Woods
 Fix For: 2.2


Remove the need to include Dojolegacy (aka. Dojo 0.4.3) so we only ship Dojo 
1.0.2 and reduce our assembly footprint a little.


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



[jira] Commented: (GERONIMO-3856) Assemble a Server Confirmation Page

2008-03-13 Thread Joseph Leong (JIRA)

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

Joseph Leong commented on GERONIMO-3856:


Progress:
 
1) Working on it...
2) Javascript added to perform check for plugin to prevent rendering null value 
500 error.
3) Working on it.. will need to determine if running on a windows / *nix based 
machine and change path location accordingly

> Assemble a Server Confirmation Page
> ---
>
> Key: GERONIMO-3856
> URL: https://issues.apache.org/jira/browse/GERONIMO-3856
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Joseph Leong
>Priority: Minor
>
> Improvements for the Assemble a Server Confirmation Page
> 1) At minimum the user should provide an artifact id otherwise assembly named 
> --bin.tar.gz will be created. The portlet should check for empty artifact id.
> 2) If no plugins are selected and 'assemble' button is pressed a nasty 
> exception will be displayed. The portlet should check if at least one plugin 
> was selected.
> 3) On the confirmation screen and on Windows the server path location will 
> contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.

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



Re: WADI 2.0-M9 - Replace buggy 2.0-M8

2008-03-13 Thread Donald Woods

Can we also upgrade to aspectj-1.5.3?


-Donald

Gianny Damour wrote:

Hi,

A problem has been identified with WADI 2.0-M8 used by Geronimo 2.1 
causing the failure of clustered applications when a specific node (the 
node hosting the singleton partition rebalancing service)  is killed (a 
normal shutdown is fine). WADI 2.0-M9 addresses this problem. This 
release is backward compatible with 2.0-M8 and hence it simply needs to 
be installed into the geronimo repository to upgrade from 2.0-M8 to 2.0-M9.


There are convenience download links for the 2.0-M9 artifacts on WADI's 
home page: http://wadi.codehaus.org/


On a related notes, I will cut a 2.0 release for the next version of 
Geronimo which adds the following features:
* State, i.e. HTTP sessions and SFSB instances, are paged on disc in 
var/temp/SessionStore after a configurable period of time in memory; and
* Monitoring of global or Service Space Envelopes received and sent per 
peer: 
http://docs.codehaus.org/display/WADI/6.+Monitor+Global+or+Service+Space+Envelopes. 



When I checked in some basic support for SFSB clustering, I added the 
ability to register arbitrary distributed services. I believe this can 
be quite handy to implement the optional distributed job execution 
features of the JEE concurrency API under development within the 
sandbox. I wrote a WIKI page describing what I mean by distributed 
services: http://docs.codehaus.org/display/WADI/2.+Distributed+Services


If people are interested by working on a Geronimo caching implementation 
on top of the WADI's infra, then please ping me as this is the next big 
feature I will be working on.


Thanks,
Gianny



smime.p7s
Description: S/MIME Cryptographic Signature


[jira] Resolved: (GERONIMO-3909) Make NamingBuilders/NamingBuilderCollection ordered

2008-03-13 Thread Jarek Gawor (JIRA)

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

Jarek Gawor resolved GERONIMO-3909.
---

   Resolution: Fixed
Fix Version/s: 2.2

Add sort priority order to NamingBuilder/NamingBuilderCollection. Also, added 
AbstractNamingBuilder.lookupJndiContextMap() method that the builders can use 
to see if a given entry was already processed or not. This is in case two 
builders are set to process the same type of DD entry. Committed these changes 
to trunk (revision 636806).


> Make NamingBuilders/NamingBuilderCollection ordered
> ---
>
> Key: GERONIMO-3909
> URL: https://issues.apache.org/jira/browse/GERONIMO-3909
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 2.2
>
>
> Sometimes it might be necessary for one NamingBuilder to run before another 
> one. Right now, the NamingBuilderCollection is un-ordered and the 
> NamingBuilder are invoked in random order. 

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



[jira] Commented: (GERONIMO-3856) Assemble a Server Confirmation Page

2008-03-13 Thread Joseph Leong (JIRA)

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

Joseph Leong commented on GERONIMO-3856:


Progress:

1) Javascript check added 
2) Javascript added to perform check for plugin to prevent rendering null value 
500 error.
3) Working on it.. will need to determine if running on a windows / *nix based 
machine and change path location accordingly

> Assemble a Server Confirmation Page
> ---
>
> Key: GERONIMO-3856
> URL: https://issues.apache.org/jira/browse/GERONIMO-3856
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Joseph Leong
>Priority: Minor
>
> Improvements for the Assemble a Server Confirmation Page
> 1) At minimum the user should provide an artifact id otherwise assembly named 
> --bin.tar.gz will be created. The portlet should check for empty artifact id.
> 2) If no plugins are selected and 'assemble' button is pressed a nasty 
> exception will be displayed. The portlet should check if at least one plugin 
> was selected.
> 3) On the confirmation screen and on Windows the server path location will 
> contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.

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



[jira] Commented: (GERONIMO-3898) Provide handy way to configure log4j for a particular app

2008-03-13 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-3898:


Documented at 
http://cwiki.apache.org/confluence/display/GMOxDOC21/Configuring+Application+Specific+Logging+with+Log4j

The request for  by default might be reasonable but is 
not really in scope of this issue.

> Provide handy way to configure log4j for a particular app
> -
>
> Key: GERONIMO-3898
> URL: https://issues.apache.org/jira/browse/GERONIMO-3898
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Logging
>Affects Versions: 2.1.1, 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1.1, 2.2
>
>
> It may or may not be obvious to people how to configure log4j for their app 
> without breaking geronimo's log setup.  We can easily provide a gbean that 
> reads a property file, removes stuff that applies to global logging, and 
> feeds the rest to log4j.  Then people can supply a properties file for their 
> apps log4j configuration, either in the classpath or var/.

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



Re: [DISCUSS] Geronimo 2.1 samples - zip files

2008-03-13 Thread Joe Bohn


Many of the sample wiki entries include *.zip files in addition to 
references to the svn repo.  These *.zip files include some snapshot of 
the source as well as the javadocs, xrefs, ears/wars, and in some cases 
even wiki html (I think including the wiki content in a zip is a bad 
idea ... it will never be up to date).


Several have spoken in favor of eliminating the zips and I was initially 
inclined to remove them myself in favor of just referencing svn.


However, that means that a user must build the samples (via maven) to 
get all the stuff included in the zip.  So the user must have svn & 
maven if they want to play with the samples on Geronimo or locally work 
with the source.


One possible compromise would be enhance the build to produce the zip 
files.  These zip files would be released when the samples themselves 
are released (and stored in an m2 repo).  We could then reference the 
released zip file artifacts from the wiki entries rather than attaching 
them directly to the wiki.  The benefit would be an svn/maven free way 
to get the source and artifacts to utilize the samples on Geronimo. 
Thoughts?




[jira] Created: (GERONIMO-3916) proxy connection does not capture the successful connection events

2008-03-13 Thread Sangjin Lee (JIRA)
proxy connection does not capture the successful connection events
--

 Key: GERONIMO-3916
 URL: https://issues.apache.org/jira/browse/GERONIMO-3916
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: AsyncHttpClient
Affects Versions: 1.x
Reporter: Sangjin Lee
Assignee: Rick McGuire
Priority: Minor


AsyncHttpClient emits monitoring events, and CONNECTION_SUCCESSFUL is emitted 
when we have a connected session.  However, the CONNECTION_SUCCESSFUL event is 
not emitted for a proxied connection.  See 
ProxyFutureListener.operationComplete()...

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



Re: [DISCUSS] Geronimo 2.1 samples - Archetype

2008-03-13 Thread Joe Bohn



The archetype needs to be documented in the wiki for 2.1+ if we intend 
to encourage its use.  I assume that is still the case (please speak-up 
otherwise).  BTW, I'm not sure what it would mean to release the 
archetype.  It produces a jar but I'm not sure what it would be used 
for.  Anybody have any opinions?


Joe


Re: [DISCUSS] Geronimo 2.1 samples - branches

2008-03-13 Thread Joe Bohn


We have the following branches in samples:
- geronimo/samples/branches/1.0
   Newly added for the migration samples.  We'll see what happens with 
this branch. We don't have the other 1.0 samples (were there any?) 
checked in.


- geronimo/samples/branches/2.0
   This includes the samples for the 2.0.* server stream.  It includes 
jsp-examples and servlet-examples but those are not the ones that we 
released with the 2.0.x releases which are included with the server at 
https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/applications/geronimo-examples. 
 We need to keep the branch but I'm wondering if we should remove the 
jsp & servlet examples from it since the "real" copies are in the tagged 
server svn repos.


- geronimo/samples/branches/2.0-M2
   I'm not sure why this branch is around. I think it was an initial 
experiment for the archetype as it contains just that and the 
calculator-stateless-pojo example.  I think this branch should be deleted.


- geronimo/samples/branches/2.1
   This was created when the 2.1 server was released.   We need this 
for the 2.1 stream and I think we need to release this soon.  This 
brings up another question ... Do we release the 2.1 samples (like we 
did for server) and keep a branch for 2.1.x-SNAPSHOT or do we just 
release the samples and assert that if something breaks the samples it 
should not be included in a subsequent 2.1.x server release?


- geronimo/samples/trunk
   Current trunk for 2.2 (just like the server trunk).  Definitely need 
to keep this and ensure that appropriate changes are reflected from 2.1.




[jira] Created: (GERONIMO-3917) response future does not complete if a connection is closed before the response is received

2008-03-13 Thread Sangjin Lee (JIRA)
response future does not complete if a connection is closed before the response 
is received
---

 Key: GERONIMO-3917
 URL: https://issues.apache.org/jira/browse/GERONIMO-3917
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: AsyncHttpClient
Affects Versions: 1.x
Reporter: Sangjin Lee
Assignee: Rick McGuire


If for *any reason* the server closes a connection without sending the 
response, calls that wait on ResponseFuture.get() for the result will not 
return.

The key issue is the way HttpIoHandler.sessionClosed() works.  The 
sessionClosed() method is invoked when a session is closed.  Currently the only 
major things it does are to call callback's onClosed() method and remove the 
timeout alarm.  If the message was not received or an exception did not occur, 
however, the future remains not complete.  Therefore, any caller that waits on 
Future.get() will never get unblocked.

The sessionClosed() method needs to detect a situation where the connection is 
*prematurely* closed while the response has not been received and cause an 
exception and complete the future.

This is a pretty critical issue.



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



Re: [DISCUSS] Geronimo 2.1 samples - branches

2008-03-13 Thread Joe Bohn

Joe Bohn wrote:


We have the following branches in samples:
- geronimo/samples/branches/1.0
   Newly added for the migration samples.  We'll see what happens with 
this branch. We don't have the other 1.0 samples (were there any?) 
checked in.


- geronimo/samples/branches/2.0
   This includes the samples for the 2.0.* server stream.  It includes 
jsp-examples and servlet-examples but those are not the ones that we 
released with the 2.0.x releases which are included with the server at 
https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/applications/geronimo-examples. 
 We need to keep the branch but I'm wondering if we should remove the 
jsp & servlet examples from it since the "real" copies are in the tagged 
server svn repos.

It looks like the ldap-sample-app was also released with the 2.0.x servers.


- geronimo/samples/branches/2.0-M2
   I'm not sure why this branch is around. I think it was an initial 
experiment for the archetype as it contains just that and the 
calculator-stateless-pojo example.  I think this branch should be deleted.


- geronimo/samples/branches/2.1
   This was created when the 2.1 server was released.   We need this for 
the 2.1 stream and I think we need to release this soon.  This brings up 
another question ... Do we release the 2.1 samples (like we did for 
server) and keep a branch for 2.1.x-SNAPSHOT or do we just release the 
samples and assert that if something breaks the samples it should not be 
included in a subsequent 2.1.x server release?


- geronimo/samples/trunk
   Current trunk for 2.2 (just like the server trunk).  Definitely need 
to keep this and ensure that appropriate changes are reflected from 2.1.







Re: [DISCUSS] Geronimo 2.1 samples - Archetype

2008-03-13 Thread David Jencks


On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:




The archetype needs to be documented in the wiki for 2.1+ if we  
intend to encourage its use.  I assume that is still the case  
(please speak-up otherwise).  BTW, I'm not sure what it would mean  
to release the archetype.  It produces a jar but I'm not sure what  
it would be used for.  Anybody have any opinions?


The new (plugin and assembly) archetypes are documented:

http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
+special-purpose+server+using+maven


If you have suggestions on how to document them better I'm all ears.   
This is the best I could think of.


thanks
david jencks


Joe




Re: [DISCUSS] Geronimo 2.1 samples - Archetype

2008-03-13 Thread Joe Bohn

David Jencks wrote:


On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:




The archetype needs to be documented in the wiki for 2.1+ if we intend 
to encourage its use.  I assume that is still the case (please 
speak-up otherwise).  BTW, I'm not sure what it would mean to release 
the archetype.  It produces a jar but I'm not sure what it would be 
used for.  Anybody have any opinions?


The new (plugin and assembly) archetypes are documented:

http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven

If you have suggestions on how to document them better I'm all ears. 
 This is the best I could think of.




David,

I'm specifically talking about the archetype for the samples located 
here: 
https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/geronimo-samples-archetype/

not the plugin or assembly archetypes.

I'm really just listing things that I think we need to clear up before 
we can release the 2.1 samples and trying to understand what it might 
mean to release the samples archetype.


Joe


Re: [DISCUSS] Geronimo 2.1 samples - Archetype

2008-03-13 Thread David Jencks


On Mar 13, 2008, at 11:41 AM, Joe Bohn wrote:


David Jencks wrote:

On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:



The archetype needs to be documented in the wiki for 2.1+ if we  
intend to encourage its use.  I assume that is still the case  
(please speak-up otherwise).  BTW, I'm not sure what it would  
mean to release the archetype.  It produces a jar but I'm not  
sure what it would be used for.  Anybody have any opinions?

The new (plugin and assembly) archetypes are documented:
http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a 
+special-purpose+server+using+maven
If you have suggestions on how to document them better I'm all  
ears.  This is the best I could think of.


David,

I'm specifically talking about the archetype for the samples  
located here: https://svn.apache.org/repos/asf/geronimo/samples/ 
branches/2.1/geronimo-samples-archetype/

not the plugin or assembly archetypes.

I'm really just listing things that I think we need to clear up  
before we can release the 2.1 samples and trying to understand what  
it might mean to release the samples archetype.


My apologies Joe, I misread the subject.
/engage brain before fingers

thanks
david jencks



Joe




Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Joe Bohn

Joe Bohn wrote:

David Jencks wrote:


On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:


Donald Woods wrote:

Joe Bohn wrote:


2) When to release the samples?  I think we should make an effort 
to release the samples concurrent with each Geronimo release.  This 
is important because the jsp & servlet examples are referenced from 
within the welcome page on Geronimo.  I suppose we could remove 
that reference and eliminate the need to release concurrently.
why not move the samples back under geronimo/server, so they are 
maintained and versioned with each release and can then be used as 
additional testsuite tests?  If not, releasing right after a server 
release is fine.


I was thinking about doing this.  It seems everybody thinks we should 
release them together anyway so what is the real value with them 
being split out?  Does anybody object to moving them back with the 
server?


well, since I thought our next goal with the server build was to 
separate it into independently released plugins, I think putting the 
samples in with the main server build would be a big step backwards.


Well, I agree that it would appear to be a step backwards from that 
perspective.  However, it would ensure the following:


1) The samples would get released (not forgotten as has been the case 
with 2.1)
2) The samples would be released concurrent with the Geronimo release so 
that they are available for use, education, and documentation from day 
1.  It seems almost everybody is in favor of this.
3) They could be leveraged in the testsuite tests (as Donald pointed 
out) to help validate our build and find problems earlier.


I fail to see too many negatives from a practical perspective but I'm 
certainly open to discussion  I want to do what is best.


Perhaps we need to refine our plugin strategy.  There are situations 
where it makes sense to split things apart but there are also situations 
where it might make sense to bundle things.


Joe



Would those folks that feel strongly about not pulling these samples 
back into the server repo please provide some rationale for their 
argument as I have done for including them?  It appears that the samples 
were removed without much thought given to how they might eventually be 
released in conjunction with a server release.  I like the idea of 
modularity but in this case I don't see clear benefits to keeping them 
separate.


Please keep in mind that including the samples in the server source 
branch and releasing them concurrent with the server does not mean that 
they are bundled with the server.  They are still independent artifacts. 
 However, it would ensure that they are vetted with the server release 
and are available when the server release is available.  The samples are 
really only there to show value on top of a Geronimo server and they are 
tied to a specific server release (at least that is how we have managed 
and documented them thus far) so having released independent of the 
server doesn't appear to bring any value.


I looked back through a number of old email threads and these samples 
were included in the welcome page with a lot of support at the time 
(with a desire to have even more samples included or downloadable from 
the welcome page) ... several folks stating that they should be included 
with the server image itself.  I certainly don't want to bundle the 
samples with the server image but having the released with the server 
makes sense to me.


Joe




Re: [DISCUSS] Geronimo 2.1 samples - releases to date

2008-03-13 Thread Joe Bohn


We have never yet released artifacts for samples apart from those that 
were released as part of a server release via plugins in 2.0.x 
(jsp-examples, servlet-examples, and ldap-sample-app).  Since these 
samples weren't included in the server svn they were not released as 
part of the 2.1 server. We need to get this cleared for the 2.1.  In 
fact, this unfinished 2.1 business is the only reason why I'm looking 
into the whole samples area right now (even though I really should have 
looked at it earlier).


The released 2.1 server has links to samples that are not released ... 
hence broken links and a bad user experience.   BTW, there are also some 
problems with this in 2.0.x ... I was able to install the jsp-examples 
but not servlet-examples or the ldap-sample-app from the links on the 
welcome page in a 2.0.2 image.  Perhaps this has never worked right 
(even when they were released).



Joe


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread David Jencks


On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:


Joe Bohn wrote:

David Jencks wrote:


On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:


Donald Woods wrote:

Joe Bohn wrote:


2) When to release the samples?  I think we should make an  
effort to release the samples concurrent with each Geronimo  
release.  This is important because the jsp & servlet examples  
are referenced from within the welcome page on Geronimo.  I  
suppose we could remove that reference and eliminate the need  
to release concurrently.
why not move the samples back under geronimo/server, so they  
are maintained and versioned with each release and can then be  
used as additional testsuite tests?  If not, releasing right  
after a server release is fine.


I was thinking about doing this.  It seems everybody thinks we  
should release them together anyway so what is the real value  
with them being split out?  Does anybody object to moving them  
back with the server?


well, since I thought our next goal with the server build was to  
separate it into independently released plugins, I think putting  
the samples in with the main server build would be a big step  
backwards.
Well, I agree that it would appear to be a step backwards from  
that perspective.  However, it would ensure the following:
1) The samples would get released (not forgotten as has been the  
case with 2.1)
2) The samples would be released concurrent with the Geronimo  
release so that they are available for use, education, and  
documentation from day 1.  It seems almost everybody is in favor  
of this.
3) They could be leveraged in the testsuite tests (as Donald  
pointed out) to help validate our build and find problems earlier.
I fail to see too many negatives from a practical perspective but  
I'm certainly open to discussion  I want to do what is best.
Perhaps we need to refine our plugin strategy.  There are  
situations where it makes sense to split things apart but there  
are also situations where it might make sense to bundle things.

Joe


Would those folks that feel strongly about not pulling these  
samples back into the server repo please provide some rationale for  
their argument as I have done for including them?  It appears that  
the samples were removed without much thought given to how they  
might eventually be released in conjunction with a server release.   
I like the idea of modularity but in this case I don't see clear  
benefits to keeping them separate.


Please keep in mind that including the samples in the server source  
branch and releasing them concurrent with the server does not mean  
that they are bundled with the server.  They are still independent  
artifacts.  However, it would ensure that they are vetted with the  
server release and are available when the server release is  
available.  The samples are really only there to show value on top  
of a Geronimo server and they are tied to a specific server release  
(at least that is how we have managed and documented them thus far)  
so having released independent of the server doesn't appear to  
bring any value.


I looked back through a number of old email threads and these  
samples were included in the welcome page with a lot of support at  
the time (with a desire to have even more samples included or  
downloadable from the welcome page) ... several folks stating that  
they should be included with the server image itself.  I certainly  
don't want to bundle the samples with the server image but having  
the released with the server makes sense to me.


I'm speculating a bit here.

This might be similar to the testsuite being a bit monolithic.

As a thought experiment, what if we...
- made the welcome page a plugin, and the piece of build including it  
also builds the samples
- the maven generated site includes the stuff you need to download  
(zips etc) (I think this is doable)

- the welcome page links to the maven  generated site
- this leaves the door open to making the welcome page + samples  
independently versioned in the future, and possibly to selenium testing.


- we split up the testsuite into integration tests for "plugins" or  
plugin groups, and they assemble the servers they need on the fly


- assemblies may or may not include the welcome page plugin.

dunno how practical this is for 2.1.1

thanks
david jencks





Joe






Re: [DISCUSS] Geronimo 2.1 samples - branches

2008-03-13 Thread Donald Woods
I'd like to see us keep a branches/2.0 and branches/2.1 around, so 
people can continue to add and enhance the samples if they wish



-Donald

Joe Bohn wrote:


We have the following branches in samples:
- geronimo/samples/branches/1.0
   Newly added for the migration samples.  We'll see what happens with 
this branch. We don't have the other 1.0 samples (were there any?) 
checked in.


- geronimo/samples/branches/2.0
   This includes the samples for the 2.0.* server stream.  It includes 
jsp-examples and servlet-examples but those are not the ones that we 
released with the 2.0.x releases which are included with the server at 
https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/applications/geronimo-examples. 
 We need to keep the branch but I'm wondering if we should remove the 
jsp & servlet examples from it since the "real" copies are in the tagged 
server svn repos.


- geronimo/samples/branches/2.0-M2
   I'm not sure why this branch is around. I think it was an initial 
experiment for the archetype as it contains just that and the 
calculator-stateless-pojo example.  I think this branch should be deleted.


- geronimo/samples/branches/2.1
   This was created when the 2.1 server was released.   We need this for 
the 2.1 stream and I think we need to release this soon.  This brings up 
another question ... Do we release the 2.1 samples (like we did for 
server) and keep a branch for 2.1.x-SNAPSHOT or do we just release the 
samples and assert that if something breaks the samples it should not be 
included in a subsequent 2.1.x server release?


- geronimo/samples/trunk
   Current trunk for 2.2 (just like the server trunk).  Definitely need 
to keep this and ensure that appropriate changes are reflected from 2.1.





smime.p7s
Description: S/MIME Cryptographic Signature


[jira] Created: (GERONIMO-3918) Upgrade to WADI 2.0-M9

2008-03-13 Thread Donald Woods (JIRA)
Upgrade to WADI 2.0-M9
--

 Key: GERONIMO-3918
 URL: https://issues.apache.org/jira/browse/GERONIMO-3918
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: dependencies
Affects Versions: 2.1.1, 2.2
Reporter: Donald Woods
Assignee: Donald Woods
 Fix For: 2.1.1, 2.2


As suggested by Gianny, upgrade from 2.0-M8 to M9

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



[jira] Closed: (GERONIMO-3918) Upgrade to WADI 2.0-M9

2008-03-13 Thread Donald Woods (JIRA)

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

Donald Woods closed GERONIMO-3918.
--

Resolution: Fixed

applied as Rev636841 in branches/2.1

> Upgrade to WADI 2.0-M9
> --
>
> Key: GERONIMO-3918
> URL: https://issues.apache.org/jira/browse/GERONIMO-3918
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.1.1
>Reporter: Donald Woods
>Assignee: Donald Woods
> Fix For: 2.1.1
>
>
> As suggested by Gianny, upgrade from 2.0-M8 to M9

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



[jira] Updated: (GERONIMO-3918) Upgrade to WADI 2.0-M9

2008-03-13 Thread Donald Woods (JIRA)

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

Donald Woods updated GERONIMO-3918:
---

Affects Version/s: (was: 2.2)
Fix Version/s: (was: 2.2)

> Upgrade to WADI 2.0-M9
> --
>
> Key: GERONIMO-3918
> URL: https://issues.apache.org/jira/browse/GERONIMO-3918
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.1.1
>Reporter: Donald Woods
>Assignee: Donald Woods
> Fix For: 2.1.1
>
>
> As suggested by Gianny, upgrade from 2.0-M8 to M9

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



Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Hernan Cunico

David Jencks wrote:


On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:


Joe Bohn wrote:

David Jencks wrote:


On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:


Donald Woods wrote:

Joe Bohn wrote:


2) When to release the samples?  I think we should make an effort 
to release the samples concurrent with each Geronimo release.  
This is important because the jsp & servlet examples are 
referenced from within the welcome page on Geronimo.  I suppose 
we could remove that reference and eliminate the need to release 
concurrently.
why not move the samples back under geronimo/server, so they are 
maintained and versioned with each release and can then be used as 
additional testsuite tests?  If not, releasing right after a 
server release is fine.


I was thinking about doing this.  It seems everybody thinks we 
should release them together anyway so what is the real value with 
them being split out?  Does anybody object to moving them back with 
the server?


well, since I thought our next goal with the server build was to 
separate it into independently released plugins, I think putting the 
samples in with the main server build would be a big step backwards.
Well, I agree that it would appear to be a step backwards from that 
perspective.  However, it would ensure the following:
1) The samples would get released (not forgotten as has been the case 
with 2.1)
2) The samples would be released concurrent with the Geronimo release 
so that they are available for use, education, and documentation from 
day 1.  It seems almost everybody is in favor of this.
3) They could be leveraged in the testsuite tests (as Donald pointed 
out) to help validate our build and find problems earlier.
I fail to see too many negatives from a practical perspective but I'm 
certainly open to discussion  I want to do what is best.
Perhaps we need to refine our plugin strategy.  There are situations 
where it makes sense to split things apart but there are also 
situations where it might make sense to bundle things.

Joe


Would those folks that feel strongly about not pulling these samples 
back into the server repo please provide some rationale for their 
argument as I have done for including them?  It appears that the 
samples were removed without much thought given to how they might 
eventually be released in conjunction with a server release.  I like 
the idea of modularity but in this case I don't see clear benefits to 
keeping them separate.


Please keep in mind that including the samples in the server source 
branch and releasing them concurrent with the server does not mean 
that they are bundled with the server.  They are still independent 
artifacts.  However, it would ensure that they are vetted with the 
server release and are available when the server release is 
available.  The samples are really only there to show value on top of 
a Geronimo server and they are tied to a specific server release (at 
least that is how we have managed and documented them thus far) so 
having released independent of the server doesn't appear to bring any 
value.


I looked back through a number of old email threads and these samples 
were included in the welcome page with a lot of support at the time 
(with a desire to have even more samples included or downloadable from 
the welcome page) ... several folks stating that they should be 
included with the server image itself.  I certainly don't want to 
bundle the samples with the server image but having the released with 
the server makes sense to me.


I'm speculating a bit here.

This might be similar to the testsuite being a bit monolithic.

As a thought experiment, what if we...
- made the welcome page a plugin, and the piece of build including it 
also builds the samples
- the maven generated site includes the stuff you need to download (zips 
etc) (I think this is doable)


Are we using any maven site today? what type of info goes there? who consumes 
it?

.zip samples download shouldn't be any different from the other downloads we 
have, right?

Cheers!
Hernan


- the welcome page links to the maven  generated site
- this leaves the door open to making the welcome page + samples 
independently versioned in the future, and possibly to selenium testing.


- we split up the testsuite into integration tests for "plugins" or 
plugin groups, and they assemble the servers they need on the fly


- assemblies may or may not include the welcome page plugin.

dunno how practical this is for 2.1.1

thanks
david jencks





Joe







Re: [DISCUSS] Geronimo 2.1 samples - zip files

2008-03-13 Thread Hernan Cunico

Joe Bohn wrote:


Many of the sample wiki entries include *.zip files in addition to 
references to the svn repo.  These *.zip files include some snapshot of 
the source as well as the javadocs, xrefs, ears/wars, and in some cases 
even wiki html (I think including the wiki content in a zip is a bad 
idea ... it will never be up to date).


Several have spoken in favor of eliminating the zips and I was initially 
inclined to remove them myself in favor of just referencing svn.


However, that means that a user must build the samples (via maven) to 
get all the stuff included in the zip.  So the user must have svn & 
maven if they want to play with the samples on Geronimo or locally work 
with the source.


One possible compromise would be enhance the build to produce the zip 
files.  These zip files would be released when the samples themselves 
are released (and stored in an m2 repo).  We could then reference the 
released zip file artifacts from the wiki entries rather than attaching 
them directly to the wiki.  The benefit would be an svn/maven free way 
to get the source and artifacts to utilize the samples on Geronimo. 
Thoughts?



Right, we can not eliminate the zip files. Having the samples in svn is a way 
for us to keep track of the updates, not a way to distribute them.
We should find a way to generate independent downloads for each of the samples, 
pretty much the same way we do with the other downloads 
(http://geronimo.apache.org/apache-geronimo-v21-release.html). Additionally, we 
could have them available as plugins, we could set up a plugin repo just for 
samples apps.

We should be able to do all this at release time.

Cheers!
Hernan


Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread Jarek Gawor
Donald,

I don't understand. How are you building the code? The automatic
builds are always done with a clean repo and we don't see builds
failing with any missing dependency error.

Jarek

On Thu, Mar 13, 2008 at 3:21 PM,  <[EMAIL PROTECTED]> wrote:
> Author: dwoods
>  Date: Thu Mar 13 12:21:46 2008
>  New Revision: 636845
>
>  URL: http://svn.apache.org/viewvc?rev=636845&view=rev
>  Log:
>  found another depend missing by running testsuite with a clean repo
>
>  Modified:
> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml
>
>  Modified: 
> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml
>  URL: 
> http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml?rev=636845&r1=636844&r2=636845&view=diff
>  
> ==
>  --- geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml 
> (original)
>  +++ geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml 
> Thu Mar 13 12:21:46 2008
>  @@ -40,6 +40,12 @@
>
>  
>  org.apache.geronimo.framework
>  +geronimo-common
>  +${version}
>  +
>  +
>  +
>  +org.apache.geronimo.framework
>  geronimo-plugin
>  ${version}
>  
>
>
>


Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread Donald Woods
I'm starting with a clean local repo and only running "mvn install" from 
under the testsuite subdir, as to run a "clean" BVT based on the 
artifacts in the hosted repos


I believe the daily build script always runs the testsuite after the 
server builds completes, right?  So the local repo is already populated 
with all the depends



-Donald


Jarek Gawor wrote:

Donald,

I don't understand. How are you building the code? The automatic
builds are always done with a clean repo and we don't see builds
failing with any missing dependency error.

Jarek

On Thu, Mar 13, 2008 at 3:21 PM,  <[EMAIL PROTECTED]> wrote:

Author: dwoods
 Date: Thu Mar 13 12:21:46 2008
 New Revision: 636845

 URL: http://svn.apache.org/viewvc?rev=636845&view=rev
 Log:
 found another depend missing by running testsuite with a clean repo

 Modified:
geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

 Modified: geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml
 URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml?rev=636845&r1=636844&r2=636845&view=diff
 ==
 --- geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml 
(original)
 +++ geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml Thu 
Mar 13 12:21:46 2008
 @@ -40,6 +40,12 @@

 
 org.apache.geronimo.framework
 +geronimo-common
 +${version}
 +
 +
 +
 +org.apache.geronimo.framework
 geronimo-plugin
 ${version}
 







smime.p7s
Description: S/MIME Cryptographic Signature


Re: [DISCUSS] Geronimo 2.1 samples - branches

2008-03-13 Thread Hernan Cunico

Joe Bohn wrote:


We have the following branches in samples:
- geronimo/samples/branches/1.0
   Newly added for the migration samples.  We'll see what happens with 
this branch. We don't have the other 1.0 samples (were there any?) 
checked in.


There were some samples apps for 1.0 scattered all across the doc but it would 
take a lot of time to dig them up.



- geronimo/samples/branches/2.0
   This includes the samples for the 2.0.* server stream.  It includes 
jsp-examples and servlet-examples but those are not the ones that we 
released with the 2.0.x releases which are included with the server at 
https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/applications/geronimo-examples. 
 We need to keep the branch but I'm wondering if we should remove the 
jsp & servlet examples from it since the "real" copies are in the tagged 
server svn repos.


- geronimo/samples/branches/2.0-M2
   I'm not sure why this branch is around. I think it was an initial 
experiment for the archetype as it contains just that and the 
calculator-stateless-pojo example.  I think this branch should be deleted.


- geronimo/samples/branches/2.1
   This was created when the 2.1 server was released.   We need this for 
the 2.1 stream and I think we need to release this soon.  This brings up 
another question ... Do we release the 2.1 samples (like we did for 
server) and keep a branch for 2.1.x-SNAPSHOT or do we just release the 
samples and assert that if something breaks the samples it should not be 
included in a subsequent 2.1.x server release?


- geronimo/samples/trunk
   Current trunk for 2.2 (just like the server trunk).  Definitely need 
to keep this and ensure that appropriate changes are reflected from 2.1.




One last thought never discussed so far. Most of the sample apps we are 
planning to move to svn+ was contributed from many different folks, most of 
them not committers.
How are we going to deal with this issue? JIRAs will be required for 
contributing and maintaining these samples. I'm afraid this will expand to the 
corresponding documentation as well.

Although I see the benefit of having the samples on svn I also realize we will be adding 
some "obstacles" for contributing. Today, anybody can chime in the doc and work 
some samples out.

I think we should discuss this more in detail as well.

Cheers!
Hernan


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Erik B. Craig
On Thu, Mar 13, 2008 at 1:47 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

> Joe Bohn wrote:
> > David Jencks wrote:
> >>
> >> On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
> >>
> >>> Donald Woods wrote:
>  Joe Bohn wrote:
> >
> > 2) When to release the samples?  I think we should make an effort
> > to release the samples concurrent with each Geronimo release.  This
> > is important because the jsp & servlet examples are referenced from
> > within the welcome page on Geronimo.  I suppose we could remove
> > that reference and eliminate the need to release concurrently.
>  why not move the samples back under geronimo/server, so they are
>  maintained and versioned with each release and can then be used as
>  additional testsuite tests?  If not, releasing right after a server
>  release is fine.
> >>>
> >>> I was thinking about doing this.  It seems everybody thinks we should
> >>> release them together anyway so what is the real value with them
> >>> being split out?  Does anybody object to moving them back with the
> >>> server?
> >>
> >> well, since I thought our next goal with the server build was to
> >> separate it into independently released plugins, I think putting the
> >> samples in with the main server build would be a big step backwards.
> >
> > Well, I agree that it would appear to be a step backwards from that
> > perspective.  However, it would ensure the following:
> >
> > 1) The samples would get released (not forgotten as has been the case
> > with 2.1)
> > 2) The samples would be released concurrent with the Geronimo release so
> > that they are available for use, education, and documentation from day
> > 1.  It seems almost everybody is in favor of this.
> > 3) They could be leveraged in the testsuite tests (as Donald pointed
> > out) to help validate our build and find problems earlier.
> >
> > I fail to see too many negatives from a practical perspective but I'm
> > certainly open to discussion  I want to do what is best.
> >
> > Perhaps we need to refine our plugin strategy.  There are situations
> > where it makes sense to split things apart but there are also situations
> > where it might make sense to bundle things.
> >
> > Joe
> >
>
> Would those folks that feel strongly about not pulling these samples
> back into the server repo please provide some rationale for their
> argument as I have done for including them?  It appears that the samples
> were removed without much thought given to how they might eventually be
> released in conjunction with a server release.  I like the idea of
> modularity but in this case I don't see clear benefits to keeping them
> separate.
>
> Please keep in mind that including the samples in the server source
> branch and releasing them concurrent with the server does not mean that
> they are bundled with the server.  They are still independent artifacts.
>  However, it would ensure that they are vetted with the server release
> and are available when the server release is available.  The samples are
> really only there to show value on top of a Geronimo server and they are
> tied to a specific server release (at least that is how we have managed
> and documented them thus far) so having released independent of the
> server doesn't appear to bring any value.


Well, hey, as long as they aren't necessarily bundled with the server then
I'm pretty okay with it.
As far as the migration samples go though, this is definitely not the place
for them, as they are intended to be checked out by the user, who is then
guided through converting them to be deployed on geronimo - they aren't
necessarily able to be deployed on geronimo prior to following the
documentation, nor are they necessarily able to be compiled used maven.



>
>
> I looked back through a number of old email threads and these samples
> were included in the welcome page with a lot of support at the time
> (with a desire to have even more samples included or downloadable from
> the welcome page) ... several folks stating that they should be included
> with the server image itself.  I certainly don't want to bundle the
> samples with the server image but having the released with the server
> makes sense to me.
>
> Joe
>
>
>


-- 
Erik B. Craig


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Jason Warner
I wasn't sure which thread to put this in, so I'll throw it in here.  So
far, it seems that when we've been discussing samples, we're lumping the
sample applications and the migration samples in together.  Is this
something we want to do?  In my mind, they aren't really the same and
shouldn't necessarily be in the same place.  AFAIK, a sample application is
supposed to be able to be checked out, built, and deployed on geronimo
straight away to highlight some feature or functionality.  The migration
samples, though, are meant to be fiddled with before they can be deployed on
Geronimo.  If we lump them all in together, how is a user supposed to know
which is which when browsing svn?  Would it make sense to keep the migration
samples in a separate space?

On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

> David Jencks wrote:
> >
> > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
> >
> >> Joe Bohn wrote:
> >>> David Jencks wrote:
> 
>  On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
> 
> > Donald Woods wrote:
> >> Joe Bohn wrote:
> >>>
> >>> 2) When to release the samples?  I think we should make an effort
> >>> to release the samples concurrent with each Geronimo release.
> >>> This is important because the jsp & servlet examples are
> >>> referenced from within the welcome page on Geronimo.  I suppose
> >>> we could remove that reference and eliminate the need to release
> >>> concurrently.
> >> why not move the samples back under geronimo/server, so they are
> >> maintained and versioned with each release and can then be used as
> >> additional testsuite tests?  If not, releasing right after a
> >> server release is fine.
> >
> > I was thinking about doing this.  It seems everybody thinks we
> > should release them together anyway so what is the real value with
> > them being split out?  Does anybody object to moving them back with
> > the server?
> 
>  well, since I thought our next goal with the server build was to
>  separate it into independently released plugins, I think putting the
>  samples in with the main server build would be a big step backwards.
> >>> Well, I agree that it would appear to be a step backwards from that
> >>> perspective.  However, it would ensure the following:
> >>> 1) The samples would get released (not forgotten as has been the case
> >>> with 2.1)
> >>> 2) The samples would be released concurrent with the Geronimo release
> >>> so that they are available for use, education, and documentation from
> >>> day 1.  It seems almost everybody is in favor of this.
> >>> 3) They could be leveraged in the testsuite tests (as Donald pointed
> >>> out) to help validate our build and find problems earlier.
> >>> I fail to see too many negatives from a practical perspective but I'm
> >>> certainly open to discussion  I want to do what is best.
> >>> Perhaps we need to refine our plugin strategy.  There are situations
> >>> where it makes sense to split things apart but there are also
> >>> situations where it might make sense to bundle things.
> >>> Joe
> >>
> >> Would those folks that feel strongly about not pulling these samples
> >> back into the server repo please provide some rationale for their
> >> argument as I have done for including them?  It appears that the
> >> samples were removed without much thought given to how they might
> >> eventually be released in conjunction with a server release.  I like
> >> the idea of modularity but in this case I don't see clear benefits to
> >> keeping them separate.
> >>
> >> Please keep in mind that including the samples in the server source
> >> branch and releasing them concurrent with the server does not mean
> >> that they are bundled with the server.  They are still independent
> >> artifacts.  However, it would ensure that they are vetted with the
> >> server release and are available when the server release is
> >> available.  The samples are really only there to show value on top of
> >> a Geronimo server and they are tied to a specific server release (at
> >> least that is how we have managed and documented them thus far) so
> >> having released independent of the server doesn't appear to bring any
> >> value.
> >>
> >> I looked back through a number of old email threads and these samples
> >> were included in the welcome page with a lot of support at the time
> >> (with a desire to have even more samples included or downloadable from
> >> the welcome page) ... several folks stating that they should be
> >> included with the server image itself.  I certainly don't want to
> >> bundle the samples with the server image but having the released with
> >> the server makes sense to me.
> >
> > I'm speculating a bit here.
> >
> > This might be similar to the testsuite being a bit monolithic.
> >
> > As a thought experiment, what if we...
> > - made the welcome page a plugin, and the piece of build including it
> > a

Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Hernan Cunico

Migration samples should definitively not go into svn because the source 
environment, the start point for those apps is intended to be a different 
platform, not Geronimo. There would be no point in keeping them into svn and 
adding them as a part of the release process.

However there are a whole bunch of other sample apps in the doc and are G 
specific and those are the ones we are discussing here. Or I need to start 
reading the whole thread again :P

Cheers!
Hernan

Jason Warner wrote:
I wasn't sure which thread to put this in, so I'll throw it in here.  So 
far, it seems that when we've been discussing samples, we're lumping the 
sample applications and the migration samples in together.  Is this 
something we want to do?  In my mind, they aren't really the same and 
shouldn't necessarily be in the same place.  AFAIK, a sample application 
is supposed to be able to be checked out, built, and deployed on 
geronimo straight away to highlight some feature or functionality.  The 
migration samples, though, are meant to be fiddled with before they can 
be deployed on Geronimo.  If we lump them all in together, how is a user 
supposed to know which is which when browsing svn?  Would it make sense 
to keep the migration samples in a separate space?


On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED] 
> wrote:


David Jencks wrote:
 >
 > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
 >
 >> Joe Bohn wrote:
 >>> David Jencks wrote:
 
  On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
 
 > Donald Woods wrote:
 >> Joe Bohn wrote:
 >>>
 >>> 2) When to release the samples?  I think we should make an
effort
 >>> to release the samples concurrent with each Geronimo release.
 >>> This is important because the jsp & servlet examples are
 >>> referenced from within the welcome page on Geronimo.  I suppose
 >>> we could remove that reference and eliminate the need to
release
 >>> concurrently.
 >> why not move the samples back under geronimo/server, so they are
 >> maintained and versioned with each release and can then be
used as
 >> additional testsuite tests?  If not, releasing right after a
 >> server release is fine.
 >
 > I was thinking about doing this.  It seems everybody thinks we
 > should release them together anyway so what is the real value
with
 > them being split out?  Does anybody object to moving them
back with
 > the server?
 
  well, since I thought our next goal with the server build was to
  separate it into independently released plugins, I think
putting the
  samples in with the main server build would be a big step
backwards.
 >>> Well, I agree that it would appear to be a step backwards from that
 >>> perspective.  However, it would ensure the following:
 >>> 1) The samples would get released (not forgotten as has been
the case
 >>> with 2.1)
 >>> 2) The samples would be released concurrent with the Geronimo
release
 >>> so that they are available for use, education, and
documentation from
 >>> day 1.  It seems almost everybody is in favor of this.
 >>> 3) They could be leveraged in the testsuite tests (as Donald
pointed
 >>> out) to help validate our build and find problems earlier.
 >>> I fail to see too many negatives from a practical perspective
but I'm
 >>> certainly open to discussion  I want to do what is best.
 >>> Perhaps we need to refine our plugin strategy.  There are
situations
 >>> where it makes sense to split things apart but there are also
 >>> situations where it might make sense to bundle things.
 >>> Joe
 >>
 >> Would those folks that feel strongly about not pulling these samples
 >> back into the server repo please provide some rationale for their
 >> argument as I have done for including them?  It appears that the
 >> samples were removed without much thought given to how they might
 >> eventually be released in conjunction with a server release.  I like
 >> the idea of modularity but in this case I don't see clear
benefits to
 >> keeping them separate.
 >>
 >> Please keep in mind that including the samples in the server source
 >> branch and releasing them concurrent with the server does not mean
 >> that they are bundled with the server.  They are still independent
 >> artifacts.  However, it would ensure that they are vetted with the
 >> server release and are available when the server release is
 >> available.  The samples are really only there to show value on
top of
 >> a Geronimo server and they are tied to a specific server release (at
 >> least that is how we have managed and documented them thus far) so
 >> having

Re: [DISCUSS] Geronimo 2.1 samples - zip files

2008-03-13 Thread Donald Woods

User wouldn't have to build anything if each sample was a plug-in

Other thought, why not create a samples assembly which would create a 
zip/tar of the binaries that could be downloaded and extracted by a user 
to their location of choice.  A similar source and repo zipfile could be 
created for distributions, like we do for the server



-Donald


Joe Bohn wrote:


Many of the sample wiki entries include *.zip files in addition to 
references to the svn repo.  These *.zip files include some snapshot of 
the source as well as the javadocs, xrefs, ears/wars, and in some cases 
even wiki html (I think including the wiki content in a zip is a bad 
idea ... it will never be up to date).


Several have spoken in favor of eliminating the zips and I was initially 
inclined to remove them myself in favor of just referencing svn.


However, that means that a user must build the samples (via maven) to 
get all the stuff included in the zip.  So the user must have svn & 
maven if they want to play with the samples on Geronimo or locally work 
with the source.


One possible compromise would be enhance the build to produce the zip 
files.  These zip files would be released when the samples themselves 
are released (and stored in an m2 repo).  We could then reference the 
released zip file artifacts from the wiki entries rather than attaching 
them directly to the wiki.  The benefit would be an svn/maven free way 
to get the source and artifacts to utilize the samples on Geronimo. 
Thoughts?





smime.p7s
Description: S/MIME Cryptographic Signature


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Jason Warner
On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

> Migration samples should definitively not go into svn because the source
> environment, the start point for those apps is intended to be a different
> platform, not Geronimo. There would be no point in keeping them into svn and
> adding them as a part of the release process.


You're suggesting the migration samples exist solely in the wiki?  The makes
them a little difficult to maintain, doesn't it?


>
> However there are a whole bunch of other sample apps in the doc and are G
> specific and those are the ones we are discussing here. Or I need to start
> reading the whole thread again :P
>

That's kind of what I was getting at.  There's really two classes of samples
here and I think everyone is just lumping them together.  Maybe they aren't
doing it intentionally, but I think some people are talking from the point
of view of migration samples and some from the sample applications.



> Cheers!
> Hernan
>
> Jason Warner wrote:
> > I wasn't sure which thread to put this in, so I'll throw it in here.  So
> > far, it seems that when we've been discussing samples, we're lumping the
> > sample applications and the migration samples in together.  Is this
> > something we want to do?  In my mind, they aren't really the same and
> > shouldn't necessarily be in the same place.  AFAIK, a sample application
> > is supposed to be able to be checked out, built, and deployed on
> > geronimo straight away to highlight some feature or functionality.  The
> > migration samples, though, are meant to be fiddled with before they can
> > be deployed on Geronimo.  If we lump them all in together, how is a user
> > supposed to know which is which when browsing svn?  Would it make sense
> > to keep the migration samples in a separate space?
> >
> > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]
> > > wrote:
> >
> > David Jencks wrote:
> >  >
> >  > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
> >  >
> >  >> Joe Bohn wrote:
> >  >>> David Jencks wrote:
> >  
> >   On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
> >  
> >  > Donald Woods wrote:
> >  >> Joe Bohn wrote:
> >  >>>
> >  >>> 2) When to release the samples?  I think we should make an
> > effort
> >  >>> to release the samples concurrent with each Geronimo
> release.
> >  >>> This is important because the jsp & servlet examples are
> >  >>> referenced from within the welcome page on Geronimo.  I
> suppose
> >  >>> we could remove that reference and eliminate the need to
> > release
> >  >>> concurrently.
> >  >> why not move the samples back under geronimo/server, so they
> are
> >  >> maintained and versioned with each release and can then be
> > used as
> >  >> additional testsuite tests?  If not, releasing right after a
> >  >> server release is fine.
> >  >
> >  > I was thinking about doing this.  It seems everybody thinks
> we
> >  > should release them together anyway so what is the real value
> > with
> >  > them being split out?  Does anybody object to moving them
> > back with
> >  > the server?
> >  
> >   well, since I thought our next goal with the server build was
> to
> >   separate it into independently released plugins, I think
> > putting the
> >   samples in with the main server build would be a big step
> > backwards.
> >  >>> Well, I agree that it would appear to be a step backwards from
> that
> >  >>> perspective.  However, it would ensure the following:
> >  >>> 1) The samples would get released (not forgotten as has been
> > the case
> >  >>> with 2.1)
> >  >>> 2) The samples would be released concurrent with the Geronimo
> > release
> >  >>> so that they are available for use, education, and
> > documentation from
> >  >>> day 1.  It seems almost everybody is in favor of this.
> >  >>> 3) They could be leveraged in the testsuite tests (as Donald
> > pointed
> >  >>> out) to help validate our build and find problems earlier.
> >  >>> I fail to see too many negatives from a practical perspective
> > but I'm
> >  >>> certainly open to discussion  I want to do what is best.
> >  >>> Perhaps we need to refine our plugin strategy.  There are
> > situations
> >  >>> where it makes sense to split things apart but there are also
> >  >>> situations where it might make sense to bundle things.
> >  >>> Joe
> >  >>
> >  >> Would those folks that feel strongly about not pulling these
> samples
> >  >> back into the server repo please provide some rationale for
> their
> >  >> argument as I have done for including them?  It appears that the
> >  >> samples were removed without much thought 

Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Erik B. Craig
On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

> Migration samples should definitively not go into svn because the source
> environment, the start point for those apps is intended to be a different
> platform, not Geronimo. There would be no point in keeping them into svn and
> adding them as a part of the release process.


The idea behind this is that we should have relevant migration apps from
version X of "JEE Application Server" to Version Y of Geronimo available
very near or at the release of Geronimo version Y. It is incredibly painful
attempting to keep migration samples relatively consistent and up to date
when not in svn repository, because as is making changes requires
downloading the older zip file, extracting it, adding it to eclipse, making
changes, deleting the eclipse project files and making sure there are no
binaries present, and then re-creating the zip and uploading it to wiki.
On top of these pains, it makes it very difficult to track changes made to
migration sample apps and we start running into potential legal issues by
the possibility of hosting binaries that should not be there. I ran into a
number of questionable pieces that I removed when cleaning up and checking
in the migration samples for server version 1.0.


>
> However there are a whole bunch of other sample apps in the doc and are G
> specific and those are the ones we are discussing here. Or I need to start
> reading the whole thread again :P


Like jason has said, there are really two different sample app types, both
of which we need to come to a clear decision on.


>
> Cheers!
> Hernan
>
> Jason Warner wrote:
> > I wasn't sure which thread to put this in, so I'll throw it in here.  So
> > far, it seems that when we've been discussing samples, we're lumping the
> > sample applications and the migration samples in together.  Is this
> > something we want to do?  In my mind, they aren't really the same and
> > shouldn't necessarily be in the same place.  AFAIK, a sample application
> > is supposed to be able to be checked out, built, and deployed on
> > geronimo straight away to highlight some feature or functionality.  The
> > migration samples, though, are meant to be fiddled with before they can
> > be deployed on Geronimo.  If we lump them all in together, how is a user
> > supposed to know which is which when browsing svn?  Would it make sense
> > to keep the migration samples in a separate space?
> >
> > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]
> > > wrote:
> >
> > David Jencks wrote:
> >  >
> >  > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
> >  >
> >  >> Joe Bohn wrote:
> >  >>> David Jencks wrote:
> >  
> >   On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
> >  
> >  > Donald Woods wrote:
> >  >> Joe Bohn wrote:
> >  >>>
> >  >>> 2) When to release the samples?  I think we should make an
> > effort
> >  >>> to release the samples concurrent with each Geronimo
> release.
> >  >>> This is important because the jsp & servlet examples are
> >  >>> referenced from within the welcome page on Geronimo.  I
> suppose
> >  >>> we could remove that reference and eliminate the need to
> > release
> >  >>> concurrently.
> >  >> why not move the samples back under geronimo/server, so they
> are
> >  >> maintained and versioned with each release and can then be
> > used as
> >  >> additional testsuite tests?  If not, releasing right after a
> >  >> server release is fine.
> >  >
> >  > I was thinking about doing this.  It seems everybody thinks
> we
> >  > should release them together anyway so what is the real value
> > with
> >  > them being split out?  Does anybody object to moving them
> > back with
> >  > the server?
> >  
> >   well, since I thought our next goal with the server build was
> to
> >   separate it into independently released plugins, I think
> > putting the
> >   samples in with the main server build would be a big step
> > backwards.
> >  >>> Well, I agree that it would appear to be a step backwards from
> that
> >  >>> perspective.  However, it would ensure the following:
> >  >>> 1) The samples would get released (not forgotten as has been
> > the case
> >  >>> with 2.1)
> >  >>> 2) The samples would be released concurrent with the Geronimo
> > release
> >  >>> so that they are available for use, education, and
> > documentation from
> >  >>> day 1.  It seems almost everybody is in favor of this.
> >  >>> 3) They could be leveraged in the testsuite tests (as Donald
> > pointed
> >  >>> out) to help validate our build and find problems earlier.
> >  >>> I fail to see too many negatives from a practical perspective
> > but 

Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread Jarek Gawor
Ok, but still, this is weird. geronimo-deploy-jsr88 already gets
geronimo-common through geronimo-system module.

Also, just running testsuites (testsuites checked out from svn) and
relying on other components to be pulled in (from remote repos) seems
bad. There is a great chance that the testsuites in svn and the
published components will be out of synch (especially since I don't
think we publish Geronimo snapshots regularly). But maybe you have
your own repo which contains up-to-date G components.

Jarek

On Thu, Mar 13, 2008 at 3:33 PM, Donald Woods <[EMAIL PROTECTED]> wrote:
> I'm starting with a clean local repo and only running "mvn install" from
>  under the testsuite subdir, as to run a "clean" BVT based on the
>  artifacts in the hosted repos
>
>  I believe the daily build script always runs the testsuite after the
>  server builds completes, right?  So the local repo is already populated
>  with all the depends
>
>
>  -Donald
>
>
>
>
>  Jarek Gawor wrote:
>  > Donald,
>  >
>  > I don't understand. How are you building the code? The automatic
>  > builds are always done with a clean repo and we don't see builds
>  > failing with any missing dependency error.
>  >
>  > Jarek
>  >
>  > On Thu, Mar 13, 2008 at 3:21 PM,  <[EMAIL PROTECTED]> wrote:
>  >> Author: dwoods
>  >>  Date: Thu Mar 13 12:21:46 2008
>  >>  New Revision: 636845
>  >>
>  >>  URL: http://svn.apache.org/viewvc?rev=636845&view=rev
>  >>  Log:
>  >>  found another depend missing by running testsuite with a clean repo
>  >>
>  >>  Modified:
>  >> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml
>  >>
>  >>  Modified: 
> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml
>  >>  URL: 
> http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml?rev=636845&r1=636844&r2=636845&view=diff
>  >>  
> ==
>  >>  --- 
> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml 
> (original)
>  >>  +++ 
> geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml Thu Mar 
> 13 12:21:46 2008
>  >>  @@ -40,6 +40,12 @@
>  >>
>  >>  
>  >>  org.apache.geronimo.framework
>  >>  +geronimo-common
>  >>  +${version}
>  >>  +
>  >>  +
>  >>  +
>  >>  +org.apache.geronimo.framework
>  >>  geronimo-plugin
>  >>  ${version}
>  >>  
>  >>
>  >>
>  >>
>  >
>


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Hernan Cunico

Well, from the wiki -> Geronimo documentation, there are 3main sets of samples, 
well actually 3 now.

1- Migration samples
2- Sample applicaitons
3- Tutorials

1- Migration samples. These should not be in svn unless we plan to maintain and 
test sample applications that are intended for JBoss, WebLogic, WAS, Tomcat or 
any other platform we want to explain how to migrate from. It could potentially 
include the need to maintain features/technologies we do not support or may 
never support.

2- Sample applications. These are the one I think we are talking about. These 
are intended to show the different feature implementations in Geronimo and the 
ones we want to vote one, keep up to date, etc...

3- Tutorials. So far, all using eclipse and GEP. No necessarily referring to 
any existing sample app. The whole point of this section, and why it's kept 
separate from the samples, is that you'll start from scratch, create a new 
project and anything that goes in is made by you (at most some copy paste from 
the doc to save some time)

Cheers!
Hernan

Jason Warner wrote:



On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico <[EMAIL PROTECTED] 
> wrote:


Migration samples should definitively not go into svn because the
source environment, the start point for those apps is intended to be
a different platform, not Geronimo. There would be no point in
keeping them into svn and adding them as a part of the release process.

 
You're suggesting the migration samples exist solely in the wiki?  The 
makes them a little difficult to maintain, doesn't it?
 



However there are a whole bunch of other sample apps in the doc and
are G specific and those are the ones we are discussing here. Or I
need to start reading the whole thread again :P


That's kind of what I was getting at.  There's really two classes of 
samples here and I think everyone is just lumping them together.  Maybe 
they aren't doing it intentionally, but I think some people are talking 
from the point of view of migration samples and some from the sample 
applications.




Cheers!
Hernan

Jason Warner wrote:
 > I wasn't sure which thread to put this in, so I'll throw it in
here.  So
 > far, it seems that when we've been discussing samples, we're
lumping the
 > sample applications and the migration samples in together.  Is this
 > something we want to do?  In my mind, they aren't really the same and
 > shouldn't necessarily be in the same place.  AFAIK, a sample
application
 > is supposed to be able to be checked out, built, and deployed on
 > geronimo straight away to highlight some feature or
functionality.  The
 > migration samples, though, are meant to be fiddled with before
they can
 > be deployed on Geronimo.  If we lump them all in together, how is
a user
 > supposed to know which is which when browsing svn?  Would it make
sense
 > to keep the migration samples in a separate space?
 >
 > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]

 > >> wrote:
 >
 > David Jencks wrote:
 >  >
 >  > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
 >  >
 >  >> Joe Bohn wrote:
 >  >>> David Jencks wrote:
 >  
 >   On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
 >  
 >  > Donald Woods wrote:
 >  >> Joe Bohn wrote:
 >  >>>
 >  >>> 2) When to release the samples?  I think we should
make an
 > effort
 >  >>> to release the samples concurrent with each Geronimo
release.
 >  >>> This is important because the jsp & servlet examples are
 >  >>> referenced from within the welcome page on Geronimo.
 I suppose
 >  >>> we could remove that reference and eliminate the need to
 > release
 >  >>> concurrently.
 >  >> why not move the samples back under geronimo/server,
so they are
 >  >> maintained and versioned with each release and can
then be
 > used as
 >  >> additional testsuite tests?  If not, releasing right
after a
 >  >> server release is fine.
 >  >
 >  > I was thinking about doing this.  It seems everybody
thinks we
 >  > should release them together anyway so what is the
real value
 > with
 >  > them being split out?  Does anybody object to moving them
 > back with
 >  > the server?
 >  
 >   well, since I thought our next goal with the server
build was to
 >   separate it into independently released plugins, I think
 > putting the
 >   samples in with the main server build would be a big step
 >  

Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Jason Warner
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

> Well, from the wiki -> Geronimo documentation, there are 3main sets of
> samples, well actually 3 now.
>
> 1- Migration samples
> 2- Sample applicaitons
> 3- Tutorials
>
> 1- Migration samples. These should not be in svn unless we plan to
> maintain and test sample applications that are intended for JBoss, WebLogic,
> WAS, Tomcat or any other platform we want to explain how to migrate from. It
> could potentially include the need to maintain features/technologies we do
> not support or may never support.
>

Isn't that what's already occurring?  I believe the migration samples have
applications attached to them that are designed for JBoss and the sample
explains how to convert it to Geronimo.  These would need to be updated
based on the changes that occur both in JBoss and Geronimo.


> 2- Sample applications. These are the one I think we are talking about.
> These are intended to show the different feature implementations in Geronimo
> and the ones we want to vote one, keep up to date, etc...


I know that Erik at least is talking about Migration samples as well.  Other
than that, no argument here.


>
> 3- Tutorials. So far, all using eclipse and GEP. No necessarily referring
> to any existing sample app. The whole point of this section, and why it's
> kept separate from the samples, is that you'll start from scratch, create a
> new project and anything that goes in is made by you (at most some copy
> paste from the doc to save some time)


I don't count tutorials in the same area as samples since no application is
involved, but that's just semantics. ;)

Thanks!


>
>
> Cheers!
> Hernan
>
> Jason Warner wrote:
> >
> >
> > On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico <[EMAIL PROTECTED]
> > > wrote:
> >
> > Migration samples should definitively not go into svn because the
> > source environment, the start point for those apps is intended to be
> > a different platform, not Geronimo. There would be no point in
> > keeping them into svn and adding them as a part of the release
> process.
> >
> >
> > You're suggesting the migration samples exist solely in the wiki?  The
> > makes them a little difficult to maintain, doesn't it?
> >
> >
> >
> > However there are a whole bunch of other sample apps in the doc and
> > are G specific and those are the ones we are discussing here. Or I
> > need to start reading the whole thread again :P
> >
> >
> > That's kind of what I was getting at.  There's really two classes of
> > samples here and I think everyone is just lumping them together.  Maybe
> > they aren't doing it intentionally, but I think some people are talking
> > from the point of view of migration samples and some from the sample
> > applications.
> >
> >
> >
> > Cheers!
> > Hernan
> >
> > Jason Warner wrote:
> >  > I wasn't sure which thread to put this in, so I'll throw it in
> > here.  So
> >  > far, it seems that when we've been discussing samples, we're
> > lumping the
> >  > sample applications and the migration samples in together.  Is
> this
> >  > something we want to do?  In my mind, they aren't really the same
> and
> >  > shouldn't necessarily be in the same place.  AFAIK, a sample
> > application
> >  > is supposed to be able to be checked out, built, and deployed on
> >  > geronimo straight away to highlight some feature or
> > functionality.  The
> >  > migration samples, though, are meant to be fiddled with before
> > they can
> >  > be deployed on Geronimo.  If we lump them all in together, how is
> > a user
> >  > supposed to know which is which when browsing svn?  Would it make
> > sense
> >  > to keep the migration samples in a separate space?
> >  >
> >  > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]
> > 
> >  > >> wrote:
> >  >
> >  > David Jencks wrote:
> >  >  >
> >  >  > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
> >  >  >
> >  >  >> Joe Bohn wrote:
> >  >  >>> David Jencks wrote:
> >  >  
> >  >   On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
> >  >  
> >  >  > Donald Woods wrote:
> >  >  >> Joe Bohn wrote:
> >  >  >>>
> >  >  >>> 2) When to release the samples?  I think we should
> > make an
> >  > effort
> >  >  >>> to release the samples concurrent with each Geronimo
> > release.
> >  >  >>> This is important because the jsp & servlet examples
> are
> >  >  >>> referenced from within the welcome page on Geronimo.
> >  I suppose
> >  >  >>> we could remove that reference and eliminate the
> need to
> >  > release
> >  >  >>> concurre

Re: [DISCUSS] Geronimo 2.1 samples - zip files

2008-03-13 Thread Joe Bohn

Donald Woods wrote:

User wouldn't have to build anything if each sample was a plug-in


That would be true if the value in a sample just in running it. 
However, I think most users want to dig into the source, make minor 
changes and tweak it as a way to jump start their own development. 
Sometime they are more interested in looking at the geronimo deployment 
plans and experimenting with different deploy options.  For those types 
of activities, they would need more than just a plugin ... they would 
need the source, build poms, ears/wars, deployment plans, etc




Other thought, why not create a samples assembly which would create a 
zip/tar of the binaries that could be downloaded and extracted by a user 
to their location of choice.  A similar source and repo zipfile could be 
created for distributions, like we do for the server


IIUC you are suggesting that instead of changing the build to generate a 
zip per sample we generate 1 zip for all of the samples.  We wouldn't 
need an assembly to do that, we could just do it manually like we do for 
the server today when we release it.  That might be ok, but at the 
moment our wiki doc explains each sample individually and I can image 
cases where the user doesn't necessarily want or need all of the sample 
content.  I think we are both on the same line regarding generating the 
zip.  If it is just 1 zip file then it can be manually created when we 
release.  But if we want to keep one per sample it makes more sense to 
have them generated in the build.  Just my opinion.





-Donald


Joe Bohn wrote:


Many of the sample wiki entries include *.zip files in addition to 
references to the svn repo.  These *.zip files include some snapshot 
of the source as well as the javadocs, xrefs, ears/wars, and in some 
cases even wiki html (I think including the wiki content in a zip is a 
bad idea ... it will never be up to date).


Several have spoken in favor of eliminating the zips and I was 
initially inclined to remove them myself in favor of just referencing 
svn.


However, that means that a user must build the samples (via maven) to 
get all the stuff included in the zip.  So the user must have svn & 
maven if they want to play with the samples on Geronimo or locally 
work with the source.


One possible compromise would be enhance the build to produce the zip 
files.  These zip files would be released when the samples themselves 
are released (and stored in an m2 repo).  We could then reference the 
released zip file artifacts from the wiki entries rather than 
attaching them directly to the wiki.  The benefit would be an 
svn/maven free way to get the source and artifacts to utilize the 
samples on Geronimo. Thoughts?







Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Hernan Cunico

Erik B. Craig wrote:



On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico <[EMAIL PROTECTED] 
> wrote:


Migration samples should definitively not go into svn because the
source environment, the start point for those apps is intended to be
a different platform, not Geronimo. There would be no point in
keeping them into svn and adding them as a part of the release process.


The idea behind this is that we should have relevant migration apps from 
version X of "JEE Application Server" to Version Y of Geronimo available 
very near or at the release of Geronimo version Y. It is incredibly 
painful attempting to keep migration samples relatively consistent and 
up to date when not in svn repository, because as is making changes 
requires downloading the older zip file, extracting it, adding it to 
eclipse, making changes, deleting the eclipse project files and making 
sure there are no binaries present, and then re-creating the zip and 
uploading it to wiki.
On top of these pains, it makes it very difficult to track changes made 
to migration sample apps and we start running into potential legal 
issues by the possibility of hosting binaries that should not be there. 
I ran into a number of questionable pieces that I removed when cleaning 
up and checking in the migration samples for server version 1.0.


This is the thing. The issue is not the sample apps. but the approach to cover migration. 
( and here everybody has its own "best" way to do the things ;-)  )

I personally think that migration from "A" to "B" should be entirely ruled (not driven) by "A". I believe that migration should primarily be a document with some samples to support such document. Such samples should ideally be developed for/by "A" to highlight their own features and implementations. People using platform "A" may use those samples as the blueprints for developing their own applications. I think focusing around those samples (developed for/by "A") is where we get the biggest bang. 


When those apps are not available we come up with our own for "A" and then use them to support our migration 
procedure. These are the docs that could potentially make it to svn but we should treat them as "foreign" and 
make sure they are up-to-date and relevant to platform "A" and not "B". These samples would not run 
on Geronimo until you migrate them following the procedures in the doc.

Does that makes sense?

Cheers!
Hernan





However there are a whole bunch of other sample apps in the doc and
are G specific and those are the ones we are discussing here. Or I
need to start reading the whole thread again :P


Like jason has said, there are really two different sample app types, 
both of which we need to come to a clear decision on.




Cheers!
Hernan

Jason Warner wrote:
 > I wasn't sure which thread to put this in, so I'll throw it in
here.  So
 > far, it seems that when we've been discussing samples, we're
lumping the
 > sample applications and the migration samples in together.  Is this
 > something we want to do?  In my mind, they aren't really the same and
 > shouldn't necessarily be in the same place.  AFAIK, a sample
application
 > is supposed to be able to be checked out, built, and deployed on
 > geronimo straight away to highlight some feature or
functionality.  The
 > migration samples, though, are meant to be fiddled with before
they can
 > be deployed on Geronimo.  If we lump them all in together, how is
a user
 > supposed to know which is which when browsing svn?  Would it make
sense
 > to keep the migration samples in a separate space?
 >
 > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <[EMAIL PROTECTED]

 > >> wrote:
 >
 > David Jencks wrote:
 >  >
 >  > On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
 >  >
 >  >> Joe Bohn wrote:
 >  >>> David Jencks wrote:
 >  
 >   On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
 >  
 >  > Donald Woods wrote:
 >  >> Joe Bohn wrote:
 >  >>>
 >  >>> 2) When to release the samples?  I think we should
make an
 > effort
 >  >>> to release the samples concurrent with each Geronimo
release.
 >  >>> This is important because the jsp & servlet examples are
 >  >>> referenced from within the welcome page on Geronimo.
 I suppose
 >  >>> we could remove that reference and eliminate the need to
 > release
 >  >>> concurrently.
 >  >> why not move the samples back under geronimo/server,
so they are
 >  >> maintained and versioned with each release and can
then be
 > used as
 >  >> additional testsuite tests?  If not, rel

Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Erik B. Craig
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner <[EMAIL PROTECTED]> wrote:

>
>
> On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:
>
> > Well, from the wiki -> Geronimo documentation, there are 3main sets of
> > samples, well actually 3 now.
> >
> > 1- Migration samples
> > 2- Sample applicaitons
> > 3- Tutorials
> >
> > 1- Migration samples. These should not be in svn unless we plan to
> > maintain and test sample applications that are intended for JBoss, WebLogic,
> > WAS, Tomcat or any other platform we want to explain how to migrate from. It
> > could potentially include the need to maintain features/technologies we do
> > not support or may never support.
> >
>
> Isn't that what's already occurring?  I believe the migration samples have
> applications attached to them that are designed for JBoss and the sample
> explains how to convert it to Geronimo.  These would need to be updated
> based on the changes that occur both in JBoss and Geronimo.
>

Correct, this is what I'm working on because they haven't been really kept
up to date - and we don't want to get burned by someone trying to get
something going or migrated that we say we have support for but have no
supporting documentation or samples.
When rewriting sample apps and documentation for 2.0, they are all meant to
go from jboss to geronimo. The process involves validating functionality on
the latest JBoss release (4.2.2GA in that case), updating documentation
where necessary, updating code where necessary, and then ensuring the
migration steps are still valid, and making changes to both documentation
and code where needed.


>
>
>
> > 2- Sample applications. These are the one I think we are talking about.
> > These are intended to show the different feature implementations in Geronimo
> > and the ones we want to vote one, keep up to date, etc...
>
>
> I know that Erik at least is talking about Migration samples as well.
> Other than that, no argument here.
>
>
> >
> > 3- Tutorials. So far, all using eclipse and GEP. No necessarily
> > referring to any existing sample app. The whole point of this section, and
> > why it's kept separate from the samples, is that you'll start from scratch,
> > create a new project and anything that goes in is made by you (at most some
> > copy paste from the doc to save some time)
>
>
> I don't count tutorials in the same area as samples since no application
> is involved, but that's just semantics. ;)
>
> Thanks!
>
>
> >
> >
> > Cheers!
> > Hernan
> >
> > Jason Warner wrote:
> > >
> > >
> > > On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico <[EMAIL PROTECTED]
> > > > wrote:
> > >
> > > Migration samples should definitively not go into svn because the
> > > source environment, the start point for those apps is intended to
> > be
> > > a different platform, not Geronimo. There would be no point in
> > > keeping them into svn and adding them as a part of the release
> > process.
> > >
> > >
> > > You're suggesting the migration samples exist solely in the wiki?  The
> > > makes them a little difficult to maintain, doesn't it?
> > >
> > >
> > >
> > > However there are a whole bunch of other sample apps in the doc
> > and
> > > are G specific and those are the ones we are discussing here. Or I
> > > need to start reading the whole thread again :P
> > >
> > >
> > > That's kind of what I was getting at.  There's really two classes of
> > > samples here and I think everyone is just lumping them together.
> >  Maybe
> > > they aren't doing it intentionally, but I think some people are
> > talking
> > > from the point of view of migration samples and some from the sample
> > > applications.
> > >
> > >
> > >
> > > Cheers!
> > > Hernan
> > >
> > > Jason Warner wrote:
> > >  > I wasn't sure which thread to put this in, so I'll throw it in
> > > here.  So
> > >  > far, it seems that when we've been discussing samples, we're
> > > lumping the
> > >  > sample applications and the migration samples in together.  Is
> > this
> > >  > something we want to do?  In my mind, they aren't really the
> > same and
> > >  > shouldn't necessarily be in the same place.  AFAIK, a sample
> > > application
> > >  > is supposed to be able to be checked out, built, and deployed
> > on
> > >  > geronimo straight away to highlight some feature or
> > > functionality.  The
> > >  > migration samples, though, are meant to be fiddled with before
> > > they can
> > >  > be deployed on Geronimo.  If we lump them all in together, how
> > is
> > > a user
> > >  > supposed to know which is which when browsing svn?  Would it
> > make
> > > sense
> > >  > to keep the migration samples in a separate space?
> > >  >
> > >  > On Thu, Mar 13, 2008 at 3:13 PM, Hernan Cunico <
> > [EMAIL PROTECTED]
> > > 
> > >  > >

[jira] Updated: (GERONIMO-3916) proxy connection does not capture the successful connection events

2008-03-13 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated GERONIMO-3916:
--

Attachment: GERONIMO-3916.patch

A suggested fix...

> proxy connection does not capture the successful connection events
> --
>
> Key: GERONIMO-3916
> URL: https://issues.apache.org/jira/browse/GERONIMO-3916
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: AsyncHttpClient
>Affects Versions: 1.x
>Reporter: Sangjin Lee
>Assignee: Rick McGuire
>Priority: Minor
> Attachments: GERONIMO-3916.patch
>
>
> AsyncHttpClient emits monitoring events, and CONNECTION_SUCCESSFUL is emitted 
> when we have a connected session.  However, the CONNECTION_SUCCESSFUL event 
> is not emitted for a proxied connection.  See 
> ProxyFutureListener.operationComplete()...

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



Re: [DISCUSS] Geronimo 2.1 samples - zip files

2008-03-13 Thread Donald Woods



Joe Bohn wrote:

Donald Woods wrote:

User wouldn't have to build anything if each sample was a plug-in


That would be true if the value in a sample just in running it. However, 
I think most users want to dig into the source, make minor changes and 
tweak it as a way to jump start their own development. Sometime they are 
more interested in looking at the geronimo deployment plans and 
experimenting with different deploy options.  For those types of 
activities, they would need more than just a plugin ... they would need 
the source, build poms, ears/wars, deployment plans, etc




You could always include the source in the generated war/ear artifact.



Other thought, why not create a samples assembly which would create a 
zip/tar of the binaries that could be downloaded and extracted by a 
user to their location of choice.  A similar source and repo zipfile 
could be created for distributions, like we do for the server


IIUC you are suggesting that instead of changing the build to generate a 
zip per sample we generate 1 zip for all of the samples.  We wouldn't 
need an assembly to do that, we could just do it manually like we do for 
the server today when we release it.  That might be ok, but at the 
moment our wiki doc explains each sample individually and I can image 
cases where the user doesn't necessarily want or need all of the sample 
content.  I think we are both on the same line regarding generating the 
zip.  If it is just 1 zip file then it can be manually created when we 
release.  But if we want to keep one per sample it makes more sense to 
have them generated in the build.  Just my opinion.




yep, trying to minimize difference from the sever releases





-Donald


Joe Bohn wrote:


Many of the sample wiki entries include *.zip files in addition to 
references to the svn repo.  These *.zip files include some snapshot 
of the source as well as the javadocs, xrefs, ears/wars, and in some 
cases even wiki html (I think including the wiki content in a zip is 
a bad idea ... it will never be up to date).


Several have spoken in favor of eliminating the zips and I was 
initially inclined to remove them myself in favor of just referencing 
svn.


However, that means that a user must build the samples (via maven) to 
get all the stuff included in the zip.  So the user must have svn & 
maven if they want to play with the samples on Geronimo or locally 
work with the source.


One possible compromise would be enhance the build to produce the zip 
files.  These zip files would be released when the samples themselves 
are released (and stored in an m2 repo).  We could then reference the 
released zip file artifacts from the wiki entries rather than 
attaching them directly to the wiki.  The benefit would be an 
svn/maven free way to get the source and artifacts to utilize the 
samples on Geronimo. Thoughts?








smime.p7s
Description: S/MIME Cryptographic Signature


[BUILD] branches/2.1: Failed for Revision: 636812

2008-03-13 Thread gawor
Geronimo Revision: 636812 built with tests included
 
See the full build-1400.log file at 
http://geronimo.apache.org/maven/server/binaries/2.1/20080313/build-1400.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/2.1/20080313
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 35 minutes 49 seconds
[INFO] Finished at: Thu Mar 13 14:58:30 EDT 2008
[INFO] Final Memory: 347M/914M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/2.1/20080313/logs-1400-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/2.1/20080313/logs-1400-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 76.584 
sec <<< FAILURE!
 
Samples: branches/2.1
=
Log: 
http://geronimo.apache.org/maven/server/binaries/2.1/20080313/samples-1400.log
 
Build status: OK
 


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Hernan Cunico


Erik B. Craig wrote:



On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner <[EMAIL PROTECTED] 
> wrote:




On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico <[EMAIL PROTECTED]
> wrote:

Well, from the wiki -> Geronimo documentation, there are 3main
sets of samples, well actually 3 now.

1- Migration samples
2- Sample applications
3- Tutorials

1- Migration samples. These should not be in svn unless we plan
to maintain and test sample applications that are intended for
JBoss, WebLogic, WAS, Tomcat or any other platform we want to
explain how to migrate from. It could potentially include the
need to maintain features/technologies we do not support or may
never support.


Isn't that what's already occurring?  I believe the migration
samples have applications attached to them that are designed for
JBoss and the sample explains how to convert it to Geronimo.  These
would need to be updated based on the changes that occur both in
JBoss and Geronimo.


Correct, this is what I'm working on because they haven't been really 
kept up to date - and we don't want to get burned by someone trying to 
get something going or migrated that we say we have support for but have 
no supporting documentation or samples.
When rewriting sample apps and documentation for 2.0, they are all meant 
to go from jboss to geronimo. The process involves validating 
functionality on the latest JBoss release (4.2.2GA in that case), 
updating documentation where necessary, updating code where necessary, 
and then ensuring the migration steps are still valid, and making 
changes to both documentation and code where needed.
 


Ok, so we all know what it'll take and agree to carry on with this. Then we 
should figure out a way to link what's on svn and the corresponding doc.
Confluence still does not support svn so I haven't figured out an alternative 
way to ensure they are in sync. Any idea?

Cheers!
Hernan



  ...   




Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Erik B. Craig
On Thu, Mar 13, 2008 at 3:32 PM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

>
> Erik B. Craig wrote:
> >
> >
> > On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> >
> > On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico <[EMAIL PROTECTED]
> > > wrote:
> >
> > Well, from the wiki -> Geronimo documentation, there are 3main
> > sets of samples, well actually 3 now.
> >
> > 1- Migration samples
> > 2- Sample applications
> > 3- Tutorials
> >
> > 1- Migration samples. These should not be in svn unless we plan
> > to maintain and test sample applications that are intended for
> > JBoss, WebLogic, WAS, Tomcat or any other platform we want to
> > explain how to migrate from. It could potentially include the
> > need to maintain features/technologies we do not support or may
> > never support.
> >
> >
> > Isn't that what's already occurring?  I believe the migration
> > samples have applications attached to them that are designed for
> > JBoss and the sample explains how to convert it to Geronimo.  These
> > would need to be updated based on the changes that occur both in
> > JBoss and Geronimo.
> >
> >
> > Correct, this is what I'm working on because they haven't been really
> > kept up to date - and we don't want to get burned by someone trying to
> > get something going or migrated that we say we have support for but have
> > no supporting documentation or samples.
> > When rewriting sample apps and documentation for 2.0, they are all meant
> > to go from jboss to geronimo. The process involves validating
> > functionality on the latest JBoss release (4.2.2GA in that case),
> > updating documentation where necessary, updating code where necessary,
> > and then ensuring the migration steps are still valid, and making
> > changes to both documentation and code where needed.
> >
>
> Ok, so we all know what it'll take and agree to carry on with this. Then
> we should figure out a way to link what's on svn and the corresponding doc.
> Confluence still does not support svn so I haven't figured out an
> alternative way to ensure they are in sync. Any idea?
>

Well, as far as that goes I have came up with two solutions...
1. Reference a branch or tag and document checking the code out via SVN and
have this in the step-by-step in the document

2. Release versions as archives of the source code, that can be published
much as we do with the server and server sources, and linked to this in the
wiki articles


>
> Cheers!
> Hernan
>
> >
> >   ...
>
>


-- 
Erik B. Craig


Re: [DISCUSS] Geronimo 2.1.1 release

2008-03-13 Thread Joe Bohn
Ok, so here is the list of things that I think were mentioned for 
inclusion in a 2.1.1 release (those that were not already complete when 
this discussion began).


Am I missing anything from the required list or are there items that 
should move up from the Optional list (or down from required)?


My take is that once we have everything under "Required" completed we 
can start the release process.  Anything from the Optional list that can 
make it in is gravy.  We need to decide when to start to lock things 
down, but in general I think we all know that we are getting close so 
please be careful what goes into the 2.1 branch now.




Required:
- GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. - 
There are patches integrated for this.  Is there more to be done?  Joe Leong
- GERONIMO-3871 archetypes for plugin and assembly. - David has already 
completed this.

- GERONIMO-3898 log4j app config gbean. - David has already completed this.
- GERONIMO-3902 start-server overrides. - Jason are you posting a patch 
for this?
- GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated 
a fix - outstanding question by Jarek
- GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated 
this ... not sure if there is more work remaining.

- GERONIMO-3858 start-server.bat fails if space in dir - no owner
- GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi 
assigned, still open
- GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned.  I'm 
not convinced this is a "must-have".
- GERONIMO-3887 bad config install for plugin causes new installs to 
fail. Joe Leong - are you planning to provide a patch?  I'm not 
convinced this is a "must-have"
- GERONIMO-3896 error processing HEAD method by default HttpServlet. 
David has fixed this in the servlet spec and it's up for a vote.  We 
need to update 2.1.1 to use this spec when final.
- GERONIMO-3906 start-server uses hard-coded credentials.  This seems 
important.  Is anybody working on this (nobody is assigned).

- GERONIMO-3918 upgrade to WADI 2.0-M9.  Donald has already completed this.




Optional:
- leverage genesis 1.4
- OpenEJB 3.0 - currently up for a vote - looks promising.  I will give 
it a try with 2.1.1-SNAPSHOT.  I think this should possibly move up to 
required (assuming no big issues are found).

- GERONIMO-3432 console wizard to generate openejb-jar.xml
- GERONIMO-3503 db pool wizard creates plans only for local-transactions
- GERONIMO-3719 monitoring agent uses sun classes
- GERONIMO-3759 tomcat clustering, no gbeans for adding static members
- GERONIMO-3783 mdb delivery problem - this seems kinda important - 
should we move it up?

- GERONIMO-3806 extraneous warning messages for ejb resource-env-def deploy
- GERONIMO-3811 ejb server portlet
- GERONIMO-3814 NPE in GBeanOverride
- GERONIMO-3819 updates to JMS resource portlet
- GERONIMO-3823 document the SystemPropertyGBean
- GERONIMO-3879 webaccess log viewer with multiple server instances has 
issues.

- GERONIMO-3900 runtime support for non-Sun JVMs.
- GERONIMO-3901 security realms portlet missing encoding option


Joe


[BUILD] trunk: Failed for Revision: 636841

2008-03-13 Thread gawor
Geronimo Revision: 636841 built with tests included
 
See the full build-1500.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/build-1500.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 31 minutes 12 seconds
[INFO] Finished at: Thu Mar 13 15:38:42 EDT 2008
[INFO] Final Memory: 307M/943M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/logs-1500-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/logs-1500-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.634 
sec <<< FAILURE!
 
Samples: trunk
=
Log: 
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/samples-1500.log
 
Build status: OK
 


Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread David Jencks
Plus this change shouldn't affect any of the information geronimo  
uses when installing plugins etc.  Please show the error you get.


thanks
david jencks

On Mar 13, 2008, at 12:54 PM, Jarek Gawor wrote:


Ok, but still, this is weird. geronimo-deploy-jsr88 already gets
geronimo-common through geronimo-system module.

Also, just running testsuites (testsuites checked out from svn) and
relying on other components to be pulled in (from remote repos) seems
bad. There is a great chance that the testsuites in svn and the
published components will be out of synch (especially since I don't
think we publish Geronimo snapshots regularly). But maybe you have
your own repo which contains up-to-date G components.

Jarek

On Thu, Mar 13, 2008 at 3:33 PM, Donald Woods <[EMAIL PROTECTED]>  
wrote:
I'm starting with a clean local repo and only running "mvn  
install" from

 under the testsuite subdir, as to run a "clean" BVT based on the
 artifacts in the hosted repos

 I believe the daily build script always runs the testsuite after the
 server builds completes, right?  So the local repo is already  
populated

 with all the depends


 -Donald




 Jarek Gawor wrote:

Donald,

I don't understand. How are you building the code? The automatic
builds are always done with a clean repo and we don't see builds
failing with any missing dependency error.

Jarek

On Thu, Mar 13, 2008 at 3:21 PM,  <[EMAIL PROTECTED]> wrote:

Author: dwoods
 Date: Thu Mar 13 12:21:46 2008
 New Revision: 636845

 URL: http://svn.apache.org/viewvc?rev=636845&view=rev
 Log:
 found another depend missing by running testsuite with a clean  
repo


 Modified:
geronimo/server/trunk/framework/modules/geronimo-deploy- 
jsr88/pom.xml


 Modified: geronimo/server/trunk/framework/modules/geronimo- 
deploy-jsr88/pom.xml
 URL: http://svn.apache.org/viewvc/geronimo/server/trunk/ 
framework/modules/geronimo-deploy-jsr88/pom.xml? 
rev=636845&r1=636844&r2=636845&view=diff
  
=== 
===
 --- geronimo/server/trunk/framework/modules/geronimo-deploy- 
jsr88/pom.xml (original)
 +++ geronimo/server/trunk/framework/modules/geronimo-deploy- 
jsr88/pom.xml Thu Mar 13 12:21:46 2008

 @@ -40,6 +40,12 @@

 
 org.apache.geronimo.framework
 +geronimo-common
 +${version}
 +
 +
 +
 +org.apache.geronimo.framework
 geronimo-plugin
 ${version}
 











Re: [DISCUSS] Geronimo 2.1.1 release

2008-03-13 Thread David Jencks


On Mar 13, 2008, at 2:08 PM, Joe Bohn wrote:

Ok, so here is the list of things that I think were mentioned for  
inclusion in a 2.1.1 release (those that were not already complete  
when this discussion began).


Am I missing anything from the required list or are there items  
that should move up from the Optional list (or down from required)?


My take is that once we have everything under "Required" completed  
we can start the release process.  Anything from the Optional list  
that can make it in is gravy.  We need to decide when to start to  
lock things down, but in general I think we all know that we are  
getting close so please be careful what goes into the 2.1 branch now.




Required:
- GERONIMO-3781 PluginInstaller CRSF when installing a new plugin.  
- There are patches integrated for this.  Is there more to be  
done?  Joe Leong
- GERONIMO-3871 archetypes for plugin and assembly. - David has  
already completed this.
- GERONIMO-3898 log4j app config gbean. - David has already  
completed this.
- GERONIMO-3902 start-server overrides. - Jason are you posting a  
patch for this?
- GERONIMO-3833 monitoring hard coded gbean names. - Viet has  
integrated a fix - outstanding question by Jarek
- GERONIMO-3837 configure allowLinking attribute - Vamsi has  
integrated this ... not sure if there is more work remaining.

- GERONIMO-3858 start-server.bat fails if space in dir - no owner
- GERONIMO-3875 Derby authentication breaks DB viewer portlet. -  
Vamsi assigned, still open
- GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned.   
I'm not convinced this is a "must-have".
Not a must have but very nice.  I thought he'd pretty much figured  
out how to do it -- if he's run out of time I can give some hints or  
do it myself.
- GERONIMO-3887 bad config install for plugin causes new installs  
to fail. Joe Leong - are you planning to provide a patch?  I'm not  
convinced this is a "must-have"
I'm not sure it's practical to fix this without a big change in the  
plugin mechanism.  I don't think it's a must-have.
- GERONIMO-3896 error processing HEAD method by default  
HttpServlet. David has fixed this in the servlet spec and it's up  
for a vote.  We need to update 2.1.1 to use this spec when final.
- GERONIMO-3906 start-server uses hard-coded credentials.  This  
seems important.  Is anybody working on this (nobody is assigned).
- GERONIMO-3918 upgrade to WADI 2.0-M9.  Donald has already  
completed this.





Optional:
- leverage genesis 1.4
- OpenEJB 3.0 - currently up for a vote - looks promising.  I will  
give it a try with 2.1.1-SNAPSHOT.  I think this should possibly  
move up to required (assuming no big issues are found).

- GERONIMO-3432 console wizard to generate openejb-jar.xml
- GERONIMO-3503 db pool wizard creates plans only for local- 
transactions

- GERONIMO-3719 monitoring agent uses sun classes
- GERONIMO-3759 tomcat clustering, no gbeans for adding static members
- GERONIMO-3783 mdb delivery problem - this seems kinda important -  
should we move it up?
It's not clear yet that this one is a bug.  There is https:// 
issues.apache.org/activemq/browse/AMQ-1618 which I'm going to try to  
get into amq shortly, but getting a release out may not be too quick.


- GERONIMO-3806 extraneous warning messages for ejb resource-env- 
def deploy

- GERONIMO-3811 ejb server portlet
- GERONIMO-3814 NPE in GBeanOverride
- GERONIMO-3819 updates to JMS resource portlet
- GERONIMO-3823 document the SystemPropertyGBean
- GERONIMO-3879 webaccess log viewer with multiple server instances  
has issues.

- GERONIMO-3900 runtime support for non-Sun JVMs.
- GERONIMO-3901 security realms portlet missing encoding option


Thanks very much for tracking this!
david jencks



Joe




Re: [DISCUSS] Geronimo 2.1.1 release

2008-03-13 Thread Hernan Cunico

I would like add to the *Required* having a little bit more complete v2.1 
documentation.

There are still a lot of topics to cover (from scratch) and to verify carried 
over content from previous releases.

Cheers!
Hernan

Joe Bohn wrote:
Ok, so here is the list of things that I think were mentioned for 
inclusion in a 2.1.1 release (those that were not already complete when 
this discussion began).


Am I missing anything from the required list or are there items that 
should move up from the Optional list (or down from required)?


My take is that once we have everything under "Required" completed we 
can start the release process.  Anything from the Optional list that can 
make it in is gravy.  We need to decide when to start to lock things 
down, but in general I think we all know that we are getting close so 
please be careful what goes into the 2.1 branch now.




Required:
- GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. - 
There are patches integrated for this.  Is there more to be done?  Joe 
Leong
- GERONIMO-3871 archetypes for plugin and assembly. - David has already 
completed this.

- GERONIMO-3898 log4j app config gbean. - David has already completed this.
- GERONIMO-3902 start-server overrides. - Jason are you posting a patch 
for this?
- GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated 
a fix - outstanding question by Jarek
- GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated 
this ... not sure if there is more work remaining.

- GERONIMO-3858 start-server.bat fails if space in dir - no owner
- GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi 
assigned, still open
- GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned.  I'm 
not convinced this is a "must-have".
- GERONIMO-3887 bad config install for plugin causes new installs to 
fail. Joe Leong - are you planning to provide a patch?  I'm not 
convinced this is a "must-have"
- GERONIMO-3896 error processing HEAD method by default HttpServlet. 
David has fixed this in the servlet spec and it's up for a vote.  We 
need to update 2.1.1 to use this spec when final.
- GERONIMO-3906 start-server uses hard-coded credentials.  This seems 
important.  Is anybody working on this (nobody is assigned).

- GERONIMO-3918 upgrade to WADI 2.0-M9.  Donald has already completed this.




Optional:
- leverage genesis 1.4
- OpenEJB 3.0 - currently up for a vote - looks promising.  I will give 
it a try with 2.1.1-SNAPSHOT.  I think this should possibly move up to 
required (assuming no big issues are found).

- GERONIMO-3432 console wizard to generate openejb-jar.xml
- GERONIMO-3503 db pool wizard creates plans only for local-transactions
- GERONIMO-3719 monitoring agent uses sun classes
- GERONIMO-3759 tomcat clustering, no gbeans for adding static members
- GERONIMO-3783 mdb delivery problem - this seems kinda important - 
should we move it up?

- GERONIMO-3806 extraneous warning messages for ejb resource-env-def deploy
- GERONIMO-3811 ejb server portlet
- GERONIMO-3814 NPE in GBeanOverride
- GERONIMO-3819 updates to JMS resource portlet
- GERONIMO-3823 document the SystemPropertyGBean
- GERONIMO-3879 webaccess log viewer with multiple server instances has 
issues.

- GERONIMO-3900 runtime support for non-Sun JVMs.
- GERONIMO-3901 security realms portlet missing encoding option


Joe



Generated NOTICE files.... a solution

2008-03-13 Thread David Jencks
As I noted in a previous thread the current NOTICE files generated by  
the apache-jar-resource-bundle 1.3 are not consistent with apache  
policy.  After some discussion on legal-discuss I've come up with a  
bundle that no one seems to be able to find anything seriously wrong  
with: we're starting to use it in geronimo.


Aside from possible use by other projects I'd like to use this in an  
upcoming ApacheDS release, so getting it quickly into a more neutral  
location would be desirable.  I've opened http://jira.codehaus.org/ 
browse/MRRESOURCES-32 and attached a patch.


The basic idea is that the NOTICE file contains only the required  
apache notice, with no extra text, explanation, horizontal rules, or  
anything else.  Additional required notices can be put in a NOTICE  
file in appended-resources and automatically appended.  Dependencies  
are listed in an additional generated DEPENDENCIES file, by  
organization, and listing the license.


Note that NOTICE files apply only to the exact contents of the jar in  
question, not to any dependencies that might be necessary to actually  
use the jar.  For work at apache the normal situation is that the  
minimal NOTICE is all that is required, and if more is needed its  
going to be because of some special historical circumstances that  
can't plausibly be tracked by maven, so explicitly recording this  
information in a human-written additional NOTICE file is quite  
appropriate.


There is certainly scope for some kind of aggregating bundle for  
assemblies that do actually contain stuff from other artifacts, such  
as wars, ears, tar.gzs, etc, but these are pretty clearly an entirely  
separate use case and likely to require considerably more work to get  
right.  I think starting work on a separate bundle for these might be  
appropriate.


I know of two problems in the patch, both in NOTICE.vm, and I haven't  
been able to figure out solutions to either:


- I can't get a blank line in between the project name and the notice
- I can't configure projectName in a suitable place so it shows up in  
the generated NOTICE.


Despite these problems I think this proposal is clearly more in line  
with apache policy and hope it can be accepted and released quickly.


Many thanks
david jencks



Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread Donald Woods


 [exec] [INFO] [INFO] 

 [exec] [INFO] [INFO] Building Geronimo TestSuite :: CORBA 
TestSuite :: Marshal EAR

 [exec] [INFO] [INFO]task-segment: [install]
 [exec] [INFO] [INFO] 


 [exec] [INFO] [INFO] [enforcer:enforce {execution: default}]
 [exec] [INFO] [INFO] [ear:generate-application-xml]
 [exec] [INFO] [INFO] Generating application.xml
 [exec] [INFO] [INFO] [tools:copy-legal-files {execution: 
install-legal-files}]
 [exec] [INFO] [INFO] Created dir: 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/classes/META-INF
 [exec] [INFO] [INFO] Copying 2 files to 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/classes/META-INF

 [exec] [INFO] [INFO] [resources:resources]
 [exec] [INFO] [INFO] Using default encoding to copy filtered 
resources.

 [exec] [INFO] [INFO] [ear:ear]
 [exec] [INFO] [INFO] Copying 
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:2.1.1-SNAPSHOT] 
to[corba-marshal-ejb-2.1.1-SNAPSHOT.jar]
 [exec] [INFO] [INFO] Copying 
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:2.1.1-SNAPSHOT] 
to[corba-marshal-client-2.1.1-SNAPSHOT.jar]
 [exec] [INFO] [INFO] Copy ear resources to 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT
 [exec] [INFO] [INFO] Could not find manifest file: 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF 
- Generating one
 [exec] [INFO] [INFO] Building jar: 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear
 [exec] [INFO] [WARNING] POM for 
'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime' 
is invalid. It will be ignored for artifact resolution. Reason: Failed 
to validate POM for project 
org.apache.geronimo.framework:geronimo-system at Artifact 
[org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime]
 [exec] [INFO] [WARNING] POM for 
'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime' 
is invalid. It will be ignored for artifact resolution. Reason: Failed 
to validate POM for project 
org.apache.geronimo.framework:geronimo-system at Artifact 
[org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime]
 [exec] [INFO] [INFO] [geronimo:start-module {execution: 
start-j2ee-corba-yoko}]
 [exec] [INFO] [INFO] Using non-artifact based module id: 
org.apache.geronimo.configs/j2ee-corba-yoko/2.1.1-SNAPSHOT/car
 [exec] [WARNING] log4j:WARN No appenders could be found for logger 
(org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory).
 [exec] [WARNING] log4j:WARN Please initialize the log4j system 
properly.
 [exec] [INFO] [WARNING] Module is already started: 
org.apache.geronimo.configs/j2ee-corba-yoko/2.1.1-SNAPSHOT/car
 [exec] [INFO] [INFO] [geronimo:start-module {execution: 
openejb-corba-deployer}]
 [exec] [INFO] [INFO] Using non-artifact based module id: 
org.apache.geronimo.configs/openejb-corba-deployer/2.1.1-SNAPSHOT/car
 [exec] [INFO] [WARNING] Module is already started: 
org.apache.geronimo.configs/openejb-corba-deployer/2.1.1-SNAPSHOT/car

 [exec] [INFO] [INFO] [geronimo:deploy-module {execution: deploy-ear}]
 [exec] [INFO] [INFO] Using non-artifact based module archive: 
/home/drwoods/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear

 [exec] [INFO] [INFO] Using non-artifact based plan: null
 [exec] [INFO] [INFO] Distributing module artifact: 
/home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear 
with plan null
 [exec] [INFO] [INFO] 


 [exec] [INFO] [ERROR] FATAL ERROR
 [exec] [INFO] [INFO] 


 [exec] [INFO] [INFO] org.apache.geronimo.common.DeploymentException
 [exec] [INFO] [INFO] 


 [exec] [INFO] [INFO] Trace
 [exec] [INFO] java.lang.NoClassDefFoundError: 
org.apache.geronimo.common.DeploymentException

 [exec] [INFO]  at java.lang.J9VMInternals.verifyImpl(Native Method)
 [exec] [INFO] 	at 
java.lang.J9VMInternals.verify(J9VMInternals.java:68)
 [exec] [INFO] 	at 
java.lang.J9VMInternals.verify(J9VMInternals.java:66)
 [exec] [INFO] 	at 
java.lang.J9VMInternals.initialize(J9VMInternals.java:129)
 [exec] [INFO] 	at 
org.a

[jira] Updated: (GERONIMO-3917) response future does not complete if a connection is closed before the response is received

2008-03-13 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated GERONIMO-3917:
--

Attachment: GERONIMO-3917.patch

I am attaching one suggested fix.  The gist of the idea is, we need to keep 
track of the fact that the request is "outstanding".  It means that it 
attempted to send the request, but has not received the response nor an 
exception occurred.  If the session is closing while the request is 
outstanding, then we trigger an exception so the future is completed and the 
onException() method on the callback fires if applicable.

Please take a look at what I did, and let me know if you have suggestions or 
comments...

> response future does not complete if a connection is closed before the 
> response is received
> ---
>
> Key: GERONIMO-3917
> URL: https://issues.apache.org/jira/browse/GERONIMO-3917
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: AsyncHttpClient
>Affects Versions: 1.x
>Reporter: Sangjin Lee
>Assignee: Rick McGuire
> Attachments: GERONIMO-3917.patch
>
>
> If for *any reason* the server closes a connection without sending the 
> response, calls that wait on ResponseFuture.get() for the result will not 
> return.
> The key issue is the way HttpIoHandler.sessionClosed() works.  The 
> sessionClosed() method is invoked when a session is closed.  Currently the 
> only major things it does are to call callback's onClosed() method and remove 
> the timeout alarm.  If the message was not received or an exception did not 
> occur, however, the future remains not complete.  Therefore, any caller that 
> waits on Future.get() will never get unblocked.
> The sessionClosed() method needs to detect a situation where the connection 
> is *prematurely* closed while the response has not been received and cause an 
> exception and complete the future.
> This is a pretty critical issue.

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



Re: [PROPOSAL] Indent 2 spaces in xml and vm files to match more common usage, especially maven.

2008-03-13 Thread Alan D. Cabrera

-0

I find 2 space indenting difficult to read.  I'm sure that I'm  
misunderstanding something so take my reply with a grain of salt.


On Mar 13, 2008, at 8:28 AM, David Jencks wrote:



On Mar 13, 2008, at 7:21 AM, Jason Dillon wrote:

-1.  I don't think there is any value in making the indent for xml  
or any other files different than the normal indent for all other  
files.


Let me give a couple of examples where the 4-space indent causes a  
lot of pain and will continue to:


- in genesis geronimo-skin we have a site.vm file that is a slightly  
modified copy of the default .vm file from doxia-sitetools.  Trying  
to update it or compare it with different indents is quite an  
experience.


I'm not terribly familiar w/ site generation.  I was under the  
impression that we leave cookies by the wiki and elves make it.  :)


Could we not just reformat the site.vm file to have 4 space indents?

- maven archetypes pop out xml with 2 space indenting, and maven xml  
has 2 space indenting.  Re-indenting our stuff any time you run an  
archetype or borrow some configuration from maven is a nuisance that  
frequently is ignored and again the spacing difference makes  
comparison quite difficult.


For those of us sensible enough to use IntelliJ, alt-cmd-L makes our  
world tidy.  Maybe we could get the archetype generator to take the  
number of spaces for an indent as a configuration parameter?


Do you have an editor that can't deal with different indents for  
different file types?


thanks
david jencks



--jason


On Mar 13, 2008, at 6:34 AM, David Jencks wrote:

IIUC we have a coding standard of a 4 space indent for all files  
(documented at http://cwiki.apache.org/GMOxDEV/coding-standards.html) 
.  This can make working with maven difficult because its files  
and xml output generatiion use 2 space indent for xml and .vm files.


I think we could make life a lot easier when using maven tooling  
to use a 2 space indent for xml and .vm and possibly other files.   
At least with IDEA its easy to have different indents for java and  
xml files.


Comments?

thanks
david jencks










Re: Generated NOTICE files.... a solution

2008-03-13 Thread Daniel Kulp

David,

I deployed a new snapshot, can you give that a try and make sure it's all 
OK?

> - I can't get a blank line in between the project name and the notice

Fixed

> - I can't configure projectName in a suitable place so it shows up in
> the generated NOTICE.

In the configuration for the remote-resources plugin, add something like:


 Apache CXF



Dan


On Thursday 13 March 2008, David Jencks wrote:
> As I noted in a previous thread the current NOTICE files generated by
> the apache-jar-resource-bundle 1.3 are not consistent with apache
> policy.  After some discussion on legal-discuss I've come up with a
> bundle that no one seems to be able to find anything seriously wrong
> with: we're starting to use it in geronimo.
>
> Aside from possible use by other projects I'd like to use this in an
> upcoming ApacheDS release, so getting it quickly into a more neutral
> location would be desirable.  I've opened http://jira.codehaus.org/
> browse/MRRESOURCES-32 and attached a patch.
>
> The basic idea is that the NOTICE file contains only the required
> apache notice, with no extra text, explanation, horizontal rules, or
> anything else.  Additional required notices can be put in a NOTICE
> file in appended-resources and automatically appended.  Dependencies
> are listed in an additional generated DEPENDENCIES file, by
> organization, and listing the license.
>
> Note that NOTICE files apply only to the exact contents of the jar in
> question, not to any dependencies that might be necessary to actually
> use the jar.  For work at apache the normal situation is that the
> minimal NOTICE is all that is required, and if more is needed its
> going to be because of some special historical circumstances that
> can't plausibly be tracked by maven, so explicitly recording this
> information in a human-written additional NOTICE file is quite
> appropriate.
>
> There is certainly scope for some kind of aggregating bundle for
> assemblies that do actually contain stuff from other artifacts, such
> as wars, ears, tar.gzs, etc, but these are pretty clearly an entirely
> separate use case and likely to require considerably more work to get
> right.  I think starting work on a separate bundle for these might be
> appropriate.
>
> I know of two problems in the patch, both in NOTICE.vm, and I haven't
> been able to figure out solutions to either:
>
> - I can't get a blank line in between the project name and the notice
> - I can't configure projectName in a suitable place so it shows up in
> the generated NOTICE.
>
> Despite these problems I think this proposal is clearly more in line
> with apache policy and hope it can be accepted and released quickly.
>
> Many thanks
> david jencks
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-- 
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog


Re: [DISCUSS] Geronimo 2.1 samples

2008-03-13 Thread Joe Bohn

David Jencks wrote:


On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:


Joe Bohn wrote:

David Jencks wrote:


On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:


Donald Woods wrote:

Joe Bohn wrote:


2) When to release the samples?  I think we should make an effort 
to release the samples concurrent with each Geronimo release.  
This is important because the jsp & servlet examples are 
referenced from within the welcome page on Geronimo.  I suppose 
we could remove that reference and eliminate the need to release 
concurrently.
why not move the samples back under geronimo/server, so they are 
maintained and versioned with each release and can then be used as 
additional testsuite tests?  If not, releasing right after a 
server release is fine.


I was thinking about doing this.  It seems everybody thinks we 
should release them together anyway so what is the real value with 
them being split out?  Does anybody object to moving them back with 
the server?


well, since I thought our next goal with the server build was to 
separate it into independently released plugins, I think putting the 
samples in with the main server build would be a big step backwards.
Well, I agree that it would appear to be a step backwards from that 
perspective.  However, it would ensure the following:
1) The samples would get released (not forgotten as has been the case 
with 2.1)
2) The samples would be released concurrent with the Geronimo release 
so that they are available for use, education, and documentation from 
day 1.  It seems almost everybody is in favor of this.
3) They could be leveraged in the testsuite tests (as Donald pointed 
out) to help validate our build and find problems earlier.
I fail to see too many negatives from a practical perspective but I'm 
certainly open to discussion  I want to do what is best.
Perhaps we need to refine our plugin strategy.  There are situations 
where it makes sense to split things apart but there are also 
situations where it might make sense to bundle things.

Joe


Would those folks that feel strongly about not pulling these samples 
back into the server repo please provide some rationale for their 
argument as I have done for including them?  It appears that the 
samples were removed without much thought given to how they might 
eventually be released in conjunction with a server release.  I like 
the idea of modularity but in this case I don't see clear benefits to 
keeping them separate.


Please keep in mind that including the samples in the server source 
branch and releasing them concurrent with the server does not mean 
that they are bundled with the server.  They are still independent 
artifacts.  However, it would ensure that they are vetted with the 
server release and are available when the server release is 
available.  The samples are really only there to show value on top of 
a Geronimo server and they are tied to a specific server release (at 
least that is how we have managed and documented them thus far) so 
having released independent of the server doesn't appear to bring any 
value.


I looked back through a number of old email threads and these samples 
were included in the welcome page with a lot of support at the time 
(with a desire to have even more samples included or downloadable from 
the welcome page) ... several folks stating that they should be 
included with the server image itself.  I certainly don't want to 
bundle the samples with the server image but having the released with 
the server makes sense to me.


I'm speculating a bit here.

This might be similar to the testsuite being a bit monolithic.

As a thought experiment, what if we...
- made the welcome page a plugin, and the piece of build including it 
also builds the samples
- the maven generated site includes the stuff you need to download (zips 
etc) (I think this is doable)

- the welcome page links to the maven  generated site
- this leaves the door open to making the welcome page + samples 
independently versioned in the future, and possibly to selenium testing.


- we split up the testsuite into integration tests for "plugins" or 
plugin groups, and they assemble the servers they need on the fly


- assemblies may or may not include the welcome page plugin.

dunno how practical this is for 2.1.1


I don't quite understand.  So are you saying that we should move at 
least some of the samples (those referenced by the welcome page) back 
into the server svn?  Or, is it possible to have the server build also 
build sample content from another repo (and if so, how is that better 
than just merging the content)?


I think I understand the maven site reference for downloads.  However, 
that isn't exactly the same function that is intended with the welcome 
page today.  It is true that there is a link to the Geronimo site 
already for accessing "additional samples" which functions in a similar 
way to your description (only referencing the wiki).  However the links 
to the 3 special samples

[jira] Created: (GERONIMODEVTOOLS-297) GEP 2.1.0 JAXB Refactoring Tasklist

2008-03-13 Thread Tim McConnell (JIRA)
GEP 2.1.0 JAXB Refactoring Tasklist
---

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


Need a high-level task list of the tasks remaining for the JAXB refactoring

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



[jira] Created: (GERONIMODEVTOOLS-298) Plugin: org.apache.geronimo.runtime.common

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.runtime.common
--

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




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



[jira] Created: (GERONIMODEVTOOLS-299) Plugin: org.apache.geronimo.runtime.v11

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.runtime.v11
---

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




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



[jira] Created: (GERONIMODEVTOOLS-301) Plugin: org.apache.geronimo.runtime.v21

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.runtime.v21
---

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




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



[jira] Created: (GERONIMODEVTOOLS-300) Plugin: org.apache.geronimo.runtime.v20

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.runtime.v20
---

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




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



[jira] Created: (GERONIMODEVTOOLS-302) Plugin: org.apache.geronimo.st.core

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.core
---

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




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



[jira] Created: (GERONIMODEVTOOLS-304) Plugin: org.apache.geronimo.st.v20.core

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v20.core
---

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




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



[jira] Created: (GERONIMODEVTOOLS-305) Plugin: org.apache.geronimo.st.v21.core

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v21.core
---

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




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



[jira] Created: (GERONIMODEVTOOLS-303) Plugin: org.apache.geronimo.st.v11.core

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v11.core
---

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




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



Upgrading Axis2 version / Geronimo's JAXWS 2.1 plan

2008-03-13 Thread Davanum Srinivas

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Folks,

At Axis2, we are trying to push out a 1.4 Release soon. Planning an RC1 this 
weekend/monday.

So questions, What's the plan to upgrade to JAXWS 2.1? I believe the cxf folks 
are already at JAXWS 2.1.

Could we please upgrade both (if not already) to get some TCK coverage and make 
sure we fix anything that crops up by
the time we cut Axis2 1.4?

thanks,
dims
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFH2eHUgNg6eWEDv1kRAkcCAKCJHdRVrvq7eQXDYQdzVk5RaoHoqgCfYzUj
wH0CdAi/fLegy77jrcprAnM=
=b9Xg
-END PGP SIGNATURE-


[jira] Created: (GERONIMODEVTOOLS-306) Plugin: org.apache.geronimo.st.ui

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.ui
-

 Key: GERONIMODEVTOOLS-306
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-306
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



[jira] Created: (GERONIMODEVTOOLS-308) Plugin: org.apache.geronimo.st.v20.ui

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v20.ui
-

 Key: GERONIMODEVTOOLS-308
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-308
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



[jira] Created: (GERONIMODEVTOOLS-307) Plugin: org.apache.geronimo.st.v11.ui

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v11.ui
-

 Key: GERONIMODEVTOOLS-307
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-307
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



[jira] Created: (GERONIMODEVTOOLS-309) Plugin: org.apache.geronimo.st.v21.ui

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.st.v21.ui
-

 Key: GERONIMODEVTOOLS-309
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-309
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



[jira] Created: (GERONIMODEVTOOLS-310) Plugin: org.apache.geronimo.deployment.v11.jaxbmodel

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.deployment.v11.jaxbmodel


 Key: GERONIMODEVTOOLS-310
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-310
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



[jira] Created: (GERONIMODEVTOOLS-311) Plugin: org.apache.geronimo.deployment.v21.jaxbmodel

2008-03-13 Thread Tim McConnell (JIRA)
Plugin: org.apache.geronimo.deployment.v21.jaxbmodel


 Key: GERONIMODEVTOOLS-311
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311
 Project: Geronimo-Devtools
  Issue Type: Sub-task
Reporter: Tim McConnell




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



Re: svn commit: r636845 - /geronimo/server/trunk/framework/modules/geronimo-deploy-jsr88/pom.xml

2008-03-13 Thread Jarek Gawor
Seems like this would be causing the dependency problem you saw:

>  'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime'
>  is invalid. It will be ignored for artifact resolution. Reason: Failed
>  to validate POM for project

Jarek

On Thu, Mar 13, 2008 at 8:03 PM, Donald Woods <[EMAIL PROTECTED]> wrote:
>
>   [exec] [INFO] [INFO]
>  
>   [exec] [INFO] [INFO] Building Geronimo TestSuite :: CORBA
>  TestSuite :: Marshal EAR
>   [exec] [INFO] [INFO]task-segment: [install]
>   [exec] [INFO] [INFO]
>  
>   [exec] [INFO] [INFO] [enforcer:enforce {execution: default}]
>   [exec] [INFO] [INFO] [ear:generate-application-xml]
>   [exec] [INFO] [INFO] Generating application.xml
>   [exec] [INFO] [INFO] [tools:copy-legal-files {execution:
>  install-legal-files}]
>   [exec] [INFO] [INFO] Created dir:
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/classes/META-INF
>   [exec] [INFO] [INFO] Copying 2 files to
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/classes/META-INF
>   [exec] [INFO] [INFO] [resources:resources]
>   [exec] [INFO] [INFO] Using default encoding to copy filtered
>  resources.
>   [exec] [INFO] [INFO] [ear:ear]
>   [exec] [INFO] [INFO] Copying
>  artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:2.1.1-SNAPSHOT]
>  to[corba-marshal-ejb-2.1.1-SNAPSHOT.jar]
>   [exec] [INFO] [INFO] Copying
>  
> artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:2.1.1-SNAPSHOT]
>  to[corba-marshal-client-2.1.1-SNAPSHOT.jar]
>   [exec] [INFO] [INFO] Copy ear resources to
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT
>   [exec] [INFO] [INFO] Could not find manifest file:
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
>  - Generating one
>   [exec] [INFO] [INFO] Building jar:
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear
>   [exec] [INFO] [WARNING] POM for
>  'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime'
>  is invalid. It will be ignored for artifact resolution. Reason: Failed
>  to validate POM for project
>  org.apache.geronimo.framework:geronimo-system at Artifact
>  [org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime]
>   [exec] [INFO] [WARNING] POM for
>  'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime'
>  is invalid. It will be ignored for artifact resolution. Reason: Failed
>  to validate POM for project
>  org.apache.geronimo.framework:geronimo-system at Artifact
>  [org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime]
>   [exec] [INFO] [INFO] [geronimo:start-module {execution:
>  start-j2ee-corba-yoko}]
>   [exec] [INFO] [INFO] Using non-artifact based module id:
>  org.apache.geronimo.configs/j2ee-corba-yoko/2.1.1-SNAPSHOT/car
>   [exec] [WARNING] log4j:WARN No appenders could be found for logger
>  (org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory).
>   [exec] [WARNING] log4j:WARN Please initialize the log4j system
>  properly.
>   [exec] [INFO] [WARNING] Module is already started:
>  org.apache.geronimo.configs/j2ee-corba-yoko/2.1.1-SNAPSHOT/car
>   [exec] [INFO] [INFO] [geronimo:start-module {execution:
>  openejb-corba-deployer}]
>   [exec] [INFO] [INFO] Using non-artifact based module id:
>  org.apache.geronimo.configs/openejb-corba-deployer/2.1.1-SNAPSHOT/car
>   [exec] [INFO] [WARNING] Module is already started:
>  org.apache.geronimo.configs/openejb-corba-deployer/2.1.1-SNAPSHOT/car
>   [exec] [INFO] [INFO] [geronimo:deploy-module {execution: deploy-ear}]
>   [exec] [INFO] [INFO] Using non-artifact based module archive:
>  
> /home/drwoods/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear
>   [exec] [INFO] [INFO] Using non-artifact based plan: null
>   [exec] [INFO] [INFO] Distributing module artifact:
>  
> /home/drwoods/svn/server-2.1.1/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-2.1.1-SNAPSHOT.ear
>  with plan null
>   [exec] [INFO] [INFO]
>  
>   [exec] [INFO] [ERROR] FATAL ERROR
>   [exec] [INFO] [INFO]
>  
>   [exec] [INFO] [INFO] org.apache.geronimo.common.DeploymentException
>   [exec] [INFO] [INFO]
>  

[jira] Created: (GERONIMODEVTOOLS-312) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB

2008-03-13 Thread Shiva Kumar H R (JIRA)
Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using 
JAXB
---

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


The fixGeronimo*Schema() function inside GeronimRuntime classes is curently 
implemented using XMLBeans. As part of GERONIMODEVTOOLS-295, xmlbeans-2.3.0.jar 
has been removed from GEP's dependencies. Hence fixGeronimo*Schema() 
functionality needs to be reimplemented using JAXB.

Classes to be changed:
1) org.apache.geronimo.st.core.IGeronimoRuntime
2) org.apache.geronimo.st.core.operations.ImportDeploymentPlanOperation
3) org.apache.geronimo.st.v11.core.GeronimoRuntime
4) org.apache.geronimo.st.v20.core.GeronimoRuntime
5) org.apache.geronimo.st.v21.core.GeronimoRuntime

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



[jira] Commented: (GERONIMODEVTOOLS-295) Delete redundant dependencies from runtime plug-ins - Make GEP thinner!

2008-03-13 Thread Shiva Kumar H R (JIRA)

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

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

Some good news!! GEP has Shred Lot of Weight and is Just 5.4MB Now!! Earlier it 
was 12.6MB, so ~57% reduction in size.

I have deleted following redundant JARs from various runtime plug-ins:
1) From \plugins\org.apache.geronimo.runtime.v11
a) geronimo-service-builder, 
b) geronimo-connector-builder, 
c) geronimo-web-builder, 
d) geronimo-naming-builder, 
e) geronimo-j2ee-builder, 
f) openejb-builder, 
g) geronimo-security-builder

2) From \plugins\org.apache.geronimo.runtime.v20
a) geronimo-service-builder, 
b) geronimo-connector-builder, 
c) geronimo-web-2.5-builder, 
d) geronimo-naming-builder, 
e) geronimo-j2ee-builder, 
f) geronimo-openejb-builder, 
g) geronimo-security-builder, 
h) geronimo-schema-jee_5

3) From \plugins\org.apache.geronimo.runtime.v21
a) geronimo-service-builder, 
b) geronimo-connector-builder, 
c) geronimo-web-2.5-builder, 
d) geronimo-naming-builder, 
e) geronimo-j2ee-builder, 
f) geronimo-openejb-builder, 
g) geronimo-security-builder, 
h) geronimo-schema-jee_5

Basically all *builder jars from 1), 2) & 3), and

4) From \plugins\org.apache.geronimo.runtime.common
a) xmlbeans-2.3.0.jar (~2.5MB)

They were earlier required by EMF plug-ins (which were coded to pick various 
XSDs from those builder JARs), and with they getting deleted through 
GERONIMODEVTOOLS-294, above dependencies have become redundant and hence 
deleted. (New JAXB model plug-ins have the XSDs directly in source tree).

The only other place where those builders JARs & xmlbeans.jar were used before, 
was to implement various fixGeronimo*Schema() functions inside GeronimRuntime 
classes. These functions will be reimplemented using JAXB as part of 
GERONIMODEVTOOLS-312.

The above listed JARs are deleted at revision: 636971

> Delete redundant dependencies from runtime plug-ins - Make GEP thinner!
> ---
>
> Key: GERONIMODEVTOOLS-295
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.0
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.1.0
>
>
> GEP is currently 13.3MB! Out of this ~11.6MB (87%) is from following four 
> plug-ins!
> 1) \plugins\org.apache.geronimo.runtime.common
> 2) \plugins\org.apache.geronimo.runtime.v11
> 3) \plugins\org.apache.geronimo.runtime.v20
> 4) \plugins\org.apache.geronimo.runtime.v21
> After GERONIMODEVTOOLS-294, many of the dependencies in above plug-ins might 
> have become redundant. Identify the redundant ones and delete them to make 
> GEP thinner :)

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



  1   2   >