(Sorry, my reply was “stuck” in the draft folder)
Many thanks! It’s great to see external products giving back to their OSS
siblings.
Hope to see more great work!
Regards,
Alan
> On Feb 28, 2017, at 3:25 PM, David Jencks wrote:
>
> I’ve merged the commits from
> On Nov 18, 2015, at 9:50 AM, Alan D. Cabrera wrote:
>
> So sorry about the egregious delay in my reply. :(
I’ve been really busy too….
>
>> On Jul 30, 2015, at 10:53 AM, David Jencks wrote:
>>
>> I am pleased to finally be able to announce
So sorry about the egregious delay in my reply. :(
> On Jul 30, 2015, at 10:53 AM, David Jencks wrote:
>
> I am pleased to finally be able to announce that the Yoko orb is now used in
> IBM’s WAS Liberty application server, the first EE 7 certified application
>
So why not release it as version=1.1 and we'll spin a 1.1.1 if more
updates are required? Not sure why we need to version it as a Milestone
release Is there a TCK required? If so, why not upgrade 2.1.5 or
2.2.1-SNAPSHOT to use the new level and verify it still passes the Java
EE 5 TCKs?
I agree, 1.1 is the best version. I'm not sure I want to try to get the
appropriate tck tests running in 2.2, but if anyone else is game.
thanks
david jencks
On Apr 22, 2010, at 10:10 AM, Donald Woods wrote:
So why not release it as version=1.1 and we'll spin a 1.1.1 if more
updates are
Gianny Damour wrote:
Hello Rick,
Sorry, this is not directly related to your question. What kind of
integration with ObjectGrid have you been working on? FWIW, I am
working on a hierarchical, transactional, distributed, partitioned and
replicated cache and data-grid solution as part of WADI
Rick McGuire wrote:
I've recently completed an activity on seeing if we could get the IBM
ObjectGrid product working with the Yoko ORB. This is a BIG CORBA
application that rooted out quite a number of fringe bugs in the Yoko
ORB. The testing effort involved no just interactions between a
I think it is time to consider publishing the 1.0 release so
there's finally an official release level to work from. I currently don't
have any work items I feel need to be done before a 1.0 release can get
created. I have a number of items I think need to get improved what I'd
prefer doing
On May 2, 2008, at 9:43 AM, Rick McGuire wrote:
I've recently completed an activity on seeing if we could get the
IBM ObjectGrid product working with the Yoko ORB. This is a BIG
CORBA application that rooted out quite a number of fringe bugs in
the Yoko ORB. The testing effort involved
Hello Rick,
Sorry, this is not directly related to your question. What kind of
integration with ObjectGrid have you been working on? FWIW, I am
working on a hierarchical, transactional, distributed, partitioned
and replicated cache and data-grid solution as part of WADI and I am
quite
So... should these be removed from the repository/pom.xml?
--jason
On Apr 22, 2008, at 4:04 AM, Rick McGuire wrote:
Jason Dillon wrote:
Why are there yoko deps listed in the repository module, but there
are no artifacts for org/apache/yoko checked in there?
Looks like it was just a missed
Jason Dillon wrote:
Why are there yoko deps listed in the repository module, but there are
no artifacts for org/apache/yoko checked in there?
Looks like it was just a missed update when trunk was switched back to
pick up the snapshot dependency. We've been shipping with a new pinned
yoko
Vasily Zakharov wrote:
Hi, all,
As far as I understand, Yoko is now a Geronimo sub-component, but as
far as I remember, there was an agreement [1] to keep the core ORB a
standalone
component so that it would be usable by, e. g. Harmony.
Harmony now uses a very (more than a year) old version of
Well, 1.0-SNAPSHOT seems fine.
Thanks!
Vasily
On Mon, Mar 31, 2008 at 12:35 PM, Rick McGuire [EMAIL PROTECTED] wrote:
Vasily Zakharov wrote:
Hi, all,
As far as I understand, Yoko is now a Geronimo sub-component, but as
far as I remember, there was an agreement [1] to keep the core
By the time we release it, it will be renamed to o.a.cxf.something.
Right now, I'm leaving the package name alone as I merge in some patches
that IONA has internally to update it to work with the latest CXF (and
latest CXF dependencies like the newer XmlSchema and such). If the
package
+1 for keeping tools.
2008/1/17, Alan D. Cabrera [EMAIL PROTECTED]:
I was wondering if we prematurely deleted tools. It would be nice to
have our own IDL compiler. I was thinking that we could move tools to
a dir in the sandbox for someone to pick up. Thoughts?
Regards,
Alan
2008/1/17, Joseph Leong [EMAIL PROTECTED]:
Hi there Alan,
In terms of starting a Wiki, there are several options out there... just to
name a few popular ones:
Confluence
http://www.atlassian.com/software/confluence/
Media Wiki
http://www.mediawiki.org/wiki/MediaWiki
Doku Wiki
Subject: Re: [YOKO] Yoko web site
:)
What does XBean and GShell do?
Regards,
Alan
On Jan 16, 2008, at 5:18 PM, Jason Dillon wrote:
Well there is this thing called HTML and you use it to make things
called pages and then put them on a web server...
:-P
What do you want... Something
Did you get this sorted... or on your way to sorted? Ping me if you
need any help... especially if its the kinda help where I don't really
have to do anything :-P
--jason
On Jan 16, 2008, at 4:41 PM, Alan D. Cabrera wrote:
I want to start creating the new Yoko website and wiki. How do I
Keep 'em around, we can always whack them later.
On Jan 17, 2008, at 1:51 AM, Alan D. Cabrera wrote:
I was wondering if we prematurely deleted tools. It would be nice
to have our own IDL compiler. I was thinking that we could move
tools to a dir in the sandbox for someone to pick up.
I assume tools will also live in CXF for the IDL-WSDL compilers. If
we keep our own copy (which I think is a good idea) we need to make
sure that our package name is different from theirs. I assume they
will eventually use o.a.cxf.something, but currently they are not:
I'm +1 for 1.0 release too.
I've reviewed japitool results for ORB area of Harmony and I have not
find any differences which are result of 1.4 compatibility of Yoko. So
it looks like there is no difference for Harmony in this case. But
yes, Harmony is 1.5 (however it has 1.6 branch :) and any 1.5
Well there is this thing called HTML and you use it to make things called
pages and then put them on a web server...
:-P
What do you want... Something backed up by confluence? Or static via svn?
--jason
-Original Message-
From: Alan D. Cabrera [EMAIL PROTECTED]
Date: Wed, 16 Jan
:)
What does XBean and GShell do?
Regards,
Alan
On Jan 16, 2008, at 5:18 PM, Jason Dillon wrote:
Well there is this thing called HTML and you use it to make things
called pages and then put them on a web server...
:-P
What do you want... Something backed up by confluence? Or static
Hi there Alan,
In terms of starting a Wiki, there are several options out there... just to
name a few popular ones:
Confluence
http://www.atlassian.com/software/confluence/
Media Wiki
http://www.mediawiki.org/wiki/MediaWiki
Doku Wiki
http://wiki.splitbrain.org/wiki:dokuwiki
PmWiki
They use confluence and auto-export.
--jason
-Original Message-
From: Alan D. Cabrera [EMAIL PROTECTED]
Date: Wed, 16 Jan 2008 21:39:43
To:dev@geronimo.apache.org
Subject: Re: [YOKO] Yoko web site
:)
What does XBean and GShell do?
Regards,
Alan
On Jan 16, 2008, at 5:18 PM
Hi Lars,
Just a note about JDK versions. Since Geronimo 2.x is targeted at JEE5,
1.5 is actually a requirement now.
By the way - Welcome to Geronimo.
Jay
Lars Kühne wrote:
On Jan 14, 2008 8:05 PM, Alan D. Cabrera wrote:
On Jan 14, 2008, at 4:35 AM, Rick McGuire wrote:
What cleanup
The Yoko ORB code still generates 1.4 compatible code. Since the ORB
doesn't have any direct dependencies on Geronimo, it probably can be
maintained as just being dependent on 1.4. On the other hand, there are
many times I wished I could use some of the stuff in 1.5 (such as the
concurrency
Lars Kühne wrote:
On Jan 14, 2008 8:05 PM, Alan D. Cabrera wrote:
On Jan 14, 2008, at 4:35 AM, Rick McGuire wrote:
What cleanup steps need to be taken with the yoko code now that it's
been made a subproject in Geronimo? The first obvious one would be
to remove the non-core components
On Jan 15, 2008, at 7:03 AM, Rick McGuire wrote:
The Yoko ORB code still generates 1.4 compatible code. Since the
ORB doesn't have any direct dependencies on Geronimo, it probably
can be maintained as just being dependent on 1.4. On the other
hand, there are many times I wished I could
On Jan 14, 2008, at 4:35 AM, Rick McGuire wrote:
What cleanup steps need to be taken with the yoko code now that it's
been made a subproject in Geronimo? The first obvious one would be
to remove the non-core components from the trunk. The second would
be to remove the incubating from
On Jan 14, 2008 8:05 PM, Alan D. Cabrera wrote:
On Jan 14, 2008, at 4:35 AM, Rick McGuire wrote:
What cleanup steps need to be taken with the yoko code now that it's
been made a subproject in Geronimo? The first obvious one would be
to remove the non-core components from the trunk. The
Heh heh. Yeah I caught up w/ all my holiday mail and saw that.
We've completed copying, though not paring down, Yoko to the Geronimo
area. Are you guys fine with me making the old Yoko area R/O?
Regards,
Alan
On Jan 9, 2008, at 1:32 PM, Daniel Kulp wrote:
Thanks Alan!
I've already
On Jan 8, 2008, at 9:22 PM, Alan D. Cabrera wrote:
I can Jira issues over to CXF. I'm guessing that issues in the
following components need to be moved over:
CorbaBinding
Idl2Wsdl
Wsdl2Idl
I'll leave these assigned to no component for the CXF team to pick up.
I decided to create a
Hi,
In order to use the CORBA classes you will need to have those jars
before the jdk's implementation.
Cheers, Edell.
-Original Message-
From: Donald Woods [mailto:[EMAIL PROTECTED]
Sent: 24 April 2007 14:44
To: gdev
Subject: Yoko and java.endorsed.dirs question
What order should
Donald Woods wrote:
What order should the paths be for java.endorsed.dirs?
Should it be -
1) JDK's lib/endorsed before Geronimo's lib/endorsed
2) Geronimo's lib/endorsed before the JDK's lib/endorsed
I'm wondering due to the following warning/exception in the
geronimo-corba module -
I'm actually seeing a failure to start the server on certain IBM JVM's,
like the IBM SDK for Solaris (or HP-UX.) This is due to a unique
packaging change, where they supply a jre/lib/endorsed directory which
contains the following -
ibmcertpathfw.jaribmjgssfw.jar
Donald Woods wrote:
I'm actually seeing a failure to start the server on certain IBM
JVM's, like the IBM SDK for Solaris (or HP-UX.) This is due to a
unique packaging change, where they supply a jre/lib/endorsed
directory which contains the following -
ibmcertpathfw.jar
Given that yoko must come first in java.endorsed.dirs, shouldn't
geronimo change to put it first? Ie in geronimo.sh and
geronimo-maven-plugin?
On 4/24/07, Rick McGuire [EMAIL PROTECTED] wrote:
Donald Woods wrote:
I'm actually seeing a failure to start the server on certain IBM
JVM's, like
Ted Kirby wrote:
Given that yoko must come first in java.endorsed.dirs, shouldn't
geronimo change to put it first? Ie in geronimo.sh and
geronimo-maven-plugin?
Well, since the person asking the question is a Geronimo committer who
appears to be looking at this issue, I was assuming he'd
Yep, I'm going to open a JIRA for it. Was verifying the fix for G3113
before diving into this problem, given all the touch points
-Donald
Rick McGuire wrote:
Ted Kirby wrote:
Given that yoko must come first in java.endorsed.dirs, shouldn't
geronimo change to put it first? Ie in
Along the same train of thought - Should we always place the Geronimo
server's lib/ext before the JVM's?
-Donald
Rick McGuire wrote:
Donald Woods wrote:
I'm actually seeing a failure to start the server on certain IBM
JVM's, like the IBM SDK for Solaris (or HP-UX.) This is due to a
Donald Woods wrote:
Along the same train of thought - Should we always place the Geronimo
server's lib/ext before the JVM's?
Probably safest. Things get placed there because we absolutely need
that version.
Rick
-Donald
Rick McGuire wrote:
Donald Woods wrote:
I'm actually seeing a
Dain Sundstrom wrote:
On Aug 11, 2006, at 12:40 PM, Dain Sundstrom wrote:
Rick,
I believe what you really want to do is to use the endorsed
directory. This allows you to override the vm implementation of
endorsed specification such as corba
You will need to configure the surefire (testing) plugin to fork your
tests into a new vm and set the endorsed dir for that new vm. The
first is easy but the second will be difficult. First off the docs
for the sure fire plugin can be found here
Looks like the bits to configure surefire are fine, except you'd want
to change the value of somedir.
I recommend that you use the dependency plugin in your module's pom
to download and install the needed jars to be placed into the
endorsed dir (which will end up in the modules
Dain pointed out that we don't want to unpack the dependencies...
so the goal should be copy, not unpack, as in:
{code:xml}
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
executions
execution
Rick, I'm curious about the inherent conflict with the classes that
ship with the JVM. Can you explain a little more about what that
means (which classes, when and how are they loaded, etc)?
thanks,
Paul
On 8/11/06, Rick McGuire [EMAIL PROTECTED] wrote:
I've run into an interesting snag with
On 8/11/06, Rick McGuire [EMAIL PROTECTED] wrote:
...
Any thoughts on how we should handle this particularly awkward situation?
I vote we (e.g. Yoko) do whatever it takes to avoid the class
conflict, and then Geronimo can forget about the JVM ORB forever.
Do we know how other open source ORBs
Aaron Mulder wrote:
On 8/11/06, Rick McGuire [EMAIL PROTECTED] wrote:
...
Any thoughts on how we should handle this particularly awkward
situation?
I vote we (e.g. Yoko) do whatever it takes to avoid the class
conflict, and then Geronimo can forget about the JVM ORB forever.
Probably a
to handle this...
1) java.endorsed.dirs setting
2) xbootclasspath
- Balaji
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
Mulder
Sent: Friday, August 11, 2006 10:57 AM
To: dev@geronimo.apache.org
Subject: Re: Yoko and Geronimo
On 8/11/06, Rick
this...
1) java.endorsed.dirs setting
2) xbootclasspath
- Balaji
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
Mulder
Sent: Friday, August 11, 2006 10:57 AM
To: dev@geronimo.apache.org
Subject: Re: Yoko and Geronimo
On 8/11/06, Rick McGuire [EMAIL
Rick,
I believe what you really want to do is to use the endorsed
directory. This allows you to override the vm implementation of
endorsed specification such as corba (https://java.sun.com/j2se/1.5.0/
docs/guide/standards/index.html). In general, you should try to keep
the stuff in the
@geronimo.apache.org
Subject: Re: Yoko and Geronimo
Are you saying that every open source and commercial ORB that wants to
run under JDK 1.5.0 requires one of these two approaches? That no one
has come up with a workaround that doesn't require user intervention?
Thanks,
Aaron
On 8/11/06, Mosur
for these cases...
- Balaji
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Aaron
Mulder
Sent: Friday, August 11, 2006 3:08 PM
To: dev@geronimo.apache.org
Subject: Re: Yoko and Geronimo
Are you saying that every open source and commercial ORB that wants to
run
FYI, in 1.2, the lib/ and lib/endorsed/* bits are now configured in
geronimo-boilerplate-minimal/pom.xml... which is picked up by all of
the assemblies.
--jason
On Aug 11, 2006, at 12:40 PM, Dain Sundstrom wrote:
Rick,
I believe what you really want to do is to use the endorsed
On Aug 11, 2006, at 12:40 PM, Dain Sundstrom wrote:
Rick,
I believe what you really want to do is to use the endorsed
directory. This allows you to override the vm implementation of
endorsed specification such as corba (https://java.sun.com/j2se/
1.5.0/docs/guide/standards/index.html).
Cool, that's a lot nicer than I had thought.
Thanks,
Aaron
On 8/11/06, Dain Sundstrom [EMAIL PROTECTED] wrote:
I'm dumb. You simply need to add the jar to lib/endorsed jar in the
boilerplate config (thanks Jason), and add it to the manifest class
path of the j2ee-system configuration (see
Alan D. Cabrera wrote, On 2/23/2006 12:59 PM:
On 2/23/2006 11:32 AM, Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan D. Cabrera wrote:
One question, do we need a PPMC? I think that we should start one
since this project has a very real possibility of
That list already exists.
- Brett
On 3/7/06, Alan D. Cabrera [EMAIL PROTECTED] wrote:
Alan D. Cabrera wrote, On 2/23/2006 12:59 PM:
On 2/23/2006 11:32 AM, Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan D. Cabrera wrote:
One question, do we
Send an email to [EMAIL PROTECTED] to join the
discussions!
-dain
On Feb 23, 2006, at 10:03 AM, Alan D. Cabrera wrote:
I think that Yoko is good to go.
ASF Infra has set up the mailing lists, SVN, and created accounts
for our new committers as well as adding the existing interested
ASF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan D. Cabrera wrote:
One question, do we need a PPMC? I think that we should start one
since this project has a very real possibility of becoming a TLP.
It's not really a matter of choice. Incubating podlings
have PPMCs regardles of where
On 2/23/2006 11:32 AM, Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan D. Cabrera wrote:
One question, do we need a PPMC? I think that we should start one
since this project has a very real possibility of becoming a TLP.
It's not
63 matches
Mail list logo