[jira] [Created] (GERONIMO-6222) Improve deployment time performance for big Java EE artifacts

Improve deployment time performance for big Java EE artifacts
-------------------------------------------------------------

                 Key: GERONIMO-6222
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6222
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: deployment
    Affects Versions: 3.0, 3.0-beta-1
            Reporter: Forrest Xia

If deploying a big Java EE artifacts from the url below[1], you may experience unacceptable deployment
performance issue, it could take more than 20 minutes to deploy a java ee artifacts with size 50M.

So we really need to make some improvement on java EE artifacts deployment.

[1] http://www-01.ibm.com/software/webservers/appserv/was/featurepacks/web20-mobile/#

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6223) problem of "XSSXSRFFilter blocked HttpServletRequest due to invalid FORM content" always happened when install WAB sample

problem of "XSSXSRFFilter blocked HttpServletRequest due to invalid FORM content" always happened when
install WAB sample
-------------------------------------------------------------------------------------------------------------------------

                 Key: GERONIMO-6223
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6223
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: osgi-bundles
    Affects Versions: 3.0
         Environment: s390x s390x s390x GNU/Linux
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux s390x-64 jvmxz6460sr9-20110203_74623 (JIT enabled, AOT enabled)
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111104 Red Hat/3.6.24-3.el6_1 Firefox/3.6.24
            Reporter: Tina Li
            Priority: Trivial

1.Install geronimo server and start server successfully
2.Install and start a WAB sample using osgi porlet
3.Click the checkbox of "WAB"
url can't be accessed normally but displayed message on firefox:

HTTP Status 400 - XSSXSRFFilter blocked HttpServletRequest due to invalid FORM content.

type Status report

message XSSXSRFFilter blocked HttpServletRequest due to invalid FORM content.

description The request sent by the client was syntactically incorrect (XSSXSRFFilter blocked
HttpServletRequest due to invalid FORM content.).

[jira] [Created] (GERONIMO-6224) NPE while accessing the system modules portlet

NPE while accessing the system modules portlet
----------------------------------------------

                 Key: GERONIMO-6224
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6224
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: console
    Affects Versions: 3.0-beta-1
            Reporter: Ivan

When I tried to stop "openejb-deployer", I got the following error. And every time I visit "System Modules"
page, I got the same error....
There may be problems in the kernel, while I think that the portlet should be more tolerant for those runtime exception.

java.lang.NullPointerException
		 at org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:251)
		 at org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:243)
		 at org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:863)
		 at org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:839)
		 at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.unloadModule(ConfigManagerPortlet.java:447)
		 at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:341)
		 at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
		 at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
		 at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
		 at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
		 at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
		 at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
		 at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0-beta-1 RC2

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0-beta-1 RC2

+1

license/notice, rat look good. I did not build (Mac OS problem), but simple test looked good. Thanks Janet!

--kevan

On Nov 30, 2011, at 1:09 AM, han hongfang wrote:

> Hi devs,
> 
> Please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 3.0-beta-1 RC2.
> 
> GEP 3.0-beta-1 supports Geronimo server 3.0-beta-1, 2.2.1, 2.1.7 and Eclipse Indigo (3.7).
> 
> [Known issue] 
> 1. GEP 3.0-beta-1 uses maven-eclipsepde-plugin v1.1, which means it can not be built successfully on
64bit win7 and 64bit macos. See following JIRAs for details.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not build GEP3.0 under win7-64bit
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not build GEP3.0 under macos-64bit
> 2. Also, please use maven v2.2.1 to build GEP 3.0-beta-1 as following JIRA is still open.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build GEP with maven 3.0
> 
> The source code zip is here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-271/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0-beta-1/geronimo-eclipse-plugin-3.0-beta-1-source-release.zip
> https://repository.apache.org/content/repositories/orgapachegeronimo-271/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0-beta-1/geronimo-eclipse-plugin-3.0-beta-1-source-release.tar.gz
> 
> The tag is here:
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0-beta-1
> 
> The deployable zip file is here:
> http://people.apache.org/builds/geronimo/eclipse/3.0-beta-1/geronimo-eclipse-plugin-3.0-beta-1-deployable.zip
> 
> The update site zip file is here:
> http://people.apache.org/builds/geronimo/eclipse/3.0-beta-1/geronimo-eclipse-plugin-3.0-beta-1-updatesite.zip
> 
> The p2 repo zip file is here:
> http://people.apache.org/builds/geronimo/eclipse/3.0-beta-1/geronimo-eclipse-plugin-3.0-beta-1-p2repo.zip
> 
> If you would like to review and/or comment on the release notes, you can find it here:
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0-beta-1.txt
> 
> Finally, I've created a Staging Site that can be used to test the update manager functions of  Eclipse
(Indigo and helios):
> http://people.apache.org/builds/geronimo/eclipse/updates/
>  
> The vote will be open for the 72-hour minimum.
>  
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
> 
> -- 
> Best regards,
> 
> Han Hong Fang (Janet)
> hanhongfang AT apache.org
> 

Bean Validation TCK version

Hi all; apologies for the cross-post.  For some time in the Apache
Bean Validation podling we intentionally lagged to the 1.0.3.GA
version of the Bean Validation TCK because it was our understanding
that this was the version included in the larger EE TCKs which
Geronimo, and now TomEE, must satisfy.  This became a real problem
with the release of version 1.0.5.GA of the TCK, which addressed a bug
in the original RI *and* TCK so severe that it is literally impossible
for a given codebase to satisfy the Bean Validation TCK >= 1.0.5.GA
and < 1.0.5.GA simultaneously.  After releasing bval-0.3-incubating,
we voted for forward progress and made our code compatible with the
1.0.5.GA TCK.  Recently I raised the issue on the Bean Validation
specification development list, and was informed by Emmanuel Bernard
that the Bean Validation TCK *has* in fact been updated in Java EE, to
version 1.0.6.GA, which our current trunk also passes. [1]  Now I'd
like to establish a comfort level among our communities that Geronimo
and TomEE will be able to use future releases of Apache Bean
Validation, for when we release 0.4-incubating (or perhaps 1.0, as a
TLP), your projects will not be able to upgrade the BV implementation
without also upgrading the corresponding TCK, or (as I am ignorant of
the procedures wrt the EE TCK) obtaining an updated version of the EE
TCK which in fact contains the updated BV TCK.

Thanks for your attention,
Matt

[1] http://lists.jboss.org/pipermail/beanvalidation-dev/2011-December/000103.html

Re: Fwd: Accepting proposals regarding early git adoption

Is the idea for this to abandon SVN and move completely over to git?

Or is it just to add git as a way for folks to manage their local copies 
of the source?

Jay

On 11/29/2011 03:22 PM, Kevan Miller wrote:
> Forwarding (with permission), in case there's interest within Geronimo community.
>
> --kevan
>
> Begin forwarded message:
>
>> From: Joe Schaefer<joe_schaefer@...>
>> Subject: Accepting proposals regarding early git adoption
>> Date: November 28, 2011 8:28:17 AM EST
>> To: Apache Infrastructure<infrastructure@...>
>> Reply-To: Joe Schaefer<joe_schaefer@...>
>>
>> While many of you are aware of the ongoing "experiment/alpha test"
>> with git hosting for CouchDB, you may not be aware of the recent
>> members <at>  discussion about git  <at>  Apache, the result of which is to
>> solicit proposals here for projects interested in adopting git now,
>> rather than after the testing phase is over.
>>
>> Any such projects you participate in should write a brief and civil
>> proposal as to why we should select you for further git testing.
>> Proposals should include statements of interest in assisting with
>> the git hosting codebase and associated jira issues from named
>> individuals on the project.
>>
>> We'll allow the remainder of the week to collect proposals before
>> deciding on who gets to go next.
>>
>

Re: Accepting proposals regarding early git adoption

Anyone can already use git locally, there are apache mirrors of most svn projects and many project's
committers expose a lot of work-in-progress on github (e.g. karaf)

See e.g. http://wiki.apache.org/general/GitAtApache

This is asking for projects that would like to use git instead of svn for their canonical apache repository. 
While I enthusiastically use git almost all the time including for almost all my geronimo work I think
geronimo is too complicated to be a useful guinea pig for git at this point.  I think it will take a lot of
thought and time to figure out how to divide up the geronimo history into appropriately sized git
projects.  For instance:

- each spec is separately releasable so it's a separate git project.  Then we need an aggretator project to
build them all at once for convenience.  Same for bundles.
- the server code was originally under cvs at root and only later moved under server.  How will this history
make it into git (this is probably solved already but I haven't looked)

thanks
david jencks

On Dec 2, 2011, at 11:14 AM, Jay D. McHugh wrote:

> Is the idea for this to abandon SVN and move completely over to git?
> 
> Or is it just to add git as a way for folks to manage their local copies of the source?
> 
> Jay
> 
> On 11/29/2011 03:22 PM, Kevan Miller wrote:
>> Forwarding (with permission), in case there's interest within Geronimo community.
>> 
>> --kevan
>> 
>> Begin forwarded message:
>> 
>>> From: Joe Schaefer<joe_schaefer@...>
>>> Subject: Accepting proposals regarding early git adoption
>>> Date: November 28, 2011 8:28:17 AM EST
>>> To: Apache Infrastructure<infrastructure@...>
>>> Reply-To: Joe Schaefer<joe_schaefer@...>
>>> 
>>> While many of you are aware of the ongoing "experiment/alpha test"
>>> with git hosting for CouchDB, you may not be aware of the recent
>>> members <at>  discussion about git  <at>  Apache, the result of which is to
>>> solicit proposals here for projects interested in adopting git now,
>>> rather than after the testing phase is over.
>>> 
>>> Any such projects you participate in should write a brief and civil
>>> proposal as to why we should select you for further git testing.
>>> Proposals should include statements of interest in assisting with
>>> the git hosting codebase and associated jira issues from named
>>> individuals on the project.
>>> 
>>> We'll allow the remainder of the week to collect proposals before
>>> deciding on who gets to go next.
>>> 
>> 

Fwd: [RESULT][IP CLEARANCE] Apache Geronimo 2.2 Dependency Upgrades

FYI

Begin forwarded message:

> From: Kevan Miller <kevan.miller@...>
> Subject: [RESULT][IP CLEARANCE] Apache Geronimo 2.2 Dependency Upgrades
> Date: December 2, 2011 4:21:35 PM EST
> To: general@...
> 
> Our 72 hour window has passed. So, I'm calling this IP CLEARANCE complete.
> 
> Thanks!
> 
> --kevan
> 
> On Nov 29, 2011, at 5:09 AM, Robert Burrell Donkin wrote:
> 
>> On Mon, Nov 28, 2011 at 11:56 PM, Kevan Miller
<kevan.miller@...> wrote:
>>> The Apache Geronimo project has received a contribution which updates a number of Geronimo
dependencies and associated code updates.
>>> 
>>> The code contributions have been attached to https://issues.apache.org/jira/browse/GERONIMO-6217
>>> 
>>> I've committed the IP Clearance form to the Incubator website -- http://incubator.apache.org/ip-clearance/geronimo-dependency-upgrades.html
>>> 
>>> The Geronimo community has passed a vote to accept the contribution -- http://mail-archives.apache.org/mod_mbox/geronimo-dev/201111.mbox/%3c1BC3AB3F-2B25-4CE4-BA7B-5C8B4764E69B-Re5JQEeQqe8AvxtiuMwx3w <at> public.gmane.org%3e
>>> 
>>> This stage of the IP clearance process is a 72-hour lazy consensus. Barring a -1, the ip clearance for
this contribution will pass in 72 hours.
>> 
>> Yes  this process is by lazy consensus.
>> 
>> If anyone sees a problem, please post a -1 to this thread to force a
>> formal review and VOTE. Kevan will close this thread by posting a
>> RESULT mail no earlier than Friday, December 2, 2011 at 12:00:00  UTC
>> [1] (by my reckoning). If you can spare a few cycles, please take a
>> look before then.
>> 
>> Robert
>> 
>> [1] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20111202T12
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>> 
> 

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0-beta-1 RC2