[jira] [Updated] (GERONIMO-6242) Fork tomcat comet sample "Chat" to geronimo samples

[Forrest Xia (Updated) (JIRA)]

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

Forrest Xia updated GERONIMO-6242:
--

Affects Version/s: 3.0-beta-1
Fix Version/s: 3.0-beta-2
   3.0
   2.2.2
   2.1.8

> Fork tomcat comet sample "Chat" to geronimo samples
> ---
>
> Key: GERONIMO-6242
> URL: https://issues.apache.org/jira/browse/GERONIMO-6242
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 2.1, 2.2, 3.0, 3.0-beta-1
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.8, 2.2.2, 3.0, 3.0-beta-2
>
>
> Fork tomcat example - Chat to geronimo samples to demonstrate Comet API
> Code source -> 
> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/examples/

--
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] [Resolved] (GERONIMO-6242) Fork tomcat comet sample "Chat" to geronimo samples

[Forrest Xia (Resolved) (JIRA)]

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

Forrest Xia resolved GERONIMO-6242.
---

Resolution: Fixed

See subversion commit tab for revisions

> Fork tomcat comet sample "Chat" to geronimo samples
> ---
>
> Key: GERONIMO-6242
> URL: https://issues.apache.org/jira/browse/GERONIMO-6242
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 2.1, 2.2, 3.0, 3.0-beta-1
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.8, 2.2.2, 3.0, 3.0-beta-2
>
>
> Fork tomcat example - Chat to geronimo samples to demonstrate Comet API
> Code source -> 
> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/examples/

--
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] [Resolved] (GERONIMO-6191) can not query the persistence unit gbean when ejb is in a war

[Rex Wang (Resolved) (JIRA)]

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

Rex Wang resolved GERONIMO-6191.


Resolution: Fixed

> can not query the persistence unit gbean when ejb is in a war
> -
>
> Key: GERONIMO-6191
> URL: https://issues.apache.org/jira/browse/GERONIMO-6191
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 3.0
>
>
> When deploy a war which contains persistence.xml and ejbs, the persistent 
> unit builder add the following gbean data to the earcontext:
> default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87
> but in the EjbDeploymentBuilder's line 209,
> It uses a pattern as following to query the persistent unit gbean data:
> [?EJBModule=.,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean]
> We can see it contains a constraint "EJBModule=.", which cause the query 
> return empty. That lead the DeploymentException("No default PersistenceUnit 
> specified, and none located");
> This is because the ejb module and the war module share the same earcontext 
> and the configuration

--
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-6242) Fork tomcat comet sample "Chat" to geronimo samples

[Forrest Xia (Created) (JIRA)]

Fork tomcat comet sample "Chat" to geronimo samples
---

 Key: GERONIMO-6242
 URL: https://issues.apache.org/jira/browse/GERONIMO-6242
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: sample apps
Affects Versions: 2.2, 2.1, 3.0
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor


Fork tomcat example - Chat to geronimo samples to demonstrate Comet API

Code source -> 
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/examples/

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

Re: [VOTE] Release Geronimo 2.1.8 RC2

[Shawn Jiang]

+1,  thanks, Forrest !

On Wed, Dec 21, 2011 at 2:05 PM, Forrest Xia  wrote:

> Hi folks,
>
> A release candidate for Geronimo 2.1.8 has been created and staged.
>
> The tag has been created here:
> https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/
>
> The staging repo is here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/
>
> The main artifacts up for vote are the source release archives:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip
>
>
> A tck execution against 2.1.8 tag is ongoing, and will be finished around
> 16 hours later. I will update the status here.
>
> The vote will be open for 72 hours.
>
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Shawn

Re: [VOTE] Release Geronimo 2.1.8 RC2

[viola lu]

+1

On Thu, Dec 22, 2011 at 9:24 AM, Yi Xiao wrote:

> Rat check's result shows just some test resources miss license-head.
> so my+1
>
>
> On Wed, Dec 21, 2011 at 11:30 PM, Forrest Xia  wrote:
>
>> Tag tck all passed!
>>
>> Here is my +1
>>
>>
>> On Wed, Dec 21, 2011 at 2:05 PM, Forrest Xia  wrote:
>>
>>> Hi folks,
>>>
>>> A release candidate for Geronimo 2.1.8 has been created and staged.
>>>
>>> The tag has been created here:
>>> https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/
>>>
>>> The staging repo is here:
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/
>>>
>>> The main artifacts up for vote are the source release archives:
>>>
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz
>>>
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip
>>>
>>>
>>> A tck execution against 2.1.8 tag is ongoing, and will be finished
>>> around 16 hours later. I will update the status here.
>>>
>>> The vote will be open for 72 hours.
>>>
>>> [  ] +1 about time to push this out the door
>>> [  ]  0 no opinion
>>> [  ] -1 not this one  (please explain why)
>>>
>>>
>>> --
>>> Thanks!
>>>
>>> Regards, Forrest
>>>
>>>
>>
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>>
>
>
> --
> Best regards!
>
>
>  John Xiao
>
>


-- 
viola

Apache Geronimo

PASS! [VOTE] Release Geronimo Tomcat 6.0.35.1

[Forrest Xia]

We have these +1 votes:
Forrest
Rex
Shawn
Viola

3 of them are PMCs, no -1 vote, so VOTE to release geronimo tomcat 6.0.35.1
pass! I will promote the repository soon.

On Tue, Dec 20, 2011 at 9:43 PM, Shawn Jiang  wrote:

> +1
>
> On Sun, Dec 18, 2011 at 8:17 PM, Forrest Xia  wrote:
>
>> Please vote for the Geronimo Tomcat 6.0.35.1 release, which is based on
>> Tomcat 6.0.35 tag, and will be used in Geronimo 2.1.8 release.
>>
>> The components up for vote are:
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-355/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.35/6.0.35.1/tomcat-parent-6.0.35-6.0.35.1-source-release.tar.gz
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-355/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.35/6.0.35.1/tomcat-parent-6.0.35-6.0.35.1-source-release.zip
>>
>> Staging repo is here:
>> 
>> https://repository.apache.org/content/repositories/orgapachegeronimo-355/
>> 
>>
>> tag is here:
>>
>> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.35.1/
>>
>>
>> Vote open 72 hours
>>
>> [ ] +1 release this
>> [ ] 0 don't care
>> [ ] -1 don't release this (please explain)
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>>
>
>
> --
> Shawn
>



-- 
Thanks!

Regards, Forrest

Re: Geronimo 3 and karaf 3

[Forrest Xia]

On Thu, Dec 22, 2011 at 2:27 AM, David Jencks wrote:

> I pushed a karaf snapshot maybe that will help?  I don't see this
> problem locally.
>
No help for server build in AHP, I will try it locally. thanks!


>
> thanks
> david jencks
>
> On Dec 21, 2011, at 8:18 AM, Forrest Xia wrote:
>
> Trunk build failed with this error when building a new module *Geronimo
> Framework, Feature :: DS and Metatype*
>
>  [INFO] Internal error in the plugin manager executing goal
> 'org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor':
> Unable to find the mojo 'features-generate-descriptor' (or one of its
> required components) in the plugin
> 'org.apache.karaf.tooling:karaf-maven-plugin'
>  Component descriptor cannot be found in the component repository:
> org.sonatype.aether.RepositorySystem.
>
>
> On Tue, Dec 20, 2011 at 2:06 PM, David Jencks wrote:
>
>> BTW, to get the regions/isolation stuff working I think we are going to
>> need to replace our use of BundleListener/SynchronousBundleListener with
>> the (updated-for-4.3) aries RecursiveBundleTracker.  I think we'll need
>> also change from ConfigurationActivator to an extender pattern.  I'd guess
>> the ConfigurationActivator functionality could be moved to
>> DependencyManager rather than having an additional tracker.
>>
>> thanks
>> david jencks
>>
>> On Dec 20, 2011, at 10:13 AM, David Jencks wrote:
>>
>> OK, I just committed this stuff, with reference to 
>> GERONIMO-6240
>> .
>>
>> Some more hints
>>
>> I can build all the way through with
>> MAVEN_OPTS="-XX:MaxPermSize=2048m -Xms2048m -Xmx4096m"
>>
>> I can start karaf after setting
>>
>> export JAVA_MAX_MEM=2048m
>> export JAVA_MAX_PERM_MEM=512m
>>
>> The car packaging is set up to stop and wait if it gets stuck.  In an
>> earlier version of this you'd get the karaf console and you could use karaf
>> commands to investigate what was going on.  For some reason this isn't
>> working now.  If you get into this situation, you need to kill the maven
>> java process some way.  Usually setting a breakpoint at DependencyManager
>> line 571 will show you a bundle that has a resolution problem that you can
>> then fix.
>>
>> The problem with the console deploy-type commands I think relates to
>> using the karaf RMIRegistry.  I'm going to modify it so it includes the
>> port as a service property, then we can look for the osgi service and get
>> its port instead of the port gbean attribute.
>>
>> thanks
>> david jencks
>>
>> On Dec 19, 2011, at 9:10 PM, David Jencks wrote:
>>
>> more not-yet-working inline
>>
>> On Dec 19, 2011, at 5:08 PM, David Jencks wrote:
>>
>> I've been spending a lot of time working to rebase geronimo on karaf 3 so
>> we can have a maintainable future and get stuff like osgi 4.3, up to date
>> aries components, and the experimental region support now in karaf.
>>
>>
>> After a lot of work I have everything except clustering building and
>> after turning off a couple problematic modules the tomcat-javaee6 server
>> starts and the web admin console appears to work at least a little bit.
>>   I'd like a little vacation this year and would like to commit this work
>> first so that others can help with the loose ends if they like.  I'll
>> probably be around to answer questions in any case.
>>
>>
>> The modules that don't start are:
>>
>>
>> activemq-broker-blueprint.  The ${X + Y} stuff is not getting evaluated
>> at all.  I don't know if this is an xbean-blueprint problem or an aries
>> blueprint problem or a side effect of running in geronimo.
>>
>> As a result activemq-ra and tomcat-console-activemq can't be started.
>>
>>
>> client-deployer.  I think this is a pretty simple gbean name problem but
>> I haven't looked into it.
>>
>>
>>
>> Here are some of the changes:
>>
>>
>> -- assemble the server using a combination of karaf assembly from
>> features and kars and geronimo assembly from geronimo plugins.  We now use
>> the same base karaf assembly stuff as the normal default full karaf
>> assembly (except I might have left out the spring feature repository).
>>
>>
>> -- basic geronimo components such as the kernel, configuration manager,
>> dependency manager, deployer, and service config builder are set up as osgi
>> declarative services so they start without any geronimo configuration.
>>  They are generally configured through config admin as appropriate.  Most
>> of these also have gbean wrappers so they can be accessed through gbean
>> references.
>>
>>
>> -- "geronimo" is started from a DS component, EmbeddedDaemon.
>>
>>
>> -- I think I'm using the karaf remote jmx security rather than ours.  The
>> capabilities are similar but not identical.
>>
>>
>> Some other things that are not working yet:
>>
>>
>> -- The (gogo) geronimo console commands that work through "remote" gbean
>> proxies don't work AFAIK.  Probably one way to fix this would be to expose
>> some more of the DS components using gbe