[JBoss Portal] - Re: Security constraints for portlets
by PeterJ
Did you want all four portlets on the same page or on different pages?
For different pages, set it up as follows:
Object RoleA RoleB Unchecked
| Page1 view -none- -none-
| Portlet1 -none- -none- view
| Portlet2 -none- -none- view
| Page2 -none- view -none-
| Portlet3 -none- -none- view
| Portlet4 -none- -none- view
Or you could do:
Object RoleA RoleB Unchecked
| Page1 view -none- -none-
| Portlet1 view -none- -none-
| Portlet2 view -none- -none-
| Page2 -none- view -none-
| Portlet3 -none- view -none-
| Portlet4 -none- view -none-
If you want all four portlets on the same page:
Object RoleA RoleB Unchecked
| Page1 view -none- -none-
| Portlet1 view -none- -none-
| Portlet2 view -none- -none-
| Portlet3 -none- view -none-
| Portlet4 -none- view -none-
And as Julien mentioned, the security on the portlets is done at the instance level, not on the window level.
Finally, in jboss-portal.sar/conf/config.xml, change the value of the core.render.window_access_denied entry to 'hide':
<entry key="core.render.window_access_denied">hide</entry>
Without this final change, in the single page scenario the users will see errors for the portlets they are not allowed to view.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974044#3974044
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974044
19 years, 7 months
[Beginners Corner] - Re: JBOSS isn't working... VERY BEGINNER
by wls
I'm new to all this as well, but seem to have had some decent luck.
The solution I took to was using NetBeans, which made it trivial to make and deploy .jsp stuff. It can send 'em to TomCat or JBoss, which I discovered were using a different ports -- so make sure you're using the right URL.
If I understand things correctly, you do not have a directory you drop JSP files into, but rather you create a WAR file (NetBeans does it for you) and move it to JBoss's server/default/deploy directory (which NetBeans also does for you).
The JBoss log files are large because they are also capturing DEBUG and INFO log items -- in other words, the system is deliberately being extremely verbose so you can see everything at a very granular level.
I believe there was a typo in the last reply, and that the file to turn this logging down a notch is log4j.xml.
But I understand your frustration, you're expecting to see a file get accessed and a 404 if it isn't there. Instead, I think it's looking inside the WAR file, and if it can't find the deployment, it just tells the browser it has no idea what you've requested. I'm not sure this appears in the log, though I suspect it does, only as some other message and not a 404. Perhaps something like no web application by that name?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974042#3974042
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974042
19 years, 7 months
[JBossWS] - Problem with XB Bindigs
by gerhardo
Hello !
I have a problem with the XB bindings. I'm using JBoss 4.0.4 GA and JBossWS 1.0.3 and manually replaced the jboss-xb-bindings.jar as described in the installation.
I generated the wsdl and other atifacts by wstools wit the following configuration:
<configuration>
| <java-wsdl>
| <service name="ShipmentService" style="document" parameter-style="bare"
| endpoint="de.emediapark.eos.ws.Shipment"/>
|
| <namespaces target-namespace="http://de.emediapark.ws/eos/shipment"
| type-namespace="http://de.emediapark.ws/eos/shipment/types"/>
|
| <mapping file="jaxrpc-mapping.xml"/>
| <webservices servlet-link="ShipmentEndpoint"/>
| </java-wsdl>
| </configuration>
|
Sending the following request to the service:
POST /eos/shipment?wsdl HTTP/1.1
| Host: EOSDBHOST:8080
| Accept-Charset: UTF-8, UTF-16;q=0.8, iso-8859-1;q=0.8
| Accept-Encoding: deflate, gzip
| Content-Type: text/xml; charset=UTF-8
| SOAPAction: ""
| User-Agent: PocketSOAP/1.5.4/PocketHTTP/1.2.7
| Content-Length: 887
|
| <S:Envelope
| xmlns:a="http://de.emediapark.ws/eos/shipment/types"
| xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
| xmlns:XS="http://www.w3.org/2001/XMLSchema"
| xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"><S:Body><a:storeAdress><city XI:type="XS:string">Hamburg</city><client XI:type="XS:int">4</client><countryId XI:type="XS:int">0</countryId><countrySign XI:type="XS:string">D</countrySign><kind XI:type="XS:int">0</kind><name1 XI:type="XS:string">XY</name1><name2 XI:type="XS:string"></name2><name3 XI:type="XS:string"></name3><number XI:type="XS:int">3123484</number><postalStreetCode XI:type="XS:int">0</postalStreetCode><status XI:type="XS:int">0</status><street XI:type="XS:string">Fuhlsbuettlerstrasse 223</street><type XI:type="XS:int">0</type><valid XI:type="XS:int">0</valid><zip XI:type="XS:string">22307</zip></a:storeAdress></S:Body></S:Envelope>
I'm getting the following error from the JBossWS service:
HTTP/1.1 500 Internal Server Error
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)/Tomcat-5.5
| Set-Cookie: JSESSIONID=DD7CF76F0B97BDA29459C7EE2D724F39; Path=/
| Content-Type: text/xml;charset=UTF-8
| Transfer-Encoding: chunked
| Date: Mon, 25 Sep 2006 21:45:04 GMT
| Connection: close
|
| 7b
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><env:Fault><faultcode>env:Client
| c
| </faultcode>
| fe
| <faultstring>org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: The prefix "XI" for attribute "XI:type" associated with an element type "city" is not bound. @ *unknown*[1,95]
| e
| </faultstring>
| c
| </env:Fault>
| 1a
| </env:Body></env:Envelope>
| 0
|
|
Can anyone give me a hint where to go from here to solve this problem.
TIA, Gerhard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974040#3974040
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974040
19 years, 7 months
[Beginners Corner] - Deploy Problem: JBoss, EJB3, NetBeans and the web.xml file s
by wls
Admittedly, I'm a beginner here, so go gentle on me.
I'm using the NetBeans 5.5 beta 2 with the JBoss 4.0.4 GA installer, which supposedly includes EJB3 stuff, from http://www.netbeans.org/products/ide/ and so far things had been working perfectly.
That was until I did right clicked "Enterprise Resources > Call Enterprise Bean" from the pop up window in an servlet of an Enterprise Application and referenced a working bean.
Now my question isn't one of using the NetBeans environment, but rather that after it generated the code, which did compile perfectly, I started getting errors that my bean could not be deployed to JBoss due to an error in the web.xml file.
Looking in the web.xml file, which I assume is some kind of deployment file (hey, I said I was new to J2EE), there is a new element in the xml called <ejb-local-ref>. And it's on this xml section that JBoss seems to be choking.
Inside http://www.netbeans.org/kb/55/ejb30-jboss.html, it suggests that JBoss automatically adds session beans to the JNDI namesspace, and thus one should remove the ejb-local-ref from the web.xml file by going to the WEB-INF folder inside the Web Pages node.
Doing so didn't help, and instead created a new problem with the bean not being bound to a name.
>From what I can tell from various Google searches and reading different documents, it seems that not only is NetBeans is generating Java EE 5 code, but deployment notation as well. And, while JBoss is using EJB3, it does not recognize the newer xml syntax.
My problem is fairly obvious, and I'm drowning in a sea of documentation that's in one world or the other, but not bridging the gap between them.
NetBeans is producing this:
javax.naming.Context c = new javax.naming.InitialContext();
| return (MyBeanLocal) c.lookup("java:comp/env/ejb/MyBean");
Which exceptions with a
anonymous wrote : javax.naming.NameNotFoundException: ejb not bound
My guess is that I need something inside the web.xml file to do that binding, but I'm just not sure what. I'm also pondering in that there seems to be a jboss.xml file that I could create, but I don't know if this is on the right track or not, either.
Would someone mind pointing me in the right direction?
Many thanks,
-Walt Stoneburner, wls(a)wwco.com
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974036#3974036
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974036
19 years, 7 months