Re: ASF Board Report for Nov 2007 is now due

2007-11-12 Thread Guillaume Nodet
Here is a draft:
   http://cwiki.apache.org/confluence/display/SM/2007-11-14
If I missed something, please edit it asap.

On Nov 12, 2007 11:30 PM, Guillaume Nodet [EMAIL PROTECTED] wrote:

 Well, we need one as a TLP, not as an incubator project ;-)


 On Nov 12, 2007 11:22 PM, Bruce Snyder [EMAIL PROTECTED] wrote:

  On 11/12/07, Guillaume Nodet [EMAIL PROTECTED] wrote:
   The meeting will take place this week at ApacheCon.
   I will work on a draft asap.
 
  I already submitted a quick note in the ServiceMix report stating that
  ServiceMix has graduated from the Incubator. However, the MoinMoin
  wiki config seems to be goofed up somehow.
 
  Bruce
  --
  perl -e 'print
  unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT*
  );'
 
  Apache ActiveMQ - http://activemq.org/
  Apache ServiceMix - http://servicemix.org/
  Apache Geronimo - http://geronimo.apache.org/
  Castor - http://castor.org/
 



 --
 Cheers,
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/


[jira] Resolved: (SM-810) Create single complete ServiceMix Shared Library

2007-11-12 Thread Guillaume Nodet (JIRA)

 [ 
https://issues.apache.org/activemq/browse/SM-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-810.


   Resolution: Fixed
Fix Version/s: 3.3
   3.2.1
   3.1.3
 Assignee: Guillaume Nodet

Move servicemix-shared-compat in the build.
URL: http://svn.apache.org/viewvc?rev=594349view=rev
URL: http://svn.apache.org/viewvc?rev=594350view=rev
URL: http://svn.apache.org/viewvc?rev=594351view=rev


 Create single complete ServiceMix Shared Library
 

 Key: SM-810
 URL: https://issues.apache.org/activemq/browse/SM-810
 Project: ServiceMix
  Issue Type: Improvement
Affects Versions: 3.0
 Environment: ServiceMix 3.0
Reporter: James Lorenzen
Assignee: Guillaume Nodet
 Fix For: 3.1.3, 3.2.1, 3.3

   Original Estimate: 1 day
  Remaining Estimate: 1 day

 The current ServiceMix Shared Library is insufficient to support proper 
 portability of existing ServiceMix components to other JBI containers, such 
 as OpenESB. For example, when installing the ServiceMix HTTP BC in OpenESB, 
 NoClassDefFoundErrors occur because the installed ServiceMix Shared Library 
 does not contain all the necessary dependencies.
 Therefore it would be a good idea to create a single complete Shared Library.
 To accomplish this here are some ideas:
 1) Combine the shared library and shared library compat projects together.
 2) Ensure the new single complete Shared Library contains the following 
 dependencies:
  a) activemq-core
  b) backport-util-concurrent
  c) commons-logging
  d) servicemix-core
  e) servicemix-services
  f) spring-2.0-rc3
  g) wsdl4j
  h) xbean-classloader
  i) xbean-kernel
  j) xbean-server
  k) xbean-spring
 When complete the dependencies under /servicemix_home/lib should be smaller.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (SM-1135) Put mandatory osgi entries in the JBI artifacts so that those artifacts can be deployed as bundles

2007-11-12 Thread Guillaume Nodet (JIRA)
Put mandatory osgi entries in the JBI artifacts so that those artifacts can be 
deployed as bundles
--

 Key: SM-1135
 URL: https://issues.apache.org/activemq/browse/SM-1135
 Project: ServiceMix
  Issue Type: Improvement
  Components: tooling
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 3.3




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component

2007-11-12 Thread David Medinets (JIRA)

[ 
https://issues.apache.org/activemq/browse/SM-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40590
 ] 

David Medinets commented on SM-1103:


I am running into this problem while starting ServiceMix from inside Eclipse 
3.3.  

I am using C:\data\support\apache-servicemix-3.3.0.4-fuse as the home for 
ServiceMix server. Then when I start it from inside of
Eclipse, I get the following error.

Any suggestions?

Starting Apache ServiceMix ESB: 3.3.0.4-fuse

Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO  - ConnectorServerFactoryBean - JMX connector available at: 
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO  - JBIContainer   - ServiceMix 3.3.0.4-fuse JBI Container 
(ServiceMix) is starting
INFO  - JBIContainer   - For help or more informations please 
see: http://incubator.apache.org/servicemix/
INFO  - ComponentMBeanImpl - Initializing component: 
#SubscriptionManager#
INFO  - DeploymentService  - Restoring service assemblies
INFO  - JBIContainer   - ServiceMix JBI Container (ServiceMix) 
started
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing
servicemix-bean-3.3.0.4-fuse-installer.zip ...
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-bean
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-bean-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing servicemix-bpe-3.3.0.4-fuse-installer.zip
...
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-bpe
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-bpe-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing
servicemix-camel-3.3.0.4-fuse-installer.zip ...
INFO  - JDBCAdapterFactory - Database driver recognized: 
[apache_derby_embedded_jdbc_driver]
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-camel
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-camel-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing
servicemix-cxf-bc-3.3.0.4-fuse-installer.zip ...
INFO  - LogTask- Logging system reconfigured using file:
file:/C:/data/support/apache-servicemix-3.3.0.4-fuse/conf/log4j.xml
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-cxf-bc
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-cxf-bc-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing
servicemix-cxf-se-3.3.0.4-fuse-installer.zip ...
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-cxf-se
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-cxf-se-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing
servicemix-drools-3.3.0.4-fuse-installer.zip ...
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-drools
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-drools-3.3.0.4-fuse-installer.zip
INFO  - AutoDeploymentService  - Directory: hotdeploy: Archive changed: 
processing servicemix-eip-3.3.0.4-fuse-installer.zip
...
WARN  - AutoDeploymentService  - Shared libraries servicemix-shared are 
not installed yet: the componentservicemix-eip
installation is suspended and will be resumed once the listed shared libraries 
are installed
INFO  - AutoDeploymentService  - Directory: hotdeploy: Finished 
installation of archive:
servicemix-eip-3.3.0.4-fuse-installer.zip
INFO  - 

Re: WSIT Support

2007-11-12 Thread ArmenH

It appears that CXF does support most of the WS-* 

Has anyone used Microsoft WCF based clients/services to show full
interoperability?



ArmenH wrote:
 
 Does ServiceMix fully support WSIT? 
 
 If not, are there plans to support it?
 
 CXF is still not fully compliant with WSIT.
 

-- 
View this message in context: 
http://www.nabble.com/WSIT-Support-tf4795567s12049.html#a13719462
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.



Re: WSIT Support

2007-11-12 Thread Freeman Fang

Hi,

We already have servicemix-cxf-bc to leverage ws-* feature from cxf.
And I also know cxf team do lots of interoperability test between cxf 
and WCF(including ws-* feature), if you are interested in this issue, I 
guess you could post this thread on cxf mailling list, where more people 
can answer your question.


Best Regards

Freeman

ArmenH wrote:
It appears that CXF does support most of the WS-* 


Has anyone used Microsoft WCF based clients/services to show full
interoperability?



ArmenH wrote:
  
Does ServiceMix fully support WSIT? 


If not, are there plans to support it?

CXF is still not fully compliant with WSIT.




  


Re: WSIT Support

2007-11-12 Thread ArmenH

Thanks,

Is the CXF used in ServiceMix version 2.0.2?


Freeman Fang wrote:
 
 Hi,
 
 We already have servicemix-cxf-bc to leverage ws-* feature from cxf.
 And I also know cxf team do lots of interoperability test between cxf 
 and WCF(including ws-* feature), if you are interested in this issue, I 
 guess you could post this thread on cxf mailling list, where more people 
 can answer your question.
 
 Best Regards
 
 Freeman
 
 ArmenH wrote:
 It appears that CXF does support most of the WS-* 

 Has anyone used Microsoft WCF based clients/services to show full
 interoperability?



 ArmenH wrote:
   
 Does ServiceMix fully support WSIT? 

 If not, are there plans to support it?

 CXF is still not fully compliant with WSIT.

 

   
 
 

-- 
View this message in context: 
http://www.nabble.com/WSIT-Support-tf4795567s12049.html#a13719874
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.


[jira] Created: (SM-1136) PreDestroy being called for each exchange when it's not configured that way.

2007-11-12 Thread Ryan Bohn (JIRA)
PreDestroy being called for each exchange when it's not configured that way.


 Key: SM-1136
 URL: https://issues.apache.org/activemq/browse/SM-1136
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-bean
Affects Versions: 3.2
Reporter: Ryan Bohn
Priority: Critical


I have a sender bean and a receiver bean, both configured using bean:endpoint 
... bean=#  The problem is that the PreDestroy method is being called 
after every MessageExchange is finished.

According to the documentation:

Attention: The Bean Endpoint schema allows to set a Bean or a Bean Name. The 
Bean will create a single instance of the POJO per endpoint whereas the Bean 
Name will create an instance per request (message exchange).

I have in my xbean.xml:

?xml version=1.0 encoding=UTF-8?

beans xmlns:bean=http://servicemix.apache.org/bean/1.0;
   xmlns:example=http://servicemix.apache.org/example;

  bean:endpoint service=example:sender endpoint=senderEndpoint 
bean=#sender/
  bean:endpoint service=example:receiver endpoint=receiverEndpoint 
bean=#receiver/

  bean id=sender class=example.Sender
property name=target value=example:receiver/
  /bean
  
  bean id=receiver class=example.Receiver
  /bean

/beans

The receiver simply implements MessageExchangeListener.

The PostConstruct and PreDestroy only gets called once on the sender
The PostConstruct only gets called once on the receiver
However, the PreDestroy gets called on the receiver for each request.

I noticed in BeanEndpoint, there is the following method:

protected void checkEndOfRequest(Request request, Object corId) {
if (request.getExchange().getStatus() != ExchangeStatus.ACTIVE) {
ReflectionUtils.callLifecycleMethod(request.getBean(), 
PreDestroy.class);
//request.setBean(null);
//request.setExchange(null);
requests.remove(corId);
}
}

It doesn't look like this class pays any attention to whether the bean is 
supposed to be a single instance of an instance-per-request, which is probably 
the cause of the problem.


If you need me to attach an example, please let me know.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: WSIT Support

2007-11-12 Thread Bozhong Lin
Just to clarify, I think CXF is used in ServiceMix version 3.2, not
version 2.0.2.

Regards,
Bo

On Nov 13, 2007 1:10 PM, Freeman Fang [EMAIL PROTECTED] wrote:
 Yes

 Freeman


 ArmenH wrote:
  Thanks,
 
  Is the CXF used in ServiceMix version 2.0.2?
 
 
  Freeman Fang wrote:
 
  Hi,
 
  We already have servicemix-cxf-bc to leverage ws-* feature from cxf.
  And I also know cxf team do lots of interoperability test between cxf
  and WCF(including ws-* feature), if you are interested in this issue, I
  guess you could post this thread on cxf mailling list, where more people
  can answer your question.
 
  Best Regards
 
  Freeman
 
  ArmenH wrote:
 
  It appears that CXF does support most of the WS-*
 
  Has anyone used Microsoft WCF based clients/services to show full
  interoperability?
 
 
 
  ArmenH wrote:
 
 
  Does ServiceMix fully support WSIT?
 
  If not, are there plans to support it?
 
  CXF is still not fully compliant with WSIT.
 
 
 
 
 
 
 
 



Re: WSIT Support

2007-11-12 Thread Freeman Fang

From my understanding, I think the question is

What's the CXF version used in servicemix? :-)

Regards

Freeman



Bozhong Lin wrote:

Just to clarify, I think CXF is used in ServiceMix version 3.2, not
version 2.0.2.

Regards,
Bo

On Nov 13, 2007 1:10 PM, Freeman Fang [EMAIL PROTECTED] wrote:
  

Yes

Freeman


ArmenH wrote:


Thanks,

Is the CXF used in ServiceMix version 2.0.2?


Freeman Fang wrote:

  

Hi,

We already have servicemix-cxf-bc to leverage ws-* feature from cxf.
And I also know cxf team do lots of interoperability test between cxf
and WCF(including ws-* feature), if you are interested in this issue, I
guess you could post this thread on cxf mailling list, where more people
can answer your question.

Best Regards

Freeman

ArmenH wrote:



It appears that CXF does support most of the WS-*

Has anyone used Microsoft WCF based clients/services to show full
interoperability?



ArmenH wrote:


  

Does ServiceMix fully support WSIT?

If not, are there plans to support it?

CXF is still not fully compliant with WSIT.