January 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - SOAP request missing namespace

by yperey

Hello, I've followed step by step the http://wiki.jboss.org/wiki/Wiki.jsp?page=WS4EEDOCClientStepByStep to deploy a web service client on JBoss 4.0.2 using JWSDP 1.6. The problem is that in the SOAP request I send to the server there are attributes of a complex type with missing namespace: <?xml version="1.0" encoding="UTF-8"?> | <soapenv:Envelope | xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Header> | <jbws:username soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">root</jbws:username> | <jbws:password soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">cm9vdDE=</jbws:password> | </soapenv:Header> | <soapenv:Body> | <ns1:LHUB_PutIntoTargetSystemsProcessRequest | xmlns:ns1="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems"> | <source>1</source> | <targets>0</targets> | </ns1:LHUB_PutIntoTargetSystemsProcessRequest> | </soapenv:Body> | </soapenv:Envelope> like for source and targets event if in the wsdl it is specified attributeFormDefault="qualified" and elementFormDefault="qualidied" as you can see: | ... | <types> | <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems" | xmlns="http://www.w3.org/2001/XMLSchema"> | <element name="LHUB_PutIntoTargetSystemsProcessRequest"> | <complexType> | <sequence> | <element name="source" type="string"/> | <element name="targets" type="string"/> | </sequence> | </complexType> | </element> | <element name="LHUB_PutIntoTargetSystemsProcessResponse"> | <complexType> | <sequence> | <element name="error" type="string"/> | <element name="description" type="string"/> | <element name="details" type="string"/> | </sequence> | </complexType> | </element> | </schema> | </types> | ... | here is my wscompile line: anonymous wrote : wscompile -gen:client -f:documentliteral -f:wsi -mapping jaxrpc-mapping-client.xml -keep config-client.xml Here is the correct SOAP envelope that I'm supposed to have: <?xml version="1.0" encoding="UTF-8"?> | <soapenv:Envelope | xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Header> | <jbws:username soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">root</jbws:username> | <jbws:password soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">cm9vdDE=</jbws:password> | </soapenv:Header> | <soapenv:Body> | <ns1:LHUB_PutIntoTargetSystemsProcessRequest | xmlns:ns1="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems"> | <ns1:source>1</ns1:source> | <ns1:targets>0</ns1:targets> | </ns1:LHUB_PutIntoTargetSystemsProcessRequest> | </soapenv:Body> | </soapenv:Envelope> Any idea ? Yann. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008779#4008779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008779

17 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Mixing schemas WildcardBinding exception

by alesj

I'm using this xml: | <?xml version="1.0" encoding="UTF-8"?> | | <beans xmlns="urn:jboss:spring-beans:2.0"> | | <bean id="testBean" class="org.jboss.test.spring.support.SimpleBean"> | <property name="refBean"><ref bean="oldBean"/></property> | </bean> | | <bean xmlns="urn:jboss:bean-deployer:2.0" name="oldBean" class="org.jboss.test.spring.support.OldBean"> | <property name="javaBeanString"><value>JavaBean</value></property> | </bean> | | </beans> and I get the following exception: | org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/C:/projects/microcontainer/classes/test/spring-int/org/jboss/test/spring/test/InstantiateMixed2TestCase.xml@13,9 | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:135) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:212) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:283) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.setUp(MicrocontainerTestDelegate.java:78) | at org.jboss.test.spring.test.TempSpringMicrocontainerTestDelegate.setUp(TempSpringMicrocontainerTestDelegate.java:48) | at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:63) | at junit.extensions.TestSetup$1.protect(TestSetup.java:18) | at junit.extensions.TestSetup.run(TestSetup.java:23) | at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) | Caused by: java.lang.ClassCastException: org.jboss.xb.binding.sunday.unmarshalling.WildcardBinding | at org.jboss.xb.binding.sunday.unmarshalling.DefaultElementHandler.setParent(DefaultElementHandler.java:109) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParticle(SundayContentHandler.java:730) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:138) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:353) | at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) | at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:169) | ... 23 more When I do it the other way around - defining root element deployment as MC schema, and using Spring bean inside deployment - it works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008769#4008769 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008769

17 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Scoped beans deployment

by alesj

What's the status of being able to define in which scope you want to put / lookup your beans? E.g. 'visible' only for current deployment unit (single xml file), whole archive deployment (multiple files in .sar, ...), whole app deployment, current kernel bootstrap, cluster, ... What I want to do with OSGi integration is be able to put in current Bundle bean (under some specific name - similar to what we do with Kernel), and then later use it when wiring beans with OSGi layer. OSGi aware beans are normal beans deployed with BeanMetaDataDeployer, which is currently bound with bootstrap Kernel. There is only special schema handling + the part that is missing = currently deployed beans being aware of their underlying Bundle. How do I get the currently deployed beans be aware of their Bundle (which is a part of DeploymentUnit attachments). Any elegant way or a horrible ThreadLocal? ;-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008731#4008731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008731

17 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Issues with passivation of nested SFSBs

by wolfc

Okay, but introduce a new object XPCHolder or something to hold the administration of XPC users. Then there is no "master", parent or child. Just an XPC holder and users. That's more easily to understand (at least to my brain :-) ). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008722#4008722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008722

17 years, 11 months

1
0
0 / 0

[Javassist development Forum] - How to use Log4j in Struts

by ashish.mishra16

I m facing problem in using log4j in my struts application. My director strutcture is SRC,Web-Root WEB-INF lib,classes,web.xml,struts-config.xml In classes i have class files, config.properties for log4j, ApplicationResources.properties. Now i m not able to read the config.properties file. in any ways, the config.properties file is like this: log4j.rootLogger=DEBUG, A1 log4j.appender.A1=org.apache.log4j.ConsoleAppender log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n. I m using the following method to read the it in LoginAction.java: static Logger logger = Logger.getLogger(LoginAction.class.getName()); try { Properties logProperties = new Properties(); logProperties.load(new FileInputStream("config.properties")); PropertyConfigurator.configure(logProperties); } catch (Exception e) { throw new RuntimeException("Enable to Load Logging Properties File"); } Please tell me how to read the config.properties file. Or what is d other ways to handle Log4J. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008650#4008650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008650

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JGroups configuration for clustering testing

by ovidiu.feodorov＠jboss.com

Clebert, What JGroups stack configurations are we using now for clustering testing? The ones from src/etc/server/default/deploy/clustered-mysql-persistence-service.xml or those from src/etc/server/default/deploy/multiplexer-stacks.xml? Thanks Ovidiu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008646#4008646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008646

17 years, 11 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: XAExpectionUnitTestCase Failures/JBossTS/JBoss 4.2

by weston.price＠jboss.com

Something about this still just doesn't seem right. I am attempting to get with the JBossTS team to discuss what, if anything, we should be doing differently. I am not sure how catching, logging (basically masking) the underlying XA exception is going to help matters. While the JcaXAResourceWrapper could do some trickery to make this problem 'go away' I am not sure this is the right approach. In the tests we are simply reporting what could very well be a real XA exception. If this is causing an IllegalStateException in JBossTS, I would really like to know what and what the *right* way to to fix this is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008641#4008641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008641

17 years, 11 months

1
0
0 / 0

[Design of JCA on JBoss] - JBAS-1434 Part 2

by weston.price＠jboss.com

Quick check of moving over to the JCA/JMS adapter. Change in standardjboss.xml is required. The easiest thing is simply to switch the default container configuration from | | <container-name>Standard Message Driven Bean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>message-driven-bean</invoker-proxy-binding-name> | to | <container-name>Standard Message Driven Bean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>jms-message-inflow-driven-bean</invoker-proxy-binding-name> | Also, as we all know, the old JMSContainerInvoker allowed for creating destinations when a listener was being deployed without one. EJB3 carries this tradition over for EJB3, but for EJB 2.x the JMS/JCA adapter will not. There are a few reasons for this a) It's not portable and JBoss specific b) While we could create a temporary destination using the JMS API, I don't think it is a good idea to carry this 'convenience' forward as it simply masks underlying configuration issues on the client. In sum, you want to use JMS/JCA inflow, create your destination. Further, I am not sure how much from the JMS API without having to fall back on JBoss specific constructs to create the destination. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008640#4008640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008640

17 years, 11 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: could not find agent library on the library path or in t

by clebert.suconic＠jboss.com

the other possibility would be... You are using Linux... and you don't have the dependency (such as the libgc) installed. You could compile the library yourself in your system... look at the manual on how to compile the libraries. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008608#4008608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008608

17 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bug in Sun compiler?

by scott.stark＠jboss.org

Its a known bug for inner classes that has been open for some time: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5087240 although, even if I pull the enum into a separate class I still see the same problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008601#4008601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008601

17 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007