Re: CXF WorkQueueManager : How to see the mbean on Jboss
Note that in order for any CXF MBean to actually be exposed, you'll have to enable the IntrumentationManager (which is disabled by default). See [1] for details. Cheers, Eoghan [1] http://cwiki.apache.org/CXF20DOC/jmx-management.html 2009/7/21 Rao, Sameer V : > CXF Asynch processing creates a ThreadPool and registers itself as > MBean. How/Under which object name does that appear in JBossAS4.3 > container? >
Re: Improving JBossWS-CXF Client Side Integration
Hi Dan, Daniel Kulp wrote: On Tue July 21 2009 11:25:56 am Alessio Soldano wrote: The ServiceImpl gets the configurer from the bus after having created the jaxws proxy factory bean. Then my custom configurer sets the props in the JaxWSProxyFactoryBean which in turns copies them to the request context in method clientClientProxy(Client c), that is called when getting the port. Now, here are my few questions: - could this be considered a proper use of the Configurer? Actually, this is EXACTLY the right use of the Configurer. Good catch. It's specifically there so the container can provide configuration to the various beans used throughout CXF. OK, thanks for confirmation. I've found just one implementation of this interface, for something related to spring configuration Our normal config mechanism is spring based. Thus, that's the implementation that is used most often. I don't know if your JBoss integration stuff exposes any of the spring config to the JBoss/CXF users. If so, you may need to keep the Spring configurer and "wrapper" it with yours. : Configurer orig = bus.getExtension(Configurer.class) bus.setExtension(new ServiceRefStubPropertyConfigurer(serviceRef, orig), Configurer.class); and have it call the wrapped configurer as well. I've switched to the wrapper approach, just to be sure I'm not reducing user's ability to set a configurer on its own (even if it's actually not possible in the usecase that led us to this issue). - I see Configurer has two methods: void configureBean(Object beanInstance); void configureBean(String name, Object beanInstance); I'd actually add another call for the configuration in ServiceImpl using the former (configureBean(Object beanInstance)) as technically speaking the latter seems to me to be used for configuring beans of a specific name and currently the ServiceImpl uses that for portName+".jaxws-client.proxyFactory" beans. I'd double check that. Instead of "adding", you MAY be able to just replace as I think the default of configureBean(Object beanInstance) is to call a getName on the instance and then call the other method. I'd leave everything as is currently then. Btw having implemented my configurer as a wrapper, I call a private method in my configurer from each of the two methods and then delegate to the corresponding method in the wrapped configurer. So everything should go on working as originally meant ;-) Let me know what do you think, considering you said this could be of use also for integrations issues besides JBossWS. Sounds perfect! OK, thanks for the insight on this. Cheers Alessio -- Alessio Soldano Web Service Lead, JBoss
maven2 repository for sdo dependencies
Hi, I've just tried building CXF trunk and had issues with finding org.eclipse artifacts required for the SDO DataBinding module. They do not seem to be in central maven repo; I've managed to get them using some official and unofficial eclipse repos, so... what repository do you currently have configured to get them? Thanks Alessio Missing: -- 1) org.eclipse.emf:ecore:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore:jar:2.2.3 2) org.eclipse.emf:ecore-change:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore-change:jar:2.2.3 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 4) org.eclipse.xsd:xsd:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.xsd -DartifactId=xsd -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.xsd -DartifactId=xsd -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.xsd:xsd:jar:2.2.3 5) org.eclipse.emf:codegen:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-tools:jar:1.1.1 3) org.eclipse.emf:codegen:jar:2.2.3 6) org.eclipse.emf:codegen-ecore:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=codegen-ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=codegen-ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-tools:jar:1.1.1 3) org.eclipse.emf:codegen-ecore:jar:2.2.3 -- 6 required artifacts are missing. for artifact: org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) -- Alessio Soldano Web Service Lead, JBoss
Re: maven2 repository for sdo dependencies
Hmm... I didn't configure anything. The tuscany poms already have something configured in them. If I wipe out my .m2/repository/org/eclispe stuff, I see it downloading from: http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2//org/eclipse/emf/ecore/2.2.3/ecore-2.2.3.jar although all the checksums fail. Do you have a repo manager or something configured that might block it? I'll see if I can figure out what we need from there and copy to central or something. Dan On Wed July 22 2009 6:00:26 am Alessio Soldano wrote: > Hi, > I've just tried building CXF trunk and had issues with finding > org.eclipse artifacts required for the SDO DataBinding module. > They do not seem to be in central maven repo; I've managed to get them > using some official and unofficial eclipse repos, so... what repository > do you currently have configured to get them? > Thanks > Alessio > > > Missing: > -- > 1) org.eclipse.emf:ecore:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.emf > -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.eclipse.emf > -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file > -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT > 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 > 3) org.eclipse.emf:ecore:jar:2.2.3 > > 2) org.eclipse.emf:ecore-change:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.emf > -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar > -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.eclipse.emf > -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT > 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 > 3) org.eclipse.emf:ecore-change:jar:2.2.3 > > 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.emf > -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.eclipse.emf > -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT > 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 > 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 > > 4) org.eclipse.xsd:xsd:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.xsd > -DartifactId=xsd -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.eclipse.xsd -DartifactId=xsd > -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT > 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 > 3) org.eclipse.xsd:xsd:jar:2.2.3 > > 5) org.eclipse.emf:codegen:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.emf > -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.eclipse.emf > -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT > 2) org.apache.tuscany.sdo:tuscany-sdo-tools:jar:1.1.1 > 3) org.eclipse.emf:codegen:jar:2.2.3 > > 6) org.eclipse.emf:codegen-ecore:jar:2.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.eclipse.emf > -DartifactId=codegen-ecore -Dversion=2.2.3 -Dpackaging=jar > -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: >
Re: maven2 repository for sdo dependencies
Hi Dan, mmh, no, I don't have any special repo manager or similar, I've just my custom maven2 settings.xml with a profile for enabling JBoss repositories if required. Btw, I'm using Maven 2.0.9, I'll try with a more recent one later, perhaps that matters. Thanks anyway, I can at least add the m2 repo below now. Alessio Daniel Kulp wrote: Hmm... I didn't configure anything. The tuscany poms already have something configured in them. If I wipe out my .m2/repository/org/eclispe stuff, I see it downloading from: http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2//org/eclipse/emf/ecore/2.2.3/ecore-2.2.3.jar although all the checksums fail. Do you have a repo manager or something configured that might block it? I'll see if I can figure out what we need from there and copy to central or something. Dan On Wed July 22 2009 6:00:26 am Alessio Soldano wrote: Hi, I've just tried building CXF trunk and had issues with finding org.eclipse artifacts required for the SDO DataBinding module. They do not seem to be in central maven repo; I've managed to get them using some official and unofficial eclipse repos, so... what repository do you currently have configured to get them? Thanks Alessio Missing: -- 1) org.eclipse.emf:ecore:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore:jar:2.2.3 2) org.eclipse.emf:ecore-change:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore-change -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore-change:jar:2.2.3 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=ecore-xmi -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.emf:ecore-xmi:jar:2.2.3 4) org.eclipse.xsd:xsd:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.xsd -DartifactId=xsd -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.xsd -DartifactId=xsd -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-impl:jar:1.1.1 3) org.eclipse.xsd:xsd:jar:2.2.3 5) org.eclipse.emf:codegen:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.emf -DartifactId=codegen -Dversion=2.2.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cxf:cxf-rt-databinding-sdo:jar:2.3.0-SNAPSHOT 2) org.apache.tuscany.sdo:tuscany-sdo-tools:jar:1.1.1 3) org.eclipse.emf:codegen:jar:2.2.3 6) org.eclipse.emf:codegen-ecore:jar:2.2.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.emf -DartifactId=codegen-e
