+1 from me, for renaming the module to implementation-spring-runtime.
I remember, we had a discussion to name it as implementation-spring-sca
due to some design changes that happened some time back. But renaming
it to implementation-spring-runtime makes more sense. Thanks.
On Tue, Jun 22, 2010
Hi Simon,
Looks like the JEE sample projects are already available as dependencies for
the itest-contribution-jee module.
Though we have the required dependencies included, maven simply does not
pickup the WAR or EAR file as dependency. The reason for the same is
explained here...
Currently, the JavaEEModuleHelper uses the
org.apache.openejb.config.DeploymentLoader, to load
the JEE archieve and due to some classloading issues, the itests were
failing.
Today, I tried writing a custom Deployer and asked the OpenEJB to use the
TCCL as the classloader.
Now, I see that some
On Mon, Feb 22, 2010 at 6:08 PM, Simon Laws simonsl...@googlemail.comwrote:
On Mon, Feb 22, 2010 at 11:55 AM, Ramkumar R ramkumar...@gmail.com
wrote:
Hi Simon,
You are right, I have been seeing the same error message. I believe, this
error should
be because of Tuscany code due to some
Hi Simon,
You are right, I have been seeing the same error message. I believe, this
error should
be because of Tuscany code due to some class loader issues for the following
reason...
While testing the itest/contribution-jee with OpenEJB v3.0.1, I noticed two
kind of error messages
1.
Hi Simon Nash,
Using OpenEJB version 3.1.2 the StringIndexOutOfBoundsException seem to get
resolved
and currently I still see the other exception as shown below (which I see
even in the older versions).
java.lang.Exception: Could not load sample/HelloworldEjbServlet.class
at
Looks good to me, +1 from me.
Ran most of the samples and demos, no issues seen. Also was able to build
the source
distribution.
On Sat, Jan 30, 2010 at 12:47 AM, Luciano Resende luckbr1...@gmail.comwrote:
Please review and vote on RC2a of the SCA 1.6 release.
The distribution artifacts,
and disabling the tracing module. How
exactly the policies will look like
and how to implement the same is something that i am trying to investigate
at this point of time.
Please let me know your comments and suggestions. Thanks.
On Thu, Jan 21, 2010 at 6:06 PM, Ramkumar R ramkumar...@gmail.com wrote
After gaining some understanding on the aspectj configuration and aspects,
able to
fix the existing issue under revision 901680.
On Wed, Jan 20, 2010 at 3:04 PM, Ramkumar R ramkumar...@gmail.com wrote:
Looks like it never worked, as the org.apache.tuscany.sca.
aspectj.UserTimingAspect class
the source.
Just learning on how the TimingAspect works in general to fix the issue
here.
On Tue, Jan 19, 2010 at 12:30 PM, Ramkumar R ramkumar...@gmail.com wrote:
Thanks Luciano, for the link, that helps to understand the purpose of this
module in detail.
Let me use this information to test them
Yesterday, I touched based with Vamsi and explained him about the issue.
Looks like there is an issue here, and Vamsi is working on to fix the issue
and update the wiki appropriately.
On Mon, Jan 11, 2010 at 1:14 PM, Ramkumar R ramkumar...@gmail.com wrote:
Thanks Vamsi, I was able to Install
The AOP based logging and tracing module (tracing-aspectj) have been added
to 2.x code base
using revision 900323.
--
Thanks Regards,
Ramkumar Ramalingam
On Mon, Jan 18, 2010 at 3:34 PM, Simon Laws simonsl...@googlemail.comwrote:
Thanks Ram
And docs on how to use it?
Simon
Let me try and collect some information on how to use this, and put the
documentation
in place.
--
Thanks Regards,
Ramkumar Ramalingam
Thanks Luciano, for the link, that helps to understand the purpose of this
module in detail.
Let me use this information to test them against 2.x code base and do
necessary
changes if required.
On Mon, Jan 18, 2010 at 11:49 PM, Luciano Resende luckbr1...@gmail.comwrote:
On Mon, Jan 18, 2010 at
- For the Java Class artifacts, the ClassLoaderModelResolver uses
the
Thread.currentThread().getContextClassLoader() as the parent class loader
to
resolve the Class References.
It may be that the parent classloader for the ClassLoaderModelResolver
is the TCCL (which I imagine is
Hi All,
Here is quick glance on how java class artifacts within the contribution are
resolved in 1.x and 2.x code base currently.
In 1.x code:
- A ContributionClassLoaderProvider is registered using
ContributionClassLoaderProviderExtensionPoint, which provides the
ContributionClassLoader
to reflect the username and
password to be used for deployment.
On Mon, Jan 4, 2010 at 5:31 PM, Ramkumar R ramkumar...@gmail.com wrote:
Hi Vamsi,
I tried with the following instructions available in the wiki [1], to
install the plugin on Geronimo v2.1.4 with Tomcat as the web container.
1
Hi Simon,
Comments inline.
The POJO CI specs 1.1 makes a recommendation that, the thread context
classloader of the thread used to invoke an
operation of a Java POJO component implementation MUST be set as the
class
loader of the contribution that contains
the POJO implementation
Hi All,
The POJO CI specs 1.1 makes a recommendation that, the thread context
classloader of the thread used to invoke an
operation of a Java POJO component implementation MUST be set as the class
loader of the contribution that contains
the POJO implementation class.
The POJO_10009 test case
Noticed that the sca folder is missing in the SVN
https://svn.apache.org/repos/asf/tuscany/java/.
Not sure if its moved to a different location OR its actually missing?.
--
Thanks Regards,
Ramkumar Ramalingam
Thanks Simon, I missed that mail.
On Wed, Nov 25, 2009 at 2:28 PM, Simon Laws simonsl...@googlemail.comwrote:
Hi Ram
Yes, we moved the Java SCA code to fit in with the new svn structure.
See Luciano's email [1]
Regards
Simon
[1]
Hi Mike,
I tried a fresh build with the latest changes...
For the change in BaseJAXWSTestCase to BaseJAXWSTestRunner few changes
were required on the following files.. and I have made the changes using the
revision numbers shown below.
tuscany-java-caa-test-runner\pom.xml - Committed revision
Fixes for 10001 and 10005, were required in the Tuscany code to validate the
uniqueness
in import.java and export.java.
Committed at revision 880717.
On Fri, Nov 13, 2009 at 3:21 PM, Ramkumar R ramkumar...@gmail.com wrote:
Hi Ant,
To begin with, I will have a look at the issue on the import
(client_javapojo.POJO_10006_TestCase)
testDummy(client_javapojo.POJO_10008_TestCase) - OASIS TUSCANY-3373
testDummy(client_javapojo.POJO_10009_TestCase)
On Mon, Nov 16, 2009 at 5:29 PM, Ramkumar R ramkumar...@gmail.com wrote:
Fixes for 10001 and 10005, were required in the Tuscany code to validate
Hi Ant,
To begin with, I will have a look at the issue on the import and exports
for the ones shown below.
testDummy(client_javapojo.POJO_9005_TestCase) import.java
testDummy(client_javapojo.POJO_10001_TestCase) import
testDummy(client_javapojo.POJO_10004_TestCase) import/classloading
Hi Ant,
Sure, I will take a look at this one.
On Thu, Nov 12, 2009 at 2:35 PM, ant elder ant.el...@gmail.com wrote:
On Tue, Nov 10, 2009 at 9:32 AM, Ramkumar R ramkumar...@gmail.com wrote:
Thanks for your suggestion Luciano.
I have fixed this issue by modifying the deployer to add
Fixes were required in the DeployerImpl code to take care of resolving
import.java using location attribute.
Committed revision 835344.
On Thu, Nov 12, 2009 at 2:42 PM, Ramkumar R ramkumar...@gmail.com wrote:
Hi Ant,
Sure, I will take a look at this one.
On Thu, Nov 12, 2009 at 2:35 PM
Here is what I see for the java-ci otests...
Failed tests:
testDummy(client_javapojo.POJO_8012_TestCase)
testDummy(client_javapojo.POJO_10008_TestCase)
testDummy(client_javapojo.POJO_10006_TestCase)
testDummy(client_javapojo.POJO_9005_TestCase)
Thanks for your suggestion Luciano.
I have fixed this issue by modifying the deployer to add dependencies
based on the namespace location attribute.
Committed at revision 834397.
On Mon, Nov 9, 2009 at 9:51 PM, Luciano Resende luckbr1...@gmail.comwrote:
On Mon, Nov 9, 2009 at 3:01 AM, Simon
The issue on 12007 required a fix in the Tuscany code and now been fixed at
revision 834397.
On Mon, Nov 9, 2009 at 9:45 PM, kelvin goodson kelvingood...@gmail.comwrote:
thanks Simon - I'll have a go at that
2009/11/9 Simon Laws simonsl...@googlemail.com:
No idea why you are seeing it and
Currently, I am looking at 12007.
On Mon, Nov 9, 2009 at 2:39 PM, ant elder ant.el...@gmail.com wrote:
On Fri, Nov 6, 2009 at 11:30 PM, ant elder ant.el...@gmail.com wrote:
On Fri, Nov 6, 2009 at 5:48 PM, Simon Laws simonsl...@googlemail.com
wrote:
Ok, a few more fixes in and down to...
The SCA Assembly Model Spec v1.1 states the following in section 11.2.1.
11.2.1 SCA Artifact Resolution
3458 When a contribution contains a reference to an artifact from a
namespace that is declared in an import
3459 statement of the contribution, if the SCA artifact resolution mechanism
is used
Here is the update on 1200x series
testDummy(client.ASM_12003_TestCase) - OASIS issue TUSCANY-3339
TUSCANY-3338
testDummy(client.ASM_12004_TestCase) - OASIS issue TUSCANY-3340
testDummy(client.ASM_12005_TestCase) - OASIS issue TUSCANY-3362
testDummy(client.ASM_12007_TestCase) - Needs
+1 to move out from the sca trunk.
On Wed, Oct 28, 2009 at 10:45 PM, ant elder ant.el...@gmail.com wrote:
What do people think about moving the otest folder that contains the
OASIS compliance tests out from the sca trunk checkout to somewhere
else? The reasons are having it part of sca makes
+1 from me.
On Wed, Oct 28, 2009 at 2:34 PM, ant elder ant.el...@gmail.com wrote:
Please vote on releasing the Tuscany OSGi JUnit Plugin.
The Tuscany OSGi JUnit Plugin is used by the Tuscany SCA project to
do unit testing of the OSGi runtime environment. We need this release
so the SCA
Hi Ant,
Here is the latest status on 1200x series...
testDummy(client.ASM_12003_TestCase) - OASIS issue TUSCANY-3339
TUSCANY-3338
testDummy(client.ASM_12004_TestCase) - OASIS issue TUSCANY-3340
testDummy(client.ASM_12005_TestCase) - TUSCANY-3326
testDummy(client.ASM_12007_TestCase) -
Hi Ant,
I will start looking from 12000 and 13000 series and take over other ones
as I complete.
On Mon, Oct 26, 2009 at 2:24 PM, ant elder antel...@apache.org wrote:
On Fri, Oct 23, 2009 at 11:08 AM, ant elder antel...@apache.org wrote:
SCA-J CAA tests:
Failed tests:
Hi Rupesh,
You are right, I agree with you. This issue is addressed in 2.x code base as
complying with OASIS 1.1 specification. There are lot other scenarios, that
are considered in 2.x apart from the one you have pointed out.
I believe we don;t have any plans to do changes in 1.x as we consider
The EJB Binding module is now available in 2.x code base.
Please let me know if you find issues or have any questions.
--
Thanks Regards,
Ramkumar Ramalingam
+1 from me.
On Fri, Oct 2, 2009 at 8:11 PM, Simon Laws simonsl...@googlemail.comwrote:
Please review and vote on RC4 of the Tuscany SCA Java 1.5.1 release.
The distribution artifacts, RAT reports, and Maven staging repository
are available for review at:
Hi Simon,
It was because of me, I have committed a fix for this issue at revision
820545.
On Wed, Sep 30, 2009 at 10:59 PM, Simon Laws simonsl...@googlemail.comwrote:
I'm seeing...
Caused by: java.io.FileNotFoundException: class path resource
The binary distribution looks good, samples and tutorials looks good.
I found that the source distribution has a file named hs_err_pid6244.log
at the root
which needs to be removed.
On Tue, Sep 29, 2009 at 10:49 PM, Simon Laws simonsl...@googlemail.comwrote:
Please review and vote on RC2 of
Hi Simon,
I just noticed that we need a change in the
SpringXMLComponentTypeLoader.java of the
implementation.spring module as mentioned in TUSCANY-3285.
I think we can include them in 1.5.1.
On Tue, Sep 29, 2009 at 12:45 PM, Simon Laws simonsl...@googlemail.comwrote:
Thanks Luciano, I'll
Hi Simon,
The fixes for TUSCANY-3285 is now available under revision 819874 in 1.5.1.
On Tue, Sep 29, 2009 at 3:24 PM, Simon Laws simonsl...@googlemail.comwrote:
Ok, Ram. If it's just the text of an error message, go ahead. Please
let me know when you're done.
Regards
Simon
--
Thanks
Hi Simon,
You are right, the fix you proposed seem to resolve the problem and I have
checked in the changes using TUSCANY-3281.
On Tue, Sep 22, 2009 at 8:22 PM, Simon Laws simonsl...@googlemail.comwrote:
Hi Ram
Haven't tried with that version. Having looked at the code though
there does
I am using IBM JDK 1.6 SR3.
I am seeing the following error message for all most all the samples that I
ran, this message occurs at the end of after the successful output.
[java] Exception in thread main java.lang.IllegalStateException: No
servlet registered at this URI: /dojo
[java] at
On Thu, Sep 3, 2009 at 1:24 PM, ant elder antel...@apache.org wrote:
On Wed, Sep 2, 2009 at 1:02 PM, Simon Lawssimonsl...@googlemail.com
wrote:
I was having thinking about backward compatibility again and wonder if
there is another approach we've not mentioned yet which may be easier
-
On Thu, Aug 6, 2009 at 8:12 PM, Douglas Leite dougsle...@gmail.com wrote:
The last updates in my project are related to allowing the existence of
concurrent exceptions, as well as providing suitable mechanisms to treat
them ([1]). The sequence diagram at [2] shows the messages exchange between
at 6:30 AM, Ramkumar R ramkumar...@gmail.comwrote:
Hi Douglas,
Were you able to get this working for you, please keep posting if you
have any issues in doing so.
On Wed, Jul 8, 2009 at 7:40 PM, Luciano Resende luckbr1...@gmail.comwrote:
On Wed, Jul 8, 2009 at 4:38 AM, Ramkumar Rramkumar
+1 from me to release.
On Thu, Jul 16, 2009 at 12:01 AM, Luciano Resende luckbr1...@gmail.comwrote:
Please review and vote on RC4 of the SCA 2.0 M3 release.
The distribution artifacts, RAT reports, and Maven staging repository
are available for review at:
Overall the distribution looks good.
While building the module src... i see the following issue...
[INFO]
[INFO] Building Apache Tuscany SCA Core Runtime
[INFO]task-segment: [clean, install]
[INFO]
On Wed, Jun 24, 2009 at 4:19 PM, ant elder antel...@apache.org wrote:
On Wed, Jun 24, 2009 at 11:29 AM, Ramkumar Rramkumar...@gmail.com wrote:
Hi Ant,
Good thought, +1 from me.
Currently, I have used AnnotationProcessorExtensionPoint to switch on/off
the annotation
support. How
Hi Ant,
Thanks for the clarification. No issue otherwise.
+1 for this RC.
On Mon, Jun 29, 2009 at 12:59 PM, ant elder antel...@apache.org wrote:
On Mon, Jun 29, 2009 at 7:27 AM, Ramkumar Rramkumar...@gmail.com wrote:
Overall the distribution looks good.
While building the module src... i
Hi Ant,
Good thought, +1 from me.
Currently, I have used AnnotationProcessorExtensionPoint to switch on/off
the annotation
support. How about giving a generic name as ConfigurationExtensionPoint
and include
multiple configuration properties using this extensionPoint.
On Wed, Jun 24, 2009 at
Fix for a switch with on/off feature for annotation support is now available
with committed revision 787589. TUSCANY-3096.
On Thu, Jun 18, 2009 at 4:17 PM, Ramkumar R ramkumar...@gmail.com wrote:
+1 for using Tuscany extension model to take care of this feature.
I will make necessary changes
Implementation Spring supports handling of multiple application contexts
using ClassPathXmlApplicationContext
and FileSystemXmlApplicationContext.
ClassPathXmlApplicationContext looks good as it accepts the path to files
relative to the contribution, but there
seems to be an issue while dealing
+1 for using Tuscany extension model to take care of this feature.
I will make necessary changes for the same.
On Mon, Jun 15, 2009 at 6:45 PM, ant elder antel...@apache.org wrote:
On Mon, Jun 15, 2009 at 2:03 PM, Simon Lawssimonsl...@googlemail.com
wrote:
Is this for 1.x, 2.x or both? I'm
On Tue, Jun 16, 2009 at 4:10 PM, Simon Laws simonsl...@googlemail.comwrote:
Works for me too. Thanks Ram
What piece of code does resolve schema by namespace?
Simon
Hi Simon,
In case of XSD, the @schemaLocation is handled by
org.apache.ws.commons.schema.XmlSchemaCollection
for any path
the patch so that you can help fix the itests?
Thanks,
Raymond
From: Ramkumar R
Sent: Monday, June 08, 2009 9:35 AM
To: dev@tuscany.apache.org
Subject: Re: How to resolve @location for implementation.spring?
Hi Raymond,
Good catch !!, I just realized that the specs does not recommend
code using r785126.
Interestingly, the namespace import resolving code has been there always
with XSDModelResolvers,
but did not give any issue as the code was not reachable.
On Mon, Jun 15, 2009 at 10:41 PM, Ramkumar R ramkumar...@gmail.com wrote:
Might be because of me, let me have a look
Hi All,
Tuscany currently provides a value add on top of the implementation.spring
specification by providing support for SCA annotations.
Looks like, it would take a while for the specification to approve on
support for SCA annotations. In the mean while
there have been some requirement from
Hi Ant,
I have checked-in code for the ASSEMBLY-8 Artifact resolution using
TUSCANY-3079.
Please include them for M3.
On Fri, Jun 12, 2009 at 9:34 PM, ant elder antel...@apache.org wrote:
On Fri, Jun 12, 2009 at 4:42 PM, Simon Lawssimonsl...@googlemail.com
wrote:
I guess there's no need
Might be because of me, let me have a look at this one.
On Mon, Jun 15, 2009 at 9:40 PM, Raymond Feng enjoyj...@gmail.com wrote:
This seems to be related to
http://svn.apache.org/viewvc?rev=784727view=rev.
--
From: Simon Laws
On Thu, Jun 4, 2009 at 10:51 PM, Simon Laws simonsl...@googlemail.comwrote:
On Thu, Jun 4, 2009 at 4:55 PM, Raymond Feng enjoyj...@gmail.com wrote:
Here is my understanding of the following statement:
3461 1. from the locations identified by the import statement(s) for the
namespace.
Currently, I am updating the contributions import and export code according
to the
OASIS recommendations.
The itest for contribution imports/exports does require the code for
creating a domain
and add multiple contributions to the domain to validate the functionality.
In 1.x, we had either the
Should we consider including the non-SCA resolution mechanism as part of the
2.x code
base same as what we have in 1.x code ?
On Wed, May 27, 2009 at 1:37 PM, Ramkumar R ramkumar...@gmail.com wrote:
Hi All,
We had a discuss on this topic (Use of non-SCA Mechanisms for Resolving
Artifacts
Hi Raymond,
Good catch !!, I just realized that the specs does not recommend the use of
@location for a URI to the spring context xml file.
But the interesting point is that, support for @location with an external
archive/directory is the latest feature addition that
we did recently, I believe
Creating a jira for each single commit will flood the dev list with
unnecessary jira notifications (create, close, etc) and will probably
make users that are lurking in the dev list to unsubscribe... It
should be pretty simple to just add a simple description on the commit
log message, and
One important recommendations from the OASIS specs for artifact resolution
mechanism is that
3458 When a contribution contains a reference to an artifact from a
namespace that is declared in an import
3459 statement of the contribution, if the SCA artifact resolution mechanism
is used to
OK Ram, interesting that we are doing it back to front. Are we also
applying the only one-level search is performed rule?
Hi Simon,
I assume that, since we only use ModelResolvers to identify the artifacts
and resolve
them accordingly, the rule of only one-level search is performed is not
Hi Simon,
Agree with you, I am one such culprit for recently checking in codes for
spring module
refactoring without a JIRA. I realized the mistake later when I had to track
the changes
that were made for the entire spring refactoring work.
My suggestion is that, we should always have a JIRA
Hi,
I would like to take up ASSEMBLY-8 Artifact resolution and get it done for
M3.
Is anyone already started working on this item, please let me know.
On Fri, May 29, 2009 at 6:20 PM, Simon Laws simonsl...@googlemail.comwrote:
On Wed, May 27, 2009 at 8:25 AM, ant elder ant.el...@gmail.com
Hi Ant,
I agree with you, +1 from me.
On Thu, May 28, 2009 at 3:45 PM, ant elder ant.el...@gmail.com wrote:
On Wed, May 27, 2009 at 4:45 PM, Simon Laws simonsl...@googlemail.com
wrote:
On Wed, May 27, 2009 at 10:48 AM, Ramkumar R ramkumar...@gmail.com
wrote:
My comments for RC1
is not
possible.
Is it right, or I am missing something?
Regards
On Mon, Mar 2, 2009 at 3:16 PM, Ramkumar R ramkumar...@gmail.com wrote:
Hi Douglas,
Well yeah the fix is now available for this issue, In Tuscany we are now
trying to support non-JAXB type using JAXB 2.0's XmlJavaTypeAdapter
Hi All,
We had a discuss on this topic (Use of non-SCA Mechanisms for Resolving
Artifacts) in the month of March under this thread
http://www.mail-archive.com/dev@tuscany.apache.org/msg05956.html
What we agreed on as a process to follow for the non-SCA mechanism is.
1. get artifact location
My comments for RC1.
Most of the samples and demos that I tested looks good, except for some
minor changes required as shown below.
INSTALL file - shows a wrong year as May 2008, should be May 2009.
CHANGES file - would be good if we can consolidate the changes in terms of
features, instead
/SpringDelegationHelloWorld.composite
/itest-implementation-spring/src/main/resources/org/apache/tuscany/sca/itest/spring/SpringHelloWorld.composite
I just checked in a fix to change the name of the composite. Now the
original issue comes up again.
Thanks,
Raymond
From: Ramkumar R
Sent: Friday, May 15, 2009 4:33 AM
Hi Ant,
Thanks for the hint, I have fixed the issue now at r777489 in 1.5.
On Fri, May 22, 2009 at 4:35 PM, ant elder ant.el...@gmail.com wrote:
On Fri, May 22, 2009 at 11:32 AM, Ramkumar R ramkumar...@gmail.com
wrote:
Hi All,
TUSCANY-3046 was raised initially with spring issues
Hi Raymond,
Let me have a look at this one and post the findings.
On Fri, May 15, 2009 at 2:05 AM, Raymond Feng enjoyj...@gmail.com wrote:
The itest-implementation-spring in 2.x build is failing due to:
https://issues.apache.org/jira/browse/TUSCANY-3027
I investigated the issue. Here is the
Hi Raymond,
I notice a different error message, though I did not notice error as you are
seeing
testServer(implementation.policies.ImplementationPoliciesTestCase) Time
elapsed: 0.313 sec ERROR!
org.oasisopen.sca.ServiceRuntimeException: The service
AnotherCalculatorServiceComponent has
Hi Luciano,
Cool stuff, I would like to experiment with this new wire format and
operation selector.
Do we have some samples in place to have a feel of this feature?
Also, I would like to study on some technical details about wire formats and
operation selectors
from SCA and Tuscany point of
I believe, this debate is growing and yet to settle with an agreement. While
the debate is still on
I would like to propose this
For 1.x lets stick to the model of having 2 modules... implementation-spring
and implementation-spring-runtime as what we have currently. As we are
expecting
On Wed, May 6, 2009 at 9:26 PM, Raymond Feng enjoyj...@gmail.com wrote:
Hi,
By further investigation of the code, I realized that the current
implementation-spring-runtime module contains the code to parse SCA
namespace and invoke the spring beans by instantiating the application
context.
Thanks Luciano, for information and the patch. Currently I am working on
refactoring
spring modules in 2.x. I should be able to work on this on starting from
next week.
On Sat, Apr 25, 2009 at 2:41 AM, Luciano Resende luckbr1...@gmail.comwrote:
On Tue, Apr 21, 2009 at 11:39 PM, Ramkumar R
On Fri, Apr 24, 2009 at 3:04 PM, Mike Edwards
mike.edwards.inglen...@gmail.com wrote:
Luciano,
The Spring implementation-xml module is one that I propose we get rid of.
It is one of my suspicious ones - it contains a single class only. This
seems very wasteful, as it does not really offer
and the artifact signings as required
for this release.
On Fri, Apr 24, 2009 at 3:19 PM, ant elder antel...@apache.org wrote:
On Fri, Apr 24, 2009 at 10:29 AM, Ramkumar R ramkumar...@gmail.com
wrote:
Hi Ant,
May be I am not sure how to verify this plugin, can you please post some
info
On Fri, Apr 24, 2009 at 3:00 PM, Mike Edwards
mike.edwards.inglen...@gmail.com wrote:
Ram,
I made a couple of fixes and changes that enables all 3 Spring modules to
work correctly under OSGi in 2.x.
Principally, the adjustments were to the manifest files, to ensure that all
dependencies
Hi Ant,
May be I am not sure how to verify this plugin, can you please post some
info on this. Thanks.
On Wed, Apr 22, 2009 at 8:32 PM, ant elder ant.el...@gmail.com wrote:
Please review and vote on releasing the alpha1 release of the Tuscany
Zip plugin module.
The zip plugin enables using
On Thu, Apr 23, 2009 at 12:44 AM, Scott Kurz scottk...@gmail.com wrote:
Ram,
Thanks for the updated summary.
I have a couple of questions, if you don't mind.
First, this is probably an obvious question, but by the SCA
resolution mechanism you mean:
1. first look in the current
On Thu, Apr 23, 2009 at 3:19 AM, Raymond Feng enjoyj...@gmail.com wrote:
The latest OASIS SCA Assembly Spec has the following:
3509 When a contribution contains a reference to an artifact from a
namespace that is declared in an import
3510 statement of the contribution, if the SCA artifact
Hi All,
I have been working on porting the implementation.spring module in 2.x and
have split the modules as implementation.spring,
implementation-spring-runtime and implementation-spring-xml and have also
ported the itest for spring in 2.x.
To successfully run the spring modules with 2.x here
This would be ok for now, but the proper fix would be to have pojo
related interfaces available in a separated module that could be
exported via OSGi and used by all pojo related extensions (e.g java,
ejb, spring). I have started doing that in implementation.pojo, but
that still need some
On Wed, Apr 22, 2009 at 12:09 PM, ant elder ant.el...@gmail.com wrote:
It looks good to me, i think its great to have spring working in 2.x. Add
it to the build!
I'd prefer if the imlementation-spring-xml module was merged into
implementation-spring as thats the pattern i thought we are
+1 from me. Verified the changes made as shown in the 2.0-RC2-RC3-diff.txt
file.
On Fri, Apr 10, 2009 at 12:06 AM, ant elder ant.el...@gmail.com wrote:
Please review and vote on RC3 of the SCA 2.0-M2 release.
The distribution artifacts, RAT reports, and Maven staging repository
are available
reference without the introduction of binding.osgi).
As Graham pointed out, the usage is limited to portion of the SCA
composition is hosted by an OSGi runtime.
Thanks,
Raymond
*From:* Ramkumar R ramkumar...@gmail.com
*Sent:* Wednesday, April 08, 2009 5:16 AM
*To:* dev@tuscany.apache.org
+1 from me.
On Mon, Apr 6, 2009 at 10:02 PM, Luciano Resende luckbr1...@gmail.comwrote:
We have made good progress recently in JMS, Web 2.0 and Java EE and I
was wondering if we are ready to get 1.5 release ?
Thoughts ?
--
Luciano Resende
Apache Tuscany, Apache PhotArk
+1 from me.
On Fri, Apr 3, 2009 at 1:09 PM, ant elder ant.el...@gmail.com wrote:
Please vote on releasing 1.0.2 of the Tuscany Maven Bundle Plugin
module. The tag for the release is:
https://svn.apache.org/repos/asf/tuscany/maven-plugins/tags/maven-bundle-plugin-1.0.2/
the Maven staging
Hi Vamsi,
In my opinion, it would be difficult to get this information in both the
read/resolve method of the ArtifactProcessor. Similar situation is noticed
in implementation.web and implementation.spring modules and they use
ComponentPreProcessor to overcome this situation. You might need to
I was able to download and unzip the artifacts successfully, and all the
samples
worked fine for me.
+1 from me.
On Mon, Apr 6, 2009 at 2:14 PM, ant elder antel...@apache.org wrote:
Please review and vote on RC2 of the SCA 2.0-M2 release.
The distribution artifacts, RAT reports, and Maven
I would like to volunteer as a mentor for the proposal submitted by Douglas,
I am currently
reviewing your proposal submitted, will update my comments asap.
On Wed, Apr 1, 2009 at 2:02 AM, Adriano Crestani
adrianocrest...@gmail.comwrote:
While Douglas does not add his proposal to the wiki, any
1 - 100 of 252 matches
Mail list logo
