Re: [jbosstools-dev] Server Runtime in automatic tetst
by Denis Golovin
I remember we have it in JBossASAdapterInitializer, which is disabled
for now, but you can make static private methods public an use them in
tests.
Use one of the system properties from this list
-Djbosstools.test.jboss.home.3.2
-Djbosstools.test.jboss.home.4.0
-Djbosstools.test.jboss.home.4.2
-Djbosstools.test.jboss.home.5.0
-Djbosstools.test.jboss.home.5.1
and open issue for me to enable required system property for jsf tests
Thanks
On 06/25/2010 06:29 AM, Viacheslav Kabanovich wrote:
> Denis,
>
> For https://jira.jboss.org/browse/JBIDE-6540, I would like to add an
> automatic test that adds JSF capabilities to Java project. Wizard can
> finish only if there is a Server Runtime in the test workspace. Do we
> have API to create a runtime at test start?
>
>
> Best regards,
> Slava
13 years, 10 months
DEBUTANTE
by juliana tchoua
Good morning to you
i'm juliana and i'm student in telecom.
i
don't know how construct a page web where we see portlet JSF interact.
I saw the examples to the jboss site but i have many errors when i deploy them.
I need your help please for know how deply the examples and
modify them to adapt for my needs. I saw that the source code aren't.
I want to do the news service to deploy to the jboss portal and now i'm
block.
Sorey for my english. I'm french.
Thank you in advance.
13 years, 10 months
insane amounts of modules added to seam test ?
by Andersen Max
Hi,
What is all this ?
<module>org.jboss.tools.seam.core.test</module>
<module>org.jboss.tools.seam201GA.core.test</module>
<module>org.jboss.tools.seam202SP1.core.test</module>
<module>org.jboss.tools.seam203CR1.core.test</module>
<module>org.jboss.tools.seam121EAP.core.test</module>
<module>org.jboss.tools.seamfp.core.test</module>
<module>org.jboss.tools.seam.pages.xml.test</module>
<module>org.jboss.tools.seam.ui.bot.test</module>
<module>org.jboss.tools.seam.ui.test</module>
<module>org.jboss.tools.seam201GA.ui.test</module>
<module>org.jboss.tools.seam202SP1.ui.test</module>
<module>org.jboss.tools.seam203CR1.ui.test</module>
<module>org.jboss.tools.seam211GA.ui.test</module>
<module>org.jboss.tools.seam220CR1.ui.test</module>
<module>org.jboss.tools.seam220GA.ui.test</module>
<module>org.jboss.tools.seam121EAP.ui.test</module>
<module>org.jboss.tools.seam.xml.test</module>
why is there a test plugin for every seam version combo !?!
That can't be right ?
/max
13 years, 10 months
merge of helios to trunk - complete
by Andersen Max
Hi,
I completed the merge. We are now on Eclipse 3.6 in trunk.
Everything compiles, but I haven't tested that everything runs all fine yet.
Things I noticed:
trunk/build/ and its content (especially build.xml) were semantically different - Nick ?
vpe had conflicting edits as discussed on irc; i've applied all incoming stuff from helios - VPE team please check that it is as expected.
documentation were edited in a few places, looked like isaac thought he were commiting to 3.1.x - did not merge it over. - Ben/Isaac can you look ?
I have to go for today, but Nick said he would monitor the builds and see if there are big fires to fix - but otherwise we
are now on 3.6 and 3.2.helios branch is dead.
I'm going to clean up jira tomorrow morning to reflect this.
Thanks for listening,
/max
13 years, 10 months
Creating a "smooks-dbm" branch....
by Tom Fennelly
Hi all.
This is just a notification that I'll be creating a "smooks-dbm" branch
(branches/smooks-dbm). Dart and I will be doing some disruptive work
there (removing the use of EMF), so best keep it away from trunk. Max
asked me to let the list know.
Regards,
T.
13 years, 10 months
Merging 3.2.helios to trunk
by Andersen Max
Warning :)
I'll start merging 3.2.helios to trunk tomorrow my time (will probably take most of the day with the svn speeds we got)
Therefore 3.2.helios should be consider frozen now.
If you got any objections to that let me know ASAP.
/max
13 years, 10 months
Re: [jbosstools-dev] Weird issue with WS code and Eclipse 3.6
by Brian Fitzpatrick
Yeah, I ran across the StackOverflow link, but didn't see anything earth shattering.
1) Definitely compiling and running against the same "stuff".
2) Ran with -Xverify:all and didn't see anything spit out in the console
3) Not creating my own classloader.
I have now updated my JDK to 1.6.0_20 at Nick's suggestion and that didn't change anything. Still getting the verifyError.
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Andersen Max" <max.andersen(a)redhat.com>
To: "Andersen Max" <max.andersen(a)redhat.com>
Cc: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>, "tools-dev" <jbosstools-dev(a)lists.jboss.org>, "external-exadel-list" <external-exadel-list(a)redhat.com>
Sent: Wednesday, June 9, 2010 4:07:49 AM GMT -07:00 US/Canada Mountain
Subject: Re: [jbosstools-dev] Weird issue with WS code and Eclipse 3.6
after brushing up on my memory on VerifyError's and especially http://stackoverflow.com/questions/100107/reasons-of-getting-a-java-lang-...
then a few suggestions:
Make sure you are actually compiling and running against the same "stuff"
Run with -Xverify:all to see if that reveals something
/max
On Jun 9, 2010, at 11:33, Andersen Max wrote:
> any chance both plugins are loaded into the same classloader ?
>
> Are you creating your own classloader ?
>
> /max
>
> On Jun 9, 2010, at 03:01, Brian Fitzpatrick wrote:
>
>> I've asked Grid to look at a patch for the compile error, but I still don't have a fix for the weird runtime error...
>>
>> There's not a lot for "java.lang.VerifyError" out there that makes much sense in this runtime context except that it's obviously a clash between the soap plug-ins somehow...
>>
>> --Fitz
>>
>> _______________________________
>> Brian Fitzpatrick (aka "Fitz")
>> Senior Software Engineer, SOA-P
>> JBoss by Red Hat
>>
>> ----- Original Message -----
>> From: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>
>> To: "Andersen Max" <max.andersen(a)redhat.com>
>> Cc: "tools-dev" <jbosstools-dev(a)lists.jboss.org>, "external-exadel-list" <external-exadel-list(a)redhat.com>
>> Sent: Tuesday, June 8, 2010 6:48:38 PM GMT -07:00 US/Canada Mountain
>> Subject: Re: [jbosstools-dev] Weird issue with WS code and Eclipse 3.6
>>
>> I'm not wrapping anything myself - I'm using the javax.soap dependency that comes as part of Eclipse.
>>
>> And the wsdl4j.jar that's in the plug-in causing the compile error is only part of my issue. We will go away from using the wsdl4j jar in the plug-in and using the javax.wsdl dependency plug-in that's part of Eclipse.
>>
>> But that only solves the compile issue, not the bizarre issue I get at runtime with the WS Tester.
>>
>> --Fitz
>>
>> _______________________________
>> Brian Fitzpatrick (aka "Fitz")
>> Senior Software Engineer, SOA-P
>> JBoss by Red Hat
>>
>> ----- Original Message -----
>> From: "Andersen Max" <max.andersen(a)redhat.com>
>> To: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>
>> Cc: "external-exadel-list" <external-exadel-list(a)redhat.com>, "tools-dev" <jbosstools-dev(a)lists.jboss.org>
>> Sent: Tuesday, June 8, 2010 6:44:24 PM GMT -07:00 US/Canada Mountain
>> Subject: Re: Weird issue with WS code and Eclipse 3.6
>>
>> shouldn't you be using some wsdl library from java it self or as an osgi library instead of
>> mixing in your own wsdl.jar ? (thinking out aloud here)
>>
>> /max
>>
>> On Jun 8, 2010, at 18:08, Brian Fitzpatrick wrote:
>>
>>> Hey all...
>>>
>>> I'm trying to fix https://jira.jboss.org/browse/JBIDE-6428 and am running into some bizarre issues...
>>>
>>> As I say in the last JIRA comment I just added:
>>>
>>> "It looks like I can take care of the compile errors, but then I end up with this:
>>>
>>> An internal error occurred during: "Invoking web service...".
>>> (class: org/jboss/tools/ws/ui/utils/JAXWSTester, method: doTest signature: (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V) Incompatible object argument for function call
>>>
>>> I'm guessing there are incompatibilities with the WSDL libraries, but nothing I do has managed to work around this yet except for removing the 1.3 version of the javax.soap plug-in from the runtime plugins. I've tried enforcing the 1.2 version as the upper bound and that doesn't help at all."
>>>
>>> Any suggestions on how to work around this? I'm using JDK 1.6.0_14 and Eclipse 3.6 RC3 plus the latest trunk build and a few fixed plug-ins from the 3.2_Helios branch.
>>>
>>> Thanks in advance. I'm pulling my hair out on this one...
>>>
>>> --Fitz
>>>
>>> _______________________________
>>> Brian Fitzpatrick (aka "Fitz")
>>> Senior Software Engineer, SOA-P
>>> JBoss by Red Hat
>>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
13 years, 10 months
