microsoftgraph / microsoftgraph/msgraph-sdk-java

Issue: Unable to Process Multiple Emails Simultaneously When Downloading Attachments and Uploading to SharePoint

Offen
#2,337 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

status:waiting-for-triage type:bug
Vorherrschende Sprache
Java
Sterne
444
Forks
154
Ø Merge
18 Std. 28 Min.
Gemergte PRs (30 T.)
4

Beschreibung

Describe the bug

When trying to download attachments from Outlook while simultaneously uploading files to SharePoint, it is not allowing multiple emails; it only processes one email at a time.

Note: Downloading attachments from a single email to local storage and uploading them to SharePoint is working fine using java graphapi.

Expected behavior

We need a process where, within a single connection, we can download attachments and upload them to SharePoint or directly download attachments to SharePoint using Java Graph API with a client secret and application ID.

How to reproduce

To download file from Outlook.
File file1 = new File(localFolder + "/" + sFileName);
System.out.printin("Path::"+LocalFolder +"/" + sFileName);
File folderTouploaded - new File(tempDownload);
for (File fileTemp : folderTouploaded.listriles()) [
if (fileTemp.isFile()) t
fileTemp.setwritable(true);
Logger-info("Name is :::" + fileTemp.getName());
Logger-info("Path is :::"+ fileTemp.getAbsolutePath());
sharerointconnection.upLoadFiLeToSharepoint(graphclient,sharePointsiterd(),sharePointdriveId(), tempDownload,
uploadPath, fileremp.getName(),file1);
deleterile(tempDownload +"/" +fileTemp.getName().tostring());

//To upload file-
Path srcFilePath = Paths.get(srcFolderName + "I" + fileName);
Logger.info("Checking::"+srcFolderName + "I" + fileName);
byte[] srcFileBytes = Files.readAtlBytes(srcfilePath);

DriveItem uploadedItem = drivertemRequestBuilden.content().buildRequest().put(srcFileBytes);

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

DEBUG]
LINFO
[INFO

4043-03-40 02120.04 s8u (MailLocal.java:680) - Path is :::D:\myfolder\sharePoint_TestingFiles\Emai
2025-03-20 09:26:04.380 (SharePointConnection.java:268) - Process started::
2025-03-20 09:26:04.380 (SharePointConnection.java:270) - Dest folder name::myfolder\Data\save
2025-03-20 09:26:04.380 (SharePointConnection.iava:271) - SharePointId:test.sharepoint.com,e76d765-86fe-
2025-03-20 09:26:04.3 (SharePointConnection.java:272) - Dest file name::myfolder\Data\save
2025-03-20 09:26:04.381 (SharePointConnection.java:297) - Process completed::
at EmailLocal.lambda$1(EmailLocal.iava:681
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown_Source)
at java.util.stream.Referenceipeline$2$1.accept(Unknown Source)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
at java.util.stream.ForEachOps$ForEachOpfOfRef.evaluateSequential(Unknown Source)
at java.util.stream.AbstractPipeline.evaluate(Unknown

</details>


### Configuration

_No response_

### Other information

_No response_

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginnen Sie mit dem Aufruf zur Anlagenverarbeitung in MailLocal.java:680 und dem in SharePointConnection.java:268-297 protokollierten Upload-Ablauf. Reproduzieren Sie den Download von Outlook-Anlagen und den Upload nach SharePoint mithilfe der Java Graph API und überprüfen Sie anschließend, dass eine Verbindung Anlagen aus mehreren E-Mails verarbeitet und erfolgreich hochlädt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java
Bereich
api, cloud
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.