I am under the impression that the open wire protocol should
always be able to maintain backward compatibility.
Does this mean that we will never change the major version ;-)
On 1/23/07, Brian McCallister [EMAIL PROTECTED] wrote:
On Jan 23, 2007, at 9:15 AM, Rob Davies wrote:
The latest
Rob Davies wrote:
Hi Brian,
this isn't exactly true - we have always incremented the major version
number with wire protocol changes when they are not backward compatible
- but it's erroneous to assume that there is a casual link between the
two - its just been coincidental to date.
+1 to adopt APR.
As 4.2 has a a different store format for some store implementations
(Kaha/rapid/quick) and we need to introduce a new default store to
maintain performance with persistent cursors, plus the change from
JRE 1.4 to JRE 1.5, the next release should be version 5.0
cheers,
Autoconf is not properly setting CXXFLAGS on Linux
--
Key: AMQCPP-51
URL: https://issues.apache.org/activemq/browse/AMQCPP-51
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions:
Valgrind reports memory leaks when running PrimitiveMapTest
---
Key: AMQCPP-52
URL: https://issues.apache.org/activemq/browse/AMQCPP-52
Project: ActiveMQ C++ Client
Issue Type: Bug
Slow consumer causes producer to block on UsageManager.waitForSpace indefinately
Key: AMQ-1136
URL: https://issues.apache.org/activemq/browse/AMQ-1136
Project: ActiveMQ
[
https://issues.apache.org/activemq/browse/AMQCPP-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQCPP-52.
--
Resolution: Fixed
This is code that is still in development. Code that is tagged with AMQCPP-30
[
https://issues.apache.org/activemq/browse/AMQCPP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler updated AMQCPP-51:
-
Fix Version/s: 2.0
Autoconf is not properly setting CXXFLAGS on Linux
[
https://issues.apache.org/activemq/browse/AMQCPP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler closed AMQCPP-51.
Resolution: Duplicate
This is a duplicate of AMQCPP-49. I have re-opened that issue to address
David J. found a couple issues with the latest changes, both have
been fixed. Posting in case you ran into these.
One was a null pointer caused during deployment:
[WARNING] Caused by: java.lang.NullPointerException
[WARNING] at org.apache.xbean.finder.ClassFinder.readClassDef
[
https://issues.apache.org/jira/browse/GERONIMO-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466671
]
Jason Dillon commented on GERONIMO-2768:
No rush, its the wrong version and should be fixed. You said
IMO, its the wrong version, and regardless of what the Java EE TCK
muck provides we should fix it.
--jason
On Jan 22, 2007, at 10:40 PM, Dain Sundstrom wrote:
On Jan 22, 2007, at 9:33 PM, Jason Dillon wrote:
On Jan 22, 2007, at 9:28 PM, David Blevins wrote:
Should probably still change
Webconsole does not work in Internet Explorer 7
---
Key: SM-824
URL: https://issues.apache.org/activemq/browse/SM-824
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.1
Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever
Key: GERONIMO-2776
URL: https://issues.apache.org/jira/browse/GERONIMO-2776
Project: Geronimo
[
https://issues.apache.org/jira/browse/GERONIMO-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lasantha Ranaweera updated GERONIMO-2776:
-
Attachment: GERONIMO-2776.patch
Axis2 Integration - Replace
Hi,
Initial patch for the replacing RPCMessageReciever with
JAXWSMessageReciever is submitted under *GERONIMO-2776*. Had to change
some of the coding to handle ?wsdl request correctly in the newer version.
Thanks,
Lasantha Ranaweera
I have noticed that during online module build timestamped versions
of geronimo jars are downloaded. These are older than the locally built
ones! I usually watch online activity carefully and zap all the
timestamped jars. But this one got away.. Thanks Matt and Kevan!
Anita
--- Kevan Miller
[
https://issues.apache.org/activemq/browse/SM-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Langborg-Hansen updated SM-824:
Attachment: main.jsp
I've changed this decorator to use empty script tags instead
[
https://issues.apache.org/activemq/browse/AMQ-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies reassigned AMQ-1077:
---
Assignee: Rob Davies
Bug in STOMP transport unsubscribe
--
[
https://issues.apache.org/activemq/browse/AMQ-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-1077.
-
Resolution: Fixed
Fix Version/s: 4.2.0
resolved by SVN revision 499032
Bug in STOMP transport
Hi,
If i use PortableRemoteObject narrow in a servlet i get a exception.
[TestHome testHome = (TestHome) PortableRemoteObject.narrow(result,
TestHome.class);]
java.lang.ExceptionInInitializerError
javax.rmi.PortableRemoteObject.clinit(PortableRemoteObject.java:36)
The RMI code (i.e,, PortableRemoteObject) is dependent on the Corba
support getting properly initialized. Your application needs to have a
dependency on the sj2ee-corba-yoko config, which handles all of that.
Rick
Krishnakumar B wrote:
Hi,
If i use PortableRemoteObject narrow in a servlet
Hi,
I tried to find out where the Role of a MessageExchange is being set. I got
stuck with the following, and was hoping that someone might help me out with
clarifying the issue(s).
1.) States of MEs
==
A MessageExchange (ME) has an array of possible states (int [][]states),
Here is the current rev of the Release Notes (far better than my
previous note). The new RELEASE NOTES are located at https://
svn.apache.org/repos/asf/geronimo/server/trunk/RELEASE-NOTES-2.0-M2.TXT
Please take a look and commit your updates directly to this file.
I'll make the copy around
David, I thought I had already fixed this... for my knowledge, what
else needed to be done?
On Jan 22, 2007, at 9:54 PM, David Jencks wrote:
Btw in somewhat related work I fixed GERONIMO-2769 so that now if
you deploy an ear without an application.xml you can get to all the
problems you
On 1/23/07, Rossmanith, Philipp [EMAIL PROTECTED] wrote:
Hi,
I tried to find out where the Role of a MessageExchange is being set. I got
stuck with the following, and was hoping that someone might help me out with
clarifying the issue(s).
1.) States of MEs
==
A
Expose JAX-WS mandatory MessageContext properties
--
Key: GERONIMO-2777
URL: https://issues.apache.org/jira/browse/GERONIMO-2777
Project: Geronimo
Issue Type: New Feature
Security
[
https://issues.apache.org/activemq/browse/SM-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-824.
Resolution: Fixed
Fix Version/s: 3.1
Assignee: Guillaume Nodet
Author: gnodet
On Jan 23, 2007, at 10:03 AM, Donald Woods wrote:
How do we handle the following requirement of the Sun CDDL?
+3.1. Availability of Source Code.
+
+Any Covered Software that You distribute or otherwise make available
+in Executable form must also be made available in Source Code form
and
[
https://issues.apache.org/jira/browse/GERONIMO-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated GERONIMO-2777:
--
Attachment: GERONIMO-2777.patch
The attached file includes a number of features:
1) Added
Will we continue to support prior server levels with the 2.0.0 Eclipse
Plug-in, or will the new plug-in only support JEE 5 2.x servers?
Seems like a good time to split the plug-in and say - use the 1.2.x
plug-in for Geronimo 1.x and use the 2.x plug-in for Geronimo 2.x.
-Donald
Rick,
Should we be initializing this as a dependency of j2ee-system or
another component? Seems like users should get this for free and not
have to declare their own dependency.
I now pause in silence waiting for the mighty ORBitor of truth to speak.
On Jan 23, 2007, at 9:36 AM, Rick
During an online build of jee-specs configs (from configs dir)
g-gbean-deployer was downloaded (see below) instead of using the one
that was built just before it. This is a know issue. The way it was
installed in the repo is strange! I have listed the relevant contents
of .m2 repo:
Directory
My mail program stripped the **. Adding them again..
Anita
--- anita kulshreshtha [EMAIL PROTECTED] wrote:
During an online build of jee-specs configs (from configs dir)
g-gbean-deployer was downloaded (see below) instead of using the one
that was built just before it. This is a
On Jan 23, 2007, at 6:56 AM, Sachin Patel wrote:
David, I thought I had already fixed this... for my knowledge, what
else needed to be done?
The code I started with only processed the geronimo application plan
if there was an application.xml. If the application.xml was missing
the
Destroying durable subscription, does not entirely destory the durable subsciber
Key: AMQ-1135
URL: https://issues.apache.org/activemq/browse/AMQ-1135
Project: ActiveMQ
Yes, my current thinking is we need to continue providing support for
previous versions of Geronimo in WTP 2.0, so thus the support code
will need to continue to reside in trunk. However, the support in
for each version of G, should be broken down into multiple features,
so that support
On Jan 23, 2007, at 7:52 AM, Matt Hogstrom wrote:
Rick,
Should we be initializing this as a dependency of j2ee-system or
another component? Seems like users should get this for free and
not have to declare their own dependency.
IIRC the way things are set up now you get the orbs
In short the timestamped pom, i.e.
geronimo-gbean-deployer-2.0-20070120.231353-2.pom
is installed in 2.0-20070120.231353-2 dir and not in 2.0-SNAPSHOT.
Thanks
Anita
--- anita kulshreshtha [EMAIL PROTECTED] wrote:
During an online build of jee-specs configs (from configs dir)
Hi,
Response between the lines...
1.) States of MEs
==
A MessageExchange (ME) has an array of possible states (int
[][]states),
which differs depending on the type of the ME. It is only being set in
the
constructor of MessageExchangeImpl.
When being sent, the method:
[
https://issues.apache.org/jira/browse/GERONIMO-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom updated GERONIMO-2638:
Fix Version/s: (was: 2.0-M2)
2.0-beta1
Deferred to beta-1 due to
The connector spec was not updated for jee5 and if you check the
connector 1.5 specification is references jta 1.0.1b. It is the
correct dependency for that spec.
Regardless, there is not reason to change the pom, since it has no
effect on the jar or any one using the dependency. It
Can you announce the new names of the mailing lists so we can update
our mail filters before the flood?
:)
-dain
On Jan 22, 2007, at 4:28 PM, Brian McCallister wrote:
Doh! I have been so pre-occupied with work I didn't mention. Bad me!
We graduated! Now to start pestering infra... ;-)
David Jencks wrote:
On Jan 23, 2007, at 7:52 AM, Matt Hogstrom wrote:
Rick,
Should we be initializing this as a dependency of j2ee-system or
another component? Seems like users should get this for free and not
have to declare their own dependency.
IIRC the way things are set up now you
On 1/23/07, Rossmanith, Philipp [EMAIL PROTECTED] wrote:
Hi,
Response between the lines...
1.) States of MEs
==
snipped
Ok. The CAN_OWNER flags are maintained along with the states; in a given
state (which has been changed by accepting or sending an ME), it is or
is not
On 1/23/07, Rossmanith, Philipp [EMAIL PROTECTED] wrote:
On a side note, I like the structure of the Cocoon documentation, where
general documentation is divided into a User and Developer part
depending on whether you want to only use the framework or want to code
On 1/22/07, David Blevins [EMAIL PROTECTED] wrote:
Ok. All of these issues should be fixed.
I did a complete clean Geronimo ( OpenEJB) build. I am still having
issues here -
1) http://issues.apache.org/jira/browse/GERONIMO-2770.
An ejb-module with a missing ejb-jar.xml will not be recognized
I'm getting a test failure this morning on trunk...
Running org.apache.geronimo.openejb.deployment.EjbModuleBuilderTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.5
sec FAILURE!
cat modules/geronimo-openejb-builder/target/surefire-reports/TEST-
The latest development is being done on ActiveMQ 4.2 - however there
are a lot of improvements between 4.1 and 4.2 - namely:
1. Use of Java 5
2. Message cursors for persistent messages
3. Spooling of temporary messages id broker memory is full
and to be delivered in the next couple of weeks:
yes, I am getting this too.
Anita
--- David Jencks [EMAIL PROTECTED] wrote:
I'm getting a test failure this morning on trunk...
Running org.apache.geronimo.openejb.deployment.EjbModuleBuilderTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.5
sec FAILURE!
Yep. I hit it, too...
--kevan
On Jan 23, 2007, at 11:56 AM, David Jencks wrote:
I'm getting a test failure this morning on trunk...
Running org.apache.geronimo.openejb.deployment.EjbModuleBuilderTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.5
sec FAILURE!
cat
[
https://issues.apache.org/jira/browse/GERONIMO-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-1716:
---
Attachment: (was: Geronimo-1716.patch)
Add usage of SimpleEncryption to
[
https://issues.apache.org/jira/browse/GERONIMO-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-1716:
---
Attachment: G1716.patch
Updated patch created against server/trunk.
Patch includes
[
https://issues.apache.org/jira/browse/GERONIMO-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-1716:
---
Affects Version/s: 2.0
1.1.1
Fix Version/s: (was: Wish
So far we have received a few positive comments, no negative and no vetos.
So are we ok with this donation and ready to move forward, possible into
incubation?
Filip
Kevan Miller wrote:
On Jan 17, 2007, at 10:33 AM, Alex Karasulu wrote:
+1 on the CCLA's with a patch submission. If it's a
Ok, one other item we don't support is an ear with an ejbjar, with no
application.xml, nor an ejb-jar.xml. The EARConfigBuilder needs to
inspect classes for any ejb related annotations in order to classify
it as an ejbjar. Same goes for other modules contained in an ear
with no module or
Woops... responded just now to the wrong thread...
Ok, one other item we don't support is an ear with an ejbjar, with no
application.xml, nor an ejb-jar.xml. The EARConfigBuilder needs to
inspect classes for any ejb related annotations in order to classify
it as an ejbjar. Same goes for
Ignore.. responded to the wrong thread.
On Jan 23, 2007, at 1:18 PM, Sachin Patel wrote:
Ok, one other item we don't support is an ear with an ejbjar, with
no application.xml, nor an ejb-jar.xml. The EARConfigBuilder needs
to inspect classes for any ejb related annotations in order to
[
https://issues.apache.org/jira/browse/GERONIMO-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466793
]
Donald Woods commented on GERONIMO-2728:
Caused by ldap-demo dependency on ldap-realm, which depends on
[
https://issues.apache.org/jira/browse/GERONIMO-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466804
]
Paul McMahan commented on GERONIMO-2728:
I agree with #1 above, and also agree with #2 in principle if
Deployer should NOT always require interfaces elements in ejb-ref
---
Key: GERONIMO-2778
URL: https://issues.apache.org/jira/browse/GERONIMO-2778
Project: Geronimo
Issue Type:
The easiest way to reference a 3.0 EJB is by dependency injection
(@EJB). But we don't have annotations working in servlets yet. So if
we go back to doing the traditional way of a lookup, we would have to
declare a ejb-ref in the web.xml
Even if the annotations are processed, they write an
Hi Lasantha,
Thanks for submitting the patch! Your patch (java portion) looks look to
me. I don't quite understand the pom.xml portion of the patch as to why the
changes are needed. Was this related to some class loading issues you
mentioned to me in another note? Also, my guess is that you
I took a look at this package and found a lot of potentially valuable
material for Geronimo users. It contains source code for a collection
of command line utils and eclipse plugins, several unit test cases,
build scripts in good working order, and good documentation.
The project is not
On Jan 19, 2007, at 2:47 PM, Hernan Cunico wrote:
Alan D. Cabrera wrote:
On Jan 18, 2007, at 6:12 AM, Hernan Cunico wrote:
Howdy,
it may sound weird asking this now but I'm either creating JIRAs
the wrong way or we are not displaying the all the info in http://
Builds for me. Hee, hee, it's so nice the be on the other side of a
build failure for once...
Regards,
Alan
On Jan 23, 2007, at 9:23 AM, Kevan Miller wrote:
Yep. I hit it, too...
--kevan
On Jan 23, 2007, at 11:56 AM, David Jencks wrote:
I'm getting a test failure this morning on
On Jan 23, 2007, at 5:16 PM, Alan D. Cabrera wrote:
Builds for me. Hee, hee, it's so nice the be on the other side of
a build failure for once...
:-)
David J fixed the problem...
--kevan
qdox dies because it cannot resolve javax/servlet/ServletContext
Key: XBEAN-71
URL: https://issues.apache.org/jira/browse/XBEAN-71
Project: XBean
Issue Type: Bug
Alright, so I figured out how to fix the naming code so that it will
work for business interfaces as well as references from servlets to
ejb for business interfaces. Dain is hacking it in now.
On Jan 23, 2007, at 11:49 AM, Prasad Kashyap wrote:
The easiest way to reference a 3.0 EJB is by
[
https://issues.apache.org/jira/browse/GERONIMO-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins updated GERONIMO-2778:
Description:
For a proper ejb-ref to an EJB 3.0 bean (i.e. a business interface) it
[
https://issues.apache.org/jira/browse/GERONIMO-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom updated GERONIMO-2607:
Affects Version/s: (was: 2.0)
2.0-M2
Applied kernel patch
[
https://issues.apache.org/activemq/browse/AMQCPP-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler reassigned AMQCPP-30:
Assignee: Timothy Bish (was: Nathan Mittler)
Add support to activemq-cpp to support
I believe this requires a formal vote of the project first.
-dain
On Jan 23, 2007, at 9:43 AM, Filip Hanik - Dev Lists wrote:
So far we have received a few positive comments, no negative and no
vetos.
So are we ok with this donation and ready to move forward, possible
into incubation?
[
https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Mittler closed AMQCPP-49.
Resolution: Fixed
The compiler options are working correctly now. Due to some problems with
For those interested and following this thread (D Jencks had a similar
NPE), both these issues are now resolved.
We can now have a ejb-jar.xml free deployment and openejb-jar.xml free
deployment.
Cheers
Prasad
On 1/23/07, Prasad Kashyap [EMAIL PROTECTED] wrote:
On 1/22/07, David Blevins
[
https://issues.apache.org/jira/browse/GERONIMO-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466893
]
Jason Warner commented on GERONIMO-2757:
When originally tackling this issue, my hope was to maintain
I think this has broken some stuff. This piece of code in
PersistenceUnitReference is no longer working:
entityManagerFactory = kernel.invoke(target,
getEntityManagerFactory);
I'll try to code around the problem for this instance, but you may
want to roll back this commit.
I branched tonight. The Geronimo version was 499258 from trunk and
OpenEJB was at 499255. I'll manually apply the appropriate fixes to
branches/2.0-M2 as needed to get the EJB sample working. There is
just a bunch of distruptive stuff I need to do in terms of updating
versions and such
[
https://issues.apache.org/jira/browse/GERONIMO-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller closed GERONIMO-2690.
--
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0-M2
[
https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller closed GERONIMO-2689.
--
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0-M2
Thanks
[
https://issues.apache.org/jira/browse/GERONIMO-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller closed GERONIMO-2691.
--
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0-M2
Fixed
JNDI, Dependency, and ClassLoader views don't work with Safari browser
--
Key: GERONIMO-2779
URL: https://issues.apache.org/jira/browse/GERONIMO-2779
Project: Geronimo
Transactional, non persistent queing very slow under Linux
--
Key: AMQ-1137
URL: https://issues.apache.org/activemq/browse/AMQ-1137
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/activemq/browse/AMQ-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37973
]
Helmut Janknecht commented on AMQ-1137:
---
I found this mailing list article:
please help guys!
what am i doing wrong (i'm doing this the xbean.xml way to create an SA with
SU's)?
XBEAN.XML:
beans xmlns:sm=http://servicemix.apache.org/config/1.0;
xmlns:rmb=http://www.rmb.co.za;
xmlns:eip=http://servicemix.apache.org/eip/1.0;
[
https://issues.apache.org/activemq/browse/AMQ-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37974
]
Helmut Janknecht commented on AMQ-1137:
---
When taking a {{jstack}} snapshot while producer is running I can see
[
https://issues.apache.org/activemq/browse/AMQCPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37975
]
Albert Strasheim commented on AMQCPP-49:
The CXXFLAGS in src/test/Makefile.am issue is weird. Changing
Declaration of extern int errno after including errno.h doesn't compile
---
Key: AMQCPP-53
URL: https://issues.apache.org/activemq/browse/AMQCPP-53
Project: ActiveMQ C++ Client
88 matches
Mail list logo
