]
Rob Stryker commented on JBIDE-1343:
------------------------------------
Samuel:
With the jbosstoolsTemp folder created, the publish would go through without error. This
is consistant with no message in the event log (a successful deploy doesn't preach its
successes, only whine about errors. This could perhaps be improved in the future to show a
clean success).
The ultimate question is: Did the application deploy 100% correctly?
Seam Project won't run out of the box
-------------------------------------
Key: JBIDE-1343
URL:
http://jira.jboss.com/jira/browse/JBIDE-1343
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.0.0.CR1
Reporter: Samuel Mendenhall
Assigned To: Rob Stryker
Priority: Blocker
Fix For: 2.0.0.GA
Attachments: jbosstools-diagnostics-20071120094034.zip, rhdsseamprob.png,
rhdsseamprob2.png
I just installed RHDS RC1, right click New -> Seam Web Project input the name, keep
all defaults (ear or war, doesn't matter) finish let it deploy and I get a simple 404
when my project loads, because it really isn't deployed by JBoss.
So, it looks like creating a simple Seam project, both Seam 1.2 AP and Seam2 either ear
or war is foobar with RC1?
The war dir structure created in my project looks like:
SeamSecurityProj.war/
|-- META-INF
|-- WEB-INF
| |-- classes
| | `-- org
| | `-- domain
| | `-- SeamSecurityProj
| | `-- session
| `-- lib
|-- img
|-- layout
`-- stylesheet
Which obviously is a problem, it should have a lot more files than this, am I missing
some flag somewhere?
Deploying looks like so:
19:11:13,932 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=SeamSecurityProjDatasource' to JNDI name
'java:SeamSecurityProjDatasource'
19:11:13,941 INFO [TomcatDeployer] deploy, ctxPath=/SeamSecurityProj,
warUrl=.../deploy/SeamSecurityProj.war/
19:11:14,088 WARN [config] Unable to process deployment descriptor for context
'/SeamSecurityProj'
no suprise there since no files are in the war, only the directory structure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: