[JBoss Tools (users)] - Re: WTP2.0.1, JBossAS-Tools-1.0.0.beta4 not publishing corre
by dlmiles
Hi Max thanks for the reply.
Okay this is what I can tell you about things:
I have an "EAR Project" called "EAREclipseManager", this has 2 artifacts added to it. These are 1 x "J2EE Utility project" called "TheLibrary" and 1 x "EJB Project" called "TheEJB".
If I do a project properties on the "EAR Project" under "J2EE Dependancies" I has a tick for both of the other two projects set. The EAR Project has the Project Facet "EAR" set to "5.0", Project References also has a tick for both of the other two projects set, Seam Support is disabled (no tick in box), Targetted Runtime is : JBoss AS 4.2.
Is is the encapsulating EAR project I am trying to publish. I don't think I need to do anything special with the project settings of the 2 contributing projects do I ?
The deployment appears to be attempted in:
/opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheLibrary.jar
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/META-INF/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/META-INF/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/foobar/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/foobar/eclipse/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/foobar/eclipse/ejb/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/foobar/eclipse/ejb/manager/
| /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/TheEJB.jar/my/foobar/eclipse/ejb/manager/test/
|
Hmm... when I run a "clean" function from the server tooling with the WTP provider driver I get an error:
[jar] Building jar: $HOME/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/EAREclipseManager.ear
| [move] Moving 1 file to /opt/jboss-4.2.1.GA/server/default/deploy
|
| BUILD FAILED
| /opt/eclipse/plugins/org.eclipse.jst.server.generic.jboss_1.5.105.v200709061325/buildfiles/jboss323.xml:33: Failed to copy $HOME/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/EAREclipseManager.ear to /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear due to /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear (Is a directory)
Is it possible to confirm 2 things:
* Which method of deployment does JBossTool-AS use, does it create an exploded EAR ? When it created that exploded EAR does it create a directory with a ".ear" extension in the deploy directory ? Does an exploded EAR need to have a .ear extension so its treated correctly by the correct deployer ?
* Does it matter that my workspace and my JBoss runtime location are on different file system (different drives), since its not possible to rename files between my workspace and the JBoss runtime location. The IDE must perform a file copy.
* When the files are copied are they copied atomically, i.e. each file is copied into tmp/filename.tmp first, then its last modified time is fixed to whatever it needs to be, then its renamed (i.e. moved) to the deploy/whatever/filename.foo.
There are other such things which should take place when updating a working runtime but maybe more on that once I have the basic thing ticking along.
Okay I have manually cleaned the JBoss deploy directory of my project and let the WTP JBoss driver do its stuff and it create an .ear file in the correct directory and when JBoss starts it finds both application.xml and my TheEJB.jar implementation.
I cleaned things again and tried with the JBossTool-AS driver and it created a directory with .ear extension, the tree is just like I put in the CODE block above, with AREclipseManager.ear/TheLibrary.jar being the only file and the application.xml and the .class files are all missing. So the problem for me appears to be with the JBossTool-AS driver (which is my preferred choice).
Would there be any call to allow JBoss to take a command line property to configure a 2nd and alternative deployment directory ? The purpose of this would be to allow for a Tomcat like situation where the workspace area could be used for the deployment, when you just alter the driver to contribute the property to the launch configuration when it sets things up. Okay it would not be 100% compatible with tomcat since the work, tmp, log, etc.. directories would also need to be picked up based on the alternative path too. Just a thought, since it would seem difficult for "clean" to mean clean if the deploy directory was not empty to start with.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092549#4092549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092549
18Â years, 7Â months
[JBoss Seam] - Re: 2.0.0.CR2 Seam-gen Error
by atarbes
I had the same problem. Something changed in hibernate-tools.jar
$ jar tvf ./seam-gen/lib/hibernate-tools.jar | grep ostgr
| $ jar tvf ../seam.old/seam-gen/lib/hibernate-tools.jar | grep ostgr
| 678 Thu Nov 09 12:47:22 PST 2006 org/hibernate/cfg/reveng/dialect/PostgressMetaDataDialect.class
|
In
| ../seam/examples/wiki/lib/hibernate-tools.jar
| 678 Thu Nov 09 12:47:22 PST 2006 org/hibernate/cfg/reveng/dialect/PostgressMetaDataDialect.class
|
PostgressMetaDataDialect is included but I get errors when running seam-gen after overriting :seam-gen/lib/hibernate-tools.jar with examples/wiki/lib/hibernate-tools.jar:
| $ bash seam generate-entities
| ...
| [hibernate] Oct 8, 2007 5:33:10 AM org.hibernate.connection.DriverManagerConnectionProvider close
| [hibernate] INFO: cleaning up connection pool: jdbc:postgresql:cpdb
| [hibernate] An exception occurred while running exporter #2:hbm2java (Generates a set of .java files)
| [hibernate] To get the full stack trace run ant with -verbose
| [hibernate] java.lang.NullPointerException
|
| BUILD FAILED
The stack trace was
| java.lang.NullPointerException
| at org.hibernate.cfg.reveng.dialect.PostgressMetaDataDialect.needQuote(PostgressMetaDataDialect.java:7)
| at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:151)
| at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
| at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:453)
| at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
|
Could anyone comment further on what happened in hibername-tools.org and how to fix this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092548#4092548
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092548
18Â years, 7Â months
[JBoss Seam] - Seam and custom JAAS problem
by mindgame
Dear all,
I have a problem (2 days old and counting...) with Seam and custom JAAS. I have written a custom JAAS login module to handle user login activity. The module is declare in component.xml,
<security:identity jaas-config-name="jaasLogin" />
A simple login page is used to obtain username and password as shown in the Seam references in Chapter 13,
| <div>
| <h:outputLabel for="name" value="Username"/>
| <h:inputText id="name" value="#{identity.username}"/>
| </div>
| <div>
| <h:outputLabel for="password" value="Password"/>
| <h:inputSecret id="password" value="#{identity.password}"/>
| </div>
| <div>
| <h:commandButton value="Login" action="#{identity.login}"/>
| </div>
|
With the above setup, there is NO problem when the user provide the correct username and password. But the problem is when the user provide a wrong username or password, the login module get invokes twice. The custom login module throw javax.security.auth.login.FailedLoginException when the login has failed. I can understand the #{identity.login} action fire the login module the first time, but have no idea what causes the login module to fire the second time immediately after the first execution and before JSF render response phase?
In addition, when I hit refresh at the login page after a failed login attempt, the login module get call each time the refresh button is hit. Is this behavior somehow related to the conversation context with respect to the login page and/or the Identity seam component?
Does anyone have any idea and insight as what is happening behind the scene?
Many thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092542#4092542
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092542
18Â years, 7Â months
[JBoss Portal] - Re: Got it y'all. Here's a working Struts bridge example (2.
by arunprasathav
I use struts 1.2.7, and jboss-portal-2.6.2.GA.
No, error is same.
At the end of log i get the following error..
"failed to create instance TestStrutsPortletInstance of porlet
"/test.TestStrutsPortlet , because porltet /test.TestStrutsPortlet is not available."
besides the above error, i get portlet initialization exception as soon as i deployed... and after some lines i get the following error,
anonymous wrote :
| 2007-10-08 15:15:53,098 ERROR [STDERR] Caused by: java.lang.ClassCastException: org.apache.portals.bridges.struts.StrutsPortlet
| 2007-10-08 15:15:53,098 ERROR [STDERR] at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.start(PortletContainerImpl.java:231)
| 2007-10-08 15:15:53,098 ERROR [STDERR] ... 73 more
| 2007-10-08 15:15:53,098 DEBUG [org.jboss.portal.core.deployment.jboss.PortletAppDeployment] Looking for the WEB-INF path of /TestStrutsPortlet
|
| Plese help me , i am getting headache with it..I deployed all the required jar files?
|
| And i have tried to run struts-demo.war example provided in portalswap.com....even in that , i got class not found exception for JbossServletContextProvider...I dont know why it is so...!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092538#4092538
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092538
18Â years, 7Â months