Unnecessary dependency
by Dmitry Geraskov
Hi, Denis,
I noticed that you have added HQLEditorPreferencePageTest to
org.hibernate.eclipse.console.test.
This class uses one method of WorkbenchUtils class from
org.jboss.tools.test plugin and it made you to add the dependency into
manifest.
The method is rather simple:
public static PreferenceDialog createPreferenceDialog(String pageId) {
return PreferencesUtil.createPreferenceDialogOn(WorkbenchUtils
.getActiveShell(), pageId, new String[] {pageId}, null);
}
I think that this dependency not so necessary to make us to create the
depency between the plugins.
If we remove using WorkbenchUtils class then repetition of code will be
minimal.
--
Best regards,
Dmitry Geraskov
15 years, 10 months
Task: Wizard Candidates for Removal
by Rob Stryker
I propose that the following "New Wizards" be removed from the "JBoss
Tools Web" section of the New wizard, as there are suitable replacements
in WTP which still, often, open using our editors.
CSS File
HTML File
JS File
JSP File
Max / Dennis: Discussion or assignment / JIRA to someone on the Exadel
Team may be appropriate if you agree with me
15 years, 10 months
Hyperlinks in Eclipse 3.4
by Victor V. Rubezhny
I looked thru the Eclipse 3.4 and WTP code for Hyperlink processing. IMHO
there are not many new things usefull for us in Eclipse 3.4 Hyperlink
processing.
There is the "org.eclipse.ui.workbench.texteditor.hyperlinkDetectors"
extention point declared in previous Eclipse versions (since 3.3). But for
some reasons we're using it only to declare our
SeamELInJavaStringHyperlinkDetector to process hyperlinks for Seam ELs in
Java-Strings in Java Editor while we're using different way to install our
detectors to XML/HTML/JSP editors (Java Editor supports this extention point
and it seems that this is the only way to build-in the Java editor to
process the Hyperlinks).
Also there is the
"org.eclipse.ui.workbench.texteditor.hyperlinkDetectorTargets" extention
point which helps to define the targets (document content types) where the
declared Hyperlink Detector is to be used for. Here is also nothing usefull
for us because our Hyperlink detectors mostly depend on partition types but
not on the content type. There is no partition targeting in Eclipse 3.4 (and
probably it will never be done).
There is nothing new in Eclipse 3.4 except the multiple Hyperlinks are shown
when more than one possibility is found. Probably some editors aren't using
this new possibility, but XML editor does.
Since the multiple choices are shown for the Hyperlinks in Eclipse 3.4 (but
not only the first Hyperlink found is shown) we could modify our hyperlink
detectors installation way to make it kosher.
15 years, 10 months
Re: a classpath container problem about JBoss server jars
by Rob Stryker
This should fix the problem then, right?
PS - remember to reply to all so the responses all go to the mailing
list ;)
gridqian wrote:
> Yes, Rob. Denny is doing this task.
>> Hi Grid:
>>
>> You should have a page similar to the jsf facet's page.
>>
>> When creating a JSF project or enabling the JSF facet (in a seam
>> project),
>> there is a page where the user selects whether to let the facet add
>> the jars
>> manually or let the server do it.
>> If the user selects let the server do it, then your facet should NOT
>> add the jars
>> and should instead let the server itself do it (aka my code, which
>> adds the container
>> with all the jars). If your user DOES select to add the jars, then
>> you should do so.
>>
>> You should be able to see an example of this by creating a new Seam
>> project.
>> One page is the JSF page.
>>
>> Try to work similar to that.
>>
>> - Rob Stryker
>>
>> gridqian wrote:
>>> Hi guys,
>>>
>>> There is a problem when I create jboss ws and rum a client sample.
>>>
>>> Now I focus on extending wtp web service framework to support
>>> JBoss WS. To do this task, we must firstly create a dynamic web
>>> project and then generate web service or web service client codes.
>>> So far I can create web service and web service client. For user's
>>> convenience I generate a client sample to call web service.
>>>
>>> But you know, if the dynamic web project is assigned a jboss server
>>> system will add a jboss server classpath container to the project
>>> classpath and add many jars into this container. These jars include
>>> jaxws-rt.jar and jaxws-tools.jar. When I run the web service client
>>> sample class, a issue occurs and the client do not call web servcie
>>> successfully. After google this issue, I found only if remove the
>>> two jars (jaxws-rt.jar and jaxws-tools.jar) from project classpath,
>>> the issue will be fixed successfully.
>>>
>>> So how to do to fix this issue? I think we have two ways:
>>> 1 when create jboss server classpath container, we do not add these
>>> two jars to the container.
>>> But in this case, I do not know whether other dynamic web projects
>>> can run successfully without these two jars.
>>> 2 Like done as before, add all of jars to jboss server container.
>>> When I
>>> create web service client project, I remove these two jars from the
>>> container.
>>> but I do not know how remove jars from a container?
>>>
>>> Which way is better? and if choose second way, who can tell me how to
>>> remove jars from a classpath container?
>>>
>>> Thanks
>>> Grid
>>
>
15 years, 10 months
QA Daily report 11 June 2008
by Aliaksey Nis
Hello , Denis
This is Daily QA report for 11 June 2008.
Tasks performed:
1. Free testing of latest available JBDS 1.1.0.GA build and
JBoss Tools 2.1.1GA.
2. Testcases updating.
Creating new testcases from JIRA issues.
Updating projects Archives testcases.
--
Best regards,
Aliaksey mailto:anis@exadel.com
15 years, 10 months
Re: Fwd: [jbosstools-commits] JBoss Tools SVN: r8706 - in trunk/ws/plugins/org.jboss.tools.ws.core: src/org/jboss/tools/ws/core/classpath and 1 other directories.
by gridqian
Ok. 'this' container is jboss ws container that is created by me. When we
create a jboss ws project, we need add a container to the project
classpath. This
container is jboss ws container. And this container include jars from EAP4.2
client folder and lib folder.
Now some jars from client folder are same to some jars from lib folder. So I
must filter them. If not, when we export these jars from classpath to
WEB-INF
lib folder, we will get some errors.
> On Wed, 11 Jun 2008 12:23:20 +0200, gridqian <fqian(a)redhat.com> wrote:
>
>
>> Aha, yes, it is my carelessness. Should add jars from client and lib
>> folder of EAP4.2
>> to this container.
>>
>
> I don't understand what you mean. Which container is "this" ?
>
> p.s. shouldn't we move this to jboss-tools-dev list so Rob et.al. could see it too ?
>
> /max
>
>>>> And about these codes that I commit:
>>>> now we copy client folder and lib folder of jboss ws to container. And
>>>> some jars from client
>>>> folder are same to the jars from lib folder. If we export this container
>>>> to web-inf lib folder, we
>>>> will get some errors for this. So I filter them. I do this as:
>>>> when add a jar to entry list, if entry list has it , do not add this jar
>>>> to entry list again.
>>>>
>>>>
>>> Copy client folder and lib folder of jboss ws to container ? That is not acceptable
>>> in the case of it being EAP 4.2. We must not require alteration of that runtime.
>>> Our support does not support JBoss WS from jboss.org, it only supports what is inside EAP 4.2
>>> thus users should not be required to alter it.
>>>
>>>
>>> /max
>>>
>>>
>>>
>>
>
>
>
>
15 years, 10 months
