|
There's still hope for 2.2...
We may be able to release 2.2 soon. Activemq has fixed the last bug
we had problems with and is fast approaching a release, openejb is
getting very close to a release for 2.2, and I've started votes on a
number of our snapshot dependencies.
At this point I'd like anyone who is working on something they'd like
to get into 2.2 to reply to this with a description of what they are
working on and an estimate for completion.
Also, if there is something you think is really necessary to get into
2.2 please reply and describe what you'd like.
many thanks
david jencks
|
|
Re: There's still hope for 2.2...
|
|
Re: There's still hope for 2.2...
I'm working on https://issues.apache.org/jira/browse/GERONIMO-4852https://issues.apache.org/jira/browse/GERONIMO-4851
https://issues.apache.org/jira/browse/GERONIMO-4850And hopefully they can be included in G22 On Fri, Sep 11, 2009 at 4:34 PM, Ivan <xhhsld@...> wrote:
I wish those JIRAs to be included in Geronimo 2.2
https://issues.apache.org/jira/browse/GERONIMO-4801
Please check my comment, I think we could just ignore the alreadyexisted exception
https://issues.apache.org/jira/browse/GERONIMO-4821
Please check my comment, I need more help on it :-(
https://issues.apache.org/jira/browse/GERONIMO-4836
If anyone could help to check the patch in the current pluto snapshot, that will be fine. or, I wish to fix it in Geronimo 2.2 firstly
https://issues.apache.org/jira/browse/GERONIMO-4493
I am working on it, and it will be finished soon
https://issues.apache.org/jira/browse/GERONIMO-4603
I am working on it, and it will be finished soon
Thanks !
2009/9/11 David Jencks <david_jencks@...>
We may be able to release 2.2 soon. Activemq has fixed the last bug we had problems with and is fast approaching a release, openejb is getting very close to a release for 2.2, and I've started votes on a number of our snapshot dependencies.
At this point I'd like anyone who is working on something they'd like to get into 2.2 to reply to this with a description of what they are working on and an estimate for completion.
Also, if there is something you think is really necessary to get into 2.2 please reply and describe what you'd like.
many thanks
david jencks
--
Ivan
-- Shawn
-Shawn
|
|
Re: There's still hope for 2.2...
|
|
Re: There's still hope for 2.2...
There are some bugs I reported regarding adding/removing connectors. I
seriously think they need to be addressed. They are:
https://issues.apache.org/jira/browse/GERONIMO-4867https://issues.apache.org/jira/browse/OPENEJB-1070https://issues.apache.org/jira/browse/GERONIMO-4860https://issues.apache.org/jira/browse/GERONIMO-4861The last one is a regression of sorts (in other words is wasn't present in 2.1).
They're all small errors, and I listed them because they can
potentially damage Geronimo's image by complicating a user's
experience. User experience is the biggest factor in a product's
success.
Q
On Fri, Sep 11, 2009 at 11:49 AM, Ivan < xhhsld@...> wrote:
> Sorry, I make a mistaken, I did not mean
> https://issues.apache.org/jira/browse/GERONIMO-4603, I mean GERONIMO-4625
>
>
> 2009/9/11 Ivan < xhhsld@...>
>>
>> I wish those JIRAs to be included in Geronimo 2.2
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4801>> Please check my comment, I think we could just ignore the alreadyexisted
>> exception
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4821>> Please check my comment, I need more help on it :-(
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4836>> If anyone could help to check the patch in the current pluto snapshot,
>> that will be fine. or, I wish to fix it in Geronimo 2.2 firstly
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4493>> I am working on it, and it will be finished soon
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4603>> I am working on it, and it will be finished soon
>>
>> Thanks !
>>
>> 2009/9/11 David Jencks < david_jencks@...>
>>>
>>> We may be able to release 2.2 soon. Activemq has fixed the last bug we
>>> had problems with and is fast approaching a release, openejb is getting very
>>> close to a release for 2.2, and I've started votes on a number of our
>>> snapshot dependencies.
>>>
>>> At this point I'd like anyone who is working on something they'd like to
>>> get into 2.2 to reply to this with a description of what they are working on
>>> and an estimate for completion.
>>>
>>> Also, if there is something you think is really necessary to get into 2.2
>>> please reply and describe what you'd like.
>>>
>>> many thanks
>>> david jencks
>>>
>>
>>
>>
>> --
>> Ivan
>
>
>
> --
> Ivan
>
--
Quintin Beukes
|
|
Re: There's still hope for 2.2...
I'm working on improving the console filter performance. Will open a JIRA... -Jack On Fri, Sep 11, 2009 at 6:11 PM, Quintin Beukes <quintin@...> wrote:
There are some bugs I reported regarding adding/removing connectors. I
seriously think they need to be addressed. They are:
https://issues.apache.org/jira/browse/GERONIMO-4867
https://issues.apache.org/jira/browse/OPENEJB-1070
https://issues.apache.org/jira/browse/GERONIMO-4860
https://issues.apache.org/jira/browse/GERONIMO-4861
The last one is a regression of sorts (in other words is wasn't present in 2.1).
They're all small errors, and I listed them because they can
potentially damage Geronimo's image by complicating a user's
experience. User experience is the biggest factor in a product's
success.
Q
On Fri, Sep 11, 2009 at 11:49 AM, Ivan < xhhsld@...> wrote:
> Sorry, I make a mistaken, I did not mean
> https://issues.apache.org/jira/browse/GERONIMO-4603, I mean GERONIMO-4625
>
>
> 2009/9/11 Ivan < xhhsld@...>
>>
>> I wish those JIRAs to be included in Geronimo 2.2
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4801
>> Please check my comment, I think we could just ignore the alreadyexisted
>> exception
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4821
>> Please check my comment, I need more help on it :-(
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4836
>> If anyone could help to check the patch in the current pluto snapshot,
>> that will be fine. or, I wish to fix it in Geronimo 2.2 firstly
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4493
>> I am working on it, and it will be finished soon
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4603
>> I am working on it, and it will be finished soon
>>
>> Thanks !
>>
>> 2009/9/11 David Jencks < david_jencks@...>
>>>
>>> We may be able to release 2.2 soon. Activemq has fixed the last bug we
>>> had problems with and is fast approaching a release, openejb is getting very
>>> close to a release for 2.2, and I've started votes on a number of our
>>> snapshot dependencies.
>>>
>>> At this point I'd like anyone who is working on something they'd like to
>>> get into 2.2 to reply to this with a description of what they are working on
>>> and an estimate for completion.
>>>
>>> Also, if there is something you think is really necessary to get into 2.2
>>> please reply and describe what you'd like.
>>>
>>> many thanks
>>> david jencks
>>>
>>
>>
>>
>> --
>> Ivan
>
>
>
> --
> Ivan
>
Quintin Beukes
|
|
Re: There's still hope for 2.2...
Is there an approximate date of Geronimo 2.2 release ? I remembered that last time, what I got is in the early October. Thanks ! 2009/9/14 Jack Cai <greensight@...>
I'm working on improving the console filter performance. Will open a JIRA...
-JackOn Fri, Sep 11, 2009 at 6:11 PM, Quintin Beukes <quintin@...> wrote:
There are some bugs I reported regarding adding/removing connectors. I
seriously think they need to be addressed. They are:
https://issues.apache.org/jira/browse/GERONIMO-4867
https://issues.apache.org/jira/browse/OPENEJB-1070
https://issues.apache.org/jira/browse/GERONIMO-4860
https://issues.apache.org/jira/browse/GERONIMO-4861
The last one is a regression of sorts (in other words is wasn't present in 2.1).
They're all small errors, and I listed them because they can
potentially damage Geronimo's image by complicating a user's
experience. User experience is the biggest factor in a product's
success.
Q
On Fri, Sep 11, 2009 at 11:49 AM, Ivan < xhhsld@...> wrote:
> Sorry, I make a mistaken, I did not mean
> https://issues.apache.org/jira/browse/GERONIMO-4603, I mean GERONIMO-4625
>
>
> 2009/9/11 Ivan < xhhsld@...>
>>
>> I wish those JIRAs to be included in Geronimo 2.2
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4801
>> Please check my comment, I think we could just ignore the alreadyexisted
>> exception
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4821
>> Please check my comment, I need more help on it :-(
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4836
>> If anyone could help to check the patch in the current pluto snapshot,
>> that will be fine. or, I wish to fix it in Geronimo 2.2 firstly
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4493
>> I am working on it, and it will be finished soon
>>
>> https://issues.apache.org/jira/browse/GERONIMO-4603
>> I am working on it, and it will be finished soon
>>
>> Thanks !
>>
>> 2009/9/11 David Jencks < david_jencks@...>
>>>
>>> We may be able to release 2.2 soon. Activemq has fixed the last bug we
>>> had problems with and is fast approaching a release, openejb is getting very
>>> close to a release for 2.2, and I've started votes on a number of our
>>> snapshot dependencies.
>>>
>>> At this point I'd like anyone who is working on something they'd like to
>>> get into 2.2 to reply to this with a description of what they are working on
>>> and an estimate for completion.
>>>
>>> Also, if there is something you think is really necessary to get into 2.2
>>> please reply and describe what you'd like.
>>>
>>> many thanks
>>> david jencks
>>>
>>
>>
>>
>> --
>> Ivan
>
>
>
> --
> Ivan
>
Quintin Beukes
-- Ivan
|
|
Re: There's still hope for 2.2...
I am working on G 2.2 samples. Basically, I hope the existing G 2.2 samples plugins could be installable and runable on G 2.2 server.
I will post my results here soon.
|
|
Re: There's still hope for 2.2...
I'm still working on Daytrader 2.2, but could use some help updating and
testing the Daytrader plugins and plans.
-Donald
Forrest Xia wrote:
> I am working on G 2.2 samples. Basically, I hope the existing G 2.2
> samples plugins could be installable and runable on G 2.2 server.
>
> I will post my results here soon.
|
|
Re: There's still hope for 2.2...
|
|
Re: There's still hope for 2.2...
On Mon, Sep 14, 2009 at 10:48 PM, Donald Woods <dwoods@...> wrote:
I'm still working on Daytrader 2.2, but could use some help updating and testing the Daytrader plugins and plans.
-Donald
Donald, once you roll out all of changes on daytrader 2.2, I will have a testing on it.
|
|
documentation is important too
Quintin Beukes-2 wrote:
They're all small errors, and I listed them because they can
potentially damage Geronimo's image by complicating a user's
experience. User experience is the biggest factor in a product's
success.
I see it that biggest problem with Geronimo is lack of good documentation, mainly good documentation on security is still missing. After reading users mailing list for a while people asks for documents about:
How to secure internal derby database from connections into geronimo from outside? They want to have something like: for database XYZ user X and Y can connect. it can be probably done by binding security realm into database. it would be great if we can click it in gui.
same thing for message queues.
oh and deployment plans are another topic. There are some samples on doc website but i would really like to see some real world example for example web application with more modules, jpa and message queues. it took me almost entire day until i managed to write it correctly myself.
|
|
Re: documentation is important too
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Yes, I agree that documentation is really important to the success of Geronimo. We have lots of changes in terms of security, web container integration mechanism as well as GEP improvements for G2.2, and we know some of information are not well documented yet. For the current status of G2.2 doc development, you may refer to
http://cwiki.apache.org/GMOxDOC22/apache-geronimo-v22-documentation-development-status.htmlBeyond these items listed, I believe there are lots of topics to be updated such as new samples, screenshots and so on. Therefore, we would appreciate any individual who can contribute to the documents and especially for those who has successful experiences with configuration of certain components.
As for the examples that you mentioned, in my understanding, G Doc already has certain topics for those: 1. Database security realm, you may refer to http://cwiki.apache.org/GMOxDOC22/database-sql-realm.html
2. Real samples, we have sample applications for test and evaluation, you may refer to http://cwiki.apache.org/GMOxDOC22/sample-applications.html#Sampleapplications-AvailableSampleApplications or WAS CE samples which can be deployed on Geronimo as well
3. Tutorial for various applications' development, which might not cover every corner by now but it would be applaudable if we could have more and more tutorials on website. For this part, you may refer to
http://cwiki.apache.org/GMOxDOC22/developing-web-applications.html http://cwiki.apache.org/GMOxDOC22/developing-ejb-applications.html
http://cwiki.apache.org/GMOxDOC22/developing-jpa-applications.html http://cwiki.apache.org/GMOxDOC22/developing-application-clients.html
http://cwiki.apache.org/GMOxDOC22/developing-web-services.htmlWe'd like to hear more about your comments to the document such as the documents are not well-orgnized? what kind of topics are missing? Or you can share your experience briefly, we can help to document? I think more details will do more help.
Thanks alot. Jeff C On Tue, Sep 15, 2009 at 5:27 AM, Radim Kolar <hsn@...> wrote:
Quintin Beukes-2 wrote:
>
> They're all small errors, and I listed them because they can
> potentially damage Geronimo's image by complicating a user's
> experience. User experience is the biggest factor in a product's
> success.
>
I see it that biggest problem with Geronimo is lack of good documentation,
mainly good documentation on security is still missing. After reading users
mailing list for a while people asks for documents about:
How to secure internal derby database from connections into geronimo from
outside? They want to have something like: for database XYZ user X and Y can
connect. it can be probably done by binding security realm into database. it
would be great if we can click it in gui.
same thing for message queues.
oh and deployment plans are another topic. There are some samples on doc
website but i would really like to see some real world example for example
web application with more modules, jpa and message queues. it took me almost
entire day until i managed to write it correctly myself.
--
View this message in context: http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25443963.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
|
|
Re: There's still hope for 2.2...
I finished the patch for the console filter to improve its performance: https://issues.apache.org/jira/browse/GERONIMO-4874Hopefully someone could review it...
-Jack On Mon, Sep 14, 2009 at 10:53 PM, Forrest Xia <forrestxm@...> wrote:
On Mon, Sep 14, 2009 at 10:48 PM, Donald Woods <dwoods@...> wrote:
I'm still working on Daytrader 2.2, but could use some help updating and testing the Daytrader plugins and plans.
-Donald
Donald, once you roll out all of changes on daytrader 2.2, I will have a testing on it.
|
|
Re: documentation is important too
Database security realm is something different, it is about checking userids against database. I am talking about restricting access to Derby
database itself.
Example: (G in default setup)
ij> connect 'jdbc:derby://localhost/SystemDatabase';
ij> show tables;
TABLE_SCHEM |TABLE_NAME |REMARKS
------------------------------------------------------------------------
SYS |SYSALIASES |
SYS |SYSCHECKS |
SYS |SYSCOLPERMS |
SYS |SYSCOLUMNS |
same for message queues. In short no security restrictions are in place.
|
|
Re: documentation is important too
Well, I think it's something missing in Geronimo. You might want to file a JIRA for this one. https://issues.apache.org/jira/browse/GERONIMOAnd I am also interested in the struggle you experienced, as you mentioned earlier, it took you almost entire day to write it correct.
Could you let us more details about the scenario, I believe your experience could help us to improve the document. Thanks alot. Jeff C On Tue, Sep 15, 2009 at 4:27 PM, Radim Kolar <hsn@...> wrote:
Database security realm is something different, it is about checking userids
against database. I am talking about restricting access to Derby
database itself.
Example: (G in default setup)
ij> connect 'jdbc:derby://localhost/SystemDatabase';
ij> show tables;
TABLE_SCHEM |TABLE_NAME |REMARKS
------------------------------------------------------------------------
SYS |SYSALIASES |
SYS |SYSCHECKS |
SYS |SYSCOLPERMS |
SYS |SYSCOLUMNS |
same for message queues. In short no security restrictions are in place.
--
View this message in context: http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25450084.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
|
|
Re: documentation is important too
RunHua Chi wrote:
We'd like to hear more about your comments to the document such as the
documents are not well-orgnized? what kind of topics are missing? Or you can
share your experience briefly, we can help to document? I think more details
will do more help.
I have not checked WAS CE examples, but examples on G web page didn't have xsd files referenced in xml header, it was quite difficult to guess what tags are used because eclipse xml editor didnt helped much. ibm documentation also didnt mention where xsd files are available via HTTP. http://publib.boulder.ibm.com/wasce/V2.1.1/en/developing-deployment-plans.htmli used some examples on web site as reference but they were too simple.
|
|
Re: documentation is important too
Hi Radim, thanks for your comments.
|
|
put XSD schemas on G web
These diagrams drawn from XSD are very nice. I recommend to put plain XSD files in text/xml format on G web similar how maven have it. Desired URL will look like:
http://geronimo.apache.org/xsd/geronimo-module-1.2.xsdwe can then start using this URL in xsi:schemaLocation so XML editors can check syntax during typing deployement plans and then update deployment examples to let people know about it.
|
|
Re: put XSD schemas on G web
|
