Hi,
Sorry, I've been a bit slow getting to your questions.
[EMAIL PROTECTED] wrote:
We were looking into using implementation.spring, but had a couple
of questions. We have a spring context with elements common across
all of our services (aspects, host connection beans, caching, etc.)
so
Brady,
A warm welcome...
Mike.
Pete Robbins wrote:
The Tuscany PPMC and Incubator PMC have voted for Brady to become a
Tuscany committer.
Congratulations and welcome Brady!
I look forward to your continued excellent contributions to Tuscany.
Cheers,
Jean-Sebastien,
Jean-Sebastien Delfino wrote:
snip
Looks like option (B) is the most preferred option with:
- one -1
- five +1
- one more spec compliant
Do we need more technical discussion? or a new [VOTE] thread to close
this issue?
Thanks for a great summary.
I'm happy with the
Simon,
I'm breaking my reply into two parts, each dealing with one of the
issues you raised originally:
Simon Laws wrote:
1/ Stateful Callbacks - Given the the following scenario where the
ConversationalClient has a reference to a ConversationalService
@Remotable
@Conversational
public
Simon,
OK, Part 2 of my reply
Simon Laws wrote:
2/ The specifications describe the freeing of state associated with a
conversation when Conversation.end() is called on a conversation object .
See section 1.6.5 of the SCA Java Annotations and APIs V1.0 specification.
Assuming that the
Venkat,
I was out on vacation when your original question was posted, so here's
my contribution.
Venkata Krishnan wrote:
Thanks Raymond. A few more questions ;-)
- The xsd defines the name attribute for PolicyIntent and PolicySet as
of type NCName. However we have model these in the model
Simon,
Comments replies inline
Simon Laws wrote:
Thanks for the clarification. I think the separate discussion of
@Conversational and @Scope(CONVERSATION) provides a good basis for
clarification in the specifications. So a further small point of
clarification on this topic.
This is about
Simon,
Yes, you've hit one of the parts of the Java spec that makes me least
comfortable.
The idea of sending around a reference for others to use is not
something that fills me with joy, when that reference is essentially a
reference to an instance. I feel the religious debates about
Folks,
In some ways, I'm glad I was on vacation while much of this debate
raged!! ;-)
Comments below.
Jean-Sebastien Delfino wrote:
[A] What we have right now, standard SCA extensions and tuscany
extensions sharing the standard SCA namespace
(B) What IMO is a more correct use of XML
+1 to the rename. Best to name the binding by the transport mechanism
involved, not the implementation used to drive it.
Yours, Mike.
Jean-Sebastien Delfino wrote:
ant elder wrote:
On 8/19/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
I'd like to rename binding-ajax to
Folks,
Jean-Sebastien Delfino wrote:
I would be surprised if impl=axis was actually in the SCDL. Instead
I'd imagine that impl=axis would be a characteristic of a particular
implementation of binding.ws, not exposed to app developers but used
by the policy framework to either select that
Shaoguang,
The Eclipse SOA Tools Project is building a graphical editor for SCA
composites. You can find the project here:
http://www.eclipse.org/stp/
In addition to the graphical composition editor, there is a range of SCA
and SOA related tooling available in this tools project.
Of
Folks,
I agree with Simon's comment - this resolution violates the SCA spec.
You are not supposed to go adding stuff to the SCA namespace that is not
approved by the SCA spec process. In particular, no additions to the
sca.xsd or sca-core.xsd are allowed.
Yours, Mike.
ant elder (JIRA)
Mark Combellack wrote:
Mark Combellack [EMAIL PROTECTED] writes:
Mike Edwards mike.edwards.inglenook at ... writes:
Mark Combellack wrote:
Is anyone else having problems creating new Tuscany Jira bug reports?
I am logged into Tuscany Jira at:
https://issues.apache.org/jira/browse/Tuscany
Jean-Sebastien Delfino wrote:
Huang Kai wrote:
Hi, Raymond,
We encountered the same problem when implementing SDO's XSDHelper.
Where we used EMF's xsd tool package for resolve xsd. Wherein we just
implemented our own XSDSchemaLocator and added it to the resource's
adapters, then we can
Components: Java SCA Spring Implementation Extension
Affects Versions: Java-SCA-Next
Reporter: Mike Edwards
Assignee: Mike Edwards
Priority: Minor
Fix For: Java-SCA-Next
Provide stateful support for Spring Beans, including Scope support
Mark Combellack wrote:
Is anyone else having problems creating new Tuscany Jira bug reports?
I am logged into Tuscany Jira at:
https://issues.apache.org/jira/browse/Tuscany
I've tried creating a new Tuscany issue of type bug and I get the following
error:
System Error
Mark,
It is working
Simon Laws wrote:
In the distributed domain contributions and any updates have to be
provisioned to each node. There are many ways of doing this, ftp, http,
shred file system , etc. to the extent that Tuscany shouldn't really care
too much about how it is achieved. I would expect that at any
Hi,
A few thoughts
snip
We have two options here:
a) Plugin a tuscany-specific resolver for WSDL4J
(javax.wsdl.xml.WSDLLocator) and XmlSchema
(org.apache.ws.commons.schema.resolver.URIResolver).
This option can handle location case 1, 2 and 3. For 2, we probably
need
some context
Hi Shaoguang,
shaoguang geng wrote:
In SCA java component implementation 1.0, most of the spec was telling the story about interface.java
interface=[interface name]. But in fact implementation.java class=[class
name]/ has done every thing.
Dose osoa mean: using interface.java the interface
Raymond,
How does this relate to the contribution resolution mechanism described
by the SCA specifications?
Yours, Mike.
Raymond Feng wrote:
Hi,
We currently use XmlSchema to load XSDs. To resolve the import/include
directives using our schemes, we provide an implementation of
Paul,
Great to hear from you! Some thoughts inline.
Paul Fremantle wrote:
I recently read Dan's blog entry on the SCA assembly model:
http://netzooid.com/blog/2007/07/22/sca-assembly-vs-spring-cxf/
That and some other discussions I've had made me think about maybe
offering the SCA assembly
Luciano Resende wrote:
Should we start thinking on a formal release guide, merging together
couple documents we already have as of today, and also creating a
checklist as it looks like couple release candidates are having the
same issues ?
+1 - yes, most definitely.
Yours, Mike.
Simon Laws wrote:
Has anyone in Tuscany made a binding that ships SOAP messages over JMS
instead of HTTP? Looking at the current code base and at the old code in
the
sandbox I don't see anything.
Simon
Simon,
Shouldn't this be a simple extension of the Web services binding?
The
ant elder wrote:
Couldn't this just use the existing Axis2 facilities, the soap/jms uri
format and be done with the scdl binding uri attribute, eg:
binding.wsuri=jms:/dynamicTopics/something.TestTopic?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactoryjava.naming.factory.initial=
Simon Laws wrote:
On 7/24/07, Mike Edwards [EMAIL PROTECTED] wrote:
Simon Laws wrote:
Has anyone in Tuscany made a binding that ships SOAP messages over JMS
instead of HTTP? Looking at the current code base and at the old
code in
the
sandbox I don't see anything.
Simon
Simon
Simon Laws wrote:
snip
Ah, thanks Mike. I didn't latch onto the implication of the word intent.
The choice we are talking about here seems more like a concrete decision
than an intent. Does this match well with the, erm, intention of intents?
Simon
It is one use of intents - and, in my
Luciano,
Yes, make it more widely available.
Yours, Mike.
Luciano Resende wrote:
Looks like XSDDocumentProcessor is not being registered with the
proper artifact extension point, and it's being only available
internally to the WSDLDocumentProcessor. Should we register it with
the extension
[
https://issues.apache.org/jira/browse/TUSCANY-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514610
]
Mike Edwards commented on TUSCANY-1389:
---
I'm OK with Jean-Sebastien's proposal. It would be useful
Simon Nash wrote:
I am implementing approach 1). The code is turning out to be
straightforward and this approach fully supports the SCA callback
spec AIUI.
The Axis2 callback MEP isn't the same as an SCA callback, and it's
confusing that these have the same name. With the Axis2 callback
MEP,
members may prefer the required approach to avoid
errors
I certainly was arguing to remove the targetNamespace from the samples,
since it had no use (didn't show anything useful in terms of those samples).
On 7/19/07, Mike Edwards [EMAIL PROTECTED] wrote:
Folks,
I tend to agree with Ant
Folks,
It is clear from reading other sections of the specification that it is
intended that @ConversationID is used in implementation classes other
than those of CONVERSATION scope.
Further down in 1.2.51 of the JavaComponentImplementation spec, it says
the following:
1. The
Folks,
I tend to agree with Ant. The namespace gets necessary once we get into
inter-contribution sharing of artifacts and then the namespace is
essential, but I dont think it is necessary or useful in the simpler
examples.
I DO think we need to add the XSD location for the SCA namespace,
[
https://issues.apache.org/jira/browse/TUSCANY-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Edwards reassigned TUSCANY-1443:
-
Assignee: Mike Edwards
sample composite files are invalid instance documents against
Shaoguang,
The SCA specifications allow for the WSDL file to be referenced from a
single location, which can include a remote location, via mechanisms
such as wsdl:location or via the SCA artifact resolution mechanism (see
SCA Assembly spec at www.osoa.org). So copying the WSDL file is not
Simon Laws wrote:
On 7/17/07, ant elder [EMAIL PROTECTED] wrote:
Fyi, I've taken the liberty of setting up Google blog alerts to send us
msgs
when sca or tuscany are found to be mentioned on someones blog, hope no
one
minds. Can switch them off if it gets annoying but I've been using this
for
[
https://issues.apache.org/jira/browse/TUSCANY-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513257
]
Mike Edwards commented on TUSCANY-1443:
---
Umm, which SCA XSDs are you referencing here?
The correct ones
1.0.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Michael Yoder [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 9:52 AM
To: Mike Edwards (JIRA)
Subject: RE: [jira] Commented: (TUSCANY-1443
+1 from me
Yours, Mike.
Luciano Resende wrote:
Amita Vadhavkar has been helping DAS for couple months and recently
also started to help on SDO and had contributed many patches. I'd like
to give her developer access to JIRA so she can manage JIRAs with more
flexibility, etc.
Thoughts ?
Folks,
I think that we should consider the idea of Website Wiki committership
separately from Code committership.
I don't think that it should be necessary for someone to have Code
committership in order to be granted update access to the Website/Wiki.
I do agree that it needs to be
Welcome Fuhwei !
Yours, Mike.
kelvin goodson wrote:
We now have sufficient IPMC votes (there were cast on the general list
where
notification of this vote was posted, see [1]) to close this vote and
welcome Fuhwei as a Tuscany committer.
Kelvin.
[1] http://www.mail-archive.com/[EMAIL
Huang,
Huang Kai wrote:
I mean that composite A has a component which uses composite B as
an implementation and that composite B has a component which uses
composite A as an implementation .
I think this use case is fairly common, eg. [Employee] has a property refer to
[Company] and
:11 PM
Subject: Re: StackOverflowException when mutual reference exist
On 7/6/07, Mike Edwards [EMAIL PROTECTED] wrote:
Huang,
I assume that by reference here, you mean a service reference? If
that is so, it should work.
If you mean that composite A has a component which uses composite B
Scott,
I think you ask a fair question here, which is definitely a question for
the Assembly spec working group to consider and answer.
Making it as succinct as I can, I think the issue is this:
For the interfaces at each end of a wire, when they are specified using
the same interface
Venkat,
I'm in favour of adding OSGi metadata to relevant jars to enable them to
act as OSGi bundles. I think that OSGi is in a different space than
other runtimes and that supporting it is a good idea.
Other comments inline...
Yours, Mike
Venkata Krishnan wrote:
Hi,
This seems ok
Folks,
OK, finally, I bite ;-)
The question for me is whether we need the SCA (Java) spec to define
some standard metadata (typically annotations) for databindings of
services references.
I make the assumption that for much of the time, it is possible to work
out the required databinding
Huang,
I assume that by reference here, you mean a service reference? If
that is so, it should work.
If you mean that composite A has a component which uses composite B as
an implementation and that composite B has a component which uses
composite A as an implementation - then this IS an
Dims,
Davanum Srinivas wrote:
Folks,
Believe it or not! we have 230 people who have karma to our svn:
https://svn.apache.org/repos/asf/webservices/
Out of these only about 74 people have made commits in the last 1
year. You can get this info by using the svn log:
svn log -v --revision
Matthieu,
Comments inline
Matthieu Riou wrote:
Hi guys,
I've done a few additional stuff on the BPEL implementation allowing a BPEL
file to be compiled by ODE upon deployment. The implementation is therefore
created and initialized with most of what would be needed by the runtime.
However
Folks,
I tend to favour this more conservative approach. There may be a
problem longer term in explaining the interfaces to writers of new
binding types and implementation types, but the mess caused to existing
implementation types and existing binding types by breaking changes in
the SPI
test
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Luciano,
How does this compare with the existing structure? This seems to
approach things from a Java perspective rather than an SCA / SDO
perspective - is that right?
It might be useful to create an example of what you mean in the
TuscanyWiki psace...
Yours, Mike.
Luciano Resende
[
https://issues.apache.org/jira/browse/TUSCANY-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509460
]
Mike Edwards commented on TUSCANY-1389:
---
I think that the right approach here is to use the XSDs for SCA
Jacek,
It's fine to post stuff about the SCA and SDO specifications here on the
Tuscany mailing list. There is also a feedback page on www,osoa.org
(the site for the specifications themselves) here:
http://www.osoa.org/display/Main/Feedback+on+SCA+Specifications
Regarding your comment here
://issues.apache.org/jira/browse/TUSCANY-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508537
]
Mike Edwards commented on TUSCANY-1389:
---
James,
Does it have to be a DTD - or will an XSD be sufficient to meet your
Jean-Sebastien Delfino wrote:
Nobody picked up my earlier post to this thread, I thought that my
concrete examples were interesting though :) so I'll repeat a concrete
example again here:
implementation.java class=calculator.CalculatorImpl
componentType file:
[
https://issues.apache.org/jira/browse/TUSCANY-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508486
]
Mike Edwards commented on TUSCANY-1377:
---
There is a mixture of 2 things here, as described in Sebastien's
[
https://issues.apache.org/jira/browse/TUSCANY-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508537
]
Mike Edwards commented on TUSCANY-1389:
---
James,
Does it have to be a DTD - or will an XSD be sufficient
Folks,
This turns out to be surprisingly difficult to do - Confluence Wiki has
no easy way to change the font size either of the whole site or of one
space. It can't be done at all just for one page... There is some
grousing about this on the Confluence forum at Atlassian (who write
+1 from me
Yours, Mike.
kelvin goodson wrote:
I'd like to propose Fuhwei Lwo as a Tuscany Committer.
According to my gmail archive he has, since mid of 2006, posted 114
times to
tusany-dev, 79 of those times resulting from interactions with JIRA issue
management.
He has raised 34 JIRAs
Folks,
My 10 cents is that it is not right to add methods to the spec API classes.
My view would be that compliance would require spec-defined classes to
provide the spec, the whole spec and nothing but the spec. This is
certainly the approach to compliance taken for most Java APIs. It's OK
Adriano,
I'm puzzled by the URL that you are using here.
When editing the Wiki, I'd expect you to be somewhere like
here:
http://cwiki.apache.org/confluence/display/TUSCANY/DAS+RDB+Menu
When viewing the Tuscany website I'd expect you to be somewhere like here:
of headers from the spec group we should use
those to replace the current Tuscany headers. Until then we should aim to
get them as close as possible.
Cheers,
On 22/06/07, Mike Edwards [EMAIL PROTECTED] wrote:
Folks,
My 10 cents is that it is not right to add methods to the spec API
classes.
My
the website structure and
add things in the DAS section of the website.
On 6/22/07, Mike Edwards [EMAIL PROTECTED] wrote:
Adriano,
I'm puzzled by the URL that you are using here.
When editing the Wiki, I'd expect you to be somewhere like
here:
http://cwiki.apache.org/confluence/display/TUSCANY
Adriano,
There is something I dont get here.
When I point my browser at the URL you give here, I get a fine Tuscany
home-page based on the Tuscany Wiki material. So in what way is it not
active??
Just to be sure you're seeing what I'm seeing, I've attached an image of
what I get in my
,
but there must be multiple componentType files. So now, what is the
relationship between them
In these more complex cases, the implementation type defines the
relationship.
Yours, Mike.
ant elder wrote:
On 6/18/07, Mike Edwards [EMAIL PROTECTED] wrote:
snip
How does that fit with the spec
Ant,
Yes, sometimes the terminology can get confusing.
snip
The component name may be nothing like the implementation name
How does that fit with the spec saying - A component type file has the
same name as the implementation file but has the extension
.componentType
? I'm looking for a
Ant,
The idea of using the component name is completely wrong and
unacceptable, I'm afraid.
The component name may be nothing like the implementation name - and an
implementation can be used multiple times by different components. The
componentType file is really to be thought of as an
Folks,
I'm a bit confused (nothing out of the ordinary there then!) about how
we intend to use the new Tuscany Wiki space.
So, the Apache Tuscany space is the material which makes up the external
Tuscany website. I understand our desire to control the update of
material there - hence there
[
https://issues.apache.org/jira/browse/TUSCANY-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505192
]
Mike Edwards commented on TUSCANY-1152:
---
The only information about this issue is the title, which is a bit
Frank,
I'm of the opinion that anything that makes it easier for developers to
get to grips with our stuff, the better. Personally, having to to
create all the Eclipse stuff has been a pain, so doing this would save
me time and effort.
I agree with your sentiment that if others want to add
Venkat,
Many thanks,
Mike.
Venkata Krishnan wrote:
Hi Mike, I have added your id in as 'confluence-administrators'.
- Venkat
On 6/13/07, Mike Edwards [EMAIL PROTECTED] wrote:
Luciano,
Only just spotted your request in the emails
My user ID is edwardsmj
Do I need to send
, Mike Edwards [EMAIL PROTECTED] wrote:
Folks,
So what's with the Edit access to the Tuscany Wiki??
I don't seem to have edit access at the moment, despite being a
committer. Who has admin rights for the Wiki? Can one of the admins
please grant me edit access, please?
Also, I know
Venkat,
+1 from me.
How to migrate content? I assume that you mean how do we control the
process? The steps in actually moving content are reasonably
straightforward - but the process for deciding to do it must mirror that
for placing code into trunk, as mentioned on some other emails...
Folks,
So what's with the Edit access to the Tuscany Wiki??
I don't seem to have edit access at the moment, despite being a
committer. Who has admin rights for the Wiki? Can one of the admins
please grant me edit access, please?
Also, I know that there was a discussion about broadening
Folks,
I think that the Spring Implementation is now in reasonable shape and is
capable of being added to the main trunk build. The basic function is
there, supporting Services, References and Properties. Advanced stuff
like scoped behaviour of components will need extra work. More test
Simon,
That's exactly what happens.
If fact, it is far, far worse than that - it searches for ALL resources,
not just composites. In the case of Spring, I have sets of
application-context.xml files in there - and it creates pointers to all
of them.
Whether resolution occurs for all the
Jean-Sebastien,
Comments inline...
Jean-Sebastien Delfino wrote:
Mike,
Good timing, as I am actually starting to work on some lazy +
incremental loading and resolution of SCA assemblies. I had the
following in mind:
step 1:
- change the CompositeProcessor to not resolve its references to
in the
hierarchy of composition are not destined for the runtime node that is
performing the resolution.
Yours, Mike.
Jean-Sebastien Delfino wrote:
[snip]
Mike Edwards wrote:
Whether resolution occurs for all the resources simply depends on
whether there are resolvers for each type of resource.
+1
+1 from me
Yours, Mike.
ant elder wrote:
On 6/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Luciano Resende wrote:
Wouldn't that fail if you start from a clean repo ? It expects the
other modules to be built or available as deployed snapshots no ?
On 6/5/07, Jean-Sebastien
Folks,
I'd just like to say that if you need Confluence help, that I have some
expertise in this area since I manage the www.osoa.org site, which is
also based on Confluence.
Yours, Mike.
ant elder wrote:
On 6/7/07, Luciano Resende [EMAIL PROTECTED] wrote:
Do you have Confluence Admin
Raymond,
Comments inline...
Raymond Feng wrote:
Hi,
Let's look at a use case:
Assuming we have a deployable composite as follows.
composite ...
component name=MyComponent
service name=MyService
binding.ws .../
/service
/component
/composite
When this
Folks,
I made an observation while debugging my composite loading code in the
Spring implementation that gave me pause for thought - and I'd like to
see if the code that handles contributions is behaving the way people
expect.
I found that in my test case, I am pointing explicitly at a
Simon,
My test case uses:
domain = SCADomain.newInstance(getCompositeName());
...where the composite name returned is related to the name of the
testcase that I'm running.
I had assumed, perhaps wrongly, that this composite was the deployable
entity in this case - since I don't
Simon,
I think that the idea is to split the material between official
Website pages and general Wiki pages. The official website pages would
be restricted to editing by committers. The rest of the Wiki can be
open to editing by all.
The simplest way for a non-committer to create
Jean-Sebastien,
OK, with the latest commit to the sandbox, there is a working version of
the Spring implementation. It has the fixes you need, plus a set of
other changes which have got the basic version working.
I'll hold off on further updates until it's in trunk.
The next step is to get
Muhwas,
I dont understand what you are saying here.
Surely, the actual service has a specific interface - it isn't simply
anything, so you can only cast to the actual business interface it
actually implements.
Or did you envisage your client code introspecting the returned service
proxy
On 5/17/07, Mike Edwards [EMAIL PROTECTED] wrote:
Haleh,
As others have said, the right hand side is superb - keep it.
The cypress image is a good idea, but the particular one that
you
have
doesn't look effective when it is Icon sized - it's too detailed
Folks,
I ran into a problem building and running the Itests for SCA.
I was unable to get the jaxws-maven-plugin resolved and the whole thing
failed - this was despite there being a copy of the plugin in my local
repository - it just turned out to be unacceptably old for some reason
best
Haleh,
As others have said, the right hand side is superb - keep it.
The cypress image is a good idea, but the particular one that you have
doesn't look effective when it is Icon sized - it's too detailed and
fussy. Better to have a simpler image with fewer, bolder trees. I'll
have a hunt
Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
Raymond Feng wrote:
ComponentReference.getReference() should give you the reference on
the component type.
Thanks,
Raymond
ComponentReference.getReference() will give you the reference from the
ComponentType. I think that Ant
ant elder wrote:
On 5/4/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Nicholas Williams wrote:
My understanding is that Tuscany does not currently validate SCDL
against the schemas. Assuming that this is correct, when do you think
such
functionality will be introduced?
Thanks
Jean-Sebastien,
+1 for sca/demos/bigbank
I'd like to show it at IMPACT 2007 in Orlando week after next - I may
ask for some help next week as I prepare ;-)
Thanks for preparing it - it helped to give the JavaOne BOF some much
needed reality !
Yours, Mike.
Raymond Feng wrote:
Hi,
Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
Yang ZHONG wrote:
WSDL has schemas and portTypes.
WSDL2Java uses SDO CodeGen to compute classes names for schemas and
generates classes for portTypes.
SDO code seem not actually generated.
Is that desired?
If not, I can look into
Venkat,
Responses inline
Yours, Mike.
Venkata Krishnan wrote:
Hi,
I am trying to bring the SPI model and the Loaders in sync with the current
level of the specs as available on OSOA site. I am currently looking at
'references' - as and how they are defined in ComponentType,
Luciano,
Removing a page is dreadfully simple - be cautious about its use. Go
into Edit mode on the page you want to delete. On the top right of the
editing pane, you will find a trash can icon with a link labelled
Remove Page. Click on either the trash can or the text and that will
the M2 samples recently from
an empty local maven repo?
...ant
On 2/27/07, Mike Edwards [EMAIL PROTECTED] wrote:
Raymond,
Thanks for your reply.
I had seen your previous note and I tried applying the lines:
init-param
param-nametuscany.online/param-name
will still be using
the
old pom.xml in your local maven repo.
I agree its not easy, which is why I've always argued a pre-built distro
complete with everything in a single download zip makes for a much easier
first time experience.
...ant
On 3/2/07, Mike Edwards [EMAIL PROTECTED] wrote:
Ant,
Yes
Folks,
1) I am arranging to publish all of the SCA spec schemas on the
www.osoa.org site - we've completed a site upgrade that now allows us to
publish random files outside the Wiki.
So, expect to see the 1.0 SCA XSDs on
http://www.osoa.org/xmlns/.
by the end of today.
Please note
Folks,
I can confirm that the current 1.0 spec schemas are available on
http://www.osoa.org/xmlns/sca/1.0/.xsd
Yours, Mike.
Jeremy Boynes wrote:
The sca-api module contains old versions of the schemas from 0.9 days.
I think we should remove these from the jar as they are orthogonal
201 - 300 of 327 matches
Mail list logo
