[JBossWS] - JAX-WS from Sessions Bean fails due to missing org/jboss/log
by ejb3workshop
I have a standalone client jar which using JAX-WS in JDK1.6 is able to consume a webservice. I would like to invoke the webservice from a session bean, so I added the webservice client JAR to my ear file and updated the application.xml file.
The problem is that when I try to invoce the client from within JBoss I get the following error.
A search in the forums and the web makes suggestions to include the jboss-common-clients.jar in the classpath. I tried added this jar to the /server/default/lib folder as well as include it within the EAR / application.xml, of which neiter worked.
If JAX-WS client is not supported what other libraries can I use to consume a web service from a Session Bean.
anonymous wrote :
| java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47)
| at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64)
| at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:120)
| at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116)
| at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254)
| at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1550)
| at org.jboss.remoting.Client.invoke(Client.java:530)
| at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:171)
| at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:322)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:230)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075829#4075829
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075829
18Â years, 10Â months
[JBoss Seam] - Starting up Asynchronous Method at startup
by damatrix
Hi,
I've been trying to get an asynchronous process to run immediately after startup of the application to automatically send email notifications. On a previous post someone recommended annotating an APPLICATION scope component method with @Observer("org.jboss.seam.postInitialize").
However i find that the method is still not called after startup. Am i missing something. Below is the Applicaition Scope component and the component with the asynchronous method.
| @Scope(ScopeType.APPLICATION)
| @Name("tradewindsMonitor")
| public class TimerMonitor implements java.io.Serializable{
|
| @In(create=true)
| TradewindsMonitorBean timerHandler;
|
| @Observer("org.jboss.seam.postInitialize")
| public void startTimer(){
| Calendar calendar = Calendar.getInstance();
| calendar.add(Calendar.MINUTE,2);
| timerHandler.sendNotifications(calendar.getTime(),new Long(86400000));
| }
|
| @Name("timerHandler")
| public class TradewindsMonitorBean implements java.io.Serializable{
|
| @In(create=true)
| private Timer timer;
|
| @In(create = true)
| private MailRenderer mailRenderer;
| @In
| private EntityManager entityManager;
|
| @Asynchronous
| public Timer sendNotifications(@Expiration java.util.Date date, @IntervalDuration Long duration) {
| ...
| return timer;
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075823#4075823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075823
18Â years, 10Â months
[JBoss Seam] - NPE when rendering PDF
by damatrix
Hi,
I've just upgraded to Seam 2.0.Beta1 and JBoss 4.2.1.GA. However i realise that all my pdf facelets now throw a null pointer exception, which wasn't the case with Seam 1.2.1.GA. The error is as ff:
| SEVERE: Error Rendering View[/infra/venuePlan.xhtml]
| java.lang.NullPointerException
| at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
| at com.lowagie.text.Image.getInstance(Image.java:460)
| at org.jboss.seam.pdf.ui.UIImage.createITextObject(UIImage.java:140)
| at org.jboss.seam.pdf.ui.ITextComponent.encodeBegin(ITextComponent.java:181)
| at org.jboss.seam.pdf.ui.ITextComponent.encode(ITextComponent.java:244)
| at org.jboss.seam.pdf.ui.ITextComponent.encodeChildren(ITextComponent.java:213)
| at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
| at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577)
| at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
| at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233)
| at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
| at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140)
| 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:619)
|
|
This is a sample facelet i've been trying to render
|
| <p:document xmlns:p="http://jboss.com/products/seam/pdf"
| xmlns:f="http://java.sun.com/jsf/core"
| xmlns:ui="http://java.sun.com/jsf/facelets" title="Floor plan -#{venue.title}">
| <p:font size="16" style="bold" ><p:paragraph spacingAfter="10" alignment="center"><p:text value="Floor plan -#{venue.title}"/></p:paragraph></p:font>
|
| <p:image alignment="center" imageData="#{venue.plan}" height="300" width="500"/>
| </p:document>
|
I've properly specified the DocumentServlet and the Seam Servlet Filter in web.xml, as well as added itext.jar and jboss-seam-pdf.jar in my WAR classpath, but to no avail. Can anyone help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075817#4075817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075817
18Â years, 10Â months
JBoss RMI
by Velidanda Srinivas
Hi,
I have an enterprise application deployed on JBoss which has to invoke Remote Method
using Java RMI.
It is working fine if I set the policy file and security manager on the command line, by
setting JAVA_OPTS in run.bat of JBoss.
But I am getting AccessControlException while trying to set policy file programmatically
by accessing the System property java.security.policy.
Does anyone had similar problem and found the resolution?
I just want to confirm,
Is it the only way to set the policy and security manager on the command line
while running under JBoss?
I am using JBoss 4.0.2 and JDK 1.5.0_06.
Thanks & Regards,
Srinivas.
________________________________________________________________________
This e-mail has been scanned for all viruses by MessageLabs.
To learn more about Singularity's business process management solutions and services please visit:
www.singularity.co.uk
www.singularity.us.com
Singularity operates globally through its offices in New York, London, Singapore, Ireland and India. Singularity Limited is incorporated in the United Kingdom with Registration Number NI 31519 and its Registered Office at 100 Patrick Street, Derry, BT48 7EL, United Kingdom.
18Â years, 10Â months