[Beginners Corner] - Re: JBoss failed JNDI lookup without any error
by horunkoya
Hello there,
I am still experiencing this problem and it is now becoming a joke as I have tried everything I know. Could somebody please help as I am quickly running out of options here. the latest exception which is no different from the previous is :
| $Proxy57
| java.lang.ClassCastException: $Proxy57
| at com.janes.jf.action.LoginAction.process(LoginAction.java:52)
| at com.janes.jf.action.RequestAction.execute(RequestAction.java:21)
| at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
| at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
| at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
| at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at com.janes.jf.filter.LoginFilter.doFilter(LoginFilter.java:24)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
The line of code that throws this exception is:
| InitialContext ic = new InitialContext();
| Object obj = ic.lookup("ejb/MAPDelegate");
| MAPDelegateHome mapHome = (MAPDelegateHome)obj;
|
ejb-jar.xml is as follows:
| ejb-jar>
| <enterprise-beans>
| <session>
| <description>Session Bean ( Stateful )</description>
| <display-name>MAPDelegate</display-name>
| <ejb-name>ejb/MAPDelegate</ejb-name>
| <home>com.janes.jf.ejb.MAPDelegateHome</home>
| <remote>com.janes.jf.ejb.MAPDelegate</remote>
| <local-home>com.janes.jf.ejb.MAPDelegateLocalHome</local-home>
| <local>com.janes.jf.ejb.MAPDelegateLocal</local>
| <ejb-class>com.janes.jf.ejb.MAPDelegateBean</ejb-class>
| <session-type>Stateful</session-type>
| <transaction-type>Container</transaction-type>
| </session>
| </enterprise-beans>
| </ejb-jar>
|
Please HELP!!!!!.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993902#3993902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993902
19 years, 4 months
[JBossWS] - Cound Not obtain the Java Type Mapping-What is wrong where t
by pshankar
I am getting the Java type mapping error even after packaging/placing the mapping class within the WAR/Server
Where exactly should the file go?
The class is built within war and also the descriptor files are there.
org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://DefaultNamespace}ArrayOf_tns2_anyType at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataR
|
My jaxrpc-mapping.xml read below
<?xml version="1.0" encoding="UTF-8"?>
| <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
| http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
| version="1.1">
| <package-mapping>
| <package-type></package-type>
| <namespaceURI>http://MySpringService</namespaceURI>
| </package-mapping>
| <service-interface-mapping>
| <service-interface>MySpringService.MySpringServiceService</service-interface>
| <wsdl-service-name xmlns:serviceNS='http://DefaultNamespace'>serviceNS:MySpringServiceService</wsdl-service-name>
| <port-mapping>
| <port-name>MySpringService</port-name>
| <java-port-name>MySpringService</java-port-name>
| </port-mapping>
| </service-interface-mapping>
| <service-endpoint-interface-mapping>
| <service-endpoint-interface>MySpringService.MySpringService</service-endpoint-interface>
| <wsdl-port-type xmlns:portTypeNS='http://DefaultNamespace'>portTypeNS:MySpringService</wsdl-port-type>
| <wsdl-binding xmlns:bindingNS='http://DefaultNamespace'>bindingNS:MySpringServiceSoapBinding</wsdl-binding>
| <service-endpoint-method-mapping>
| <java-method-name>listConfigurationName</java-method-name>
| <wsdl-operation>listConfigurationName</wsdl-operation>
| <method-param-parts-mapping>
| <param-position>0</param-position>
| <param-type>java.lang.String</param-type>
| <wsdl-message-mapping>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:listConfigurationNameRequest</wsdl-message>
| <wsdl-message-part-name>in0</wsdl-message-part-name>
| <parameter-mode>IN</parameter-mode>
| </wsdl-message-mapping>
| </method-param-parts-mapping>
| <wsdl-return-value-mapping>
| <method-return-value>DefaultNamespace.ArrayOf_tns2_anyType</method-return-value>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:listConfigurationNameResponse</wsdl-message>
| <wsdl-message-part-name>listConfigurationNameReturn</wsdl-message-part-name>
| </wsdl-return-value-mapping>
| </service-endpoint-method-mapping>
| <service-endpoint-method-mapping>
| <java-method-name>getName</java-method-name>
| <wsdl-operation>getName</wsdl-operation>
| <wsdl-return-value-mapping>
| <method-return-value>java.lang.String</method-return-value>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:getNameResponse</wsdl-message>
| <wsdl-message-part-name>getNameReturn</wsdl-message-part-name>
| </wsdl-return-value-mapping>
| </service-endpoint-method-mapping>
| <service-endpoint-method-mapping>
| <java-method-name>setName</java-method-name>
| <wsdl-operation>setName</wsdl-operation>
| <method-param-parts-mapping>
| <param-position>0</param-position>
| <param-type>java.lang.String</param-type>
| <wsdl-message-mapping>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:setNameRequest</wsdl-message>
| <wsdl-message-part-name>in0</wsdl-message-part-name>
| <parameter-mode>IN</parameter-mode>
| </wsdl-message-mapping>
| </method-param-parts-mapping>
| </service-endpoint-method-mapping>
| </service-endpoint-interface-mapping>
| </java-wsdl-mapping>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993900#3993900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993900
19 years, 4 months
[JBoss Seam] - Seam & Maven2
by mzeijen
I think it would be great if there was some support for Maven2 together with Seam. I am not the only one that would want that because there where already several topics on this subject.
Here is a ref to one of them: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92547
The problem that is Gavin doesn't work with Maven2 (yet ;) ) and that is why there isn't any support for it. He said:
anonymous wrote : If you guys want solid Maven support, then one of you is going to have to step up and work on it, and promise to maintain it
I am willing to be that Guy.
Here is a list with things that I want do:
- Try to get the Seam libraries into the mayor Maven2 repositories and maintain them.
- Try to get as many of the dependency libraries, that aren't in the mayor Maven2 repositories, into those repositories.
- Try to get someone to maintain those dependency libraries in the mayor Maven2 repositories.
- Create and maintain archetypes for seam (already working on that)
- Create patches for the generating tool so that it can create Maven2 enabled projects.
- Write wiki information about Seam and Maven2.
- Give forum support on Maven2 problems with Seam
At this moment the biggest problem are the dependencies. Several aren't to be found in the major repositories and from others I need to know the version. I also need to unravel the thirdparty-all.jar into separate libraries, from which I then need to know the version.
To get this party rolling I need some active support from Gavin (and JBoss). He knows probably everything about the libraries that are used.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993895#3993895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993895
19 years, 4 months