Re: JMX enabling in CXF 2.2.6
Thanks Eoghan,
I will try it out.
Regards,
Ulhas Bhole.
On Fri, Mar 19, 2010 at 11:34 AM, Eoghan Glynn wrote:
> A-ha, my bad, I assumed you were using the remote process option ... so you
> just can't see the CXF MBeans when you connect via the jconsole local
> process option?
>
> That's easy, just ensure your injected InstrumentationManager bean picks up
> the *platform* MBeanServer as opposed to creating a fresh one. Its the
> platform MBeanServer that the local process option will go for by default.
>
> Simply modify your config as follows to set the usePlatformMBeanServer
> property:
>
> class="org.apache.cxf.management.jmx.InstrumentationManagerImpl">
>
>
>
>
>
> value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
>
> BTW in the remote case, you don't even need to specify the cxf/cxf as
> remote
> user/pass as this is not authenticated (unlike SMX/karaf).
>
> /Eoghan
>
> On 19 March 2010 10:29, Ulhas Bhole wrote:
>
> > Hi Eoghan,
> >
> > I did a few tests and it looks like if I try to connect to the process
> from
> > JConsole it doesn't show CXF JMX stats. If I create a new connection
> using
> > JMX URL and username/password (cxf/cxf) I do see the CXF MBean appearing.
> >
> > Thanks for the help.
> >
> > Regards,
> >
> > Ulhas Bhole
> >
> > I just did a few tests
> >
> > I just tried it on 2 different machines (Linux and Mac) using JDK 1.5
> > On Fri, Mar 19, 2010 at 10:05 AM, Ulhas Bhole
> > wrote:
> >
> > > Thanks Eoghan for quick reply. I will try to update build.xml target
> and
> > > check. I was putting cxf.xml in $CXF_HOME/samples/wsdl_first_rpclit
> > > directory and I think it was picked up because when I ran client it did
> > got
> > > AddressAlreadyInUse for JMX port and also I could connect to the server
> > > using JConsole.
> > >
> > > I will try your route.
> > >
> > > Regards,
> > >
> > > Ulhas Bhole
> > >
> > >
> > > On Thu, Mar 18, 2010 at 10:05 PM, Eoghan Glynn
> > wrote:
> > >
> > >> Ulhas,
> > >>
> > >> How are you picking up the config file?
> > >>
> > >> For example, if you're running the server via ant, you'd need to
> change
> > >> the
> > >> server target defined in $CXF_HOME/samples/wsdl_first_rpclit/build.xml
> > >> from:
> > >>
> > >> depends="build">
> > >> > >>param1="${basedir}/wsdl/hello_world_RPCLit.wsdl"/>
> > >>
> > >>
> > >> to:
> > >>
> > >> depends="build">
> > >> > >>jvmarg1="-Dcxf.config.file=cxf.xml"
> > >>param1="${basedir}/wsdl/hello_world_RPCLit.wsdl"/>
> > >>
> > >>
> > >> Alternatively, you could change the
> > >>
> $CXF_HOME/samples/wsdl_first_rpclit/src/demo/hwRPCLit/server/Server.java
> > >> to
> > >> use the SpringBusFactory to explicit identify the config file when
> > >> creating
> > >> the Bus.
> > >>
> > >> But obviously you must make the connection to the config in *some*
> way,
> > >> otherwise the intrumentation config will have no effect. BTW I just
> > >> confirmed that the CXF MBeans appear as expected with this demo using
> > your
> > >> config file and the first approach described.
> > >>
> > >> Cheers,
> > >> Eoghan
> > >>
> > >>
> > >> On 18 March 2010 17:24, Ulhas Bhole wrote:
> > >>
> > >> > Hi,
> > >> > I am trying to enable JMX instrumentation in CXF 2.2.6 sample
> > >> > (wsdl_first_rpclit) but when I try to connect to server using
> JConsole
> > I
> > >> > don't see any CXF MBeans. Do I need to do anything in addition to
> > >> > configuring Instrumentation manager?
> > >> >
> > >> > Here is my cxf.xml that I am using to enable instrumentation. I am
> not
> > >> > updating any implementation to collect endpoint statistics just want
> > to
> > >> see
> > >> > cxf stats first like Bus.
> > >> >
> > >> > http://www.springframework.org/schema/beans";
> > >> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > >> > xmlns:jaxws="http://cxf.apache.org/jaxws";
> > >> > xmlns:cxf="http://cxf.apache.org/core";
> > >> >
> > >> > xsi:schemaLocation="
> > >> > http://www.springframework.org/schema/beans
> > >> > http://www.springframework.org/schema/beans/spring-beans.xsd
> > >> > http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd
> > >> > http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd
> ">
> > >> >
> > >> >
> > >> > > >> > class="org.apache.cxf.management.jmx.InstrumentationManagerImpl">
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > > >> > value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > > >> > class="org.apache.cxf.management.counters.CounterRepository">
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Regards,
> > >> >
> > >> > Ulhas Bhole
> > >> >
> > >>
> > >
> > >
> >
>
[ANN] Apache CXF version 2.2.7 released!
The Apache CXF team is proud to announce the availability of the latest patch for the 2.2.x fixes branch: version 2.2.7 Apache CXF is an open source services framework. CXF helps you build and develop services using front end programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. This is mostly a patch release to fix problems and issues that users have encountered. 2.2.7 fixes over 55 JIRA issues reported against 2.2.6.See: http://cxf.apache.org/apache-cxf-227-release-notes.html For more information see: * Download: http://cxf.apache.org/download.html * Website: http://cxf.apache.org/ * Mailing lists: http://cxf.apache.org/mailing-lists.html If you have feedback, questions or would like to get involved in the CXF project please join the mailing lists and let us know your thoughts. The Apache CXF Team http://cxf.apache.org/ signature.asc Description: This is a digitally signed message part.
was ce and cxf
Hello, Running mtom sample on websphere app server ce(community edition) it gives me following exception. It seems that was ce comes with axis2 implementation. Has anybody successfully deployed cxf on was ce ? I would appreciate the response. Regards, Manoj modeler error: Response wrapper bean names must be unique and must not clash with other generated classes. Class: com.sample.backoffice.service.BackOffice method testDataHandler(javax.xml.ws.Holder,javax.xml.ws.Holder) at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServiceAP.java:202) at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServiceAP.java:191) at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServiceAP.java:187) at com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.generateWrappers(WebServiceWrapperGenerator.java:231) at com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.processMethod(WebServiceWrapperGenerator.java:141) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitMethodDeclaration(WebServiceVisitor.java:468) at com.sun.tools.apt.mirror.declaration.MethodDeclarationImpl.accept(MethodDeclarationImpl.java:53) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.processMethods(WebServiceVisitor.java:392) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.postProcessWebService(WebServiceVisitor.java:356) at com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.postProcessWebService(WebServiceWrapperGenerator.java:111) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitInterfaceDeclaration(WebServiceVisitor.java:138) at com.sun.tools.apt.mirror.declaration.InterfaceDeclarationImpl.accept(InterfaceDeclarationImpl.java:44) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.inspectEndpointInterface(WebServiceVisitor.java:439) at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitClassDeclaration(WebServiceVisitor.java:159) at com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.accept(ClassDeclarationImpl.java:107) at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.buildModel(WebServiceAP.java:345) at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.process(WebServiceAP.java:230) at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:72) at com.sun.tools.apt.comp.Apt.main(Apt.java:466) at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:269) at com.sun.tools.apt.main.Main.compile(Main.java:1113) at com.sun.tools.apt.main.Main.compile(Main.java:975) at com.sun.tools.apt.Main.processing(Main.java:106) at com.sun.tools.apt.Main.process(Main.java:96) at com.sun.tools.apt.Main.process(Main.java:78) at com.sun.tools.ws.wscompile.CompileTool.buildModel(CompileTool.java:603) at com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:536) at com.sun.tools.ws.util.ToolBase.run(ToolBase.java:54) at com.sun.tools.ws.util.WSToolsObjectFactoryImpl.wsgen(WSToolsObjectFactoryImpl.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:204) at org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:193) at org.apache.geronimo.jaxws.builder.JAXWSTools.invokeWsgen(JAXWSTools.java:175) at org.apache.geronimo.jaxws.builder.WsdlGenerator.invokeWsgen(WsdlGenerator.java:357) at org.apache.geronimo.jaxws.builder.WsdlGenerator.generateWsdl(WsdlGenerator.java:331) at org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:222) at org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:175) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:447) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
Re: Will your project feature at ApacheCon North America 2010?
On 3/22/2010 9:35 PM, Kevan Miller wrote: > Apologies for the broadcast message... > > In thinking about ApacheCon 2010, I began to wonder if there is interest in > creating an "Enterprise Java" track for the conference. I think there is the > potential for a lot of interesting content. Many of our projects are busy > implementing JSR specs for Java EE6. Also, the OSGi Alliance EEG has created > several EE-focuse specifications with more on the way. I'm sure each of our > projects have a number of internal developments which we're also interested > in sharing. Absolutely! We already expected to have meta-tracks; essentially one room of the Enterprise development resources, one room of Server technologies, one room of Cloud - NoSQL - Persistence etc etc. Whoops - there went all the rooms :) > I'm guessing that some of our projects have already initiated their own track > programs. Which I think is fine. I don't think it's a conflict to have > technology specific tracks. However, if you're interested in joining forces, > let me know. I think it would help foster greater interactions between our > projects and also result in a very interesting conference track. +1 - several of these projects will have a track day, but this many wouldn't fit and I'm sure many hadn't identified a day of content for the general public, but want to present one or two talks. > To help to start aggregating potential presentations, I've created a Wiki > page -- > http://cwiki.apache.org/confluence/display/GMOxPMGT/ApacheCon+NA+2010+--+Enterprise+Java+Track Thank you! > At this point, we do not need to identify specific presentations. But we do > need to insure that there is sufficient interest. Agreed - in fact it's better for the track if two Foo project presentations fit, but there are five proposals. This means there's an opportunity to choose the strongest programming, and also probably highlights an opportunity for a meetup for the more obscure or less focused talk ideas. > If I've left out any projects who you think might be interested in > participating, please feel free to pass this along... We trust you are offering to be the liason/coordinator for these 'assorted' track days? :)
Re: CXF version 2.2.7?
FYI, it's released. On Mon, Mar 22, 2010 at 3:47 AM, S. Ali Tokmen wrote: > Here's my +1 for the tagged CXF 2.2.7 version > > S. Ali Tokmen > savas-ali.tok...@bull.net > > Office: +33 4 76 29 76 19 > GSM: +33 66 43 00 555 > > Bull, Architect of an Open World TM > http://www.bull.com > > > Le 20/03/2010 04:07, Daniel Kulp a écrit : >> >> On Friday 19 March 2010 6:58:07 am S. Ali Tokmen wrote: >> >>> >>> Hello again >>> >>> Version 2.2.7 seems to be tagged :) Is that the final tag? When do you >>> expect it to land on the Maven repos? >>> >> >> The VOTE was started last night. Thus, it will conclude Sunday >> night/monday >> morning at which point it will get promoted and synced. Thus, by Tuesday >> it >> will be in Central if all goes well. >> >> Dan >> >> >> >> >>> >>> Cheers >>> >>> S. Ali Tokmen >>> savas-ali.tok...@bull.net >>> >>> Office: +33 4 76 29 76 19 >>> GSM: +33 66 43 00 555 >>> >>> Bull, Architect of an Open World TM >>> http://www.bull.com >>> >>> Le 15/03/2010 17:51, Daniel Kulp a écrit : >>> On Monday 15 March 2010 10:32:45 am S. Ali Tokmen wrote: > > Hello > > This is excellent news :) Is the "next week" this week (i.e., week 11 > of > 2010) ? > Yea. I'm HOPING to do the build on Wednesday, but I want to try and get some UsernameToken optimizations in before then. If I don't get them in before thursday, I'll just do the build and they can wait for 2.2.8. Dan > > Cheers > > S. Ali Tokmen > savas-ali.tok...@bull.net > > Office: +33 4 76 29 76 19 > GSM: +33 66 43 00 555 > > Bull, Architect of an Open World TM > http://www.bull.com > > Le 13/03/2010 05:10, AllanSLim a écrit : > >> >> Hi Sergey, >> >> Thanks for the update! >> >> regards, >> Allan >> >> Sergey Beryozkin-5 wrote: >> >>> >>> Hi Allan >>> >>> Dan is planning to do a release sometime next week. >>> >>> cheers, Sergey >>> >>> On Fri, Mar 12, 2010 at 5:22 PM, AllanSLim >>> >> >> wrote: >> Hi Guys, We were wondering when will version 2.2.7 be released? Our code is dependent on one fix that Sergey added, and we cannot use the trunk, because it might not be stable. thanks, Allan -- View this message in context: http://old.nabble.com/CXF-version-2.2.7--tp27880271p27880271.html Sent from the cxf-user mailing list archive at Nabble.com. >> >> > > -- Craig Tataryn site: http://www.basementcoders.com/ podcast:http://feeds.feedburner.com/TheBasementCoders irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin twitter: craiger
Re: was ce and cxf
On Tuesday 23 March 2010 1:32:07 pm Purohit, Manoj R wrote: > Hello, > > Running mtom sample on websphere app server ce(community edition) it gives > me following exception. It seems that was ce comes with axis2 > implementation. > Has anybody successfully deployed cxf on was ce ? > I would appreciate the response. I don't think I've ever heard of anyone even trying. You MAY be able to get a response on the Geronimo lists or on the WAS CE lists. IBM recently added stuff to WAS to allow use of other JAX-WS runtimes, but I don't know if that code was also added to the CE version. Also don't know if you could uninstall the axis2 based JAX-WS version which is interfering, or, at the very least, turn off the annotation scanning at startup which is causing this. Dan > > > Regards, > Manoj > > modeler error: Response wrapper bean names must be unique and must not > clash with other generated classes. Class: > com.sample.backoffice.service.BackOffice method > testDataHandler(javax.xml.ws.Holder,javax.xml.ws.Holder< > javax.activation.DataHandler>) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServ > iceAP.java:202) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServ > iceAP.java:191) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.onError(WebServ > iceAP.java:187) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.g > enerateWrappers(WebServiceWrapperGenerator.java:231) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.p > rocessMethod(WebServiceWrapperGenerator.java:141) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitMetho > dDeclaration(WebServiceVisitor.java:468) at > com.sun.tools.apt.mirror.declaration.MethodDeclarationImpl.accept(MethodDe > clarationImpl.java:53) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.processMet > hods(WebServiceVisitor.java:392) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.postProces > sWebService(WebServiceVisitor.java:356) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceWrapperGenerator.p > ostProcessWebService(WebServiceWrapperGenerator.java:111) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitInter > faceDeclaration(WebServiceVisitor.java:138) at > com.sun.tools.apt.mirror.declaration.InterfaceDeclarationImpl.accept(Inter > faceDeclarationImpl.java:44) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.inspectEnd > pointInterface(WebServiceVisitor.java:439) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitClass > Declaration(WebServiceVisitor.java:159) at > com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.accept(ClassDecl > arationImpl.java:107) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.buildModel(WebS > erviceAP.java:345) at > com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.process(WebServ > iceAP.java:230) at > com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.proce > ss(AnnotationProcessors.java:72) at > com.sun.tools.apt.comp.Apt.main(Apt.java:466) > at > com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:269) at > com.sun.tools.apt.main.Main.compile(Main.java:1113) > at com.sun.tools.apt.main.Main.compile(Main.java:975) > at com.sun.tools.apt.Main.processing(Main.java:106) > at com.sun.tools.apt.Main.process(Main.java:96) > at com.sun.tools.apt.Main.process(Main.java:78) > at > com.sun.tools.ws.wscompile.CompileTool.buildModel(CompileTool.java:603) at > com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:536) at > com.sun.tools.ws.util.ToolBase.run(ToolBase.java:54) > at > com.sun.tools.ws.util.WSToolsObjectFactoryImpl.wsgen(WSToolsObjectFactoryI > mpl.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 39) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm > pl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) > at > org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:204) > at > org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:193) > at > org.apache.geronimo.jaxws.builder.JAXWSTools.invokeWsgen(JAXWSTools.java:1 > 75) at > org.apache.geronimo.jaxws.builder.WsdlGenerator.invokeWsgen(WsdlGenerator. > java:357) at > org.apache.geronimo.jaxws.builder.WsdlGenerator.generateWsdl(WsdlGenerator > .java:331) at > org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.jav > a:222) at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSS > erviceBuilder.java:175) at > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(Tomcat > ModuleBuilder.java:447) at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder
