Bug 243361

Summary:	[compiler] different behaviour from javac (sdk1.6.0_7) and eclipse-java-compiler
Product:	[Eclipse Project] JDT	Reporter:	Thomas Bogner <bogner>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	VERIFIED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	kent_johnson, Olivier_Thomann, remy.suen
Version:	3.3.1
Target Milestone:	3.5 M4
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Thomas Bogner

2008-08-06 15:26:55 EDT

Build ID:  M20071023-1652

Steps To Reproduce:
1.import com.sun.xml.internal.ws.wsdl.parser.InaccessibleWSDLException; in java-file
2. in eclipse class-file is build without any error/warning.
3. compiling with javac fails with:
ic.java:1: package com.sun.xml.internal.ws.wsdl.parser does not exist
import com.sun.xml.internal.ws.wsdl.parser.InaccessibleWSDLException;


More information:
com.sun.xml.internal.ws.wsdl.parser.InaccessibleWSDLException is located in rt.jar but it is only for internal use in java runtime, so the error reported from javac is correct. why doesnt eclipse recognise this.

Comment 1 Kent Johnson

2008-08-08 11:58:28 EDT

The error reported by javac is not part of the compiler spec.

It is a proprietary error that Sun has chosen to 'protect' their internal code, much like the warning javac issues for :

import com.sun.corba.se.spi.activation.LocatorOperations;

X.java:1: warning: com.sun.corba.se.spi.activation.LocatorOperations is Sun prop
rietary API and may be removed in a future release

Comment 2 Kent Johnson

2008-11-10 09:29:58 EST

Closing since this is a Sun specific error message & is not covered by the Compiler spec.

Comment 3 Jerome Lanneluc

2008-12-08 05:19:58 EST

Reopen to assign

Comment 4 Jerome Lanneluc

2008-12-08 05:20:52 EST

(In reply to comment #2)
> Closing since this is a Sun specific error message & is not covered by the
> Compiler spec.
>

Comment 5 Olivier Thomann

2008-12-08 22:05:57 EST

Verified for 3.5M4 using I20081208-1800