[JBossWS] - java.lang.UnsupportedOperationException: setProperty must be
by ohummel
Installed the latest WS support on Jboss 4.0.4GA and everything seemed to work until I actually tried to access the WS. I paste the exception that occurred below. I believe it might be a classpath issue, but I have no idea where it comes from...
Any help greatly appreciated. TIA!
16:20:03,221 ERROR [SOAPFaultExceptionHelper] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden in subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:356)
at org.jboss.ws.soap.SOAPMessageImpl.(SOAPMessageImpl.java:65)
at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:209)
at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:142)
at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:190)
at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
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 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.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:495)
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)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972333#3972333
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972333
19 years, 7 months
[JBoss Seam] - Re: Glaring Security Hole?
by bfagan
I'm not stating that the data is insecure, but that the model is.
A company's data model can constitute proprietary information or trade secret.
What I'm blatantly saying is that as much as sessions beans require @WebRemote to have their methods exposed under Seam Remoting, entity beans in the same distribution should be afforded the same level of preventative measure.
Instantiating a *new* object tells me plenty about how the database is modeled and in some cases can reveal proprietary information or trade secret.
A developer may wish to prevent various entity beans from having their model exposed. I'll go a step further and say that entity beans should not have their model exposed by default, but that they should be configured with @WebRemote as well. It fosters uniformity and errs on the side of security.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972331#3972331
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972331
19 years, 7 months
[JBoss Portal] - Changing portal-server.war configurations
by ovidiucn
Hello!
I'm trying to migrate an existing application to JBoss Portal. I need some advice regarding the resources located in the portal-server.war application.
To successfully configure the authentication module i have to modify the 'portal-server.war' module (security domain, login/error jsp(s)).
So, my question: is there any possible way to leave the portal-server.war module as it is (i.e. override somehow the configurations found in this module by deploying a custom module along with jboss-portal.sar application - as we can do for themes, layouts) - from my understanding until now... this cannot be done.
Or, do i have to import/modify and build/package/redeploy each time? This question stands also if i'm going to change another jboss portal files/modules this way.
Are there any 'best practices' more generally how to we dynamically modify deployment descriptors (web.xml, ejb-jar.xml) embedded in deployable archives (war, jar, rar, sar, ear) during compile/deployment?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972329#3972329
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972329
19 years, 7 months