[JBoss Portal] - Re: WSRP consumer
by chris.laprun＠jboss.com
"jboss_ms" wrote : I am using jboss portal 2.6.
Note that we don't currently support 2.6. That said...
"jboss_ms" wrote :
| 1)if I make a portlet as a remotable( portlet.xml) , does it become a WSRP Producer. So does it implement the 4 interfaces and we need not write any code to make it a WSRP producer. I am not able to understand how jboss portal supports WSRP from the documentation provided.
|
Making a portlet remotable makes it available for remote publishing via Portal's WSRP producer. If your portlet is correctly deployed and made remotable, it should appear in the "self" portlet provider in the admin interface. This means that it is now available to be consumed by remote consumers that connect to Portal's producer. "self" is a WSRP consumer connected to Portal's WSRP producer so you should be able to see your portlet there. If not, there is a problem. Look at the doc for more details. However, it does seem like you might be misunderstanding how WSRP works... I suggest reading the WSRP primer at http://www.oasis-open.org/committees/download.php/21178/wsrp-primer-1.0.html if you haven't already done so.
"jboss_ms" wrote :
| 2) Is it only the admin can create an instance and become a WSRP consumer? What is the role of other users with respect to WSRP....
|
Just like only admins can create and deploy portlets, the same holds true for WSRP portlets. Users can use WSRP portlets just like regular portlets.
Hope this helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992022#3992022
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992022
19 years, 4 months
[Security & JAAS/JBoss] - HowTo Link LDAP-Group with Roles?
by Zwitsch
Hi,
I spend nearly the whole day, reading tutorials, forums and books... I finally got my authentication working but am stuck with the authorization.
I can login, but am getting - reasonably - a 403 error.
I'm originally coming from WebSphere where the EAR links the LDAP-Groups with the JAAS roles with a ibm-application-bnd.xmi.
But how can I make it on Jboss???
I set up login-config.xml, application.xml (ear), jboss-web.xml and web.xml to make the authentication happen. Any other file to edit/add?
Thanks in advantage for you help!
Zwitsch
application.xml
| <display-name>
| KaskoEAR</display-name>
| <module>
| <web>
| <web-uri>Kasko.war</web-uri>
| <context-root>kasko</context-root>
| </web>
| </module>
| <security-role id="user">
| <description>User</description>
| <role-name>user</role-name>
| </security-role>
| <security-role id="poweruser">
| <description>Poweruser</description>
| <role-name>poweruser</role-name>
| </security-role>
| <security-role id="admin">
| <description>Admin User</description>
| <role-name>admin</role-name>
| </security-role>
| </application>
web.xml (extract)
!-- Security Config -->
|
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>Kasko Login</realm-name>
| </login-config>
|
| <!-- Security Contraints -->
|
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>Admin</web-resource-name>
| <url-pattern>/Start</url-pattern>
| <http-method>GET</http-method>
| <http-method>POST</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>admin</role-name>
| </auth-constraint>
| </security-constraint>
|
| <!-- Security Roles -->
|
| <security-role>
| <description>Administrator</description>
| <role-name>admin</role-name>
| </security-role>
jboss-web.xml
<jboss-web>
|
| <context-root>/kasko</context-root>
|
| <security-domain>java:/jaas/testdomain</security-domain>
|
| </jboss-web>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992020#3992020
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992020
19 years, 4 months
[JBoss Eclipse IDE (users)] - JBossIDE 2.0.0Beta2 missing JBoss Launch configuration
by kdalley
I'm trying to complete the tutorial with the latest jbosside bundle and I'm on step 10. The step says to open the Debug... configurations dialog and to select or create a new JBoss server configuration. The problem is that there are no JBoss server definitions that I can select to create a new configuration. All that I have are: Apache Tomcat, Eclipse Application, Equinox OSGi Framework, Generic Server, Generic Server (External Launch), Java Applet, Java Application, JBoss AOP Application, JUnit, JUnit Plug-in Test, Remote Java Application and SWT Application. That's it. Is there something that I'm missing? How do I get the JBoss 2.4.x, JBoss 3.0.x, JBoss 3.2.x, JBoss 4.0.x and JBoss Remote configuration definitions in my ide that are shown in the tutorial and are missing?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992019#3992019
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992019
19 years, 4 months
[JBossWS] - Wrong package name for nested object properties
by oglueck
Happens in
JBoss AS 4.0.4 with WS 1.0.3, 1.0.3SP1,
JBoss AS 4.0.5 with WS 1.0.4
I have the data model classes in ch.logobject.test.model.ws.
=== WSDL ===
Initially generated by JBossWS from the model. Later modified manually, deployed in META-INF/wsdl and referenced in the @WebService annotation.
<definitions name='testService' targetNamespace='http://i.session.test.logobject.ch/jaws' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://ws.model.test.logobject.ch/jaws' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://i.session.test.logobject.ch/jaws' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<schema elementFormDefault='qualified' targetNamespace='http://ws.model.test.logobject.ch/jaws' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:ns1='http://i.session.test.logobject.ch/jaws' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://ws.model.test.logobject.ch/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<schema elementFormDefault='qualified' targetNamespace='http://i.session.test.logobject.ch/jaws' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:ns2='http://ws.model.test.logobject.ch/jaws' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://i.session.test.logobject.ch/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
<soap:operation soapAction=''/>
<soap:body use='literal'/>
<soap:body use='literal'/>
<soap:operation soapAction=''/>
<soap:body use='literal'/>
<soap:body use='literal'/>
<soap:address location='http://127.0.0.1:8080/playground-sb/Websvc'/>
== WS interface ==
@WebService(
name="test",
wsdlLocation="META-INF/wsdl/playground.wsdl"
)
@SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
@Remote
public interface IWebsvc {
@WebMethod
String echo(String s);
@WebMethod
Response f(
@WebParam(name="a") String a,
@WebParam(name="b") int b,
@WebParam(name="d") Calendar d,
@WebParam(name="e") boolean e,
@WebParam(name="p") Person p);
}
== SOAP message (from Eclipse Webservice Explorer) ==
<?xml version="1.0" encoding="UTF-8" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:q0="http://i.session.test.logobject.ch/jaws" xmlns:q1="http://ws.model.test.logobject.ch/jaws" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<q0:f>
<q0:a>dg</q0:a>
<q0:b>345</q0:b>
<q0:d>2006-12-07T16:27:31.171Z</q0:d>
<q0:e>true</q0:e>
<q0:p>
<q1:age>345</q1:age>
<q1:name>dfdfg</q1:name>
<q1:profession>
<q1:experience>45</q1:experience>
<q1:name>dfg</q1:name>
</q1:profession>
</q0:p>
</q0:f>
</soapenv:Body>
</soapenv:Envelope>
== Exception ==
Note the wrong package name for the Profession class! The bug renders JBossWS completely unusable for more complex datamodels! Please also check what happens when the model spans several packages. I know JAWS support is not complete, but letting JBoss generate my WSDLs is not an option. They are interoperability documents after all, and changes need to be managed carefully.
org.jboss.ws.WSException: org.jboss.ws.binding.BindingException: org.jboss.ws.jbossxb.UnmarshalException: Failed to parse source: Failed to resolve class name for {http://ws.model.test.logobject.ch/jaws}profession: No ClassLoaders found for: ch.logobject.test.session.i.Profession
[exec] at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:323)
[exec] at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233)
[exec] at org.jboss.ws.binding.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:103)
[exec] at org.jboss.ws.binding.EndpointInvocation.getRequestPayload(EndpointInvocation.java:117)
[exec] at org.jboss.ws.integration.jboss.ServiceEndpointInvokerEJB3.invokeServiceEndpoint(ServiceEndpointInvokerEJB3.java:120)
[exec] at org.jboss.ws.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:151)
[exec] at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:195)
[exec] at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:373)
[exec] at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:116)
[exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
[exec] at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:77)
[exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
[exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
[exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
[exec] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
[exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
[exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
[exec] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
[exec] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
[exec] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
[exec] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
[exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
[exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
[exec] at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
[exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
[exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
[exec] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
[exec] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
[exec] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
[exec] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
[exec] at java.lang.Thread.run(Thread.java:595)
[exec] Caused by: org.jboss.ws.binding.BindingException: org.jboss.ws.jbossxb.UnmarshalException: Failed to parse source: Failed to resolve class name for {http://ws.model.test.logobject.ch/jaws}profession: No ClassLoaders found for: ch.logobject.test.session.i.Profession
[exec] at org.jboss.ws.jbossxb.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:103)
[exec] at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:250)
[exec] ... 30 more
[exec] Caused by: org.jboss.ws.jbossxb.UnmarshalException: Failed to parse source: Failed to resolve class name for {http://ws.model.test.logobject.ch/jaws}profession: No ClassLoaders found for: ch.logobject.test.session.i.Profession
[exec] at org.jboss.ws.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:66)
[exec] at org.jboss.ws.jbossxb.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:95)
[exec] ... 31 more
[exec] Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve class name for {http://ws.model.test.logobject.ch/jaws}profession: No ClassLoaders found for: ch.logobject.test.session.i.Profession
[exec] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:178)
[exec] at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
[exec] at org.jboss.ws.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:62)
[exec] ... 32 more
[exec] Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve class name for {http://ws.model.test.logobject.ch/jaws}profession: No ClassLoaders found for: ch.logobject.test.session.i.Profession
[exec] at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.loadClassForTerm(RtElementHandler.java:1038)
[exec] at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.classForNonArrayItem(RtElementHandler.java:1367)
[exec] at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.startElement(RtElementHandler.java:693)
[exec] at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.startParticle(RtElementHandler.java:89)
[exec] at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:504)
[exec] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:323)
[exec] at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
[exec] at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
[exec] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
[exec] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
[exec] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
[exec] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
[exec] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
[exec] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
[exec] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:174)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992012#3992012
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992012
19 years, 4 months