WSDL-Java wrapped (vs. non-wrapped) with doc-lit-wrap WSDL with named complexType

I was wondering about the decision to have the WSDL2Java tool map the following WSDL pattern onto a non-wrapped Java interface when using doc-lit-wrapped WSDL: ...types complexType name=getGreetings sequence element name=name

JPA and Transaction Manager extensions

FYI, I've updated the JPA and TM extensions to work off the latest kernel. I will also be converting these extensions over to leveraging the integration test harness (iTest plugin). Jim - To unsubscribe, e-mail: [EMAIL

Re: WSDL-Java wrapped (vs. non-wrapped) with doc-lit-wrap WSDL with named complexType

Once binding is involved within WSDL2Java, one WSDL portType/message can end up with multiple Java classes respective to different bindings. It mixes business logic and wire format :-( Assuming involving binding is de facto, and only one binding each WSDL portType/message, maybe we can change

SCA 1.0 reference target syntax

FYI, I've checked in support for the SCA 1.0 syntax for specifying component references using the target attribute. I also updated all samples and integration tests. The old .95 style of specifying the reference target URI will no longer be supported. I now plan to move Service and

Data source extension updates

FYI, I've moved the data source extension which allows services to obtain pooled db connections up to the latest kernel version. I've removed the old SCATestCase-based integration tests temporarily. I would like to split these out as separate integration tests similar to how the Spring

Tossing CompositeComponent, r511391

I have removed all of the CompositeComponent specializations from the kernel so have been able to remove the interface and all references to it :-) This simplifies the kernel code quite a bit as it only refers to Component and in certain circumstances AtomicComponent. I'm going to further

Re: Tossing CompositeComponent, r511391

There's still a reference to parent Component in the builder API e.g. +public ServiceBinding build(Component parent, ServiceDefinition serviceDefinition, LocalBindingDefinition bindingDefinition,

Re: Tossing CompositeComponent, r511391

On Feb 24, 2007, at 5:42 PM, Jeremy Boynes wrote: There's still a reference to parent Component in the builder API e.g. +public ServiceBinding build(Component parent, ServiceDefinition serviceDefinition,

Multi-VM support and sparse trees, was: Tossing CompositeComponent, r511391

On Feb 24, 2007, at 5:49 PM, Jim Marino wrote: On Feb 24, 2007, at 5:42 PM, Jeremy Boynes wrote: There's still a reference to parent Component in the builder API e.g. +public ServiceBinding build(Component parent, ServiceDefinition serviceDefinition,

RE: Spring extension release

Cool. Once I get the work I am doing on the slave side of federation out of way, I can port the groovy component type to 1.0 and also look at a JXTA binding based on the stuff we have been working on for discovery. Ta Meeraj From: Jim Marino [EMAIL PROTECTED] Reply-To:

Re: EJB code dump, was: svn commit: r511225 [1/4]

On Sunday 25 February 2007 09:36, Jeremy Boynes wrote: On Feb 23, 2007, at 10:26 PM, [EMAIL PROTECTED] wrote: Author: rfeng Date: Fri Feb 23 22:26:55 2007 New Revision: 511225 URL: http://svn.apache.org/viewvc?view=revrev=511225 Log: [sca-integration-branch] Add EJB reference