-
1. Re: changes in the JBoss tools?
akazakov May 24, 2009 6:51 AM (in response to nitm)Did you create your seam projects by wizards? If you imported it then you have to use "Right-click on projectName-ds.xml->Make deployable" menu to deploy -ds.xml.
-
2. Re: changes in the JBoss tools?
nitm May 24, 2009 7:35 AM (in response to nitm)yes, i created the project using the wizard.. i even did that 3 times just to make sure i'm not missing something..
i will try the "Make deployable" option when i get home, though it's not something i needed to do in the past, and as for the rules files, it won't even create it so it's a bigger problem.
thanks, nitzan; -
3. Re: changes in the JBoss tools?
akazakov May 24, 2009 8:19 AM (in response to nitm)Looks like a bug. Please report it to JIRA. Don't forget to describe detailed steps to reproduce it.
-
4. Re: changes in the JBoss tools?
nitm May 24, 2009 7:41 PM (in response to nitm)i reported a bug to jira: https://jira.jboss.org/jira/browse/JBIDE-4371
also, as i wrote there, the "Make deployable" on the ds file prompt this message: "There are no servers that support deploying single files"
is there a way to overcome the security rules issue? i'm not sure what to put in that file.
thanks, nitzan; -
5. Re: changes in the JBoss tools?
maxandersen May 25, 2009 4:35 AM (in response to nitm)"nitm" wrote:
i reported a bug to jira: https://jira.jboss.org/jira/browse/JBIDE-4371
Are you sure you are using the same version of seam as before ?
security.drl is as far as I remember not a requirement in seam 2 and it was definitly never supposed to be in the root of the EAR since that is a broken assumption about classloading.
also, as i wrote there, the "Make deployable" on the ds file prompt this message: "There are no servers that support deploying single files"
Then you don't have one of our AS adapters configured, and that also explains any issue with why -ds.xml is not deployed. -
6. Re: changes in the JBoss tools?
nitm May 25, 2009 4:55 AM (in response to nitm)yes, i'm using the same seam version as i used to (2.1.1GA), the only thing that changed is the version of the JBoss Tools.
the security.drl wasn't in the root of the ear but in the META-INF directory (if i remember correctly).
if it's not a requirement and the wizard does not generate it, at least it should not configure it in the components.xml.. this does cause some exceptions (added to the jira post)
what AS adapters ?
i'm using a fresh installation of eclipse and i updated the Tools from the stable update site.
was there another thing i should of done/configure?
thanks, nitzan; -
7. Re: changes in the JBoss tools?
akazakov May 25, 2009 7:41 AM (in response to nitm)"nitm" wrote:
what AS adapters ?
i'm using a fresh installation of eclipse and i updated the Tools from the stable update site.
was there another thing i should of done/configure?
See JBoss Server View->New->Server->JBoss Community->... -
8. Re: changes in the JBoss tools?
nitm May 25, 2009 4:01 PM (in response to nitm)oh, ok, now i can add the ds file and deploy it.
why is there a difference between the two servers?
thanks! -
9. Re: changes in the JBoss tools?
maxandersen May 25, 2009 4:52 PM (in response to nitm)"nitm" wrote:
why is there a difference between the two servers?
thanks!
Because the feature of being able to deploy any resource is something that WTP does not provide by default, only we do that - so that is why it only works for our AS adapters.