[Installation, Configuration & Deployment] - Classloading: There are JARs inside my EAR, and my brain hur
by mikeattibco
I have an EAR with JARs inside it. The MET-INF/MANIFEST.MF points to these jars:
Class-Path: ./first.jar ./second.jar
...implying that the appserver should look in the root of the EAR to find these files. This issue has received some attention on these boards, solved by:
| <attribute name="Java2ClassLoadingCompliance">true</attribute>
| <attribute name="UseJBossWebLoader">true</attribute>
|
However, this doesn't completely solve the problem. Although the EAR does deploy and run, I still get lots of exceptions at some point in the process which complain that they cannot find /jboss/deploy/first.jar, etc. Also, when the "Init J@ee application" line appears as it opens the EAR, the JAR files are still listed as non-deployable, although in 3.2.6 they are consiedered deployable (don't know if that matters, but I think that if they were considered deployable, JBoss would never go looking for /jboss/deploy/first.jar.
What else do I need to do here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957493#3957493
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957493
20 years, 2 months
[JBoss jBPM] - Re: Web console failing
by kukeltje
Wow, lots of info, so as promised a detailed answer.
Indeed if you just deploy the app yourself, there is no userdatabase. It is empty. The dropdownlist is no real login. In 3.2 that will change and the user will be taken from the http request, so it is easier to set yourself from any mechanism.
It could be that the 500 error is cause by not logging in first. That is the (rather basic and not fault tolerant) behaviour of the 3.1 webapp (there is a jira issue for this, but since 3.2 will change have a much more serious and robust webapp, I think it will not be fixed for 3.1.
Regarding the population of the db, there are some ant tasks (at least with 3.2) that you can call and pass some additional parameters to have the xml config that comes with 3.2 to generate sql insert statements. There also is a jira issue to combine the usermanagement of the jboss portal and create some generic mechanism/app to do this. otoh, the identity service should become more pluggable so you can drop in your own mechanism. Do not expect that for 3.2 however.
(to be honest, I added my own users by dusting of my sql knowledge and inserted some manually for demo purposes ;-))
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957490#3957490
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957490
20 years, 2 months
[JBoss jBPM] - Re: Web console failing
by brado
This appears to be caused by 3 bugs in the header2.jsp of the 3.1.1 starter's kit. The navigation links are as follows:
| <a href="home.jsp">...</a>
| <a href="admin.jsp">...</a>
| <a href="monitor.jsp">...</a>
|
The problem is that web.xml specifies the following server mapping for the JSF Servlet:
| <servlet-mapping>
| <servlet-name>FacesServlet</servlet-name>
| <url-pattern>/faces/*</url-pattern>
| </servlet-mapping>
|
which means that the FacesServlet won't pick up the hrefs listed. Here's how the code should read, and after I made these changes, they worked:
| <a href="faces/home.jsp">...</a>
| <a href="faces/admin.jsp">...</a>
| <a href="faces/monitor.jsp">...</a>
|
If there's other information known about this problem, I'd be happy to know.
Thanks,
Brad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957489#3957489
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957489
20 years, 2 months