BA_Service_Haus
Regular Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Problems with abstract data-type
Hi, I now have prepared a project to reproduce the problems. But I'm not able to send the project by using the Support-form. It's just not working on my side (maybe some safety restrictions, I don't know). May I send the project file to a certain eMail adress?5.1KViews0likes0CommentsRe: Better Support of XML-Data-Sources
Hi nmrao, there is a main difference between your example and mine. I want to use an node-element as "Row XPath" while you used an attribute. I try to explain it with a more realistic example. In the follwoing response I want to get all names (ueb:name) of all customers (kun:kunde). This leads to the error, I described before. Best regards4.5KViews0likes0CommentsRe: Better Support of XML-Data-Sources
Hi Rao, sorry, this doesn't work. I need to declare the namespace of "firstName" in the ColumnXPaths-Field, like : declare namespace ns2='http://test.com/names'; ns2:firstName/text() Otherwise I only get emtpy rows (btw. the count is correct). Also I wonder what the "select" button at "Column XPaths" is for, when one cannot select the required xPath. Best regard4.5KViews0likes0CommentsRe: Better Support of XML-Data-Sources
Hi Rao, the wildcard (*) is matching all namespace prefixes, isn't it. So if using it, one cannot ensure, that the correct/required namespace prefix is used. e.g. *:name is matching ns2:name and ns3:name Maybe this could be ensured by checking the schema compliance of the corresponding soap response. But this is nothing but a workaround. Anyway, if there are two nodes of the same name, which can be distinguished only by their namespace, this workaround isn't helpfull anymore. The followong example shows, what I mean. There a two name-nodes. One contains the original spelling (inlcuding mutated vowels/umlauts), the other one <ns1:person> <ns2:name>Dömme</ns2:name> <ns3:name>Doemme</ns3:name> </ns1:person> To be true, this migth be a rare scenario. But you know Murphy's law, don't you? Best regards3KViews0likes0CommentsRe: Better Support of XML-Data-Sources
Hi Rao, thanks for your help. This worked indeed. But this solution does not consider a certain namespace prefix, which may be important in some test scenarios. Also the described error still exists when using the select button. Best regards2.9KViews0likes0CommentsRe: Better Support of XML-Data-Sources
Hello nmrao, your proposal didn't work in my case. The error message still occures. I guess the problem is caused by the fact, that the selected column (xPath) has a namespace prefix different from the declared ones in "Row xpath". See my example in the other post. person (row xpath) has namespace prefix "ns1" name (column xpath) has namespace "ns2" But when selecting the column xpath, no namespace declaration is done. At least this is what I guess because of the error message. Best regards3KViews0likes0CommentsRe: soapUI ignores deletion of WSS-Configuration
Here are the requested screenshots: 1. I deleted the existing WSS-Configuration "ABC" 2. In the Auth(Basic)-Tab the Outgoing-WSS-Configuration "ABC" is still selected (was already selected before deleting it) 3. When trying to select another WSS-Configuration, "ABC" is still selectable best regards1.8KViews0likes0CommentsProblem when loading Schema in deployed Mock
Hi, when I deploy my soapUI Pro Mock to a WebLogicServer, I get the following error-log-message: 14:36:14,394 DEBUG [AbstractWsdlDefinitionLoader] Returning baseInputSource [file:/C:/Temp/swep/WSDLGenerator/src-gen/KundenVerwaltung_v_2_0.wsdl] 14:36:14,445 ERROR [SoapUI] An error occurred [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl], see error log for details <24.11.2014 14:36 Uhr MEZ> <Error> <com.eviware.soapui.mockaswar.MockAsWarServlet> <BEA-000000> <null java.lang.Exception: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.load(AbstractDefinitionContext.java:176) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.load(AbstractDefinitionContext.java:119) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.loadIfNecessary(AbstractDefinitionContext.java:95) at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.<init>(WsdlMockRunner.java:65) at com.eviware.soapui.impl.support.AbstractMockService.start(AbstractMockService.java:261) at com.eviware.soapui.impl.support.AbstractMockService.start(AbstractMockService.java:231) at com.eviware.soapui.impl.support.AbstractMockService.start(AbstractMockService.java:46) at com.eviware.soapui.mockaswar.MockAsWarServlet.init(MockAsWarServlet.java:96) at javax.servlet.GenericServlet.init(GenericServlet.java:242) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:244) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3748) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3714) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2283) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2182) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused By: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123) at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.getDocumentBuilder(WSDLReaderImpl.java:165) at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:346) at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:305) at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:289) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlInterfaceDefinition.load(WsdlInterfaceDefinition I would expect the schema files to be loaded from the soapUI Project file (which is included in the generated war-archive). But obviously there seems to be a problem. Can you please give me a hand? Best regards685Views0likes0Comments