Re: CXF on WebLogic 9.2
Thanks for your suggestions. I tracked down the problem and it turns out that geronimo-ws-metadeta_2.0_spec-1.1.1.jar was being put on the WebLogic classpath twice, which was causing the error. Thanks again, Ben dkulp wrote: > > > It may be the xml-apis.jar. I'm not sure why we have it in lib. It > shouldn't be needed. I'll try excluding it and seeing if things still > build. > > Dan > > > On Thursday 07 February 2008, chengas123 wrote: >> Hi, >> I'm afraid I'm getting the QName issue again. I have no idea as to >> what was different in the very short span of time I was not getting >> the error. I do have the prefer-web-inf-classes set in my >> weblogic.xml file and I am using 2.0.4. Any other ideas on how I >> could track down the source of the issues? >> >> Thanks, >> Ben >> >> Barry Fitzgerald wrote: >> > Hello, >> > >> > I've had a similar problem before and I think you can fix it with a >> > prefer-web-inf-classes >> > element in your weblogic.xml. See here: >> > http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html >> > >> > To set this on a server wide basis see here: >> > http://e-docs.bea.com/wls/docs92/programming/classloading.html >> > >> > Hope this helps, >> > >> > Barry >> >> Daniel Kulp wrote: >> > On Jan 31, 2008 9:07 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: >> >> FYI: for 2.0.4, we specifically switched to the geronimo version >> >> as it does NOT have the QName class in it like the stax-api version >> >> that we used in 2.0.3 does. Thus, the problem should be >> >> reduced. >> >> >> >> Dan > > > > -- > J. Daniel Kulp > Principal Engineer, IONA > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15362446.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
It may be the xml-apis.jar. I'm not sure why we have it in lib. It shouldn't be needed. I'll try excluding it and seeing if things still build. Dan On Thursday 07 February 2008, chengas123 wrote: > Hi, > I'm afraid I'm getting the QName issue again. I have no idea as to > what was different in the very short span of time I was not getting > the error. I do have the prefer-web-inf-classes set in my > weblogic.xml file and I am using 2.0.4. Any other ideas on how I > could track down the source of the issues? > > Thanks, > Ben > > Barry Fitzgerald wrote: > > Hello, > > > > I've had a similar problem before and I think you can fix it with a > > prefer-web-inf-classes > > element in your weblogic.xml. See here: > > http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html > > > > To set this on a server wide basis see here: > > http://e-docs.bea.com/wls/docs92/programming/classloading.html > > > > Hope this helps, > > > > Barry > > Daniel Kulp wrote: > > On Jan 31, 2008 9:07 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > >> FYI: for 2.0.4, we specifically switched to the geronimo version > >> as it does NOT have the QName class in it like the stax-api version > >> that we used in 2.0.3 does. Thus, the problem should be > >> reduced. > >> > >> Dan -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: CXF on WebLogic 9.2
Hi, I'm afraid I'm getting the QName issue again. I have no idea as to what was different in the very short span of time I was not getting the error. I do have the prefer-web-inf-classes set in my weblogic.xml file and I am using 2.0.4. Any other ideas on how I could track down the source of the issues? Thanks, Ben Barry Fitzgerald wrote: > > Hello, > > I've had a similar problem before and I think you can fix it with a > prefer-web-inf-classes > element in your weblogic.xml. See here: > http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html > > To set this on a server wide basis see here: > http://e-docs.bea.com/wls/docs92/programming/classloading.html > > Hope this helps, > > Barry > Daniel Kulp wrote: > > > > On Jan 31, 2008 9:07 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > >> >> FYI: for 2.0.4, we specifically switched to the geronimo version as it >> does NOT have the QName class in it like the stax-api version that we >> used in 2.0.3 does. Thus, the problem should be reduced. >> >> Dan > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15344877.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
Hello,
I've had a similar problem before and I think you can fix it with a
prefer-web-inf-classes
element in your weblogic.xml. See here:
http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html
To set this on a server wide basis see here:
http://e-docs.bea.com/wls/docs92/programming/classloading.html
Hope this helps,
Barry
On Jan 31, 2008 9:07 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> FYI: for 2.0.4, we specifically switched to the geronimo version as it
> does NOT have the QName class in it like the stax-api version that we
> used in 2.0.3 does. Thus, the problem should be reduced.
>
> Dan
>
>
> On Thursday 31 January 2008, William Zhu wrote:
> > on CXF2.0.4, it's "geronimo-stax-api_1.0_spec-1.0.jar".
> >
> >
> >
> > chengas123 <[EMAIL PROTECTED]> wrote:
> >
> > Haha. I would have realized that was the same .jar
> > The only one included in 2.0.4 is stax-utils-20060502.jar
> >
> > YI (William) ZHU wrote:
> > > actually, it's "stax-api-1.0.1.jar".
> > > (on CXF 2.0.2 and CXF 2.0.3)
> > >
> > >
> > >
> > > chengas123 wrote:
> > >
> > > I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find
> > > any file name stax-api.jar in the lib directory.
> > >
> > > YI (William) ZHU wrote:
> > >> stax-api jar file is in \{CXF-home}\lib
> > >>
> > >> unpackage it, you will find the javax.xml.namespace.QName class.
> > >>
> > >> delete it, and re-package the file.
> > >>
> > >> try it.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
Re: CXF on WebLogic 9.2
FYI: for 2.0.4, we specifically switched to the geronimo version as it
does NOT have the QName class in it like the stax-api version that we
used in 2.0.3 does. Thus, the problem should be reduced.
Dan
On Thursday 31 January 2008, William Zhu wrote:
> on CXF2.0.4, it's "geronimo-stax-api_1.0_spec-1.0.jar".
>
>
>
> chengas123 <[EMAIL PROTECTED]> wrote:
>
> Haha. I would have realized that was the same .jar
> The only one included in 2.0.4 is stax-utils-20060502.jar
>
> YI (William) ZHU wrote:
> > actually, it's "stax-api-1.0.1.jar".
> > (on CXF 2.0.2 and CXF 2.0.3)
> >
> >
> >
> > chengas123 wrote:
> >
> > I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find
> > any file name stax-api.jar in the lib directory.
> >
> > YI (William) ZHU wrote:
> >> stax-api jar file is in \{CXF-home}\lib
> >>
> >> unpackage it, you will find the javax.xml.namespace.QName class.
> >>
> >> delete it, and re-package the file.
> >>
> >> try it.
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: CXF on WebLogic 9.2
Thank you for your help. I finally got WebLogic to start. I'm not sure what exactly I did to fix it, but part of it was definitely clearing the weblogic cache. Thanks again, Ben ianroberts wrote: > > chengas123 wrote: >> I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any >> file >> name stax-api.jar in the lib directory. > > 2.0.4 ships geronimo-stax-api_1.0_spec-1.0.jar instead, but this doesn't > include the QName class so probably doesn't help you. > > Ian > > -- > Ian Roberts | Department of Computer Science > [EMAIL PROTECTED] | University of Sheffield, UK > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15214832.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
chengas123 wrote: I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file name stax-api.jar in the lib directory. 2.0.4 ships geronimo-stax-api_1.0_spec-1.0.jar instead, but this doesn't include the QName class so probably doesn't help you. Ian -- Ian Roberts | Department of Computer Science [EMAIL PROTECTED] | University of Sheffield, UK
Re: CXF on WebLogic 9.2
on CXF2.0.4, it's "geronimo-stax-api_1.0_spec-1.0.jar".
chengas123 <[EMAIL PROTECTED]> wrote:
Haha. I would have realized that was the same .jar
The only one included in 2.0.4 is stax-utils-20060502.jar
YI (William) ZHU wrote:
>
> actually, it's "stax-api-1.0.1.jar".
> (on CXF 2.0.2 and CXF 2.0.3)
>
>
>
> chengas123 wrote:
>
> I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
> name stax-api.jar in the lib directory.
>
>
>
> YI (William) ZHU wrote:
>>
>> stax-api jar file is in \{CXF-home}\lib
>>
>> unpackage it, you will find the javax.xml.namespace.QName class.
>>
>> delete it, and re-package the file.
>>
>> try it.
>>
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213728.html
Sent from the cxf-user mailing list archive at Nabble.com.
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: CXF on WebLogic 9.2
Haha. I would have realized that was the same .jar
The only one included in 2.0.4 is stax-utils-20060502.jar
YI (William) ZHU wrote:
>
> actually, it's "stax-api-1.0.1.jar".
> (on CXF 2.0.2 and CXF 2.0.3)
>
>
>
> chengas123 <[EMAIL PROTECTED]> wrote:
>
> I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
> name stax-api.jar in the lib directory.
>
>
>
> YI (William) ZHU wrote:
>>
>> stax-api jar file is in \{CXF-home}\lib
>>
>> unpackage it, you will find the javax.xml.namespace.QName class.
>>
>> delete it, and re-package the file.
>>
>> try it.
>>
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213728.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
actually, it's "stax-api-1.0.1.jar".
(on CXF 2.0.2 and CXF 2.0.3)
chengas123 <[EMAIL PROTECTED]> wrote:
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
YI (William) ZHU wrote:
>
> stax-api jar file is in \{CXF-home}\lib
>
> unpackage it, you will find the javax.xml.namespace.QName class.
>
> delete it, and re-package the file.
>
> try it.
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213356.html
Sent from the cxf-user mailing list archive at Nabble.com.
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: CXF on WebLogic 9.2
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
YI (William) ZHU wrote:
>
> stax-api jar file is in \{CXF-home}\lib
>
> unpackage it, you will find the javax.xml.namespace.QName class.
>
> delete it, and re-package the file.
>
> try it.
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213356.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
stax-api jar file is in \{CXF-home}\lib
unpackage it, you will find the javax.xml.namespace.QName class.
delete it, and re-package the file.
try it.
chengas123 wrote:
>
> Hi,
> I was getting a "java.lang.NoSuchMethodError:
> javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2,
> but seemed to have solved it by following a post
> (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding
> -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to
> my WebLogic startup.
> However, I'm now getting:
> java.lang.RuntimeException: [was class java.net.ConnectException] Tried
> all: '1' addresses, but could not connect over HTTP to server:
> 'java.sun.com', port: '80'
> My only guess is it's trying to validate a DTD or something and is being
> blocked by our corporate firewall. I have no idea how to tell weblogic
> about our proxy. Configuring the proxy would be a good short-term
> solution since it would allow development to move forward. However,
> ultimately I'm probably going to need another solution since I'm not sure
> this would fly in our production environment.
>
> Thanks,
> Ben
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213281.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
scriptor$MyWebAppDescriptor.createXMLStreamReader(WebAppDescriptor.java:243) at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:369) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729) at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:778) ... 19 more > YI (William) ZHU wrote: > > How about you put the jar file "xml-resolver-1.2.jar" in your webLogic > classpath? > (keep this > -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory > setting) > > Or make sure CXF's jars in your classpath. > > I agree that "Configuring the proxy" is not a good solution. > > Hope this can help. > > Yi Zhu > > > > chengas123 wrote: >> >> Hi, >> I was getting a "java.lang.NoSuchMethodError: >> javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2, >> but seemed to have solved it by following a post >> (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding >> -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to >> my WebLogic startup. >> However, I'm now getting: >> java.lang.RuntimeException: [was class java.net.ConnectException] Tried >> all: '1' addresses, but could not connect over HTTP to server: >> 'java.sun.com', port: '80' >> My only guess is it's trying to validate a DTD or something and is being >> blocked by our corporate firewall. I have no idea how to tell weblogic >> about our proxy. Configuring the proxy would be a good short-term >> solution since it would allow development to move forward. However, >> ultimately I'm probably going to need another solution since I'm not sure >> this would fly in our production environment. >> >> Thanks, >> Ben >> >> > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15212932.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
How about you put the jar file "xml-resolver-1.2.jar" in your webLogic classpath? (keep this -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory setting) Or make sure CXF's jars in your classpath. I agree that "Configuring the proxy" is not a good solution. Hope this can help. Yi Zhu chengas123 wrote: > > Hi, > I was getting a "java.lang.NoSuchMethodError: > javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2, > but seemed to have solved it by following a post > (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding > -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to > my WebLogic startup. > However, I'm now getting: > java.lang.RuntimeException: [was class java.net.ConnectException] Tried > all: '1' addresses, but could not connect over HTTP to server: > 'java.sun.com', port: '80' > My only guess is it's trying to validate a DTD or something and is being > blocked by our corporate firewall. I have no idea how to tell weblogic > about our proxy. Configuring the proxy would be a good short-term > solution since it would allow development to move forward. However, > ultimately I'm probably going to need another solution since I'm not sure > this would fly in our production environment. > > Thanks, > Ben > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15211777.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) > at > org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49) > at > weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:375) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) > at > weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:83) > at > weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1591) > at > weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2734) > at > weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:892) > at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:336) > at > weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) > at > weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) > at > weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) > at > weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) > at > weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) > at > weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) > at > weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) > at > weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) > at > weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26) > at > weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641) > at > weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) > at > weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229) > at > weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154) > at > weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at > weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181) > at > weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352) > at > weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52) > at > weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186) > at > weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at > weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) > at > weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at > weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at > weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173) > at > weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) > at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) > > > > > chengas123 wrote: >> >> I was getting a "java.lang.NoSuchMethodError: >> javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2 >> > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15210360.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:375) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:83) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1591) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2734) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:892) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:336) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) chengas123 wrote: > > I was getting a "java.lang.NoSuchMethodError: > javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2 > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15208547.html Sent from the cxf-user mailing list archive at Nabble.com.
CXF on WebLogic 9.2
Hi, I was getting a "java.lang.NoSuchMethodError: javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2, but seemed to have solved it by following a post (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to my WebLogic startup. However, I'm now getting: java.lang.RuntimeException: [was class java.net.ConnectException] Tried all: '1' addresses, but could not connect over HTTP to server: 'java.sun.com', port: '80' My only guess is it's trying to validate a DTD or something and is being blocked by our corporate firewall. I have no idea how to tell weblogic about our proxy. Configuring the proxy would be a good short-term solution since it would allow development to move forward. However, ultimately I'm probably going to need another solution since I'm not sure this would fly in our production environment. Thanks, Ben -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15193763.html Sent from the cxf-user mailing list archive at Nabble.com.
